The "Backend Editor and Frontend Editor" options under Edit/ Add Post for contributor(role) users are not visible since I have updated Salient 10.5.3 to 12.1.6.
I found the way to enable it through WPBakery Page Builder Settings, but what if I have already more than 100 sites running. I am looking to find the way to set it as "enabled" by default for all contributor Users.
Please update to the Latest Salient Theme Version.
The current version of the theme is 13 and the current version of the page builder is 6.6. Salient versions older than v11 won't be compatible with WordPress 5.5.
Here's the documentation on the available methods for updating Salient: http://themenectar.com/docs/salient/updating-salient/#methods Once you've updated that, the update for the included page builder will become available. Note that "Visual Composer" also renamed their plugin on Envato to "WPbakery page builder" a couple of years back.
We have more than 10,000 sites running under our setup: WordPress 5.7.1 and Salient 12.1.6(We decided to go for this because on that time, it was most compatible version). To update the Salient 13.0, we need another 3 months to run the whole process including testing again. And our company is not ready to do so. Therefore, we need a quick fix for this solution.
I hope you understand my situation and try to support us..
Thanks for the code, which I have already added to my child theme(functions.php) but every time I click to the "Backend Editor" button, it shows this message "Custom HTML is disabled for your user role. Please contact your site Administrator to change your capabilities."
Hey,
The "Backend Editor and Frontend Editor" options under Edit/ Add Post for contributor(role) users are not visible since I have updated Salient 10.5.3 to 12.1.6.
I found the way to enable it through WPBakery Page Builder Settings, but what if I have already more than 100 sites running. I am looking to find the way to set it as "enabled" by default for all contributor Users.
Let me know if there is any possibility..
Thanks,
Hey Again
Please update to the Latest Salient Theme Version.
The current version of the theme is 13 and the current version of the page builder is 6.6. Salient versions older than v11 won't be compatible with WordPress 5.5.
Here's the documentation on the available methods for updating Salient: http://themenectar.com/docs/salient/updating-salient/#methods Once you've updated that, the update for the included page builder will become available. Note that "Visual Composer" also renamed their plugin on Envato to "WPbakery page builder" a couple of years back.
Here's an update guide on what to expect when jumping many major releases at once: http://themenectar.com/docs/salient/important-salient-update-for-new-envato-requirements/ take a read through before the update, as many things have changed.
To get a list of Bug Fixes and new Feature addons in the Latest Theme updates view change log here http://themenectar.com/changelogs/salient.html .
Best.
ThemeNectar Support Team
Hey Tahir,
We have more than 10,000 sites running under our setup: WordPress 5.7.1 and Salient 12.1.6(We decided to go for this because on that time, it was most compatible version). To update the Salient 13.0, we need another 3 months to run the whole process including testing again. And our company is not ready to do so. Therefore, we need a quick fix for this solution.
I hope you understand my situation and try to support us..
Thanks in advance,
Tim
Hi Tim,
Please allow us to escalate this to the developer to add in response.
Thanks.
Hey Time, you can programmatically enable the editors for specific roles by adding the following snippet into your child theme functions.php file:
Hi,
Thanks for the code, which I have already added to my child theme(functions.php) but every time I click to the "Backend Editor" button, it shows this message "Custom HTML is disabled for your user role. Please contact your site Administrator to change your capabilities."
Thanks,
Hi,
I added this extra filter to resolve this message issue..
add_filter( 'vc_role_access_with_unfiltered_html_get_state', '__return_true' );
Thanks,