Jim M

Unfortunately, we would not provide support to old versions. Is there a reason that you are not directly upgrading your live install or attempting that with the test install? That we can assist with any issues.

This like is utilizing a contains-like search pattern, which is why you are getting results like this because it is looking for a non-exact match. Whereas, you are wanting an exact match here. I have tagged a developer to confirm this is intended.

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.

Is this on your test site? I see that is running the latest release but we would require email address rather than display name as it seems your login is setup to use that.

You can do this by going to the login page on the front-end -> click "Forgot your password?" This will reset passwords for the standard login handler.

Thanks! I've transferred this to a ticket so we can further investigate. Please watch your email for further correspondence.

These would be automatically deleted from our support ticket engine as this is no longer supported. This has been this way for over a year now, I'm afraid. If you do not know this password, you can provide us an unrestricted administrator account.

Are you still experiencing this issue? If so, do you have an example?

You will need to contact your hosting provider again. Unfortunately, that is just showing it enabled. The GD module would show up in the phpInfo (last screenshot) further down the page. The “enabled” section is just you telling PHP to use GD. It isn’t stating the module is running itself. Our compatibility script simply uses PHP functions that are built in to test if these modules are loaded. If that is tripping, as seen, the GD module is not loaded correctly or PHP hasn’t been restarted since it was enabled.

I would advise reaching out to your hosting provider here. While you may be sending the option to enable GD, the module may not be loaded.

Hey Jeff, Good to see you back around but I am sorry to hear about your issues, both with your health and family plus your community. Unfortunately, we do not have a service which would aid you in bringing your site back from a malware/virus attack. Typically, this would be handled by your hosting provider, as getting in through your hosting is how the attacker was able to modify/place these files in the first place. My first recommendation though is that if you haven't changed all your administrator passwords by now, do that immediately. The good news though, with your interest in upgrading, that would hopefully remove any backdoors in place which the attacker may have placed in existing files on your server and potentially remove any malware/viruses in the core files. Finally, I would encourage you to explore our Cloud platform if you feel there is a security issues on your existing hosting or you feel overwhelmed by managing all technical aspects of your community and just want to focus on the community part. Please let us know if you're interested in talking with our sales team about Cloud and we can open that communication for you. If you need assistance in getting your site back online and have any questions regarding our software, we can certainly answer those with an active support license. However, we do not offer virus/malware removal as a part of our support. If you need assistance with that and potentially, direct upgrading assistance to help get you over these humps, there are third party providers to help with that. Moving on with the upgrade conversation and brushing up on your last conversation with us, it was around upgrading from 4.5, which is quite older now (as you're aware in your comments). There were concerns about the third party applications/plugins/themes and customizations on your community which the upgrader was warning you about that you needed to ensure compatibility with. The unfortunate news, I have for you, is that upgrading to the latest release will be a little more complicated as these third party applications/plugins/themes and customizations on your community will need to be compatible not only with our latest release of the software but also with PHP 8. As the PHP version you're on now has become unsupported by PHP themselves so we also have dropped support. The good news, is that now is a good time as any to evaluate your third party applications/plugins/themes and customizations and see if you really need them 100%. If you can go without them and that will make your life easier to upgrade/manage/etc... I would advise to uninstall it ASAP! The other option is to work with the third party authors to ensure there is a suitable upgrade path for that item. If there is not a suitable path to upgrade, time to also uninstall 🙂 . Third party applications/plugins/themes and other customizations are great because they help add niche/custom functionality to your community that won't be in the core software but they also add a lot of management, stress, and cost on your end to ensure their compatibility between upgrades/etc... because they are code written by others so would fall outside our scope of support. This is what you need weigh. Feel like this was/is a huge contention point for yourself and what caused you to give up. Might be time to reduce overhead and simplify your community so that you are no longer overwhelmed and scared at each upgrade. That would enable you to simply click a button and have the automatic upgrader do it's thing to get you between releases 🙂 . Pease let us know if you have any questions on that.

You would need to enable that same permission for the member group you want to allow. They then would be able to delete their content in the same way a moderator would but for only their own. For example, to delete their own topic they would go to the topic -> click Moderator actions -> Delete. To delete a post, they would go to their post -> click the three dots in the top right of their post -> Delete.

My first recommendation here is to upgrade to the latest release. If you encounter this again, please let us know and keep the user in the current state. Please also ensure that the third party applications/plugins/themes are upgraded and compatible with the release you're on to prevent any inadvertent issues.

This is being investigated on our side. Sorry for the lack of response 🙂 .

You would need to provide them the table and column in the error.

There likely may be more columns. You will need to keep checking the System Log and working with your hosting provider till this is resolved. Alternatively, you will need to have them disable safe mode in mysql.

Thanks for posting! Unfortunately, this issue is beyond the scope of our technical support. 👩‍💻 Our technical support is happy to help you with the Invision Community platform, but we're unable to help with things like server management, theme questions and modifications. I've moved this to our Community Support area where other Invision Community owners will see it and help where they can.

This would be too many registration attempts and Spam Defense is preventing a false positive. You will want to temporarily disable this in ACP -> Members -> Spam Prevention -> Spam Defense, if you are testing a lot or Whitelist your IP addresses that you want to test with.

This will be with PHP as it is the one performing the move.

This will be in your email 🙂 .

You would need to allocate more memory to PHP to move these files.

Please be advised that the Test URL is a one-time set URL. You will want to ensure that you utilize a sub-domain of the domain which you have on your Live URL so that if you need to change servers, it is simply a DNS change. Rather than having to reset your Test URL on the license. An example of that would be, if your Live URL is on example.com, then your test URL could be test.example.com As a one-time courtesy, I have gone ahead and reset the Test URL for you. Please ensure that you utilize a sub-domain of the domain for your Live URL.

As mentioned, you will want these to process. The system has already identified these and expects these to move.

Sorry, looks like you may have missed this question: What do you have set for Allow Customer to Choose Rate?