Unable to create or import new pod in Multisite

[Pezzab]

Update: perhaps not a Pods specific issue after all. It looks like the problem I am having is related to the APC Object Cache Backend plugin - when this is disabled Pods seems to behave itself once more. It seems that there can be problems with this plugin where items in admin are being cached causing confusing behaviour and various issues.

Apparently it is possible to stop APC from caching admin items but I'm running Nginx and can only find Apache related solutions.

I'm working on a WP site on a Multisite install.

I already imported one Pod without a hitch. If I try to create a new pod on the site or import it via Migrate packages I get:

"Pod using already exists, you can not reuse an object across multiple pods"

Subsequent attempts to add the pod give me:

"Pod podname already exists" but the pod does not appear in the Edit pods list. Clearing cache has no effect.

My WP set up:

WordPress Version: 3.8

PHP Version: 5.3.2-1ubuntu4.7ppa5~lucid1

MySQL Version: 5.1.72

Server Software: nginx/1.4.1

Your User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:26.0) Gecko/20100101 Firefox/26.0

Session Save Path: /var/lib/php5

Session Save Path Exists: Yes

Session Save Path Writeable: Yes

Session Max Lifetime: 1440

WPDB Prefix: wp15

WP Multisite Mode: Yes

WP Memory Limit: 64M

Pods Network-Wide Activated: Yes

Pods Install Location: /mysite.com/public/wp-content/plugins/pods/

Pods Tableless Mode Activated: No

Pods Light Mode Activated: No

Currently Active Plugins:

Akismet: 2.5.9
Batcache Manager: 1.2
Pods - Custom Content Types and Fields: 2.3.18
WordPress MU Domain Mapping: 0.5.4.3 

[Pezzab]

Just an update - I network deactivated all plugins then tried both Clean up and Reset options. Neither one has any effect - the pod that I had in place before comes back again (zombie like) while I still get the errors mentioned above while attempting to add new pods.

I don't get any additional messages with debug switched on.

[Pezzab]

Oh joy, it seems that Batcache is the issue. I disabled it (including renaming object-cache.php and advanced-cache.php to make sure it was completely deactivated) and I was able to start adding new pods, but.

Once I had disabled it the original Pod no longer appeared but my new Pod was there ready to edit. It might be that having Domain Mapping switched off might affect it but so far reactivating doesn't seem to make any difference.

Update: just to be thorough: creating a pod gives me a "Pod not found" error. It also turns out that even when I can see the original pod in the edit pods list that if I go to edit it I also get "Pod not found" - but I still seem to be able to modify the content of that pod.

Any ideas how or why Batcache might affect Pods?

For info, a similar issue with ACF:

http://old.support.advancedcustomfields.com/discussion/comment/10391

I've just ditched WP Super Cache in favour of BC because it seems so much more stable on a multisite set up - I really don't want to have to go back to fire fighting caching issues with WPSC if I can help it.

Just when I thought my ideal set up was within my grasp :)

[sc0ttkclark]

Thanks for the info, will look at it as part of 3.0

[Pezzab]

Cheers - apologies for what turned out to be a garbled report. The culprit seems to be object-cache.php, removing this from the picture gets everything working again. Suffice to say things seem to get pretty messed up as long as it is in wp-content.

At some point I'll try this out on a single site install and report back.

Obvs I shouldn't rule out that there could be issues with my server set up (apc.ini etc) that might be causing this - I'm a Batcache newbie and realise this is generally the preserve of more experienced devs.

[Pezzab]

Just an update - I've set up Batcache on my single install blog (same server as the Multisite above).

Pods seems to work fine in this context with Batcache and APC Object Cache Backend plugins both active.

[Pezzab]

Update re multisite: If I install the apc.php dashboard and go to User Cache Entries and/or Per-Directory Entries and delete user or opcode cache then newly created Pods do appear in Pods Admin.

The issue seems to be new Pods not appearing on the Pods admin list so caching is affecting display rather than creation. Similarly if I add new fields to existing pods the count doesn't go up in the Pods admin list either (or not until I've deleted the cache as described above).