Hi Stefan,
Thank you for reaching out and sharing these details.
We haven’t been able to replicate this issue on our end yet, as newly created PHP snippets are saving and displaying correctly in our test environment.
To help us investigate this potential regression and narrow down what might be happening, could you provide a few extra details?
- Snippet Details: Does this happen with all PHP snippets or only specific types (e.g., PHP snippet, Universal, Shortcode)? Also, are you saving specific code or special characters?
- Plugin Conflict: If possible, try temporarily deactivating other plugins to see if a conflict with another plugin or page builder (or a caching/optimization plugin) is clearing the editor. To do this safely, please follow the steps suggested here https://docs.themeisle.com/wordpress/theme-doesnt-work-as-expected-troubleshooting-guide
- Environment Info: What PHP version and WordPress version are you currently running?
- Browser Console: When the code disappears after opening the editor, do you see any JavaScript errors in your browser console (F12 > Console tab)?
Once we have this information, we’ll be in a much better position to pinpoint the cause and work on a fix if a bug was introduced.
Thank you for your patience and help!
Best regards,
Hi,
thank you for your reply.
We can provide some additional information based on what we observed.
The issue does not seem to affect all newly created PHP snippets. We have created simple PHP snippets after the update and they can be saved and reopened normally.
We encountered the problem while creating some new, more structured PHP snippets that also included JavaScript and <script> blocks.
In those cases, the snippet could initially be created and saved. However, when reopening it, the code appeared correctly in the editor for a moment and then disappeared, leaving the editor empty.
Existing snippets created before the latest update, including complex snippets of this type, continue to work normally.
We also tested a very simple new PHP snippet containing a basic <script> block and that worked correctly, so the presence of JavaScript alone does not seem to be enough to trigger the issue.
The behaviour therefore appears to occur only under certain conditions with newly created snippets, which we have not yet been able to isolate.
Since we had been using this type of PHP/JavaScript snippet successfully before the latest update, we wanted to report the behaviour in case there has been a change in the editor, validation or sanitization process that could explain it.
Thank you for investigating.
Hi,
just a quick update following our previous report.
Today we worked extensively with Woody Snippets for several hours, creating, editing, saving and reopening multiple PHP snippets, including fairly structured ones.
The issue we reported yesterday did not occur at all today. All snippets were saved and reopened normally, and the editor remained stable throughout the entire session.
We have not made any specific change on our side intended to solve the issue, so we cannot explain why the problem occurred yesterday and has not appeared again today.
We thought this additional information could be useful for your investigation.
We will let you know if the issue occurs again.
Hi Stefan,
Thank you for your update! It really helps.
As, for the moment, we are not able to replicate the issue, and no other similar reports have been filed, so we can wait for a few days, to see if the issue still appears on your site or not.
Kind regards!
