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

    (@bmarshall511)

    Sounds like you upgraded from v3. That’s expected as v4 is a complete rewrite and uses a different filename for the core plugin file. Unfortunately, there’s not a way around this, but you won’t encounter this again after updating to v4.

    Thread Starter hommealone

    (@hommealone)

    Thanks very much Ben, much appreciated, and thanks for making this great plugin available!

    Plugin Author Ben Marshall

    (@bmarshall511)

    No problem. I haven’t given up on trying to find a solution though. I know it’s a pain, so hopefully, I can come up with something to make it a smoother upgrade from v3 to v4.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Still getting de-activated upon update’ is closed to new replies.