• Resolved Paul

    (@paultgoodchild)


    With your upgrade to v2.0 you’ve changed the registered plugin file from yoast-seo-acf-content-analysis.php to yoast-acf-analysis.php.

    I hope you’re aware of the impact here that most people wont realise – after you upgrade, WordPress will disable the plugin immediately because it can’t find the previously registered file.

    This could be a huge headache for many and you might want to revert that particular change in a patch before all 20,000 of the sites upgrade to this.

    If anyone uses automatic updates, this will break for them since the plugin will be automatically disabled for them.

    Cheers!

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Contributor Thomas Kr?ftner

    (@kraftner)

    Thanks for mentioning it, this actually was an oversight, you’re right. Although as some time has passed I am not sure if changing this back and causing the same issue again now might not make it even worse.

    I have opened a ticket on github anyway to discuss this further.

    Plugin Contributor Thomas Kr?ftner

    (@kraftner)

    So, this was an annoying mistake, thanks for letting us know.
    Unfortunately some time has passed while we were busy with other things and now we’re in a situation where already ~50% of all users have upgraded so we’d deactivate the plugin for half of the users in any case. Therefore we decided to leave things as they are. We’ll try to do our best to not let something like that happen again.

    For more details on the decision process you can have a look at the issue on github if you want: https://github.com/Yoast/yoast-acf-analysis/issues/75

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘registered plugin file change’ is closed to new replies.