Jim M

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

That isn't a natural occurring URL. Someone would need to type that in so I would not be worried about it.

You would need to create an unmodified theme in the ACP -> Customization -> Themes. Ensure it is available for your member group, then scroll to the bottom of the page on the front-end and switch to the unmodified theme.

Would recommend switching to an unmodified theme and trying again. If the unmodified theme does not have an issue, it likely your modified theme.

I am seeing this it specifically on this install. I have logged a bug particular for Chrome on this in our internal tracker. See if this helps.

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.

As mentioned, we are unable to provide server support.

I'm afraid, I cannot reproduce this error on a clean installation with not customizations. Without being able to fully investigate your instance in an unmodified state, I cannot provide further support.

Sorry, we do not provide hosting support. We have provided proof it works in a normal environment, it would be up to yourself to troubleshoot your environment to see why it doesn't work there.

There is a ton of custom Javascript there.

I'm afraid, without being able to review the issue, we're unable to provide further support as I cannot reproduce this.

Worth noting running PHP 8.1.28 on my test server, I am not seeing the error you're mentioning above when using PHP mail so this look to be configuration related, I'm afraid.

If you have any modifications, please be sure to disable those, including themes, applications, plugins, etc... If that does not help, please provide a link to the given item.

Server hosting support is outside our scope of support. You would need to work with your hosting provider if you are unsure. Please ensure you're on the latest release of PHP 8.1 (8.1.28 is available).

Good solution!

You will want to ensure nothing on your server or firewall is blocking or manipulating the request. Otherwise, the expected result will not match and you will continue to receive this message.

Would recommend posting any feature suggestions in our Feedback forum.

There are no means to do this via the core software currently. You're more than welcome to suggest this in our Feedback forum.

Please note that this will continue regardless of if we move your topic or not.

Your login requires email address and you have inserted display name, please insert email address for the ACP credentials. Please also be sure to be PHP 8.1. As you're on PHP 8.0 right now.

What Randy is talking about would be on your server, not in our software.

The language is very secure that is why 😄 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.

As Randy mentioned, this is not something which we support, nor do we recommend it. There is a ton of potential for mistakes and errors. If your hosting provider has verified that in the database copy that had the crashed search index table has no other crashed tables. Have you tried regenerating like Nathan suggested above? Assuming no other tables are corrupted, that may be the solution you're looking for here.

Apologies for the confusion. Just for clarity, this is what I was referring to but either works as they lead to the same place: Glad to hear you were able to resolve the issue. While I understand you're not happy with this change, it is actually done to ease the support process and make it easier to find answers yourself and get help faster. For years, we have been saying that forums are an amazing resource for support but have never used it, value answers sat behind tickets, never to be reused again, along with our community laid to waste. We decided about 2+ years ago now to transfer all the start of technical support from tickets to forums; essentially "eat our own dog food" type scenario. We sent out emails alerting all our clients of this change and posted in our community here. Many had the same mentality as yourself, it was a downgrade, support will be horrible, etc... I think a lot of those individuals, after actually using it now prefer our community/forum support over tickets as they can find/get help faster and compare what they're facing to previous issues. As you have seen here, a very high percentage tickets are still handled by our staff (hi, I am a staff member 🙂 ) . However, we do have third party providers who provide third party services who tend to answer as well and that is benefit too because you get aware of their services and get assistance from them. Then we also have clients who just like being here and interacting/helping everyone. Just like on your community, people like to help others and discuss something that bond them together for no real monetary gain. That is what makes a healthy community, and, in this case, it is centered around our product. Sorry, believe there is a misunderstanding here or misremembering. Even in our previous support pattern of allowing tickets first, we did not provide support for hosting environments, such as PHP, database, etc... That has not changed as we moved to this community pattern. If you have questions on software requirements of the server, etc... we can answer that, but we cannot tell you specifics about your hosting environment or how to configure/perform an action in them. That is for your hosting provider to perform or tell you. If you do not have a support contract with your provider, you may wish to hire a server administrator or switch to our Cloud platform where you won't have to worry about those items. Also, in the classic support forum that we're in now, we do allow server-based questions to be answered by fellow clients so you could post that up here and gain insights. Ultimately, while we do not directly support server environments, there's no reason to struggle on your own. You have options. Apologies, this is indeed something to improve on in the software. Those not using UTF8MB4 are few and far in between and may have missed the upgrade step where it was required to change. I will bring this up internally. As mentioned above, this is indeed a gap in the software and of that, few and far in between are not using UTF8MB4. However, is indeed something we need to correct.

Check that you have all files up to date. You disabled any third-party applications/plugins. You are on PHP 8.0 or 8.1.