Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • #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,
    Jason

    #994421

    Hey Jason,

    Can you please specify the pages that have this issue and give us the editor user too?

    Best regards,
    Victoria

    #994425

    Second that. Have the same issues since today on two sites with newest WordPress and Enfold. Will watch for answers to @jason

    #994641

    Sure thing Victoria, basically any page (but I tried About & News). Editor details attached.
    Thanks,
    Jason

    #994642

    I should add, the Classic Editor is installed & activated, I haven’t tested with it deactivated, actually will do so now… done – no difference.

    #994776

    Hi 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,
    Victoria

    #995179

    Hi Victoria,
    I disabled all plugins – no difference, I’m still unable to edit existing pages under the Editor role.
    Thanks,
    Jason

    #995275

    For me this did the trick: after disabling the plugin BackWPUp 3.6.0 the avia builder loaded again.

    #995579

    Hi jorche,

    Glad you got it working for you! :)

    If you need further assistance please let us know.

    Best regards,
    Victoria

    #995585

    Hi 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,
    Victoria

    #995781

    Hi 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!
    Jason

    #995824

    Hi Jason,

    Great, glad you found a solution and thanks for sharing :-)

    Please let us know if you should need any further help on the topic.

    Best regards,
    Rikard

Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.