• Resolved rosmariewe

    (@rosmariewe)


    I am using foogallery 2.4.22. A new problem occured: the WP “Editor” role is not able to edit/create foogalleries any more (4 weeks ago, this was definitely still working). The existing galleries can be seen, but not edited. (I additionally used the “Members” plugin to grant the foogallery rights for the WP Editor role: all items are ticked).

    Thank you for support!

    Rosmarie

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support elviiso

    (@elviiso)

    Hi @rosmariewe

    I have been running tests on FoGallery 2.4.22 as I tried to replicate what you described but from my end, when the “Gallery Creator Role” is set to “Editor”, all users with the editor user role can create new galleries and edit existing galleries. I have created a brief recording while I was running one of these tests to demonstrate this: https://www.loom.com/share/268de52ab5774ae394577a59f7524f89

    Kindly ensure that you are using the default WordPress user roles and are setting the gallery editor role from FooGallery -> Settings -> Gallery Creator Role which will allow you to select the “Editor” role as demonstrated in the recording above.

    Thanks.

    Regards,
    Elvis

    Thread Starter rosmariewe

    (@rosmariewe)

    Hi Elvis,

    this was it! The creator role in Foogallery was set to “Default” (strange, that it has been working before….). Changing this to “Editor” solved the problem!

    Thank you very much for your fast and comprehensive response and the solution straight to the point! This helped a lot!

    kind regards, Rosmarie

    Hi, there is no support for non default user roles any more ? It was working with no problem a few weeks ago. I have got custom user role made by duplicate editor role. If I select this role in Settings of Foogallery, there is no item at WP admin menu. Even if I select “author” role at Foo settings, the user with Editorcopy role cant see Foo at admin menu. Thanx

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