• Resolved Polaris

    (@namrur)


    Hello,
    I’m using LiteSpeed Cache plugin, but it doesn’t causing me a similar issue with any other plugin, I believe this issue is something that may needed to be solved in your side.

    When having an active snippet and trying to edit the code, the “Save” does not actually saving the edited code. I have found out that any existing saved code will be saved in some scenarios, only if I’ll refresh first the page with the field of the existing snipped first.

    The only thing I can think that may be the cause of the issue, is the fact that Admin has logged out from Admin in some point from by the system, while leaving an existing snippet code opened on screen. Then, after re-loggin, it seems that your plugin does not recognize that the system is logged back, so it quietly refused to save the snippet changes.

    If you can’t avoid this behavior, can you please show a pop-up a warning message, asking the user to refresh the page before trying to edit or save the code which was left opened?

    In addition, your plugin does not show any indication if the saving was dome successfully (neither shows any error in such scenario), so the snippet screen looks like it did updated.

    And last, when there is some warning message of your plugin (in other actions), it appears under the “Save Snippet” button, in an are that is usually non scrollable, and it laced anyway too low and outside the working area on the screen (at least on 14″ laptop).

    It would be great if you could move the saving buttons to the top sidebar, show a “Successful Saving” indication on screen, and show the error messages at side bar underneath the save buttons?

    Last, it would be great if you can use only one saving button (instead of 2 currently, which causes some confusion during work and many updates), and keep one simple “Save” (and than “Update”) button, and the snippet been active or not, would be left to set only buy the existing Toggle.

    Thank you!

Viewing 1 replies (of 1 total)
  • Plugin Contributor Verdi Heinz

    (@ver3)

    Hi, @namrur Thank you for the detailed report and suggestions.

    You’re right: a Save button should save, not merely look confident while doing nothing. Based on the sequence you described, the WordPress session expiring while the editor remained open is more likely to be relevant than LiteSpeed Cache.

    After logging back in, the original editor page may still contain expired authentication data. Even then, Code Snippets should detect the failed save and clearly tell you to refresh or log in again. It should never appear to have saved changes when it has not.

    We’re preparing Code Snippets 3.10.1 for release within the next 24 hours, containing fixes for several confirmed issues introduced in 3.10.0. We have not yet confirmed that this exact session-expiry scenario is covered, so we do not want to promise that before reproducing it. Once 3.10.1 is available, please update and test again. Before testing, copy any unsaved changes somewhere safe. If the issue continues, please let us know:

    • Your WordPress version
    • Your PHP version
    • Your browser and browser version
    • Whether it happens only after being logged out and back in, or also during a fresh session

    Your interface suggestions are also valid: saves need clear success or failure feedback, errors should remain visible on smaller screens, and the relationship between saving and activation should be easier to understand.

    We’ll review those separately from the immediate saving issue. Thanks again for taking the time to explain this so thoroughly. Detailed reports like this save us from having to negotiate with the Save button ourselves.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.