Kowsar Hossain

Hi @evielutions,

At the moment, this feature isn’t available. However, if there’s significant demand for it, I’ll consider adding it in the future. Thanks.

@jstepak Since we’ve made some changes as mentioned previously, kindly wait for the next release and see if it improves the scenario

Hi @wabetainfo,

1. After reviewing the error log, it appears that there are warnings originating from WordPress Core as well. For instance, the following log entry originates from a WordPress Core file:

[23-Oct-2023 02:20:22 UTC] PHP Warning: Undefined array key "scheme" in /home/user/public_html/wp-includes/canonical.php on line 726

Given that warnings are also emerging from WordPress Core, it’s possible that the root cause of the issue lies elsewhere. In that scenario, even if we address this on our end, it will only resolve the warning associated with WP-Optimize, not those from WordPress Core. It is recommended to investigate this aspect as well.

2. In our development, we couldn’t reproduce this issue; however, we are implementing additional checks before using HTTP_HOST to suppress warnings like this from our end. Due to some unavoidable reasons, this particular development is delayed. We’ll try to include it in the next update, i.e., version 3.3.1.

Thanks

@tes-india @dotch Could you please check your access log to see if there is anything unusual? If you happen to come across a 503 error, there’s a possibility it’s been logged there. I would appreciate it if you (or anyone else here) could share the access log via https://pastebin.com/

It should be available in cPanel or the hosting dashboard, or you can ask your hosting provider about it.

@volkerforster Are you suggesting that WooCommerce’s default order search includes a field for searching orders by product? I find that hard to believe. Could you please provide a screenshot as evidence of your claim?

To the best of my knowledge, WooCommerce’s order search allows for searching using just two parameters: Dates and Customers. You can find a screenshot for reference here: https://prnt.sc/kTDRG3KfMwuY

I’d appreciate it if you could double-check and confirm, or inform me if I’ve overlooked something. Thank you.

@orientalantiquesuk If you’ve deactivated WP-Optimize via FTP (either by renaming or deleting it), here are the steps you should follow:

1. In the wp-content directory, delete the advanced-cache.php file (if it exists).
2. In the wp-content/uploads directory, either delete the .htaccess file (if it exists), or rename it to something else (e.g., .htaccess.bak) as a precaution.
3. In the wp-config.php file, remove the following line: define('WP_CACHE', true). Screenshot: https://prnt.sc/bqAUrjGkpP7a
4. In the root directory (where the wp-config.php file is located), open the .htaccess file and eliminate any lines that contain code added by WP-Optimize. Screenshot: https://prnt.sc/GN_26zPL66u3
   These lines are added only when “Browser static file caching” is enabled. Feel free to skip this step if you wish to continue using browser caching even after deactivating WP-Optimize; it won’t cause any issues. However, keep in mind that the .htaccess file is quite sensitive, so be sure to create a backup before making any edits in case something goes wrong.

Note 1: These steps are general and apply to most caching plugins.
Note 2: While there may be additional residual files, I haven’t listed them here because they pose no harm if left untouched.
Note 3: If you manage to make the plugin work by following the workaround mentioned in this thread and subsequently deactivate the plugin from the plugin’s screen, all the above steps will be taken care of automatically.

Thanks.

Hi @rick7653

This is Kowsar from the development team.

You mentioned that an older version worked for you. Could you please specify which version it was? Also, I’m interested about your site’s resource usage statistics from cPanel if you have them as per this screenshot

Update: Up to now, we’ve received reports exclusively from NameCheap and Godaddy users. In order to validate these reports, we conducted testing with WP-Optimize on both NameCheap and Godaddy hosting platforms, and it performed without any issues. This led us to conclude that only a specific subset of users may be experiencing difficulties. We have also reached out to their respective support teams, but unfortunately, their assistance has not been helpful. More details in this thread

Thanks

@redriteuk You can also follow the same steps mentioned above.

In accordance with www.ads-software.com forum rules, I’m unable to request access here, and you can’t provide access in this forum. This would be a violation of the rules for both of us. For more information, please refer to: https://www.ads-software.com/support/guidelines/

I’m just waiting to receive access from our premium user through our official support channel. Once we have that, we intend to resolve this issue for good.

@tes-india Also, please delete the .htaccess file from the ‘wp-content/uploads/’ directory. Additionally, ensure that you’ve added the following code inside the wp-config.php file: define( 'WPO_USE_WEBP_CONVERSION', false );

If it still doesn’t work, could you try changing the PHP version from cPanel? Sometimes, changing the PHP version can trigger a server restart, potentially resolving server-related issues.

@amsgator Since you’re interested, we conduct some checks to determine whether WebP conversion tools are available through your hosting or not. Depending on the results, we either display or hide the following option in settings: https://prnt.sc/W98LoCXGq7Zg

By define( 'WPO_USE_WEBP_CONVERSION', false ), you are essentially bypassing these checks.

Now we know that those checks didn’t work well with your specific environment. However, the reason for this is still unknown. The only way to find the answer is to gain access to an affected website and conduct further investigation. We attempted to collaborate with Namecheap but received a rather frustrating response. So now, we are exploring other ways.

Good to know that it worked; now we know where to look.

I doubt ShortpSixel is the cause since another user experiencing the same issue doesn’t even use ShortpSixel.

The wpo-plugins-tables-list.json file serves the purpose of identifying which plugin creates specific database tables within WP-Optimize’s Database Optimization page. It’s worth noting that this file is harmless and unrelated to the current issue.

Can anybody try the following steps and then activate the plugin to see if the issue is resolved?

1. In your wp-config.php file, add the following line:

define( 'WPO_USE_WEBP_CONVERSION', false );

2. Delete the .htaccess file from the “wp-content/uploads/” directory.

Additionally, I’m curious about the resource usage statistics from cPanel. Would someone be able to share that information? You can refer to this screenshot for guidance: https://prnt.sc/LFzIiEy-6WAG

Thanks

@wooplugins @ilwoody I’ve added WooCommerce HPOS support, so it should work now. Please update to the latest version (v4.0) and let me know if you still face any issues. Thanks

@wp-opti Depending on the server environment, there are instances where the preload function may initiate after the second click. However, this should not be a significant concern because, in such cases, the preload functionality continues to operate in the background.

As for the “embed” folder situation, it does appear to be somewhat unusual and might be related to a plugin conflict. The only way to confirm is by conducting a plugin conflict test. In other words, try disabling all plugins except WP-Optimize and check if this issue gets resolved. If it does, then gradually re-enable each plugin one at a time to identify which one is causing the problem. It’s advisable to carry out this test on a staging site or ensure you have a complete backup of your website before proceeding.

@amsgator This is unfortunate, I can recall a recent incident involving a hosting company (I’m not mentioning the name here) that reached out to us regarding WP-Optimize causing problems for one of their customers. They collaborated with us to address the issue. They conducted their own investigation in the interest of their customer and pinpointed the exact part of our codebase that was causing the conflict.

Cache preloading serves as just one example; there are other features that can be CPU intensive.

I have one more question, If you reset the WebP serving method from WP-Optimize, does it permanently resolve the issue? Here’s a screenshot demonstrating how to perform the reset: https://prnt.sc/tXxreDNwP-IE

Alternatively, if you disable the WebP feature, does it resolve the issue? I’m trying to narrow things down.

Assuming you’ve deactivated the plugin through the File Manager, I presume that reactivating it should not immediately trigger a 503 error. This should give you the opportunity to swiftly reset the WebP serving method before encountering the 503 error again.

I would greatly appreciate it if anyone could provide this piece of information. Thanks