feature req: don't allow to disable PO on backend

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Jeff Sterup

    (@foomagoo)

    What version of the plugin are you running? Can you explain the problem?

    Thread Starter wp.Man

    (@wpman-1)

    PO 2.9.5

    no problem, i just happened to globally disable the PO JS and i had the disable on admin/backend enabled also, so when i logged off and back on… see where this is going ??

    just thought it might be a good idea to not allow PO JS to be disabled from within PO – hehe

    Plugin Author Jeff Sterup

    (@foomagoo)

    No I don’t see where this is going. Can you please explain what you are saying. It is possible for you to disable PO globally but it should have no effect on the admin. Can you please explain what the problem is. I don’t have a problem when I disable it globally.

    Thread Starter wp.Man

    (@wpman-1)

    if one disables the PO JS globally, and selects the option to propagate the global disable options to the back-end (admin), and then logs out and back in, how will they be able to change any settings when PO is no longer available?

    Plugin Author Jeff Sterup

    (@foomagoo)

    It should be available. Are you not seeing the menu option on the admin? I have no issues on any of the sites I run this plugin on.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘feature req: don't allow to disable PO on backend’ is closed to new replies.