System Information
- Strapi Version: v4.23.1
- Operating System:
- Database: PosqgreSQL
- Node Version: v20.18.0
- NPM Version:
- Yarn Version:
We encountered a problem with the Record locking plugin when our users were trying to access the content manager in the Strapi admin.
As soon as they clicked on “Content Manager” they were met with a warning that the current single types were being edited by someone else and they couldn’t navigate to any other place than back to the admin console.
We have removed the plugin which solved the current issue so we could investigate further what is causing this problem.
What we have found is that users with a different role (Editors) automatically land on the first Single Types we have when they click on “Content Manager”. But with the admin role you “land” on the first Collection Type instead. So the warning from the plugin is not so strange after all…
We would like to be able to use the Record locking plugin so my question is if there is any way to control where the users/roles “land” when they click on “Content Manager”?
As far as I know we haven’t made any settings for this to be different between the roles so I can’t find an explanation way this is happening in the first place.
UPDATE
Found an explanation for the problem!
- When updating the Editor roles permission to view the first content type in the “Content Types” list the user “lands” on this instead of the “Single Types”.
- This should be considered a bug imo, user should land on the first available content type they have access to or it should be configurable where to “land”.