Jim M

Sorry, customization requests and anything associated with those would be outside our scope of support so asking about those that are processed are beyond our support. Please be advised I have moved your topic to our community support forum so you may get customization advice from a peer developer.

Sorry, the author would need to assist you with any questions regarding their plugin. Customizations would be outside our scope of support.

I'm afraid, that would indicate that you would need to work with the author to resolve this. It is the plugin which is attempting to accomplish something for you which the core software does not do so you would need to work with the plugin author.

Please disable any third party applications/plugins and switch to an unmodified theme to see if that helps. If not, please provide us access: We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.

I'm afraid, there is limited support for localhost installations. Is there an existing key with the same name in your database?

These bugs mentioned in the topic you pasted are solved in 4.7.0 which is currently in Beta. You're welcome to test this if you wish.

Caching would not be related to CRON. If your constants.php does not have Redis present and your /datastore directory is writable, this warning can be cached so you will want to dismiss it and then see if it comes back. Please let us know 🙂 .

Thank you! Please be advised I have moved this to a ticket so that we can better investigate this for you. Further communication will be provided via email.

Could you please provide the example member's display name and URL you're attempting to post? We can then investigate further. Also, sorry to bring this up again but nothing was explicitly stated on the above. Could you please state if you're using mod_security or varnish?

Please see the following steps to troubleshoot this: Please ensure that you're using 8.0 and not 8.1. You specified 8.0 for WordPress so just want to double check you are using 8.0. Please use the following file to ensure that your hosting provider or server admin installed all required modules of PHP to run our software: https://invisioncommunity.com/files/file/7046-invision-community-requirements-checker/?do=getNewComment If the above are all good, a 500 Internal Server Error is very much like the check engine light on your car. It states something is wrong but not exactly what or where. Please work with your hosting provider or server admin to obtain the Server Error logs for this error and either resolve the issue (if it is server related) or provide it to us so that we can further assist you.

While I appreciate your feedback, it comes back to developing and making the product better as we move forward with version 4 and beyond. It simply is not feasible to continue developing and supporting past versions indefinitely. Discontinuing support is very much a common thing in software development lifecycles as versions age (we actually did kept support for quite some time after version 4 was launched and matured). With version 3, there is nothing stopping you from using an installation, however, you will hit many roadblocks as many of the server infrastructure, 3rd party integrations (such as CAPTCHA), etc... have been discontinued, sun-setted, etc... by their own developers. Just a note here as we are getting into this information, PHP 5.6, which is the highest version of PHP which can run version 3 of IPB, is no longer supported by PHP themselves for 3+ years now and many hosting providers due to that choose not to run it or have it available to their customers. You may still find some that run it but as it is no longer supported by PHP, running 5.6 is a security concern 🙂 . @Tschieny, if you have any questions about switching or upgrading to version 4, we're happy to answer any questions. However, if you continue to run version 3 (which is completely fine if you want to), we will move this to our peer community support forum as version 3 is no longer supported.

Best suggestion would be to upgrade your hosting to a plan or provider that does not limit your database size or is more inline with your growth. (Have you considered our cloud?) The short story is that you’re growing (congrats!) and the tables listed hold core content of your community. So the only way to get in line with your hosting would be hurting your community by sacrificing content. Once you start doing this, it’s a slippery slope, you’ll have to keep doing it to stay in line with the hosting. If you have the ability to upgrade, it’s the best idea to prevent this from happening and continue growing your community. Best of luck!

Yep, as mentioned by Terabyte (who is faster than me this week at answering this week 🙂 ), the flag is driven by the locale and the locales are fed from your server. If you do not see your locale in the list there, you would need to work with your hosting provider or server administrator to have it installed.

Please be advised I have tagged a developer to this topic so they can verify what is happening here.

Glad to see you found the answer 🙂 .

I have messaged you the secret key 🙂

Unfortunately, you will need to ensure it’s compatible with 4.18. 4.19 is a different version than our software runs so there could be slight incompatibilities.

Please ensure that your permissions and folders/files are owned by the correct user/group for your new environment. If you continue to have issues, please contact your hosting provider to verify what is set. Often during a move, things can get changed and moving to a new environment, things can be different. IE if your new host is running suPHP or suexec, folders would need to be 755 and files 644 to be executed/writable. If you want to provide us access via the Client Area we can take a quick peek if you’d like. The high five is for thanking Terabyte, as that is the correct answer for the error shown 🙂.

To have Invisible Captcha work, your key will need to be authorized/setup for it. If you did not do that for your key, it simply won’t work. Therefore, your options are: 1. to leave it on reCAPTCHA 2 as you have now 2. if you want to use Invisible CAPTCHA, switch to the default key 3. if you want to use Invisible CAPTCHA, setup your key for Invisible CAPTCHA

We have the following guide on how to perform upgrades: https://invisioncommunity.com/4guides/welcome/install-and-upgrade-r259/ However, there isn't really a best practice list outside of what I mentioned in my other post. I would recommend the below, seeing as you are so far behind in updates. Additionally, setting up a test install may be a good idea if you have a lot of customizations to test or simply want to test upgrading. Before performing any core software upgrades, do some research of the third party applications/plugins/themes/etc... you have installed and see what is available for the most recent release. If you there are any that aren't mission critical, now is a good time to perhaps uninstall those. When you're ready to perform the core update: Turn your community offline. Take a full backup (database and files). (for those reading who are cloud, you're all set here) Disable all third party applications, plugins, and language packs. Create an unmodified theme and set it as the default theme (ensure your administrators who are helping with the upgrade use that theme) Perform the core upgrade. As you are so far behind, it may be a good idea to perform a manual upgrade (see guide above for more details on that). If any issues with the core upgrade, please create a topic here and someone will help you 🙂 . Have a look over your community to ensure things went well. This is a good idea for the next step. Once the core upgrade completes, you will want to consider looking at getting your third party items in line: As you are coming from 4.4, you will want to setup the Marketplace integration and go through onboarding. There should be a notification to do this in the notification bell of the ACP (top right). This will step you through which applications/plugins/themes/language packs you have installed from the Marketplace or are custom (aka custom development you had done or installed from elsewhere). You will want to upgrade each application/plugin/theme/language pack independently and then test before moving to the next one. This will allow you to tell what may be breaking and causing that break. For third party items which have no compatible release with our core software you just upgraded to, be very cautious of enabling these but ultimately, enabling these independently of others is advised. Done! These "best practices" are really an extremely cautious approach coming from a rather old version. Point upgrades (e.g. 4.6.11 to 4.6.12), you likely would not need to be this cautious but I would stress item 2.2 (Backups) for any self-hosted client for any upgrade, no matter how small.

As mentioned by Terabyte, your CAPTCHA key looks to be incorrect or otherwise not working so you will want to see if you have your own account. If so, you will need to check the key/secret to ensure it is correct from the admin area on CAPTCHA.

You can view all block cache settings in ACP -> System -> Advanced Configuration.

ACP > Support > Clear System Caches

Please have the Cloud client ensure you are on their Cloud package as an alternate who can submit support replies. Unfortunately, often is the case there are multiple packages, and permissions incorrectly set which would trigger our bounce back and the ticket to be deleted. (I was actually just helping where the individual was set on their self-hosted license and the same thing happened). However, if they have you as an alternate, you should be able to login to the Client Area to submit the ticket. If you do not have that option, setup was not done correctly and need to be adjusted. Please have the client contact us if any questions.