{"id":48,"date":"2010-09-07T11:05:33","date_gmt":"2010-09-07T17:05:33","guid":{"rendered":"http:\/\/www.p14nd4.com\/blog\/?p=48"},"modified":"2025-11-17T13:57:30","modified_gmt":"2025-11-17T19:57:30","slug":"wordpress-vbulletin-bridge-vbridge-disabling-wp-super-cache","status":"publish","type":"post","link":"https:\/\/www.p14nd4.com\/blog\/2010\/09\/07\/wordpress-vbulletin-bridge-vbridge-disabling-wp-super-cache\/","title":{"rendered":"WordPress vBulletin Bridge (vbridge) disabling WP Super Cache"},"content":{"rendered":"\n

As mentioned in my previous post<\/a>, I’ve been playing with WordPress<\/a>, vBulletin<\/a>, vBridge<\/a>, and some other stuff as part of my work for my other site, TechwareLabs<\/a>. One of the other plugins I utilize on that site is WP Super Cache<\/a>, which I discovered was an easier way to accomplish basic static caching instead of trying to jump into the deep end of learning mod_cache, memcache, and other sorts of fancy things for an actual elegant solution<\/a>.<\/p>\n\n\n\n

Unfortunately, these are complicated systems, and vbridge in particular seems slightly less polished than some more widely utilized components (though, in fairness, its user base is considerably smaller than most wordpress plugins).<\/p>\n\n\n\n\n\n\n\n

It was actually in the course of trying to track down the issue of why the TechBargains Hot Deals Widget<\/q> is such an obnoxious memory hog (full disclosure: it may just be the final straw that’s breaking the camel’s back, but it does legitimately seem to be a pretty damn big piece straw) that I discovered WP SuperCache wasn’t doing its thing any more. After a little initial troubleshooting of my own, I acted on a hunch, and googled wordpress vbridge supercache, and was fortunate enough to immediately find a pertinent result<\/a>.<\/p>\n\n\n\n

As nasium<\/a> was kind enough to share, the Complete Vbridge Plugin<\/q> apparently adds a variable ajax<\/code> to the PHP $_POST<\/code> variable, which WP Supercache’s criteria flags as reason not to cache. I wasn’t entirely convinced his solution of entirely removing these lines from wp-content\/plugins\/wp-super-cache\/wp-cache-phase2.php<\/code> was appropriate:<\/p>\n\n\n\n

PHP<\/span>