How do I Know Who has An SP Pagebuilder Article Checked Out? - Question | JoomShaper

How do I Know Who has An SP Pagebuilder Article Checked Out?

GP

Gary Piland

SP Page Builder 9 months ago

How do I know who has an SP Pagebuilder article checked out?

0
4 Answers
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 9 months ago #182148

Hello Gary,

Thanks for reaching out to us.

You can find out who has an SP Page Builder article checked out by going to Content → Articles in the Joomla admin panel. Look for the lock icon (🔒) next to the article title and hover over it to see which user has it checked out.

If you have the right permissions, you can unlock it by going to System → Global Check-in or click on lock icon.

Hope that helps!

Thanks,

0
GP
Gary Piland
Accepted Answer
9 months ago #182232

These are SPPB articles, they don't show up in Conent - Articles, you have to look under SP Pagebuilder - Articles. That is where the padlocks aren't showing up.

0
GP
Gary Piland
Accepted Answer
9 months ago #182231

We can’t get padlocks to show up in SPPB when an article is being edited by other superusers. This is happening in Firefox, Chrome and Safari.

Screenshot #1

On the left we are logged in on Firefox as superuser “gary” and on the right we are logged in on Chrome as superuser “alex”.

User “alex” is editing 2 different SPPB articles - Additional Services and ATMs.

User “gary” doesn’t show a padlock on either SP Pagebuilder article. NOTE: We cleared cache, reloaded the pages, quit out of the browsers and tried several times to get the padlocks to show up. They don’t.

And worse - different superusers can edit articles at the same - whoever saves last overriding the other person’s edits. This is a major problem on sites with more than one editor obviously.

Screenshot #2

This second screenshot shows the exact same problem with “gary” in Firfox editing 2 SPPB articles and there are no padlocks showing in “alex”’s Chrome admin screen.

0
Ziaul Kabir
Ziaul Kabir
Accepted Answer
Support Agent 9 months ago #182254

Hello,

We’ve identified the issue and are working on resolving it. A fix should be included in the next release.

Thank you for your patience and understanding.

0