You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, I'm enqueueing the CSS / JS as soon as you activate the plugin. But if the user's theme already includes the CSS and JS, then we would be including these files twice and bloating the site. There also could be version differences that would impact how this swiper works with other swipers on the page.
We should create an options page that allows the user to toggle on / off including the default CSS and JS for swiper and to use their own enqueued version instead. It would be a good idea to also have a message saying something to the affect of "This plugin was built for Swiper version x.x.x, using any other version may have unintended side effects and could cause the slider to not work properly. Proceed with caution".
The text was updated successfully, but these errors were encountered:
Currently, I'm enqueueing the CSS / JS as soon as you activate the plugin. But if the user's theme already includes the CSS and JS, then we would be including these files twice and bloating the site. There also could be version differences that would impact how this swiper works with other swipers on the page.
We should create an options page that allows the user to toggle on / off including the default CSS and JS for swiper and to use their own enqueued version instead. It would be a good idea to also have a message saying something to the affect of "This plugin was built for Swiper version x.x.x, using any other version may have unintended side effects and could cause the slider to not work properly. Proceed with caution".
The text was updated successfully, but these errors were encountered: