Anthony Somerset

the issue there is minify then disabling minify should work as a workaround in the meantime

i’m having this same error with a different theme, but things seem to be working ok

things seem to be working ok for me right now however my error log is filling – i get the message on wp_cron requests as well….

i looked at a couple of the themes .php files (castiel theme) that were generating the error, they were loading wp-load.php to get the variables to dynamically generate css or js output but obviously those scripts did not call wp_footer for obvious reasons

it looks like the error could be related to the use of w3-total-cache – as the error text is only found in nextgen-gallery/non_pope/class.photocrati_resource_manager.php on lines 121-129

// If W3TC is installed and activated, we can't output the
                        // scripts and manipulate the buffer, so we can only provide a warning
                        if (defined('W3TC')) {
                                define('DONOTCACHEPAGE', TRUE);
                                if (!did_action('wp_footer')) {
                                        error_log("We're sorry, but your theme's page template didn't make a call to wp_footer(), which is required by NextGEN Gallery. Please add this call to your page templates.");
                                }
                                else {
                                        error_log("We're sorry, but your theme's page template didn't make a call to wp_print_footer_scripts(), which is required by NextGEN Gallery. Please add this call to your page templates.");
                                }
                        }

this check is obviously over-zealously and wrongly checking some files

you need to install/configure the various options on the server and within the PHP config (eg install the APC module) before they become usable in W3TC

Its probably a good idea to wrap the functions.php snippet in a check to see if the plugin is activated and available so theres no errors if for some reason the code becomes active on a site that doesnt have the plugin activated

this works well for me as well

can we feature request this in as an optional setting in the plugin itself?

can confirm this fixes for me

I’d be interested in hearing more thats for sure

having tbar not even existing in the plugin would be great – at the moment it still loads the css for is despite me disabling it in wp-admin and the site optimiser in me does not like that one bit

W3TC and Wp-Super-cache are conflicting plugins.

while you might be able to get them to work together, they are written to try and perform the same core function – cache your site, its not advisable to try and run both together – W3TC is a more thorough approach while WP-super-cache only tackles page caching and cdn offloading really

i’m in agreement about this

what if all plugin developers started doing this?

i appreciate you need to advertise your work and this plugin is free, but whats wrong with putting a page within your plugin section for the same info? rather than on every page when logged in (via admin bar)

My guess would be that MaxCDN/NetDNA is not exposing the custom Cnames in the API or W3TC is unable to search them for some reason.

I suspect we will need to either get NetDNA to support that in the API or get Frederick to update W3TC to add a field for MaxCDN/NetDNA temporary URL to use that for the API communications

even though i’m getting zone not found, the cdn is still working correctly, i just dont have purge support for assets within w3tc

You need to really make sure your uploads folder is replicated over your cluster, in linux GlusterFS would be a good candidate to achieve this (or NFS)

in windows, a standard windows share might do the trick for the uploads folder, that way all servers get access to all the same upload files – i’m not sure how that will handle from a performance perspective though for you and your traffic

your trying to download and compile source on windows, of course its going to fail out of the box, you will likely have to manually install sphinx on windows first and use the plugin without letting it isntall sphinx

i’ve only ever see this fail if the htaccess file was messed up in the first place and was missing things like the #BEGIN WORDPRESS headers etc and other rules mixed in.

rule of thumb if you’ve ever got more than the default stuff going on in your htaccess file, is to back it up first and if worse comes to worse, manually install the htaccess rules in the file, the manual rules can be found on the install page of the plugin

how did your file get hosed? was it totally cleaned or what?

you’d get more benefits by first moving to wp-multisite for the installs, the the opcode cache would be more efficient

excellent posting

i put all that code in a custom php widget and it works perfectly

any suggestions on getting post views and post date?

as a follow up to this, cloudfront is GZIP’ing some content or most GZIP’able content anyway automatically with the gzip options turned on in W3TC