This support ticket is created vor 3 Jahre. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
Hello, I have just updated to the latest versions of Types, Views, Forms and Access over the weekend. I also updated WPML and related plugins.
Since doing this, my site Editors cannot see links to add new posts or edit posts (for regular posts or custom post types).
As an emergency fix, I've had to disable Access from managing those post types.
I realise that this was a known issue between Access and WPML once, but I thought this was resolved.
ANy ideas?
thanks
Alan
As discussed in the chat, you can report here the results of your tests when you get the time to. I am setting this as waiting for your feedback which should keep it open for 3 weeks.
Update: I have cloned the site to run locally on Xampp, and even with all non Toolset / WPML plugins disabled and using the default 2020 theme, I am still seeing the issue whereby the EDITOR roles do not have access to create or edit posts or Custom Post Types, if Posts are set up to be "Managed by ACCESS".
In ACCESS, switching to "Use default WP read permissions" for Posts is necessary to enable Editors to edit and create all post types again.
That seems like a bug, unless, I am missing something. Would it be possible to take a copy of your website and debug it locally? If yes, please create an administrator user for me and share it in your next reply, which will be private. I'll log in and install Duplicator or All In One Migration to take the copy. You can delete that user later.
Thank you, Alan, I confirm the credentials are working for me. I just need to make sure that I fully understand the issue that you are facing.
I created and edited two (private)posts while Access is still active without issues. One post for the default Post type, that is not managed by Access. And one post from the "Group" post type that is managed with Access:
- hidden link
- hidden link
Am I missing something? What steps should I follow to see this issue?
I can see the issue, it happens when the post type is managed by Toolset and WPML plugin activated. Let me debug the copy of your website and get back to you/
Our 2nd Tier and other team members were not able to reproduce the issue with the copy of your website. Either the one directly taken from your website or another one from my copy. So, I migrated your site to our online platform and the issue was reproducible with different outcomes hidden link
When Posts are managed by Toolset, the editor is not able to create new regular or custom posts.
When Posts are not managed by Toolset, the editor can create regular posts and custom posts that are not managed by Toolset. The editor cannot create custom posts that are managed by Toolset.
I escalated this to our 2nd Tier, he'll investigate it and we'll get back to you as soon as possible.
Finally, we narrowed the issue down to an MU-plugin "disable-logged-out-plugin.php", once we deactivate it the Toolset Access control works as expected with WPML. You can check in this clone website hidden link
I wanted to check that on your website, so, I renamed the plugin to ".disable-logged-out-plugin.php" adding a dot at the beginning to prevent its execution, but that seems to crash the backend, and I can't access it anymore to test it further.
Please allow me FTP access to rename the plugin back and recover the website. Your next reply will be private to let you share credentials safely.
Please note that I will just recover the website, I won't investigate anything further with the plugin. This is custom code and is therefore out of the scope of the support.
I had forgotten about that mu-plugin!
Thank you for figuring out that it was causing the issue.
I have removed it, and the back end is now accessible again.
Awesome Alan, I logged into your website and I can confirm it too. I am marking this ticket as resolved, you can reopen it in 12 hours if you still need assistance with this issue. Feel free to open a new ticket for any other question or request.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.
