28/02/2017 at 10:47 #3384
How can I allow additional rights that are not available as an option in the selection? In my case it is about the “Divi Theme Options” from manufacturer Elegantthemes. A 404 error is triggered for the selected user role.
Thanks in advance for your reply.
Best regards28/02/2017 at 13:12 #3385
Give me more details about what do you try to achieve. Screenshots will be very helpful.22/09/2017 at 17:07 #4206
Hello, I would like to take up the topic again. I had not received a notification at the time that an answer came and just remembered that I had already posted.
Divi is a premium theme by Elegantthemes. If I want to give a user role permissions on the theme, I get the following message:
The requested URL /wp-admin/et_divi_options was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
The links or the areas are the following, which I would like to share:
This is what WP Admin looks like:
Interestingly, the Divi Theme also has user rights for various user roles. But for this user group everything is active.
How can I do this with the User Role Editor that the user roles I created can access it?
I thank you for the attention and thank you in advance for the reply.
Best regards23/09/2017 at 04:00 #4207
These user capabilities are required by Divi in order role can work with menu items under the ‘Divi’ menu:
I tested with Divi verison 22.214.171.124/12/2017 at 11:25 #4505
I’m ashamed that I’m only reacting now. Your help has worked wonderfully. Many many thanks. (:15/12/2017 at 11:53 #4506
No problem. Thanks for the feedback.15/07/2019 at 12:05 #5811
I must now reopen the topic. Since one of the last updates these settings don’t work anymore. I can open the visual editor in the frontend, but I don’t see an editor in the backend anymore. Where do I get the thinking error?
Levent16/07/2019 at 01:29 #5812
Re-check if needed option is enabled for a role inside Divi’s internal Role Editor.
If it will not help, can you share the latest version of Divi?16/07/2019 at 06:57 #5813
in the Divi settings for the user roles I have actually already checked before. All permissions are active. Where can I send you the current version? (:16/07/2019 at 12:03 #5814
Upload a .zip to DropBox, Google Drive or similar service and send the link to support [at-sign] role-editor.com16/07/2019 at 13:45 #5815
Mail just left. Thank you very much for your help. (:17/07/2019 at 02:07 #5818
My test showed that user with custom role, which includes just ‘edit_posts’, ‘publish_posts’, ‘edit_published_posts’ sees and can use “Use the Divi Builder” button at the back-end post editor page.
thank you for your support. I get this displayed in the console:
JQMIGRATE: Migrate is installed, version 1.4.1 post-metabox.js?ver=126.96.36.199:1 Uncaught TypeError: Cannot read property 'replace' of undefined at e.value (post-metabox.js?ver=188.8.131.52:1) at new e (post-metabox.js?ver=184.108.40.206:1) at t.value (post-metabox.js?ver=220.127.116.11:1) at t.value (post-metabox.js?ver=18.104.22.168:1) at new u (post-metabox.js?ver=22.214.171.124:1) at HTMLDocument.<anonymous> (post-metabox.js?ver=126.96.36.199:1) at i (load-scripts.php?c=1&load=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,moxiejs,plupload&ver=5.2.2:2) at Object.fireWith [as resolveWith] (load-scripts.php?c=1&load=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,moxiejs,plupload&ver=5.2.2:2) at Function.ready (load-scripts.php?c=1&load=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,moxiejs,plupload&ver=5.2.2:2) at HTMLDocument.J (load-scripts.php?c=1&load=jquery-core,jquery-migrate,utils,jquery-ui-core,jquery-ui-widget,jquery-ui-position,moxiejs,plupload&ver=5.2.2:2)
It’s interesting that this only happens with this user role. Can you do anything with it?
Many greetings17/07/2019 at 10:18 #5820
Did you block any post meta boxes for this role? If Yes, try to remove blocking and make another test. If that will help you can play with meta boxes one by one to isolate which meta box blocking causes this JS error.17/07/2019 at 18:16 #5821
That was actually a good keyword and I’m annoyed that I didn’t come up with it on my own.
I swapped Yoast for Rankmath. Rankmath has its own role system. That was deactivated. But I activated that and granted this role 2 rights over the Rankmath rights system and now it works again. The devil is sometimes really in the detail. 😉
Many thanks again for the common error search and the great teamwork. (:
- You must be logged in to reply to this topic.