-
AuthorPosts
-
August 7, 2018 at 3:02 am #994177
Hi there,
Here’s an odd one. Pages I’ve created (as an admin) come up blank when going to edit them as an editor.
There’s no trouble creating a new page & using ALB as an editor.
Where should I start looking?
Everything is up to date, there’s no caching enabled – it’s a staging site.
Login details below.
Thanks,
JasonAugust 7, 2018 at 1:36 pm #994421Hey Jason,
Can you please specify the pages that have this issue and give us the editor user too?
Best regards,
VictoriaAugust 7, 2018 at 1:44 pm #994425Second that. Have the same issues since today on two sites with newest WordPress and Enfold. Will watch for answers to @jason
August 8, 2018 at 1:05 am #994641Sure thing Victoria, basically any page (but I tried About & News). Editor details attached.
Thanks,
JasonAugust 8, 2018 at 1:10 am #994642I should add, the Classic Editor is installed & activated, I haven’t tested with it deactivated, actually will do so now… done – no difference.
August 8, 2018 at 9:55 am #994776Hi Jason,
Thank you :)
There are a few plugins that make changes in user roles and permissions and so can be causing the issue. Can you please deactivate all plugins and see if the issue persists?
Best regards,
VictoriaAugust 8, 2018 at 11:38 pm #995179Hi Victoria,
I disabled all plugins – no difference, I’m still unable to edit existing pages under the Editor role.
Thanks,
JasonAugust 9, 2018 at 8:12 am #995275For me this did the trick: after disabling the plugin BackWPUp 3.6.0 the avia builder loaded again.
August 9, 2018 at 4:28 pm #995579Hi jorche,
Glad you got it working for you! :)
If you need further assistance please let us know.
Best regards,
VictoriaAugust 9, 2018 at 4:32 pm #995585Hi Jason,
It can be that when plugins are deactivated their settings are not properly removed from the database and so the roles are not acting right.
Best regards,
VictoriaAugust 10, 2018 at 2:17 am #995781Hi Victoria,
Ok, so I’ve fixed it. I installed Members to take a look at what the editor role could do, it turns out this role didn’t have post edit capabilities, enabling these fixed the issue.
I can only surmise that this was historical as I certainly didn’t restrict the editor capabilities myself.
Cheers!
JasonAugust 10, 2018 at 6:51 am #995824 -
AuthorPosts
- You must be logged in to reply to this topic.