No Code Attached Yet
avatar Webdongle
Webdongle
16 Feb 2025

Steps to reproduce the issue

Open up an Article for edit
Set Unpublished
Click the preview button

Expected result

Article displays in popup window

Actual result

Popup window displays Page not found

System information (as much as possible)

Additional comments

When Article is unpublished then the preview button at the top shows page not found
If page is set 'Registered' then the front end menu shows (in the popup window) with a not authorised message (this is with SU selected in the 'Registered' view level).

It seems as if the the preview popup is not handling the ACL correctly.

The preview window in the JCE editor works as expected.

avatar Webdongle Webdongle - open - 16 Feb 2025
avatar Webdongle Webdongle - change - 16 Feb 2025
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 16 Feb 2025
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 16 Feb 2025
avatar brianteeman
brianteeman - comment - 16 Feb 2025

That is the expected behaviour as the front end is being loaded as a gust user as has been discussed many many times.

The solution to this is to enable shared sessions in the global config. Then the front end will be loaded as the same user as the admin

avatar tecpromotion tecpromotion - change - 16 Feb 2025
Status New Closed
Closed_Date 0000-00-00 00:00:00 2025-02-16 20:56:55
Closed_By tecpromotion
avatar tecpromotion tecpromotion - close - 16 Feb 2025
avatar tecpromotion
tecpromotion - comment - 16 Feb 2025

Expected behaviour and approach as described.

avatar Webdongle
Webdongle - comment - 16 Feb 2025

OK I Get it. When someone is using test logins in the front end they have to set Shared Sessions to yes to preview while editing the document. Then set Shared Sessions to no to test the various test users in the different user groups. Then set Shared Sessions back to yes if they wish to preview further edits.

And admin who don't normally have Shared Sessions set to yes have to change the setting (then back again) every time they edit an Article. That all makes perfect sense now. Thank you

Add a Comment

Login with GitHub to post a comment