What's happening and how can I fix it? I have the latest version of the plugin, have tried disabling all plugins, which fixed it. If I enable 1 plugin (the one that serves my images) the problems appear.
My slider is really long (25+ pages) , but shouldn't it lazy load it?
The problem is quite erratic. The fallback fonts appear once in a while. And on Safari I don't seem to have any issues.
Thank you for getting in touch with us. My name is Attila and I'm happy to assist you today.
I would like to confirm that we have received your message. Due to the nature of the issue you are experiencing, I will have to contact and consult with the development team first. I will get back to you as soon as I can.
We appreciate your patience while we're working towards your ticket.
The fallback font is a debug message from the browser. It implies that you might see a different font for a moment until the browser loads them properly. Usually this does not have any visible effect, only the download speed is a little slower than the browser would like it. This can happen because you have a slower connection, or it could be related to other external services as well, like Google Fonts is temporary slower than usual. If you check it, you can see in the list, that it's not only LayerSlider related. Your theme's and other plugin's fonts are also listed there.
The stuck loading indicator is almost certainly related to a 3rd party plugin, as you've also confirmed it. LayerSlider has lazy load built-in, but unfortunately if your theme or another plugin also uses a similar solution, they could interfere with each other. We are always trying to maximize compatibility with other items, but it's not always possible from our end only.
What plugin are you using exactly ? Please check its settings, there might be an option that can adjust this.
1) Yeah other fonts are loaded. But those gstatic fonts are coming from Layerslider and I'm only using 1 font family in Layerslider, Lato, which is why I'm curious to why it pulls in all of them. Is there no way to force Layerslider to only load the used fonts?
2) The loading indicator works when I disable my Amazon Web Services plugin, which pushes media files to AWS and serves them over https. It works flawlessly everywhere. And it worked for Layerslider for the first week or so in Chrome too. Not sure why it suddenly freezes. I understand that you're not able to troubleshoot third party plugins though, it just touched no other plugins than Layerslider when the issue came up.
1. It only loads the fonts that you are including to the Google Fonts section in the plugin. We are planning to create slider-specific fonts in the future, but it's not available yet. The browser DevTools is showing more requests because the browser loads different font variants for every script (latin, cyrillic, greek, etc). Even though you can set scripts in the LayerSlider settings, the Google API usually does not respect it, overwrites it and loads others as well.
2. This problem shouldn't happen under normal circumstances. We are using W3 Total Cache with Amazon CloudFront CDN. It's a really similar setup to yours and it's working without any problem for us. It's certain that the error is not caused by Amazon's service or the HTTPS, that plugin can do other things as well that might conflict, I'd recommend to look around in the settings to see if you can find anything related. You could also try out/test it with another plugin. We are always working towards 100% compatibility with other plugins, and we are investigating 3rd party item conflicts to see if we can adjust them from our end. However no other user experienced or reported this issue in the past, so we believe that the problem is not located on our end, regardless we will try to look into this further.
Hey there,
Thanks for a great plugin so far.
I've got an issue with fallback fonts. In the console it says I have a slow network (got 50MB+).
Screenshot: http://b3.ms/yk5MWoXGMQ2W
Also, it often freezes if I click next too quickly. I have to wait 10 seconds or so before I can click next or it gets stuck on the loading icon:
http://b3.ms/gPG9YjVrA7JQ
What's happening and how can I fix it? I have the latest version of the plugin, have tried disabling all plugins, which fixed it. If I enable 1 plugin (the one that serves my images) the problems appear.
My slider is really long (25+ pages) , but shouldn't it lazy load it?
The problem is quite erratic. The fallback fonts appear once in a while. And on Safari I don't seem to have any issues.
Looking forward to hear from you.
Hello Emilvillumsen,
Thank you for getting in touch with us. My name is Attila and I'm happy to assist you today.
I would like to confirm that we have received your message. Due to the nature of the issue you are experiencing, I will have to contact and consult with the development team first. I will get back to you as soon as I can.
We appreciate your patience while we're working towards your ticket.
Hello,
The fallback font is a debug message from the browser. It implies that you might see a different font for a moment until the browser loads them properly. Usually this does not have any visible effect, only the download speed is a little slower than the browser would like it. This can happen because you have a slower connection, or it could be related to other external services as well, like Google Fonts is temporary slower than usual. If you check it, you can see in the list, that it's not only LayerSlider related. Your theme's and other plugin's fonts are also listed there.
The stuck loading indicator is almost certainly related to a 3rd party plugin, as you've also confirmed it. LayerSlider has lazy load built-in, but unfortunately if your theme or another plugin also uses a similar solution, they could interfere with each other. We are always trying to maximize compatibility with other items, but it's not always possible from our end only.
What plugin are you using exactly ? Please check its settings, there might be an option that can adjust this.
Hey again,
1) Yeah other fonts are loaded. But those gstatic fonts are coming from Layerslider and I'm only using 1 font family in Layerslider, Lato, which is why I'm curious to why it pulls in all of them. Is there no way to force Layerslider to only load the used fonts?
2) The loading indicator works when I disable my Amazon Web Services plugin, which pushes media files to AWS and serves them over https. It works flawlessly everywhere. And it worked for Layerslider for the first week or so in Chrome too. Not sure why it suddenly freezes. I understand that you're not able to troubleshoot third party plugins though, it just touched no other plugins than Layerslider when the issue came up.
Hope this info helps :)
Thank you for the feedback. I'll consult with the dev to see if they can provide any further advice and get back to you with the results.
Hello,
1. It only loads the fonts that you are including to the Google Fonts section in the plugin. We are planning to create slider-specific fonts in the future, but it's not available yet. The browser DevTools is showing more requests because the browser loads different font variants for every script (latin, cyrillic, greek, etc). Even though you can set scripts in the LayerSlider settings, the Google API usually does not respect it, overwrites it and loads others as well.
2. This problem shouldn't happen under normal circumstances. We are using W3 Total Cache with Amazon CloudFront CDN. It's a really similar setup to yours and it's working without any problem for us. It's certain that the error is not caused by Amazon's service or the HTTPS, that plugin can do other things as well that might conflict, I'd recommend to look around in the settings to see if you can find anything related. You could also try out/test it with another plugin. We are always working towards 100% compatibility with other plugins, and we are investigating 3rd party item conflicts to see if we can adjust them from our end. However no other user experienced or reported this issue in the past, so we believe that the problem is not located on our end, regardless we will try to look into this further.