You need to be logged in to post in the forum - Log In

An active JCE Pro Subscription is required to post in the forum - Buy a Subscription

Support is currently Offline

Official support hours
Monday to Friday
09:00 - 17:00 Europe/London (BST)

Please create a new Ticket and we will get back to you as soon as we can.

#105221 JCE version 2.8.17 problem with save

Posted in ‘Editor’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Latest post by pnussbau on Monday, 07 September 2020 21:11 BST

pnussbau
I install the new version and run into a bug inside php-code. After save he change the code "->" ">".
Becaus the security an this page I post the example as attachment. Sorry I can't upload an document, becaus all possible types are unsupported....

Please have a look at the last line.

In version 2.8.16 ist the same behaviour and in version 2.8.14 it works fine.

So I made a downgrade to version 2.8.14 until you have a solution to this bug.

Best regards
Peter Nussbaumer

Ryan
If you click the Toggle Editor button (the "power" button in the top left above the editor toolbar) before saving, is the PHP code displaying correctly?

If you then save, without switching the editor back on, is the PHP code changed?

Ryan Demmer

Lead Developer / CEO / CTO

Just because you're not paranoid doesn't mean everybody isn't out to get you.

pnussbau
Hi Ryan
I try this "power" Button. If I click on then the code will be changed to the wrong result. Als the same behaviour as the "Save"-Button

Ryan
I'm not seeing this in any of my tests. Please send me a login - https://www.joomlacontenteditor.net/contact/site-login

Ryan Demmer

Lead Developer / CEO / CTO

Just because you're not paranoid doesn't mean everybody isn't out to get you.

pnussbau
I send you the login-data
Best regards
Peter

Ryan
I install the new version and run into a bug inside php-code. After save he change the code "->" ">".


This only occurs when saving the content while in the Code tab, so this can be fixed by setting the Validate Content option in Editor Profiles -> Plugin Parameters -> Source Code to No.

I have done this on your site.

Ryan Demmer

Lead Developer / CEO / CTO

Just because you're not paranoid doesn't mean everybody isn't out to get you.

pnussbau
Many Thanks for you assistance and have a good day
Bedst regards
Peter