WP Super Cache & Ninja Forms

According to Ninja Forms support:

“It seems that the reason that these are getting created is due to the submission data being stored as post data, so the caching plugin is trying to precache unneeded post data from Ninja Forms. I would recommend contacting the WP Super Cache team and see if they have any information to help you configure their plugin efficiently to only cache actual posts.”

I left WP-Super cache pre-loading overnight. It ran continuously, churning through nearly 20,00 “posts” and was still going 16 hours later.

Buehler? Anyone?

The preload function never used the rejected strings list but I just added some code to check that list now.

Grab the development version from the download page at https://odd.blog/y/2o (instructions are included) and the preload should work much faster. I’d like to hear if it helped as this will obviously be useful for others too.

Many thanks! After installing the beta I started then pre-load process. It’s clearly still chewing through a lot of posts. It processed 4,000 posts in one hour. Last time it processed 20,000 posts in 16 hours.

For some reason using the beta garbage collection was still enabled even in pre-load mode. Thus the preloaded files were automatically removed, defeating the purpose of the preload.

I uninstalled the beta plugin. Wiped the cache. Then installed it anew. Preloading is still taking vastly too long. 19 hours for what it thinks of as 34300 posts. At least garbage collection is not running, so the cache persists.

99% of that post content is form submission data that should not be retained. I expect that manually pruning the database is the only effective solution.

I was eventually able to eliminate all the custom posts generated by the Ninja Forms plugin. That eliminated 56,000+ posts. Now preloading the entire site takes 10 minutes, which is inline with expectations.

I used the Bulk Delete plugin, which is able to delete custom posts up to 1000 at a time.

Now an XML export of the entire site is 5 MB, vs 60+ MB with all the NF_SUB posts.

What I have not been able to discover is what changed that caused the mess. Not sure if it was NF 3.x, WP update, or something other.