WordPress.org

Ready to get started?Download WordPress

Forums

Plugin Organizer
[resolved] Update breaks on MS with no workaround (34 posts)

  1. kisshomaru
    Member
    Posted 1 year ago #

    See the other thread, however i can't workaround it. My steps were: put 3.5.2 update first. Tried deleting the plugin entirely, re-installing it, re-updating 3.5.2, as soon as the plugin is enabled for multisite the front end stops with error 500.
    Backend works and I can deactivate it to return site to normal.
    Please fix.

    http://wordpress.org/extend/plugins/plugin-organizer/

  2. kisshomaru
    Member
    Posted 1 year ago #

    Option in settings to: "Selective Plugin Loading: Disable" will return site to normal on 3.5.2, but it does remove the proper functionality of the PO.
    I believe there is a bug in the MU plugin for 3.5.2.

  3. jasonpaulweber? You've already posted a thread about this topic.

    http://wordpress.org/support/topic/great-plugin-update-will-break-site-read-this-first?replies=1

    Please stop posting all of your replies to these topics, you've already made your point. Posting to all the threads like that is considered spamming.

    Second? Do not solicit people to contact you off of these forums again here. As you already know that is discouraged.

    Edit: Also? All the old versions are available here.

    http://wordpress.org/plugins/plugin-organizer/developers/

    No one should obtain an old version from off of these forums.

  4. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    Go to the settings page, Settings->Plugin Organizer in the admin menu, and under Manage MU plugin file at the bottom check Delete and then submit. After that is done and successful click Move and then Submit. Let me know if that caused any errors or fixed anything.

  5. kisshomaru
    Member
    Posted 1 year ago #

    I am not jason..somth.
    Reading the other threads, I saw the need to post this for MS, as it seems there were some workarounds, they are not working for me.

    That said, Jeff, thanks for the response, I saw the update as well and tried it. I also tried deleting the MU and everything else and re-installing. I had just a few simple rules so it was not too much trouble for me. So now, as soon as I hit activate (network) plugin (so this is on a fresh install with no previous rules left), all sites are down with error 500.
    I should also mention that I have an ssl site network. Everything is ssl.

  6. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    I just went and activated plugin organizer on a multi site install with 9 different sites on it. I was able to network activate the plugin with no issues. WP 3.5.1

  7. kisshomaru
    Member
    Posted 1 year ago #

    Tried again installing the 3.0.6 this time, still from scratch, on my 3.5.2. Same 500 error...

    Update: Went back to 2.6.3 that works with 3.5.2 and seems stable. So what is so wrong with the MU file that gets into 500 errors?
    Looking at other threads, I am not the only one doing this.
    Again, my configuration is:
    WP 3.5.2, MS install in a subfolder and https allover.

  8. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    What is the error that you are getting? You should see something in your php error log.

  9. kisshomaru
    Member
    Posted 1 year ago #

    As soon as I enable Selective plugin loading in settings on 3.0.6 version, the following php err is logged when trying to access the site and a 500 is thrown in browser:
    [29-Jun-2013 05:55:07 UTC] PHP Fatal error: Call to undefined function wp_get_current_user() in /home/ddd/public_html/aaa/wp-includes/capabilities.php on line 1281

    Line 1281 is this: $current_user = wp_get_current_user();
    from function:
    /**
    * Whether current user has capability or role.
    *
    * @since 2.0.0
    *
    * @param string $capability Capability or role name.
    * @return bool
    */
    function current_user_can( $capability ) {
    $current_user = wp_get_current_user();

    if ( empty( $current_user ) )
    return false;

    $args = array_slice( func_get_args(), 1 );
    $args = array_merge( array( $capability ), $args );

    return call_user_func_array( array( $current_user, 'has_cap' ), $args );
    }

  10. kisshomaru
    Member
    Posted 1 year ago #

    Version 3.0.7 broke both back and front end this time (used to only break front end 3.0 to 3.0.6). Had to manually delete it.

    The error is still related to wp_get_current_user it seems.

    [02-Jul-2013 16:35:57 UTC] PHP Fatal error: Call to undefined function wp_get_current_user() in /home/aaa/public_html/aaa/wp-includes/post.php on line 2121
    Line 2121 is the $user = wp_get_current_user(); from

    function wp_count_posts( $type = 'post', $perm = '' ) {
    	global $wpdb;
    
    	$user = wp_get_current_user();
  11. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    Try version 3.0.8. I was making a call to wp_count_posts to count the number of plugin groups and create a default group if it didn't exist. I removed that check in the new version.

  12. kisshomaru
    Member
    Posted 1 year ago #

    I was able to install and activate version 3.0.8.
    However, we are now back to the original issue: when activating selective loading, the front end gives 500 error. The following is logged again as before:
    [02-Jul-2013 18:07:10 UTC] PHP Fatal error: Call to undefined function wp_get_current_user() in /home/aaa/public_html/aaa/wp-includes/capabilities.php on line 1281

  13. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    And it gives you this error over and over again if you keep going to the page right?

  14. kisshomaru
    Member
    Posted 1 year ago #

    Yes, it used to. Now I see though, after I tried again with loading a different page it started to give another one:
    [02-Jul-2013 19:20:35 UTC] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 523800 bytes) in /home/aaa/public_html/aaa/wp-includes/query.php on line 1922

  15. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    Try increasing the allowed memory while the upgrade is performed. You should allocate more than 128mb of memory for wordpress 3.0+.

  16. kisshomaru
    Member
    Posted 1 year ago #

    Fair enough:
    This is the latest 3.0.9, still installed from scratch:

    [04-Jul-2013 06:07:12 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 523800 bytes) in /home/aaa/public_html/aaa/wp-includes/plugin.php on line 763

    Thanks for working on this.

    PS. Looking at the other opened threads on more or less the same issue, may I suggest, that if different type of errors are in different places across multiple installs, it might be a memory leak or a specific bad loop on 3.5.2 specifically.

  17. kisshomaru
    Member
    Posted 1 year ago #

    Same issue with 3.0.10 and WP 3.5.2:
    [08-Jul-2013 15:19:06 UTC] PHP Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 523800 bytes) in /home/aaa/public_html/aaa/wp-includes/plugin.php on line 763

  18. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    That is strange. No one else is reporting this issue. Do you have any other plugins installed? Are you running the default theme?

  19. kisshomaru
    Member
    Posted 1 year ago #

    I do have a bunch of plugins installed, yes. I am running Suffusion theme on the main site.
    I did try to deactivate half of the plugins and retried, but with no luck.
    I noticed there are other unsolved support threads with the 500 issue, and my guess is that it is the same problem.
    I will try some more things, I didn't had the time to disable everything yet and retry, however, 2.6.3 was/is working with my configuration, so not sure what has happened, the issue seems to be in the MU file, but where/when not sure...

  20. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    Did you manually delete the entire plugin? Including the file in the mu-plugins folder and then reinstall it from wordpress.org or are you just doing the auto update? 95% of the errors I fix for people are because they have an old version of the mu plugin still installed.

  21. kisshomaru
    Member
    Posted 1 year ago #

    Yes Jeff, I always verify that everything is gone manually, however, I'm not sure that the old 2.6.3 database stuff is all gone since I remember at the time that I did an upgrade (which started this issue). Since then I have tried uninstalling manually, then only installing 2.6.3 and uninstalling it before I try any 3.0 installs.

  22. kisshomaru
    Member
    Posted 1 year ago #

    Hi Jeff,

    I might have found the issue. I have one plugin called BuddyPress Docs that seems to conflict with the PO. The plugin can't be used by itself and requires BuddyPress installed.
    What I did was to deactivate all plugins, enabled PO first, worked, then started enabling one by one. After seeing that the BP Docs was the conflicting one, I continued activating the rest. That one seems to be the only one conflicting. Deactivating either that or PO will have the site working again.
    Can you please look into it and see why this is happening? Those are totally different plugins with different functions, so it is very strange. Also keep in mind that it is working with the old 2.6.3.

  23. Jeff Sterup
    Member
    Plugin Author

    Posted 1 year ago #

    I don't currently have a test site where I can install the docs plugin since our data center is having cooling issues and the dev servers are shut down. When I get a chance I will look into the conflict to see if it is an issue that my plugin is causing or the docs plugin.

  24. kisshomaru
    Member
    Posted 1 year ago #

    Thanks Jeff, I'll try to backup the docs manually and re-install that plugin as well. Maybe an update on that one was at fault. I'll keep you updated, but please look into it when you can as it is working with prior to 3.0, so something changed in PO as well on this.

  25. kisshomaru
    Member
    Posted 11 months ago #

    This is still an issue. Conflict with the BuddyPress Docs plugin. Enabling selective plugin in PO will break site with error 500.
    I currently disabled BuddyPress Docs to make sure PO has no other major issues in tests, but this is a problem.

  26. Jeff Sterup
    Member
    Plugin Author

    Posted 11 months ago #

    Is this issue also fixed now that you can change the load order of the docs plugin?

  27. kisshomaru
    Member
    Posted 11 months ago #

    I'm working on this. It seems it didn't lock down when activating buddypress docs. However, as soon as I did that, something else happened:
    The section for Custom Post Type Support in settings no longer displayed anything, then, I got this strange php errors (and then more when I disabled PO):

    [13-Aug-2013 18:32:01 UTC] WordPress database error Table 'wp_Wp9_PO_post_plugins' doesn't exist for query DELETE FROM wp_Wp9_PO_post_plugins WHERE post_id = 1671 made by include('wp-admin/edit-form-advanced.php'), wp_delete_post_revision, wp_delete_post, do_action('delete_post'), call_user_func_array, PluginOrganizer->delete_plugin_lists
    [13-Aug-2013 18:34:07 UTC] PHP Warning:  array_diff() [0function.array-diff0]: Argument #1 is not an array in /home/z/public_html/z/wp-content/plugins/plugin-organizer/lib/PluginOrganizer.class.php on line 938
    [13-Aug-2013 18:37:42 UTC] WordPress database error Table 'wp_Wp9_PO_post_plugins' doesn't exist for query DELETE FROM wp_Wp9_PO_post_plugins WHERE post_id = 1670 made by wp_delete_post, wp_delete_post_revision, wp_delete_post, do_action('delete_post'), call_user_func_array, PluginOrganizer->delete_plugin_lists
    [13-Aug-2013 18:37:42 UTC] WordPress database error Table 'wp_Wp9_PO_post_plugins' doesn't exist for query DELETE FROM wp_Wp9_PO_post_plugins WHERE post_id = 1672 made by wp_delete_post, wp_delete_post_revision, wp_delete_post, do_action('delete_post'), call_user_func_array, PluginOrganizer->delete_plugin_lists
    [13-Aug-2013 18:37:42 UTC] WordPress database error Table 'wp_Wp9_PO_post_plugins' doesn't exist for query DELETE FROM wp_Wp9_PO_post_plugins WHERE post_id = 1669 made by wp_delete_post, do_action('delete_post'), call_user_func_array, PluginOrganizer->delete_plugin_lists
    [13-Aug-2013 18:42:42 UTC] PHP Warning:  Missing argument 2 for wpdb::prepare(), called in /home/z/public_html/z/wp-content/plugins/plugin-organizer/lib/PluginOrganizer.class.php on line 1228 and defined in /home/z/public_html/z/wp-includes/wp-db.php on line 992
    [13-Aug-2013 18:42:42 UTC] WordPress database error Table 'wp_blogs' doesn't exist for query SELECT blog_id FROM wp_blogs made by require('wp-admin/plugins.php'), deactivate_plugins, do_action('deactivated_plugin'), call_user_func_array, PluginOrganizer->deactivated_plugin

    Now I'm deleting PO and BPDOCS and putting everything back to see what is going on.

  28. kisshomaru
    Member
    Posted 11 months ago #

    I am unable to start from scratch. Deleting the PO with or without the preserve settings will leave everything in the database (so when I add it back everything is still there, hence, I believe, the errors for me).
    How can I safely purge the database from all PO related entries before reinstall?

  29. kisshomaru
    Member
    Posted 11 months ago #

    OK, first bug that I found is in the lib\PluginOrganizer.class.php at line 1228:
    $sites = $wpdb->get_results( $wpdb->prepare( "SELECT blog_id FROM wp_blogs" ) );
    The problem is that wp_ does not exist for me. The database prefix should be queried from wp or supplied separately by user.
    (One can and most should change the prefix). So yes, I have different prefix - same for all tables.
    I quick search through your source files for wp_ shows this as a hardcoded value in more than one place.

  30. Jeff Sterup
    Member
    Plugin Author

    Posted 11 months ago #

    DOH!!! I missed that. Apparently my mental note to change it got erased. It shouldn't be hard coded anywhere else. All the other queries (which are only for the old tables) should be using the prefix variable. If you see it somewhere else please let me know where so I can remove it. I'll be releasing a patch in a few minutes.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.