I coudln’t understand. automatic-rock.nl is in the sub-directory? How is it possible? Do you have shared hosting?
Hi Emre,
I mean that wordpress runs from a subdirectory, like this:
http://codex.wordpress.org/Giving_WordPress_Its_Own_Directory
Typically wordpress runs from the directory /wordpress/ in the site root. Ofcourse the .htaccess is outside this directory and in the root. Only your plugin doesn’t seem to ‘see’ this.
Besides this I also wonder why it takes so long to make generate the cached files?
Before I used WP Super Cache and it cached my entire site in less than 10 minutes. Like I said before it now makes about 1 file per 10 minutes. Any idea why it is so slow?
There is no limiting in the wp fastest cache. Pages are cached when they are visited. Therefor, maybe your pages are not visited rapidly.
About directory; I didn’t test it before honestly. I will test it and I will fix the issue.
Hi Emre,
I’m sorry about the speed. I misunderstood how Fastest cache works. In WP super cache I had the option to preload cache. But that pages are cached when they are visited should be fine ofcourse.
It would be nice if you could make it work with a directory install. Since the cache is being created I assume it something in the .htaccess that needs to be changed. Unfortunately I don’t know much about rewrite rules, but I’ll take a look if I can spot something
Hi Emre,
Like I said I don’t know much about it, and I broke my site 🙂
So I’m putting a back-up back, my site will be online again in a few minutes.
One thing I noticed in .htaccess is this:
RewriteCond %{DOCUMENT_ROOT}/WORDPRESSDIR/wp-content/cache/all/WORDPRESSDIR/$1/index.html -f
RewriteRule ^(.*) "/WORDPRESSDIR/wp-content/cache/all/WORDPRESSDIR/$1/index.html" [L]
I think this should be like this:
RewriteCond %{DOCUMENT_ROOT}/WORDPRESSDIR/wp-content/cache/all$1/index.html -f
RewriteRule ^(.*) "/WORDPRESSDIR/wp-content/cache/all/$1/index.html" [L]
So I removed that, but it didn’t change anything.
If you want me to test anything just ask, I don’t mind experimenting a bit 🙂
Kind regards,
Benno
thank you 🙂 as you said, it is a path issue. I will fix it and inform you
Hi Emre,
Any luck in finding a solution?
Yesterday I broke my site again, so I think I should stop trying to fix it myself.. 😉
Best regards,
Benno
I promise you 🙂 I will solve this problem until weekends
no sorry 🙁 I am afraid of mixing code. can you give me your cpanel login info? I will solve it for you.
@emre Vona: Sorry but that’s not cool and really goes too far. Accessing a user’s system like this makes you responsible for that user’s system. If you make changes and something breaks later on as a result, then it is your fault.
Get information, ask for log data, have the user contact you & seek copies of the PHP files. Look but don’t touch. If your code is the problem, then produce a fix and post it here. If the theme or another plugin is at fault, then inform the user, suggest a fix, offer to contact the other developer and/or update your FAQ.
But do not try to make changes to the user’s files in this way. That’s really going too far outside of your area of responsibility.
Hi Emre,
I’m afraid that goes too far indeed. Like I said I don’t mind experimenting a bit, but I like to keep my login info to myself
The cache files to get made, that not the issue. Only how to get visitors there?
Is it possible that you try setup a site with wordpress in a subdirectory and see if you can make it work?
Otherwise I guess I have to go back to wp-supercache, it works with that :/
The lastest version of WP Fastest Cache seems to have solved the problem.
Thank you Emre!
your welcome 🙂 if my users are happy, I am happy too