-
Notifications
You must be signed in to change notification settings - Fork 10.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Woocommerce shop manager role breaks WPBakery Page Builder roles. #21886
Comments
I have the same issue. |
WPBakery probably required additional capabilities to function? Perhaps reach out to the team at WPBakery and enquire what capability is required to have the menu visible? Once they provide you with that, you can use the Members plugin again and just add that capability to the shop manager role to have the menu show up. |
Here's an update of WPBakery:
So, this problem could be solved in the next release. 😄 |
This is still an issue as of 11/23. Reverting to previous version does not help either. Contacted WP Bakery, same response as above. Probably time to start looking for an alternative page builder... |
WPBakery Page Builder Version 5.6 still doesn't work with user Role Shop Manager |
Having the same issue, where is the fix? My clients with shop manager role need ability to edit with the page builder. |
@jogoyo @gottschild @phlegx Contact WP Bakery Support. I've contacted them and got the usual run around "we'll fix this in a future release." If more people contact them, maybe they will realize the seriousness of their mistake. It has been a major disruption to our workflow. https://support.wpbakery.com/ |
Got the same problem here. The shop manager role is configured to allow the use of the Page Builder in the Product Post Type but it doesn't work. My client has lots of products to edit and this is a vital feature for him! Please help. WordPress 4.9.8, WooCommerce 3.5.2, WPBakery Page Builder 5.6 |
Same problem! When is a fix expected? Oh, btw: making a clone of the Shop Manager role, and calling it something like 'Shop manager clone' made the page builder accessible for us again. But this in its turn breaks access to other plugins (like pdf invoices) which are dependant on the 'Shop Manager' role. But hé, this could help people out for a bit. |
Same problem here ! I'm a big fan of elementor ... here is one more reason ! |
Has anyone figured out a fix to this yet? We're going on the third month of this bug here... Cloning the shop manager role seems to be a fix, but it breaks too much other functionality for us. |
Same issue here - did anybody find a solution? |
Still no solution... |
Unfortunately not (...), here's the response from the support:
|
Same canned response here... I've been contacting them once every two weeks or so... Exceptionally terrible service. |
Works fine for me with latest wordpress and WPBakery Page Builder |
update In line: wp-content/plugins/woocommerce/includes/wc-user-functions.php:397 shop_manager role is not set as editable_role but it setup'ed a some other role "customer" and this causes an issue when opening the edit page/post view. Fix will be available in next relaase of WPBakery Page Builder,
|
The fix is not working for me, seems they havnt solved the issue yet. |
Describe the bug
I use the latest Woocommerce version and also the latest WPBakery Page Builder. Like described here (docs.woocommerce.com) I have installed Wordpress plugin Members to give a user with role
editor
also the roleshop_manager
. For the user with roleseditor
andshop_manager
, the WPBakery Page Builder disappear (is no more available) in edit post or page.To Reproduce
Steps to reproduce the behavior:
editor
: Individually -> page and posts.editor
.shop manager
to the user with roleeditor
and save it.Expected behavior
If the user with role
editor
andshop manager
edits a post or page, WPBakery Page Builder should be activated and available because roleeditor
has this capability (see step 4.). If I remove roleshop manager
from the user, all works fine like expected.Isolating the problem (mark completed items with an [x]):
WordPress Environment
The text was updated successfully, but these errors were encountered: