Problem with svg files growing in size. Please help

#1
When I installed the LiteSpeed Cache plugin, I encountered an issue on the site where when I go to the translated page for a different language, the SVG files are enlarged in size. I have already confirmed that this is caused by the plugin because I have encountered the same issue on more than one site. How can I solve this issue?
I tried cleaning and deleting temporary files, but it didn't solve the issue.
How can I restore the site to the way it was before installing the plugin?
 

Attachments

#3
This try :
To resolve the issue of SVG files being enlarged on translated pages when using the LiteSpeed Cache plugin, follow these steps:
Step 1: Configure LiteSpeed Cache Settings
  1. Exclude SVG Files from Optimization:
    • Go to the LiteSpeed Cache settings in your WordPress admin dashboard.
    • Navigate to the "Media" settings.
    • Find the option for excluding file types from optimization and add .svg to the list.
  2. Disable Image Optimization for Translated Pages:
    • Go to the "Image Optimization" settings.
    • Ensure that any options related to optimizing images for translated or specific pages are turned off.
Step 2: Clear Cache and Purge CDN
  1. Clear LiteSpeed Cache:
    • Go to LiteSpeed Cache > Toolbox > Purge.
    • Select "Purge All" to clear all cached data.
  2. Purge CDN Cache (if applicable):
    • If you are using a CDN (Content Delivery Network), purge the CDN cache to ensure the changes are reflected globally.
Step 3: Check for Plugin Conflicts
  1. Disable Conflicting Plugins:
    • Temporarily disable other plugins related to images or translations to see if the issue persists.
    • If the issue is resolved after disabling a specific plugin, that plugin might be conflicting with LiteSpeed Cache.
Step 4: Revert to Default Settings (if necessary)
  1. Reset LiteSpeed Cache Settings:
    • If the issue persists, try resetting LiteSpeed Cache settings to default.
    • Go to LiteSpeed Cache > Settings > Advanced > Reset Settings.
Step 5: Restore Site to Pre-Plugin State
  1. Backup Restoration:
    • If you took a backup of your site before installing LiteSpeed Cache, restore the site from that backup.
    • Use your backup plugin or hosting provider’s backup feature to revert the site to its previous state.
  2. Manual Cleanup:
    • Deactivate and delete the LiteSpeed Cache plugin.
    • Clear any remaining cache manually by deleting the cache folder via FTP or your hosting file manager (usually located in wp-content/cache).
Step 6: Contact LiteSpeed Support
  • If the issue is still unresolved, consider reaching out to LiteSpeed support for assistance. They might provide a more specific solution based on your site configuration.
Additional Tips
  • Use a Staging Site: Always test changes on a staging site before applying them to the live site to avoid downtime.
  • Check for Updates: Ensure that all your plugins, themes, and WordPress core are up to date to minimize compatibility issues.
 

serpent_driver

Well-Known Member
#4
This try :
To resolve the issue of SVG files being enlarged on translated pages when using the LiteSpeed Cache plugin, follow these steps:
Step 1: Configure LiteSpeed Cache Settings
  1. Exclude SVG Files from Optimization:
    • Go to the LiteSpeed Cache settings in your WordPress admin dashboard.
    • Navigate to the "Media" settings.
    • Find the option for excluding file types from optimization and add .svg to the list.
  2. Disable Image Optimization for Translated Pages:
    • Go to the "Image Optimization" settings.
    • Ensure that any options related to optimizing images for translated or specific pages are turned off.
Step 2: Clear Cache and Purge CDN
  1. Clear LiteSpeed Cache:
    • Go to LiteSpeed Cache > Toolbox > Purge.
    • Select "Purge All" to clear all cached data.
  2. Purge CDN Cache (if applicable):
    • If you are using a CDN (Content Delivery Network), purge the CDN cache to ensure the changes are reflected globally.
Step 3: Check for Plugin Conflicts
  1. Disable Conflicting Plugins:
    • Temporarily disable other plugins related to images or translations to see if the issue persists.
    • If the issue is resolved after disabling a specific plugin, that plugin might be conflicting with LiteSpeed Cache.
Step 4: Revert to Default Settings (if necessary)
  1. Reset LiteSpeed Cache Settings:
    • If the issue persists, try resetting LiteSpeed Cache settings to default.
    • Go to LiteSpeed Cache > Settings > Advanced > Reset Settings.
Step 5: Restore Site to Pre-Plugin State
  1. Backup Restoration:
    • If you took a backup of your site before installing LiteSpeed Cache, restore the site from that backup.
    • Use your backup plugin or hosting provider’s backup feature to revert the site to its previous state.
  2. Manual Cleanup:
    • Deactivate and delete the LiteSpeed Cache plugin.
    • Clear any remaining cache manually by deleting the cache folder via FTP or your hosting file manager (usually located in wp-content/cache).
Step 6: Contact LiteSpeed Support
  • If the issue is still unresolved, consider reaching out to LiteSpeed support for assistance. They might provide a more specific solution based on your site configuration.
Additional Tips
  • Use a Staging Site: Always test changes on a staging site before applying them to the live site to avoid downtime.
  • Check for Updates: Ensure that all your plugins, themes, and WordPress core are up to date to minimize compatibility issues.
LiteSpeed Cache plugin doesn't support svg images because these image type is not an image, its's a document, so any advicements to this issue are obsolete.
 
#5
This try :
To resolve the issue of SVG files being enlarged on translated pages when using the LiteSpeed Cache plugin, follow these steps:
Step 1: Configure LiteSpeed Cache Settings
  1. Exclude SVG Files from Optimization:
    • Go to the LiteSpeed Cache settings in your WordPress admin dashboard.
    • Navigate to the "Media" settings.
    • Find the option for excluding file types from optimization and add .svg to the list.
  2. Disable Image Optimization for Translated Pages:
    • Go to the "Image Optimization" settings.
    • Ensure that any options related to optimizing images for translated or specific pages are turned off.
Step 2: Clear Cache and Purge CDN
  1. Clear LiteSpeed Cache:
    • Go to LiteSpeed Cache > Toolbox > Purge.
    • Select "Purge All" to clear all cached data.
  2. Purge CDN Cache (if applicable):
    • If you are using a CDN (Content Delivery Network), purge the CDN cache to ensure the changes are reflected globally.
Step 3: Check for Plugin Conflicts
  1. Disable Conflicting Plugins:
    • Temporarily disable other plugins related to images or translations to see if the issue persists.
    • If the issue is resolved after disabling a specific plugin, that plugin might be conflicting with LiteSpeed Cache.
Step 4: Revert to Default Settings (if necessary)
  1. Reset LiteSpeed Cache Settings:
    • If the issue persists, try resetting LiteSpeed Cache settings to default.
    • Go to LiteSpeed Cache > Settings > Advanced > Reset Settings.
Step 5: Restore Site to Pre-Plugin State
  1. Backup Restoration:
    • If you took a backup of your site before installing LiteSpeed Cache, restore the site from that backup.
    • Use your backup plugin or hosting provider’s backup feature to revert the site to its previous state.
  2. Manual Cleanup:
    • Deactivate and delete the LiteSpeed Cache plugin.
    • Clear any remaining cache manually by deleting the cache folder via FTP or your hosting file manager (usually located in wp-content/cache).
Step 6: Contact LiteSpeed Support
  • If the issue is still unresolved, consider reaching out to LiteSpeed support for assistance. They might provide a more specific solution based on your site configuration.
Additional Tips
  • Use a Staging Site: Always test changes on a staging site before applying them to the live site to avoid downtime.
  • Check for Updates: Ensure that all your plugins, themes, and WordPress core are up to date to minimize compatibility issues.
I tried it but it doesn't work.
 
Top