edwinov
Forum Replies Created
-
Forum: Reviews
In reply to: [Autoptimize] Constant warningsThanks Frank,
that seems to have fixed it. Updated rating. You can have the instructional flight any time!
Cheers.
Forum: Reviews
In reply to: [Autoptimize] Constant warningsHi Frank,
I just unchecked “Also aggregate inline CSS”.
I’ll keep an eye on the cache and see if this makes any difference.
URL : canterburyglidingclub.nz
Cheers,
Edwin
Forum: Reviews
In reply to: [Autoptimize] Constant warningsHa! I never noticed that “Show advanced settings” button before. Did now, these are my settings:
[x] Optimise HTML code?
[ ] Keep HTML comments?[x] Optimise JavaScriptCode?
[ ] Force JavaScript in <head>?
[ ] Also aggregate inline JS?
Exclude scripts from AO : seal.js/jquery/jquery.js
[ ] Add try-catch wrapping?[x] Optimise CSS Code?
[ ] Generate data?
[x] Also aggregate inline CSS?
[ ] Inline and Defer CSS?
[ ] Inline all CSS?
Exclude CSS from AO : admin-bar.min.css, dashicons.min.cssCDN Base URL : [empty]
Cache folder /home/…/wp-content/cache/autooptimize/
Can we write? Yes
Cached styles and scripts : 305 files[x] Save aggregated as static?
[x] Also optimise for logged in?Is that of any help identifying the problem?
Edwin
I have clarified why 1 star in in my updated review.
But you could always transfer 1 million dollars into my account in Switzerland and I promise you I will make it 5 stars!
🙂
I reinstalled helicon ape, I created an empty and writable .htaccess file. I reinstalled the fastcache plugin.
This time when trying to activate it it was complaining the file wasn’t writable (it was) and to copy some code to the very beginning of .htaccess manually (which I did). I then refreshed the fast cache plugin page in WordPress, the page crashed. I had to reboot my server to get it going again.
So I didn’t even get to trying the redirect but look, many people use helicon’s ape and it works for all of them. I guess your plugin just works fine on apache but needs some work to run on IIS as well.
I will now try another cache plugin.
Thanks anyway.
I have removed the plugin already. But these are the facts:
*I only needed an .htaccess file your plugin
*I installed helicon’s ape (see link above) just for this
*With helicon’s ape installed I created an empty .htaccess file
*After enabling your plugin, the .htaccess file had data in it, I don’t remember what exactly, but it was definitely being written to by your plugin
*After visiting my WordPress site (ONLY from a browser on which I was NOT logged in) I could see a cache folder being created and different subfolders for the different posts on my WordPress site, so that part ALL works
*I checked the index files in the cache folders, they all had the “<!– WP Fastest Cache file was created in 0.330816984177 seconds, on 08-01-14 9:01:35 –>” message in it, so the caching itself (when NOT logged in) works perfectly
*Whenever I refreshed a page though I would just never get one of the cached index files, the page ALWAYS (when NOT logged in) just has the “<!– need to refresh to see cached version –>” at the bottomSo everything works, EXCEPT you are not returning an actual cached page. If you fix that, I’d be very happy.
Since I deinstalled both the plugin and helicon’s ape already I can not try any redirection rule but given that almost everything about your plugin works I am pretty sure the .htaccess part worked well.
Hi Emre,
I needed IIS for other stuff anyway and when looking into WordPress I noticed it could be hosted on IIS as well. It works great, except for your plugin.
I know what .htaccess is for, which is why I installed this :
http://www.helicontech.com/ape/
As I said, stuff IS being cached, it’s just that the cached files are NOT the ones being send to the browser. Since most of your plugin is working I’d say this should be a simple fix.