Hello, there, my friend!
Thank you so much for your kind words. 🙂 I really do appreciate it! Thank you!
1. Yes, that is the case. But as you also proposed in your ticket there are ways to inform the user about this and I believe I will add something of this sort in a future version.
2. This is a major concern for us and it is indeed troublesome! I would very much like to try and debug it! Can you guide me to your setup or give me your original htaccess file so I can reproduce the problem?
I think you could reproduce the issue rather easily, by following these steps:
1 – Create a new WP installation.
2 – In wp settings, change the permalink structure to ‘post name’, and save.
3 – Install the plugin, tweak a couple settings (here’s the settings I used http://i.imgur.com/oU7R16A.png) and activate it.
After these steps, my posts were unaccessible through their direct links: http://blog/post-name would give me a 404 error.
To solve the issue, I went back to wp settings, and changed the permalinks structure from ‘post name’ to a different option, saved, changed back to ‘post name’ and saved again.
—-
As I mentioned before, Adaptive Images was unable to create the cache folders, so the server permissions might maybe play a part on this .htaccess problem too?
—-
Another thing that I just remembered is that even after adding the ‘/assets/imgs’ folder to the plugin’s Watched directories, it did not reflect into the .htaccess, I added the following line manually:
‘ RewriteCond %{REQUEST_URI} /assets/imgs [OR]’
To be honest I have no idea if that was needed, but it seemed the right thing to do 😀
Hello, Pedro,
Finally I got round to test the 3 steps you mentioned above but I could not reproduce the problem! Perhaps the issue has been fixed by accident by now or you had some different setup in your server.
Let me know if there is anything more I can for you!
Cheers,
Takis
I think it might have had something to do with the permissions on my installation.
I installed the plugin on another setup and the bug did not appear, but neither did the failure to create the cache folder.
Either way, if it pops up again I’ll be ready to document it properly.
Thanks again, Takis!
Great, I ‘ll be glad to help!
Best,
Takis
