Hi there,

Thanks for contacting us. Sorry for the inconvenience. Will you please provide me the Joomla administrator access to check the issue? I will check & get back to you soon. 

-Thanks

But of course :)

I was having exactly this problem, and I suspect browser cache (at least). One solution that worked on my issue is I do front end editing in Chrome, and review the changes in Firefox (not logged in). For some reason, this is working.

Also, I have checked your article and no problem found.

https://prnt.sc/ckUnrtX-vPYY

Thanks.

Not sure what to do about it then, but will have to edit from backend - but will that be possible with SPPB 4?

(...editing Joomla native articles from backend when using SPPB as the editor?) (I would hate to have to change design in the middle of everything)

Cleaned all cache.

In Chrome it's still the same. Then tried Safari - same result. (Have not got Firefox installed)

EDITING JOOMLA NATIVE ARTICLE MADE WITH SPPB - FROM FRONTEND

1. When I login and turn on edit - the site opens in a new page
2. No matter how I edit - it looks good - and I save - and all looks good
3. Then I hit Close - and the page shuts down - and I'm re-directed to the frontpage
4. When I go back to the page I edited, nothing is saved.
5. Now, my only option is to edit from backend - an option that you guys will close down anytime soon
6. Do you get why I keep going on about this?-)

Could I get you to make a small change in a "Lorem ipsum" text on the page - from frontend - so I can see that it is possible - and even better will you record while you are doing it, so I can have a change to see if I do something different than you?

Thanks in advance

I will try to pul together a screencast of some sort today. It does involve using different browsers on (in my case) different monitors. Not to put too fine a point on things, Joomla's lack of a reliable front-end editing facility has long been a pain point - and it may be related to the way the platform handles security. I'm not an expert, but what would look more like an exploit than someone modifying content from the front end?

@John Juhl I think your site only occurred this problem. I have checked my end & no problem found. Maybe, third-party extensions or script occurred the problem. Thanks