Fist Full of Crisco
Forum Replies Created
-
Forum: Plugins
In reply to: [W3 Total Cache] JS minify cause JQuerry errorjquery error might be an ordering issue. meaning, jquery is being combined into the file after someone who needs it. jquery should come first. u can use manual mode to set the proper order or do it via code.
I have no problems.Forum: Plugins
In reply to: [W3 Total Cache] wp-config.php outside of rootFor me i also relocated my wp-config.php for security reasons but you seem to be doing it wrong. To save me time i just found a guide that outlines the correct way:
https://www.groovypost.com/howto/improve-wordpress-securitty-wp-config-php-location/Forum: Plugins
In reply to: [W3 Total Cache] Remove type=”text/javascript”You beat me to the answer ??
Forum: Plugins
In reply to: [W3 Total Cache] How to eliminate render blocking resources with W3TC??then you are misunderstanding the article. It makes a significant difference.
1. Have you checked to see that your js/css files are combined and minified and placed at the bottom of the page?
2. Are you using browser caching?
3. How many other resources are you loading on the page?
4. Be careful when using object and dbase caching. They can slow your site if configued incorrectly.
Forum: Plugins
In reply to: [W3 Total Cache] Duplicate files showing on my siteJust checked your page. I dont see the problem. All your css and js files are coming from your CDN only; nothing local.
Forum: Plugins
In reply to: [W3 Total Cache] Local iframe caching1. iframe contents are only displayed at runtime within the client’s browser, not server-side, therefore can’t be cached.
2. PDFs are loaded and interpreted by the client’s browser (internally or as an extension/plugin), not server-side, therefore can’t be cached.
If you want it cached then i recommend dropping iframe and using some tool on your server-side that can read and display pdf content as html so you can then embed it on the page prior to sending it to the client’s browser.
Forum: Plugins
In reply to: [W3 Total Cache] Question About Order of htaccess rulesLooks good to me
Forum: Plugins
In reply to: [W3 Total Cache] Question About Order of htaccess rulesMight be wiser to have it before, if u plan on enabling the ssl caching option in w3tc in the future.
Btw, it might be preference, but, alternatively, you can replace this
RewriteCond %{SERVER_PORT} 80
with
RewriteCond %{HTTPS} off
.. as a way to make it clearer what you are doing.
Are you using Content-Security Policy (CSP) rules? Just wondering if they might be misconfigured (too restricted). If its not enabled then disregard what i said.
Curious, why are you caching the wp admin(?) login page? Typically, most people dont cache that page. I figure the issue is the use of a ‘nonce’ which is getting cached. Shame developers don’t use ajax more often knowing that most sites will sooner or later make use of caching software.
So i doubt its a bug in w3tc and actually short-sited software makers not taking into consideration the existence of caching tools.
Forum: Plugins
In reply to: [W3 Total Cache] TTFB increase after re-activationgood money says u are using object caching and/or database caching.
Forum: Plugins
In reply to: [W3 Total Cache] Wildards in minify exclusionsregex is your friend.
at least in the w3tc community edition it supports full regex. i could have sworn the official version also supported it. regex is far more superior to simple wildcards.Forum: Plugins
In reply to: [W3 Total Cache] Compatibility Check – Network ModeIt means you’re not using the multi-user version of wordpress. In short, it shoudl say “off” if you aren’t using that feature. For example mine says “off” and its working fine because i am using w3tc to handle my single site.
Forum: Plugins
In reply to: [W3 Total Cache] W3 Total cache not working with wordpress 5.0Works 100% fine for me and i am using an earlier (custom) w3tc version, not 0.9.7. Likely its a compatibility issue with a different plugin, not w3tc.
Forum: Plugins
In reply to: [W3 Total Cache] cURL error 56Sounds like you are using the precache loader, whereby you are having w3tc recache pages after a certain time. Seems like a dik move by your provider blocking loopback http requests. You could use a proxy to get around this problem.