Multisite crash update 2.4

I just tried updating a network site running Pods 2.3.18 and WordPress 3.9 to Pods 2.4 and I received no errors. I can’t think of why the class PodsForm wouldn’t exist. Possibly an interrupted download. Can you try again in a testing environment and see if that works?

Updates to WordPress 3.9.1 and tried the Pods update again. No luck though, Pods 2.4 still breaks my multisite.

Perhaps usefull.

My other modules:
– Addthis Smart Layers
– Blog Copier
– Codepress Admin Columns
– Disable Comments
– Genesis Simple Edits
– Genesis Translations
– Multisite Enhancements
– Responsive Lightbox
– TinyMCE Advanced
– WordPress MU Domain Mapping
– WordPress SEO (Yoast)
– WP Mail SMTP

My theme is build on the Genesis framework.

But I still doubt that this will influence the behaviour of the PodsAPI.

Jory-

Have you tried doing the update with no other plugins active?

Deactivating plugins will break the multisite aswell.
I’ve done a full re-install, and it still breaks.

The 2.3.18 version also has problems with the PodsForm class at the Widget section (after the PodsForm widget is stops loading and I can’t edit any widgets anymore).

Problem with 2.3.18 is fixed, file was somehow not complete.
Tried to update to 2.4 again after this fix. Still the same fatal error.

Is this the same error about the class PodsForm? The only thing that would be causing that is if the file was incomplete. You can use the security plugin WordFence to scan for plugin and theme files that are different from the version in the www.ads-software.com repository. That might be a good test and isn’t a bad practice in general.

I run a little over a dozen multisite networks, all of which have Pods. Never any issues with upgrades. However, of the list of plugins you have, I only use Domain Mapping and SEO (Yoast). I once used Multisite Enhancements, but that plugin caused a lot of issues for me, so I stopped.

If I were debugging this, I would turn off everything that is non-essential, and try that. Although what ya really need to is to copy the site and database to a test instance, so you can really go nuts there (ie turn off all the other plugins).

Allright, found it!

Please comment on what I did since I don’t know wether it will break future updates.

File: init.php (pods root)

Line 135 to 140.

if ( false !== pods_compatibility_check() && !is_network_admin()) {
     $pods_form = pods_form();

     $pods_init = pods_init();
}

I changed this to:

$pods_form = pods_form();
if ( false !== pods_compatibility_check() && !is_network_admin()) {
     $pods_init = pods_init();
}

Oh, and thanks for the tip about WordFence! That helped a lot!

I’m glad to see you got this working. I’m wondering why that conditional would have failed for you. Scott will have to take a look at that.

Thanx Jory, +1 for your patch ??

To be addressed here:

https://github.com/pods-framework/pods/issues/825#issuecomment-56620588

I have got the same crash again with the 2.5.1.2 update.

Changed this:

if ( false !== pods_compatibility_check() ) {
		        $pods_form = pods_form();

		        if ( ! is_network_admin() ) {
			    $pods_init = pods_init();
		        }

	        }

into this:

if ( false !== pods_compatibility_check() ) {
		        $pods_form = pods_form();

			$pods_init = pods_init();
		        /*if ( ! is_network_admin() ) {
		        }*/

	        }

And it was resolved again. Does anyone know why this happens?

New issue:
https://github.com/pods-framework/pods/issues/2803