06/06/2018 at 14:40 #4925
There seems to be a bug with custom roles. When I have “Activate per form user access management for Gravity Forms” enabled and I login to my custom role and try to add a custom post or page, the post is added but the session times up, occasionally timing out the site.
To describe the process:
1. I login with a custom role
2. I create a new page.
3. I hit publish.
4. The spinning wheel next to publish keeps spinning and eventually comes up with an error of: “Connection lost. Saving has been disabled until you’re reconnected. We’re backing up this post in your browser, just in case.”
When I check the page list after the page is added.
Disabling “Activate per form user access management for Gravity Forms” seems to resolve this issue. Do you have any idea why this maybe happening?
Below is a list of all the capabilities that the custom role uses:
view-customer-area-menu06/06/2018 at 15:20 #4926
Generally, URE’s Gravity Forms access add-on modifies WP_Query SQL expression for the queries related to the GF database tables and should not influence on a WP queries related to the posts or pages.
Can you look at the server logs if they contain any related information from PHP or/and MySQL about endless recursion, timeout, etc. and share it with me?06/06/2018 at 15:39 #4927
Where abouts would you like me to look? I’ve looked through the server logs and I haven’t seen any indicators on where this maybe erroring out.06/06/2018 at 15:51 #4928
Repeat the action which leat to request timeout and look for the latest records at:
Is it suitable for this case to export database, plugins and theme files using “UpdraftPlus” plugin and share with me (support [at-sign] role-editor.com) via DropBox or Google Drive?
I would setup your site copy at my local dev. environment and test the issue with debugger then.10/06/2018 at 05:35 #4937
One more question – Do you use the latest version of URE Pro? There was a bug probably related to your issue, which was fixed with version 4.46.11/06/2018 at 12:51 #4940
Thank you very much Vladmir, that fixed the issue!
- You must be logged in to reply to this topic.