Kimberly

What do you have inside the textbox under: Performance > Minify > HTML & XML –> Ignored comment stems ?

Is it empty? If so you might want to just add some non-existent name in the box. My guess is this should stop the warnings.

Cheers
Kimberly

If these are a finite # of urls you could simply add mod_rewrite .htaccess [R=302] (or R=301) redirect rules there instead and save yourself a whole lot of time — and would be much faster and dramatically less resource intensive on your site.

Although i can give u an htaccess solution server headers give the browser permission to do things, but don’t actually require the browser to do them. (ex: the FF UI gives the user fine-tuning choices– Once per session, Every time I view the page, When the page is out of date (default), or Never.) Also, a “no-cache” header from the server will prevent caching of the new version, but will not flush the old version out of the browser cache. The solution has to happen on the client side and involves useless-but-unique query strings to the URL

jquery to modify the 768 rules after doc ready/bind would be another ez option

curious..why dont u just include your own css file via wp_enqueue_script(..) with a low priority (e.g. 99) which will ensure it gets included after the bootstrap and in this file u writing the exact same conditions for the 768 @media queries, same selector, same property but with default values that equate to what they were pre 768 (to get the values back to a normal state). And then below this officially add your @media queries for 850.

Alternatively, you could dequeue the bootstrap script entirely and enqueue your own css making sure it has an exact copy of cotents of the bootstrap css but with modified @media queries for 850 instead of 768.

In your functions.php file insert (dont forget to replace mobile.gadgetmagik.com with your actual mobile page):

$useragent=$_SERVER[‘HTTP_USER_AGENT’];
if(preg_match(‘/(android|bb\d+|meego).+mobile|avantgo|bada\/|blackberry|blazer|compal|elaine|fennec|hiptop|iemobile|ip(hone|od)|iris|kindle|lge |maemo|midp|mmp|mobile.+firefox|netfront|opera m(ob|in)i|palm( os)?|phone|p(ixi|re)\/|plucker|pocket|psp|series(4|6)0|symbian|treo|up\.(browser|link)|vodafone|wap|windows ce|xda|xiino/i’,$useragent)||preg_match(‘/1207|6310|6590|3gso|4thp|50[1-6]i|770s|802s|a wa|abac|ac(er|oo|s\-)|ai(ko|rn)|al(av|ca|co)|amoi|an(ex|ny|yw)|aptu|ar(ch|go)|as(te|us)|attw|au(di|\-m|r |s )|avan|be(ck|ll|nq)|bi(lb|rd)|bl(ac|az)|br(e|v)w|bumb|bw\-(n|u)|c55\/|capi|ccwa|cdm\-|cell|chtm|cldc|cmd\-|co(mp|nd)|craw|da(it|ll|ng)|dbte|dc\-s|devi|dica|dmob|do(c|p)o|ds(12|\-d)|el(49|ai)|em(l2|ul)|er(ic|k0)|esl8|ez([4-7]0|os|wa|ze)|fetc|fly(\-|_)|g1 u|g560|gene|gf\-5|g\-mo|go(\.w|od)|gr(ad|un)|haie|hcit|hd\-(m|p|t)|hei\-|hi(pt|ta)|hp( i|ip)|hs\-c|ht(c(\-| |_|a|g|p|s|t)|tp)|hu(aw|tc)|i\-(20|go|ma)|i230|iac( |\-|\/)|ibro|idea|ig01|ikom|im1k|inno|ipaq|iris|ja(t|v)a|jbro|jemu|jigs|kddi|keji|kgt( |\/)|klon|kpt |kwc\-|kyo(c|k)|le(no|xi)|lg( g|\/(k|l|u)|50|54|\-[a-w])|libw|lynx|m1\-w|m3ga|m50\/|ma(te|ui|xo)|mc(01|21|ca)|m\-cr|me(rc|ri)|mi(o8|oa|ts)|mmef|mo(01|02|bi|de|do|t(\-| |o|v)|zz)|mt(50|p1|v )|mwbp|mywa|n10[0-2]|n20[2-3]|n30(0|2)|n50(0|2|5)|n7(0(0|1)|10)|ne((c|m)\-|on|tf|wf|wg|wt)|nok(6|i)|nzph|o2im|op(ti|wv)|oran|owg1|p800|pan(a|d|t)|pdxg|pg(13|\-([1-8]|c))|phil|pire|pl(ay|uc)|pn\-2|po(ck|rt|se)|prox|psio|pt\-g|qa\-a|qc(07|12|21|32|60|\-[2-7]|i\-)|qtek|r380|r600|raks|rim9|ro(ve|zo)|s55\/|sa(ge|ma|mm|ms|ny|va)|sc(01|h\-|oo|p\-)|sdk\/|se(c(\-|0|1)|47|mc|nd|ri)|sgh\-|shar|sie(\-|m)|sk\-0|sl(45|id)|sm(al|ar|b3|it|t5)|so(ft|ny)|sp(01|h\-|v\-|v )|sy(01|mb)|t2(18|50)|t6(00|10|18)|ta(gt|lk)|tcl\-|tdg\-|tel(i|m)|tim\-|t\-mo|to(pl|sh)|ts(70|m\-|m3|m5)|tx\-9|up(\.b|g1|si)|utst|v400|v750|veri|vi(rg|te)|vk(40|5[0-3]|\-v)|vm40|voda|vulc|vx(52|53|60|61|70|80|81|83|85|98)|w3c(\-| )|webc|whit|wi(g |nc|nw)|wmlb|wonu|x700|yas\-|your|zeto|zte\-/i’,substr($useragent,0,4)))
header(‘Location: https://mobile.gadgetmagik.com’);

Cheers
Kimberly

Looks fine to me.

In W3tc is minify enabled? Try disabling (uncheck it within the Performance > General Settings area). I am curious. From ur snapshot (thanks) it seems at least some of your css is there and others it is not (assuming u havent inlined any of it).

Do u have firebug? Love to know if under the console area it has any javascript errors.

In w3tc make sure both the minify and page cache are unchecked and let me know if your site appearance goes back to normal. From there were can work out whats going on.

Do u have a domain i can check out? Can you log file path and order of each css and js file u have? From there once we proceed to enable minify/page cache we can know the proper order when things go bad.

Ah you had a maintenance mode plugin too? Curious…do you see a: .maintenance file in your root folder (the folder where wp-settings.php file is located)? Note the prefixed “.” which indicates its a hidden file so depending on your environment this file may not display by default. You will need to remove this file to prevent maintenance mode from activating. This file is triggered by wordpress and simply tells wordpress when to set your site (the time) in maintenance mode. Also if you see in your wp-content folder a maintenance.php file that is what is generating the actual html page during maintenance. However, without the .maintenance file this php file shouldn’t be triggered so you don’t need to delete it.

As for your minified files popping up again. So to be clear when using a file manager you are seeing a new folder in /wp-content/cache/minify/000000/<your domain here> created (even when you delete the cache folder) and inside you see several minified files regenerated (even after deletion)?

Secondly, on your website homepage do you see one of these minified files in the source? meaning the homepage is actually using this newly generated minified file?

And thirdly, i know you said it was disabled but just to be sure, under Performance > General Settings > Minify — the Minify checkbox is unchecked. Correct?

I’m wondering then if in your wp-cron (called “cron” in your dbase under the wp_options table)is still triggering the w3tc_minify action every xx days and this plugin therefore is ignoring your disable request (ie, a bug). I know page caching has a prime caching feature that does a auto recaching but minify only has one for external files. I wonder if then this plugin is attempting to re-minify external files that it found, ignoring your disable minify request. Under: Performance > Minify > Adanced – Update external files every does it have a value in the range of a few days or earlier?

Thanks for the info
Kimberly

Not sure how comfy you are in coding but you could set up a wp_shcedule_event (or a action on new admin logins or media gallery access) in your theme’s functions.php file to check your cdn for new files and if one/more exists then put them into your local media library. I guess one would be better off making a simple plugin to do this than to put the feature in a functions.php (to make it easier to enable/disable by all admins). It would be fairly easy to do but sadly the only thing i dont have experience in is connecting to a remote cdn — the script to do so is actually made avail via w3tc as u are aware so wouldnt be trivial to scrape but im a bit busy.

Ah you had a maintenance mode plugin too? Curious…do you see a: .maintenance file in your root folder (the folder where wp-settings.php file is located)? Note the prefixed “.” which indicates its a hidden file so depending on your environment this file may not display by default. You will need to remove this file to prevent maintenance mode from activating. This file is triggered by wordpress and simply tells wordpress when to set your site (the time) in maintenance mode. Also if you see in your wp-content folder a maintenance.php file that is what is generating the actual html page during maintenance. However, without the .maintenance file this php file shouldn’t be triggered so you don’t need to delete it.

As for your minified files popping up again. So to be clear when using a file manager you are seeing a new folder in /wp-content/cache/minify/000000/<your domain here> created (even when you delete the cache folder) and inside you see several minified files regenerated (even after deletion)?

Secondly, on your website homepage do you see one of these minified files in the source? meaning the homepage is actually using this newly generated minified file?

And thirdly, i know you said it was disabled but just to be sure, under Performance > General Settings > Minify — the Minify checkbox is unchecked. Correct?

I’m wondering then if in your wp-cron (called “cron” in your dbase under the wp_options table)is still triggering the w3tc_minify action every xx days and this plugin therefore is ignoring your disable request (ie, a bug). I know page caching has a prime caching feature that does a auto recaching but minify only has one for external files. I wonder if then this plugin is attempting to re-minify external files that it found, ignoring your disable minify request. Under: Performance > Minify > Adanced – Update external files every does it have a value in the range of a few days or earlier?

Thanks for the info
Kimberly

assuming disk ehanched – when u empty cache:
1. it renames each file with a postfix “.old”
2. If you dont have Purge Prime enabled then it is done. It will wait for visitors to visit each page; it is then that it will recache a new version.
3. If u have purge prime enabled then it goes about recaching each page

im guessing this plugin is trying to minify the .js(?) files that your Download buttons point to? You could simply add a regex expression to exclude the pattern from the minification process.

this plugin automatically adds it to the config.

your server is down; couldnt check your site.