Venkat Raj
Forum Replies Created
-
@marcosf Yes, we have fixed the
file_put_contents warning. Regardingfile_get_contents as you said yourself, the checks are already in place. So, I wanted to confirm that this happens repeatedly.
Moreover, sincefile_put_contents throws a warning the empty.htaccessitself shouldn’t be inuploadsfolder.
For some reason, NGINX config allows.htaccessto be created with read/write access and denies actually reading/writing, then I’m afraid you could manually remove those permissions@marcosf We are aware of this issue and is already fixed. Will be available to you in the next release. Some hosting providers with NGINX server prevent use of
.htaccessfor performance enhancement.
Having said that, I believe you somehow have.htaccessfile in theuploadsfolder but don’t have read/write permission to it? Could you please confirm that you get this warningfile_get_contentsrepeatedly? Thanks@roicecz No issues. I’m looking into it and will get back to you after weekend
@mike8040 When viewing
source codeif the HTML doesn’t containwebpbut the devtools says so, then it is because of redirection method at work. So, yes, it is happening on the server side.
One it won’t load side by side, it will only load one version either jpg or webp@jakubjosefforman I have added this to our
possible feature listOnce we have update, we will update youWebP
1. Checks if webp conversion tools are available on your server
2. Checks if webp format can be served using redirect method (only .htaccess is supported)
3. If redirection is not possible, it will changesrcattribute to havewebpformat (only when the browser has support for webp format)
Failed purge on updates
You are saying that you have to clear minify cache yourself. But the page cache is purged, right? If so, It is expected behavior.
Since html page cache is purged, it will be regenerated and serve new page. My guess is that the old minify assets are served instead of new one because the update doesn’t contain a version bump for its static assets such as js/css files. If they have it, then new set of minify assets are generated which in turn referenced in newly cached pages.@roicecz Please submit the form here https://getwpo.com/ask-pre-sales-question/
Yes, it is a pre sales question form, but it will reach our support channel. ThanksThe function
purge_post_on_updateis hooked tosave_postandwp_trash_postaction hooks. Theoretically it won’t fire on login page.
Anyways, it is good to write defensive code, so we will add this null check in the upcoming release.@webpart We tried to reproduce the issue at different servers with no success. Could you please
export settingsand share with us?
Unless we have a way/step by step instructions to reproduce the issue, I’m afraid that I couldn’t help much.@roicecz Could you please check file permissions of the left over image files? Unfortunately, you won’t see any error log statements in
debug.logfile as thewp_delete_filefunction suppresses the file deletion outcome.
https://developer.wordpress.org/reference/functions/wp_delete_file/@roicecz Could you please confirm that all three sites are using WP Optimize version 3.2.10 ? Because the issue has been fixed in that version and you can see the change logs here
https://wordpress.org/plugins/wp-optimize/#developers@mrmatteastwood In our testing, it seems Bricks Builder stable version 1.6.1 solved the issue. Am I right?
@kevajo225 The healthcheck says that
Page caching is detected but server response time is still slow.
That means that WP Optimize page caching is working, you need to upgrade your server@lestexas60 You could do this in the
Settingstab . See the screenshot
https://ibb.co/dBsRnwQ@jsardin I tried to reproduce the issue with RankMath version 1.0.105
It doesn’t seem to createrobots.txt
WP Optimize neither creates it nor deletes it. It only adds required rules usingrobots_txthook
How do you conclude that WP Optimize makes yourrobots.txtfile disappear?