Pages Edited In Front End Don't Save Permanently
blue_Shift
I've done the work twice now - SPPB 3.8.9 PRO. This is a problem I had in some other build using price list, and this bug makes it impossible for my client to use the product.
blue_Shift
Accepted AnswerIt is working now - the most important discovery is there needs to be a menu item associated with the SP Page for front page edits to save, even if it's a hidden item (for development).
blue_Shift
Accepted AnswerUPDATE: The other Add-Ons all seem to work, only price list doesn't write changes in a permanent way. (It seems to work in a kind of cache, but changes are lost on quit). This is true whether Price List is used on the top level of the page, or nested inside a tabbed / accordion Add-on.
Once the page I'm working on is grokked, I can provide superadmin to a page one of your devs can test.
blue_Shift
Accepted AnswerUPDATED UPDATE: This is happening in front end editing even on regular items, now, too. Padding and margin settings on various addons and rows work fine, until I click the close button in the bottom left. It appears that there is a temporary file while working in the front end that does not get written out to a production file. I've just run Akeeba Fix Perissions (again) but....
The reason I am doing this is the client attempted this and had the exact same problem, so now I'm working for free.
Superadmin credentials in the hidden field, above.
UPDATED UPDATE TO THIS UPDATE: Might this condition be the cause this: when I enter via the 'Edit Page' directly on the front end, rather than launching the Front End Editor from SPPB? ie, a session ID must be issued from SPPB for this to work properly?
