[resolved] Should I deactivate the plugin before upgrading to the next WP 3.8? (10 posts)

  1. Marcelo Pedra
    Posted 1 year ago #

    Hello guys, I'm aware of all the buzz around MP6 being shipped built-in the coming versions of WP. Congratulations by the way!

    I just wanted to ask if the plugin will be automatically deactivated and deleted when WP is updated to 3.8, or should I do that manually?

    Any concerns? any plans?
    Thank you


  2. Shapeshifter 3
    Posted 1 year ago #

    I have the same question with a followup:

    Will the components (or Bits & Pieces) be implemented into the Core incrementally, or all at once?

    If incrementally, should current users of the plugin disable it right now during that process.

    Is there any ETA on when the Bits & Pieces of MP6 will start to be added to the 3.8 alpha core?

  3. Shapeshifter 3
    Posted 1 year ago #

    I just deactivated the MP6 Plugin and deleted it from my server. Core developers are in the process right now of integrating MP6 into the core.

    Don't want software conflicts between the Core and a plugin.

  4. Marcelo Pedra
    Posted 1 year ago #

    I bet they will automagically deal with this. When you upgrade WP to 3.8, it should have the routines built-in to detect MP6 plugin, deactivate it, uninstall it, and then proceed with WP upgrade.
    Sounds logic, huh?

  5. Shapeshifter 3
    Posted 1 year ago #

    I agree !

  6. TechKang
    Posted 1 year ago #

    No worries. The upgrade process (see wp-admin/includes/upgrade.php) will "Deactivate MP6 on update to 3.8." See github.com/WordPress/WordPress/commit/8b8c8e96e7f3cb67f0c8ae18541a7a1b6fe3a96b

    [sig moderated as per the Forum Rules]

  7. Marcelo Pedra
    Posted 1 year ago #

    Great, but why only deactivate it if they could uninstall it as well? Or can't they?

  8. TechKang
    Posted 1 year ago #

    Perhaps they would like to give you more control and avoid problems caused by deleting the MP6 plugin, such as losing the modification to the php/css/... files of MP6 by your own.

  9. Marcelo Pedra
    Posted 1 year ago #

    Got it. Ok to me. I'll delete it then.

  10. hobbsy
    Posted 1 year ago #

    I just updated a blog from 3.7.1 (with MP6 plugin v2.2.1 installed) to WP 3.8

    Just a couple of notes on the behaviour:

    The Core upgrade went smoothly.
    On returning to view the plugins list afterwards, MP6 is still there but has now been disabled. WP tells me that there's an update (v2.3 from v2.2.1) ready for MP6.

    As it was just a test blog (that doesn't matter if it breaks) I clicked on upgrade plugin. I'm not sure if my CHMOD permissions were wrong but I got this message (and then the plugin disappeared from my plugins list)

    Update Plugin
    Downloading update from https://downloads.wordpress.org/plugin/mp6.zip…
    Unpacking the update…
    Installing the latest version…
    Removing the old version of the plugin…
    Could not create directory. /public_html/wp-content/plugins/mp6/
    Plugin update failed.

    the /mp6/ folder still exists in the plugins folder but it is no longer listed within the WP dashboard plugins list (of course MP6 is now part of WP3.8 so I guess this was to be expected)

    I will now just manually delete the /mp6/ folder via FTP

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • MP6
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic