Support » Plugin: PHP code snippets (Insert PHP) » Snippet reactivated on edit – Bug

  • On editing an inactive snippet the snippet is then re-activated.

    The activation state should be honoured.

    Editing a snippet should not change the activation status.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author webcraftic

    (@webcraftic)

    Hi,

    I’m sorry, I needed to update other plugins. Now I’m back to you and can help you.

    Unfortunately, some users believe that their snippets don’t work, because forgot to activate a snippet.

    This problem in usability creates a lot of support tickets. If you know a more beautiful solution, I will definitely think about it.

    Best redards, Alex

    snaphappyme

    (@snaphappyme)

    Hi Alex,

    What about checking active status on save?

    [-] If never saved (activate=null), then save and activate
    [-] if inactive (has been saved before but is now inactive), then ask “Activate on save?”

    It’s just as bad if/not worse reactivating a code segment that has been marked “deactivate” as the odds suggest the code was turned off for a good reason….

    Anyhow, give my idea some thought and see if we all get what we want 😉

    snaphappyme

    (@snaphappyme)

    BTW,

    If the workflow remains unchanged please put big alert message near [save] that says “Warning: Saving will reactive the code segment”

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.