Fred
Forum Replies Created
-
Forum: Plugins
In reply to: [Swift Performance Lite] Swift only caches my FRONTPAGEHi,
We logged in, but another cache plugin is installed and active.
We are not allowed to deactiva third party plugins, so unfortunately we can not help you futher.Thanks for understanding.
Forum: Plugins
In reply to: [Swift Performance Lite] ExpiresByType image/jpg missing.jpg extension can be declared with Content-type : image/jpeg
There isn’t any image/jpg attribute for content-type.Forum: Plugins
In reply to: [Swift Performance Lite] non-Latin charactersHi, it should be cached. I think there is an issue with UTF-8 encoding on your site.
You could also try to add
ini_set( 'default_charset', 'UTF-8' );
at the top of your wp-config.php file.
Forum: Plugins
In reply to: [Swift Performance Lite] Swift + WPML currency switcherPlease share your URL here.
Maybe it is related to WC currency switcher, then you need to enable GEO IP Support in Settings -> Woocommerce. But without more information, it’s just a guess.
Ask your hosting provider if they received similar reports? It might be related to adding an extra security layer with recaptcha in front of WP-login.
I think it can`t be related to Swift as standard Admin login URLs are excluded from cache in Swift. Is there any other cache layer active? Did you enable Caching for logged in users in Swift?
Are you using any security plugin/rewrite URL for your standard wp-admin/login.php?
if so, you might exclude that URL from caching.Forum: Plugins
In reply to: [Swift Performance Lite] hello my Lazyload not workingUnfortunately I can’t see why Lazyload doesn’t work after you reinstalled the plugin. The only thing I can suggest for now is to export your current setting, uninstall Swift completely and reinstall. You can import your current configuration then.
Swift didn’t make any changes to Lazyload code, it must be related to something else what′s causing a possible conflict.
The Fastest solution for you is to disable lazyload in Swift and use A3 Lazy Load for this feature. One extra plugin doesn’t overload your site.Only with Pro version our Support is able to take a closer look into this specific issue and help further.
Hope you understand.
Forum: Plugins
In reply to: [Swift Performance Lite] hello my Lazyload not workingHi, I see indeed that lazyload is not working.
typeof($(“img”).lazyload) === “function”
falseTo check if it is related to Swift or somewhere a conflict, you could disable lazy load in Swift and install a plugin for lazyload, just to check if that is working on your site.
Forum: Plugins
In reply to: [Swift Performance Lite] Caching & Plugin organiser questionNo, if you enable Separate Scripts & Styles, Swift setup cache with a different set of CSS/JS for each page. With most cache plugins, when a page is visited for the first time, the page is build into the cache. The first visitor therefore, have to wait a little longer, before the page is fully loaded and served. Swift’s unique prebuild function ensures that a fast and cached page is always present and delivered.
Forum: Plugins
In reply to: [Swift Performance Lite] Site Error (Fatal Error)Swift does not interfere with user accounts and certainly does not interfere with creating an admin.
Regarding to your issue, It seems the installation was interrupted for some reason. Please remove the plugin and reinstall it.Did you set homepage in Clear Cache on Update Post by Page in Settings->Caching->General?
- This reply was modified 6 years, 2 months ago by Fred.
Forum: Plugins
In reply to: [Swift Performance Lite] hello my Lazyload not workingPlease share your URL here, so we can take a closer look into this issue.
Forum: Plugins
In reply to: [Swift Performance Lite] Swift only caches my FRONTPAGEDid you solve this issue already? If I visit some pages on your website, they are cached and fast ??
Forum: Plugins
In reply to: [Swift Performance Lite] HTTP to HTTPSDid you read the article?
Remove rules in .htaccess and add this in Swift
##——Force HTTPS——##
RewriteCond %{HTTPS} off
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Header set Strict-Transport-Security “max-age=31536000” env=HTTPS