CoffeeCake

Fixed your typo.
1. Have a test copy of your production environment. What does that mean?
Same version of OS, same version of PHP, same version of web server, same version of MySQL, same extensions, same configurations, different hostname, behind a firewall or otherwise secured. Not "kind of the same," or "almost the same," or "completely different." Same plugins, extensions, themes, languages, configuration for IPS Ensure things that interact with the outside world (payments processors, e-mail configurations, APIs, etc.) are pointed to corresponding test environments as well. You don't want real payments being processed or real e-mails being sent out from your test environment that affect your members. 2. Make changes in your test environment and document your changes carefully, noting the exact steps you took.
3. Test!
4. Have an issue in test? Investigate and open a ticket.
5. No issues, follow the same steps you documented in step 2 in your production environment.
If you're doing it any other way, you're gonna have a bad time.

It's a bit concerning to see security issues not addressed for 4.5, and forcing an upgrade to 4.6. While we are in the process of testing, things aren't at a state yet here in the community where third-party developers have released compatible updates to their extensions.
Why isn't there a 4.5 patch? See:
Some guidance and communication on when a branch will become end of life would be appreciated.

It's a bit concerning to see security issues not addressed for 4.5, and forcing an upgrade to 4.6. While we are in the process of testing, things aren't at a state yet here in the community where third-party developers have released compatible updates to their extensions.
Why isn't there a 4.5 patch? See:
Some guidance and communication on when a branch will become end of life would be appreciated.

It's a bit concerning to see security issues not addressed for 4.5, and forcing an upgrade to 4.6. While we are in the process of testing, things aren't at a state yet here in the community where third-party developers have released compatible updates to their extensions.
Why isn't there a 4.5 patch? See:
Some guidance and communication on when a branch will become end of life would be appreciated.

We have multiple providers, yet for IPS, we use sendgrid with the built in sendgrid integration.

Maybe this time, with Britney tax.

When you have a section that has many subsections, it is impossible to go thru each section because it will collapse the tree each click and you have to find the section you were in and open in t again.
it would be most helpful if there was a dynamic previous/next links at the end of the article on the content page 
 

Cloudflare Firewall? Yea also a great and cheap solution. 

Never mind, I got curious and found the documentation:
https://zapier.com/apps/invision-community/integrations
It looks like putting a member into a usergroup via Zapier isn't an option. All of the actions are "create" -- no "edit" or "move" or "modify."
Can you make API calls with your third party product?
https://invisioncommunity.com/developers/rest-api?endpoint=core/members/DELETEitem

This is a very old version from 2015, shouldn't you update it?

Hi, there is some way to let guests see their own topics that are pending approval?
For example, if our forum requires accepting new topics and we add a new topic as a guest, after adding it, topic does not display in the forum view, which can be confusing and some people may think that the topic has not been added.


Yes, there is a note at the top but not everyone sees it.

███████░░░░░░░███░░░░░░███░█████░████░███ ░░░█░░░░█████░█░█░████░█░░░░░█░░░█░░░░█░█ ░░░█░░░░█░█░█░███░█░░█░███░░░█░░░██░░░██░ ░░░█░░░░█░░░█░█░░░█░░█░░░█░░░█░░░█░░░░█░█ ███████░█░░░█░█░░░████░███░░░█░░░████░█░█  

I'd recommend avoiding using a host that sets arbitrary limits. IPS doesn't have anything out of the box that would limit the number of e-mails sent out per hour and per day. Consider using a third-party mailing service such as Sendgrid.
However! You can set defaults and disable e-mail as an option in configuring your community's default notification settings from the ACP:
This may help keep e-mail to a minimum.

Honestly, the response in 2019 was the problem. It should have been PWA today + future app then. But, good news that PWA isn't being ignored anymore.

I reported both issues as a bug (via support request--the bug tracker doesn't allow me to post new ones anymore), and an additional one where secondary groups are not returned as documented by /core/me.
To retrieve the e-mail address, I found that I did not need to update the scope, but rather simply include /core/me/email as allowed in the existing scope (which is not called "email").
It may be that the documentation needs to be updated to say "must include 'email' as the name of your scope" or "must allow /core/me/email."

And lastactivity is returned in unixtime rather than formatted time. Also, secondary groups are not returned by /core/me. I've created a support ticket, but logging here in case anyone else goes crazy for a weekend trying to figure out why things that should work aren't.

Should /core/me return the member's e-mail address? The API documentation suggests it does, yet it does not.

Aaaaaannnnd resolved. Not sure if that trailing slash thing is a bug. But, fixed my issue with the third-party. That was a journey.

Further along, I've confirmed that IPS is sending the needed data to the third-party application. The issue may be in how the JSON is formatted vs. what the third-party expects.

@bfarber: Yes, I'm doing an OAuth2 request. Ultimately, if I understand the workflow correctly, application redirects to oauth/authorize, user logs in, redirected back to application, which creates an access token (hitting oauth/token) and then application requests /api/core/me to get id/username/email, etc. for the authenticated user.
After much debugging and injecting outputs through both IPS and the third party application, I found that the post for the token call was failing because I had defined the token URI as example.com/oauth/token instead of example.com/oauth/token/. I'm not sure if this is a peculiarity of nginx and my web server configuration with php-fpm, but when I added the trailing slash, the script would receive the post request with the expected variables. Prior to that, the script would only see the post request with no elements provided.
Now, I'm at the point where the token is given, yet the third-party application is complaining that the id is not being sent from the call to /api/core/me which has the token in the Authentication header. Further along the chain, yet still not quite there. Working on adding debug code to IPS to see exactly what's being returned by /api/core/me.

And hey, a sweet discount for prepaying subscriptions longer than in six month intervals would be a nice birthday gift to us. 🎂

I'll regret this, but not much...plugin attached (xml file) and it will add a toggle to the comment form when reading a topic.
I'm off now to go wash the sugar taste out of my mouth.
Note: no support is provided for this plugin, as it is a 'proof of concept' for an application which is now available in the MarketPlace.
(NE) Kindness.xml

You can have multiple servers to send mail. You can only have one solution that receives mail per domain level. You need to take care to setup your domain's SPF and DKIM records, however you can have one service used by IPS to send outbound mail and an entirely different service to receive mail.
Your MX records (mail exchange) will point to the configuration used by your inbound service. This will be supplied by your web host, a mail provider (Google Workspace, Amazon Workmail, Office 365, etc), and your IPS instance will point to whatever provider you want to be using for outbound mail generated by the community software. example.com can have one set of MX records, while forum.example.com can have another set, but you likely do not have a need for more MX records than whatever you'd like to use to receive e-mails to support@example.com, etc.
You will configure IPS to use the mail provider for your bulk mail activities, and separately setup e-mail for inbound mail.
The only slight complication is if you use the Commerce Support tool to process inbound e-mail. If so, you will need to provide for a way for IPS to receive that inbound mail. You can setup IPS to check via POP3/IMAP in that instance, or use forwarding to route to another domain/subdomain for processing.