Re: ZX Slideshow official thread
I've now had a chance to try out the .css coding to see how it affects the slides.
As the original poster mentioned, he added it just to the responsive.css because he didn't want it to affect his desktop. This code worked well for Responsive mode of the site...but broke the desktop version.
Got me thinking about your plugin...so changed the responsive.css back to the original, and added this code to the /templates/mycustomtemplate/css/index_home (as this index_home is a file from the plugin):
{
.background-image {position: absolute;top: 0;left: 0;width: 100%;height: auto;}
.background-image__image {display: block;width: 100%;height: auto;-o-object-fit: cover;object-fit: cover;}
.swiper {width: 100%;height: 13vh;min-height: auto;max-height: auto;background-color: #46677b;}
.slideButton__text {font-size: .8rem;margin-bottom: 0;padding: 5px 5px;}
Added this right to line1 so it picks it up first...and voila! It made displayed the desktop version perfectly as well as the responsive mode. Tested by clicking on the slides to insure URL working, let them scroll through and back again.....all worked perfectly in both modes and nothing in the Debug Logs.
I will now create a template for my slides at 1162px x 369px as I find this size works in relation to the overall width of the site. (I know my slides on this test site are different sizes right now...just testing to see what I like best.)
Thanks again for your work on this plugin!
Re: ZX Slideshow official thread
Hi balihr......
Love this plugin and its been working great on my Zen Cart v.2.1 site, but yesterday, unpkg.com server went down and is still down today. In looking at the plugin it looks like it is running a script from their server (swiper bundle).
Is it possible to include this code in the plugin rather than running the script....as now that they're down, it slows my site to grind. I have turned off the plugin for now to mitigate this....but wondered what other options are available so I don't have to rely on other's servers.
I've read about others switching to jsDelivr....but still relying on a 3rd party server.
I am sure there is a good reason to run a script from a 3rd party site vs. including the code in the plugin. I am not a coder....so just wanted to ask.
Thanks!
Re: ZX Slideshow official thread
Hi,
I was using ZX Slideshow v2.1 and v2.2 on ZC 1.5.6c without issues.
Now I have a testcart using 2.1.0, and have installed v3.0.0 of the plugin.
I ran the uninstall SQL patch for v2.2 on my database.
After that I copied all the admin and cart files across, modifying the two templates to insert the slider as explained (CSS file directly from the plugin as is).
The admin configuration had no issues, but slides do not display.
The jscript error in the browser debugger simply says:
Quote:
TypeError: currentSlide is undefined
at the
Code:
var currentSlide = this.slides[this.activeIndex];
in the
Code:
jQuery(window).on("load", function ()
of the jscript_zx_slideshow.php file.
There are no Zencart level debugging logs.
I have tried to check that I did not forget some editing changes but cannot seem to find any issue at the moment.
If anyone has ideas on where I should be looking, I would be most grateful.
Re: ZX Slideshow official thread
I got the advice from Google that his is related to various problems with swiper.js, and am debugging this now, sorry for the noise.
Firefox also does not manage to retrieve the swiper-bundle.min.js which will need to be hosted locally.
Re: ZX Slideshow official thread
Re: ZX Slideshow official thread
Hi all,
It turns out that the issue was a simple reading and comprehension issue. The DB query for zx_slideshow v3 in the zx_slideshow.php template file only looks for slide group 'home', and I had put in the same slide group for each slide as I had used in v2.1/2.2.
The dialogue for setting up slides does not fix the slide group to 'home', I guess that the idea is that one can clone this template file in other places and have different slide groups as needed in those template files.
The slideshow now works perfectly. Moral of the story: before thinking about Javascript and DOM issues, check if there is actually any data to work with.