Open Access Errors

Hi there, @dsc462!

It will always lead to “Incorrect Login Details.”

Is there any way to get rid of this page or put our own SSO in place of it?

That is interesting. I looks like this could be due to the setup on the site. We do not recommend SSO plugins with Sensei, since that generally causes issues with the login functionality.

Ideally we would set the course to open access. However, we imported this course and for some reason clicking on open access leads to this error:

Updating failed. Could not update the meta value of _genesis_hide_title in database.

It looks like you’re using the Genesis theme, so to ensure this is not happening due to a conflict with your theme, can you try conflict testing?

Here is how you can do it: https://woocommerce.com/document/how-to-test-for-conflicts/

Let us know how it goes!

Hi Joash,

Thank you so much for your quick response. We have tested for conflict regarding these issues. On a similar import in a different environment, no such error occurs and we can select open access and save with no issues. On the site with the error, when we switch to a non-Genesis theme, the error simply changes to:

Updating failed. Could not update the meta value of _course_featured in database.

Which is interesting because we have not changed the course featured value for any course.

Regarding your recommendation for not using SSO, we are using this as part of an educational institution with thousands of users, so this is not an option. Is there a way to at least prevent that login screen from showing up especially since we are unlikely to have local accounts/login. (Like maybe instead of the login screen, it shows up as an error such as “You must be logged in to take this course” OR Maybe it redirects the user to our login instead?) Seeing this login screen is sure to confuse our clients and users.

Thanks for the update, @dsc462

On the site with the error, when we switch to a non-Genesis theme, the error simply changes to […]

Interesting. Something specific to this site seems to be causing the error. Other than changing the theme, it would be worth testing if this error also happens when no plugins are enabled (besides Sensei).

Regarding your recommendation for not using SSO, we are using this as part of an educational institution with thousands of users, so this is not an option

You can override the default login functionality by customizing this page on a Child Theme: https://github.com/Automattic/sensei/blob/trunk/templates/user/login-form.php
That would need to be done by copying it to [YourChildThemeNameHere]/sensei/user/login-form.php

Customizing that would extend out of our scope of support, so if you need assistance with making changes to it, you can try https://jobs.wordpress.net/ or https://jetpack.pro/ if you need help

Hi Joash,

Thank you so much for the information regarding the customization of a child theme. I truly appreciate your detailed response.

We have multiple themes installed and it might be difficult to add this custom to each one. Would it be possible for our team to implement a custom php solution that covers all themes in one go?

Additionally, we wanted to inquire about support for paid users. Would you have any idea what licensing looks like for multisite environments and if the support that comes with that could help us with this issue?

You’re very welcome, @dsc462!

We have multiple themes installed and it might be difficult to add this custom to each one. Would it be possible for our team to implement a custom php solution that covers all themes in one go?

We have not tested that exact use case, but with customisation, almost anything can be done.

Additionally, we wanted to inquire about support for paid users. Would you have any idea what licensing looks like for multisite environments and if the support that comes with that could help us with this issue?

For multisites, we recommend the Agency plan which allows for Sensei to be used on 20 sites. If you need more than that, our team can look into a custom solution for you.

With regards to whether our support team can help with these issues, it would be worth checking our Support Policy first. Looking at the customization required, that would extend out of scope, but issues with Sensei itself (when other plugins/themes are disabled) will be covered.

Hi there,

It has been a while since we have heard from you, so I’m marking this topic as resolved.

But if you have any further questions or need some more help, you’re welcome to reply here or open another thread.