Thanks so much for pointing me in that direction Scott!

I DID see a bunch of fatal memory errors when I upgraded to 3.3, but was able to solve them by placing a copy of my php.ini in /wp-admin. I didn't see the error you found when I loaded the pods setup page. I would love to know how you found it...

After some research, the actual solution is editing "default-constants.php" in /wp-include. For some reason, in 3.3 they have this in the file: (line 18)

// set memory limits
    if ( !defined('WP_MEMORY_LIMIT') ) {
        if( is_multisite() ) {
            define('WP_MEMORY_LIMIT', '64M');
        } else {
            define('WP_MEMORY_LIMIT', '32M');
        }
    }

    if ( ! defined( 'WP_MAX_MEMORY_LIMIT' ) ) {
        define( 'WP_MAX_MEMORY_LIMIT', '256M' );
    }

So, although I was indicating in my site root and /wp-admin that I wanted to allocate 128m, it was resetting that to 32m.

After updating line 23 to:

define('WP_MEMORY_LIMIT',128M');

pods is working properly now and I suspect many other plugins will appreciate the breathing room as well.

Looks like your site is running out of memory. Here's the exact error (file location removed):

Fatal error:  Allowed memory size of 33554432 bytes exhausted (tried to allocate 30720 bytes)
in /path/to/wp-content/plugins/wp-db-backup/wp-db-backup.php on line 1044

When you upgraded your site and plugins to the latest versions, perhaps now your site is using more memory now than before. This is absolutely not a bug with Pods itself, but it would be a great idea to display these types of fatal errors to the user instead of nothing happening at all (visually).

Try contacting your web host, or if you've got the expertise you can dive in and adjust your memory limit per-site using htaccess, PHP (wp-config.php), or however you choose to do.

Send access to uhoh@podsframework.org and I'll see what I can find out for you.