Jim M

If you have mod_security or any other security module enabled, please disable it to test what is happening here. Otherwise, we require access to see what is happening: 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 Nathan mentioned, they would only receive this if they have configured it as such. If there are any further questions, please let us know.

Glad to hear you were able to complete the upgrade 🙂 .

If there are any issues on the software-side of things, please let us know and we can certainly assist there 🙂 . However, upgrading the software itself is pretty straight-forward, as mentioned above.

I'm afraid, you will want to continue to simplify your environment as I am unable to reproduce this. It seems each step that you're taking to simplify it keeps removing errors so if you are unable to find any errors logs, simplifying it down to a basic server may be your only choice. If you have any caching, at any level, you will want to disable it completely. You may wish to check all server permissions, including file/folder ownership as that may impact things additionally. While I would expect this to be a global issue, it may be further impacted if there is any caching.

This would be a server problem if you’re being directed elsewhere. Typically, this is encountered with mod_security and other security modules.

Minimum is PHP 7.4 so need to have your hosting provider upgrade you to a server with it or change providers. There is no other option if you can’t run minimally PHP 7.4, I’m afraid.

I can't explain what is happening either. Everything is fine from this end. If it was a software issue, I would expect it to remain an issue regardless. If you're using a load balancer, CloudFlare, proxies, etc..., I would suggest reducing your complexity and making things simpler to get it working then add in complexity.

Only things which you can have them do is clear their browser's cache and as they're using an iPad, ensure they're using Safari (ensure iPadOS is updated to the latest release)

Unfortunately, when viewing, I am no longer receiving the 404 error in the ACP or the errors mentioned on the front-end.

You may wish to log into the Client Area and download a full set of files then extract these to your local computer. Once done, upload the content of the "ips_***" folder to your server, overwriting what is there. When all files successfully upload, please go to /admin/upgrade . If you're still getting a 504 error, you will need to work with your hosting provider to resolve the 504. I'm afraid, there is no CLI.

When I renamed your .htaccess file, I am no longer encountering these errors. I would suggest removing everything in your .htaccess file except for our URL rewrites and try again. Something looks to be redirecting or mis-interrupting requests there.

Unfortunately, you would need to go back to their support as they did not resolve the problem which is at hand here.

This is currently a known issue which is currently still an open bug so there is no resolution at this time.

Could you please provide a URL to where you have this? I can then look at the images and what is happening here.

Yes, using the custom field there that you have setup would perform that. If you aren't doing anything custom with the display of the field on the profile, I would just suggest using the default option as that will give you Title: Value . You would need to use the member search, you can search custom profile fields.

Sorry, a little confused in what you're attempting to do here. You are modifying the custom formatting for profile and topics. This would not change in the search. In search, it would just display their display name with a link to their profile if a value is found. Additionally, {$Discord} and {$Discord Username} are not variables so you would not want to use them as such. The name of the field should be put there by simply using {$title} so there is no need to change that.

It should but there are things in the process which could of course, creating conflicts or issues outside our control (i.e. slow write to disk) with that and result in what you've encountered. Glad to hear though you found the resolution to your issue!

Our auto-upgrader in the ACP, does only track what is changed version to version and applies that in the upgrade. However, you would receive an alert to any manually modified files during the upgrade or in the Support tab of the ACP. The notice should have gone out last year. It may be worth double checking the email address on file in the Client Area for your account just to ensure. This way you can get your information "straight from the horses mouth" 🙂 .

I’m a little confused by their statement here. A 403 error shouldn’t be caused by this. 403 would mean there is a permission error on the server and thus cannot access the file and therefore run. Could you please have them clarify?

The original client was incorrectly assuming that priority support was the only way to receive support, I was correcting that assumption. I never stated that priority support was or was not offered. However, we only offer support which is conduct through our forum here (there is no priority support).

Support is still covered under self-hosted licenses. The avenue to receive support has only changed. Our same staff will be here to assist you in this forum for any software support needs. Our staff has access to the client area to obtain secure access to your access details you provide and we can escalate your ticket, should it require doing so. What is it that you require support for? We’re here to help 🙂.

You would want to reach out to your hosting provider with any concerns here. It would be hard for us from a software perspective confirm or deny this. Depending on what was happening on the server at the time, it is conceivable that a database could become corrupted while running a long task, such as a backup, and the server was restarted/shutdown/etc... If you or your hosting provider restored a previous database after that, that would explain what is happening.

A completely blank white page is often the sign of a suppressed PHP or server error. You would want to consult your server error logs on your server for more information here. However, simply guessing here, if you are guided by an intranet (i.e. VPN or network), it could also be these users don't have access to your sub-domain and are getting a default page. This, unfortunately, would be up to yourself to diagnose as that would be a network issue. If you are unsure how, you will want to work with your hosting provider on these items.