wpmansour

Apologies for the confusion caused. Our development team has acknowledged this issue and escalated it as a top priority. A patch addressing this problem will be released soon. We recommend keeping an eye on the latest plugin updates, as the fix will be included in an upcoming version.

If you encounter further challenges or need interim guidance, feel free to reach out. Thank you for your patience!

It seems like the issue is with your hosting setup. Since WebP works on Edge, the issue likely lies in how the server handles Firefox’s new Accept header.

To fix this, try using a CDN like Cloudflare to serve WebP automatically, bypassing the server limitations. If that’s not an option, reach out to hosting provider support to confirm if WebP negotiation is supported.

It seems like the issue with your product page CSS is related to caching. When you make changes or updates, old cached versions may cause styling issues. Purging the cache, as you’ve done, usually resolves this. Even if the products weren’t edited, global CSS updates can affect them if the cache isn’t refreshed.

To avoid this in the future, try enabling automatic cache purging in WP-Optimize whenever you make changes. If the problem persists, consider excluding CSS files or specific pages from caching. Let me know if you need help with these settings!

Do you not see the “Deactivate” button at all, or does nothing happen when you click on it?

WP-Optimize supports PHP 8.3, but it’s important to ensure that your WordPress installation is also updated to the latest version, as compatibility issues can arise if either is outdated. Please verify that your WordPress version is the latest release.

For now, if the issue persists, I recommend downgrading your PHP version to 8.2. This version has more stable support from both WordPress and its plugins, allowing your site to function properly until further updates ensure full compatibility with PHP 8.3.

Hi Joyca, The notice you’re encountering often happens when translation files are triggered earlier than expected. To help pinpoint the cause:

• Do you have any custom code or hooks related to language files, or are you using a multilingual plugin like WPML or Polylang on your site?
• Have you added or updated any custom code in functions.php or a similar file recently?

Let us know so we can assist further and resolve this quickly for you!

Thanks for raising this issue! We’ve looked into the recent changes in Firefox’s Accept header, and it seems Mozilla has updated the default to better adhere to web standards. This change impacts how image formats like WebP are handled, as they are no longer explicitly listed in the header. It’s a standardization effort that aligns with Safari’s behavior and resolves compatibility issues seen in the past.

Here’s what you can do to address this:

1. Check WP-Optimize’s WebP Settings: Ensure that WebP is enabled in WP Admin > WP-Optimize > Images > Image Compression. This allows WP-Optimize to handle WebP conversion and serving.
2. Server-Side Content Negotiation: If you’re using Apache, you can add this to your .htaccess file to ensure WebP is served where supported, even with the updated header:

<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_ACCEPT} image/webp
RewriteCond %{REQUEST_FILENAME} (.*)\.(jpe?g|png)$
RewriteCond %{DOCUMENT_ROOT}/$1.webp -f
RewriteRule (.+)\.(jpe?g|png)$ $1.webp [T=image/webp,E=accept:1,L]
</IfModule>
<IfModule mod_headers.c>
Header append Vary Accept env=REDIRECT_accept
</IfModule>

This ensures WebP is served when possible, regardless of the Accept header specifics.

This change also impacts tools like PageSpeed Insights, which may misinterpret the missing WebP delivery, despite browser support. Using these adjustments should help you maintain performance and compatibility.

Let us know if you need further clarification or assistance! Thanks!

From what you’ve shared, it seems the WP_CACHE constant is correctly set in your wp-config.php file, but Divi’s Visual Builder is having trouble. This could happen if there’s a conflict between the cache system and Divi’s editor. Here’s a systematic approach to resolving this:

1. Check for Multiple Caching Plugins:
   • Ensure that only one caching solution is active on your site. If you have other caching plugins (e.g., WP Super Cache, W3 Total Cache, or server-side caching provided by your host), consider disabling them temporarily to isolate the issue.
2. Regenerate Cache Configuration:
   • Deactivate and reactivate WP-Optimize. This will recreate the advanced-cache.php file, which ensures caching is set up correctly.
3. Clear and Disable Cache Temporarily:
   • Go to WP-Optimize settings and clear all cache. Temporarily disable caching to see if this resolves the issue with the Divi Visual Builder. If it does, we can re-enable caching and configure exclusions for Divi later.
4. Check File Permissions:
   • Ensure the wp-content directory and its subdirectories (especially cache) have the correct permissions (e.g., 755 for directories and 644 for files). Incorrect permissions can sometimes interfere with caching.
5. Look for Theme or Plugin Conflicts:
   • Divi and WP-Optimize are generally compatible, but sometimes specific configurations or additional plugins can cause conflicts. Temporarily switch to a default theme (e.g., Twenty Twenty-Three) and disable other plugins to test if the issue persists.
6. Examine the Server Environment:
   • Some hosting providers enforce caching or optimization at the server level, which could conflict with WP-Optimize. Check with your hosting provider for any server-side caching or optimization features that might interfere.
7. Debug Mode for Caching:
   • If you’re still having issues, enable debug mode in wp-config.php by adding:

define('WP_DEBUG', true);
define('WPO_CACHE_FILENAME_DEBUG', true);

This will provide additional information in the HTML source of your pages, which could help identify why the Visual Builder isn’t working as expected.

If none of these steps resolve the issue, could you share more details? For example:

• What PHP version is your site running?
• Do you see any errors in the browser console or your server logs when the Visual Builder is failing?
• Does disabling WP-Optimize entirely allow Divi’s Visual Builder to work?

Feel free to update here if you need further guidance. We’ll be happy to help!

Thank you for your detailed query and for sharing the screenshot to provide additional clarity. Let me address your concerns regarding the Database > Optimizations feature in WP-Optimize.

1] What does “Tables would be optimized (97)” mean?

The number “97” represents the total number of database tables in your WordPress site. It is not an indication of how many tables specifically require optimization. Instead, it highlights that all 97 tables will be scanned during the optimization process, and only those with overhead or fragmentation will undergo actual optimization.

This static count (97 in your case) will not reduce after the optimization process because it reflects the total tables present in your database, not just the ones needing optimization.

2] Expected Outcome After Running “Run All Selected Optimizations”:

After executing all selected optimizations:

• You should see a message confirming that the optimization process was completed successfully.
• However, upon refreshing the page, the “Tables would be optimized (97)” count will remain unchanged. This is expected behavior, as WP-Optimize recalculates and displays the total number of tables available, regardless of whether they required optimization or not.

3] Why Doesn’t the Number of Tables Reduce to Zero?

The number will not reduce or “zerorise” because it’s a static count of all tables in your database, not a metric indicating pending optimizations. To confirm successful optimizations:

• Check the Tables tab within the WP-Optimize interface.
• Look for a reduction in the “Overhead” column for individual tables (e.g., previously fragmented tables should now display 0 bytes).
• This is a better indicator that optimization has been successfully performed.

Best Practices for Database Optimization:

• Take regular backups (using UpdraftPlus backup tool) before running optimizations.
• Use the “Scheduled Cleaning” feature in the Settings tab to automate routine maintenance and ensure your database remains optimized over time.
• Review the Table Information to verify changes and detect any future overhead build-up.

I hope this clarifies your concerns!

Sometimes, minification settings can conflict with JavaScript and CSS elements, causing interactive features like sliders, filters, and dropdowns to stop working.

Could you try turning off the “Process JavaScript files” minify option in WP-Optimize to see if this resolves the issue? To do this, go to WP Admin Panel > WP-Optimize > Minify and toggle off the Process JavaScript files option. Then, clear all caches by navigating to WP-Optimize > Cache and clicking Purge Cache. Also, clear your browser cache to make sure no old files are interfering.

Let me know if this helps restore your site’s functionality!

Hey @tomasabonis,

I completely understand how disappointing it can feel to put so much effort into your site, only to experience slow loading times. Here are a few key actions with WP-Optimize that should help improve your site’s performance:

1. Enable Page Caching: Head to WP Admin > WP-Optimize > Cache to enable page caching. This will allow WP-Optimize to serve cached versions of your pages, reducing the load time since the server doesn’t need to regenerate each page on every visit.
2. Optimize the Database: WP-Optimize can help clear unnecessary data like post revisions, spam comments, and trashed items, which can bloat your database and slow things down. Go to WP Admin > WP-Optimize > Database, select the optimizations you’d like, and hit “Run All Selected Optimizations.”
3. Compress and Lazy Load Images: Image compression is another great way to speed things up. WP-Optimize offers image compression and lazy loading, which means images only load when they’re about to be visible. Find these settings under WP-Optimize > Images.
4. Minify CSS and JavaScript: You can reduce page load time by minifying (and optionally combining) CSS and JavaScript files. WP-Optimize’s Minify settings let you handle this with ease.
5. Static File Caching: By caching static files (like images and CSS), WP-Optimize helps browsers quickly load repeat resources. This is handy for returning visitors and is adjustable under the Cache settings.

One last tip: your hosting server does play a critical role in delivering content efficiently. If you’ve already optimized everything on your site, consider using a Content Delivery Network (CDN). A CDN distributes your site content across multiple servers worldwide, which can significantly improve load times for your visitors no matter where they are.

Hope this helps, thanks!

Hi there! To resolve the JS merging issue, try clearing the WP-Optimize cache, along with any CDN and browser caches you may have. Then, ensure “Combine JS files” is enabled in your WP-Optimize settings. Once that’s done, check your site to see if everything is merging as expected. If the issue persists, feel free to share your site URL with the settings enabled so we can troubleshoot further!

It sounds like the homepage cache isn’t updating for new blog posts, which can be a bit of a hassle with all your frequent updates. Here are a couple of quick things to try: First, try setting a shorter cache lifespan in WP-Optimize > Cache to help the homepage refresh more frequently. Next, be sure to check the box for “Automatically preload content after it is purged” in the cache settings—this will keep your cache fresh by automatically updating it at intervals.

As a quick workaround, you might also consider temporarily excluding the homepage from caching so new posts show up immediately (though it might add a tiny bit to load time).

I’m glad to hear the issue was resolved : )

I’m glad to hear that, Thanks!