Jim M

It will let me get into one of them but not both. The standard login handler can be enabled in ACP -> System -> Login & Registration.

It seems that whenever I attempt to sign in again, i.e. sign in from the front-end and then try to sign in the ACP, is when I get the error. Without this functioning, we cannot support you here, I'm afraid. Our only way forward would be to enable the standard login handler so that we can login on both the front-end and ACP.

I still get the original error when logging into the ACP.

We would need access to the ACP though so the front-end login will not work for us here. You can temporarily disable the SSO while we investigate this if we run into issues.

The credentials we have on file are rendering the below through your SSO: Credentials are incorrect or you do not have permissions to login. If this is your first time visiting from the old site, please reset your password.

Please ensure that the member in question is able to see the club. If permissions have changed, it would indeed reflect that. Our account does not have authorization to login to the Admin CP so you would need to allow that.

I am not able to reproduce this. All the users you listed, all have the Club listed under their profile like so:

They would need to have filled out their Display Name as their Display Name. That is how the software works by default 🙂 . If you incorrectly did this previously with a third party login provider/api or the user inserted their actual name as their display name, the system was instructed to show that as their display name.

Probably not the name but rather the required markup there if your settings are super strict and blocking markup or HTML-like parameters.

On my test installation, I am not having any issues with translating this key. You may wish to check to ensure that your server does not have mod_security or any other security modules which may be blocking it.

This would be a hosting issue. Please contact your hosting provider or server administrator for assistance on installing the missing delegate.

Could you please post here or put the display name of the user who you're seeing this on in the Notes section of the Access Details of the Client Area? The few individuals I've checked thus far, do indeed have this showing up.

I removed most of your constants.php and the real reason for the issue is showing now. An important table, core_sys_conf_settings , does not exist.

While it shouldn't, that is the only thing which has changed so would be worth questioning to them on your configuration and if there should be optimizations done. All tables, including core_search_index, should be InnoDB.

You would need to check how those are created and how they are logging in. It sounds like you're creating a new user again so it would be true that they couldn't use that display name again.

You would want to contact your hosting provider/server administrator for assistance. If the only thing which has changed is that your MySQL got upgraded, that is likely a breadcrumb which you will need to review with them. It would seem odd that no configuration or search parameter changed to lead to a slowdown.

If the users were imported or you are using an external site to create users, whether that's through an SSO or API, if they are missing a display name or password, the system will prompt them when logging in as this is require information.

You would need to check and ensure CRON is working as when saving I receive this: In order to enable this setting you must make the .../applications/core/interface/task/task.php file executable (i.e. chmod 0777). Thus, new changes won't be saving till that is addressed. Once I switch background tasks to run via Traffic, changes worked with issue

You can rename the constants.php file to something else to test. I can take a look at why it is looking for a dev folder if you are able to provide FTP 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 only see your custom settings. I do not see our settings.

The dev folder would only be present when in dev mode. You will want to check your constants and remove IN_DEV

If your .htaccess rules are working, why are you setting this as well in the ACP?

You shouldn't be using IN_DEV mode on your production installation.

Looking at your community, I am seeing custom CSP rules. Not the ones setup in the ACP. You cannot run both 🙂 . You would need to choose to set it one or the other. The referrer policy is indeed being set though.

This is generally an issues with PHP connecting to your database server. Can read through the topic here with individuals encountering the same issue: