Same problem this morning. Image (natural 132*204) resized to 578*893. I had to remove pictures from slides because it´s unusable and ugly…
The same problem here. Had to go back ver 2.1.14.
Thread Starter
Malae
(@malae)
My issue with the update was found on a development site on a WAMP server and was corrected by reverting to the previous version. I delayed updating the active site until a new update was made available.
Surprised that there had been no response to this posting, I returned to the Support topics and found that a post made a day later, Images Issue mentioning essentially the same problems, had been answered.
The problem was apparently caused by the inclusion of the wrong owl.carousel.css file, which has now been replaced with the correct one. Unfortunately the plugin version number was not changed, when the file was changed to the correct version and to fix the problem you must manually download the new plugin file, delete the plugin folder and replace it with the new one, which is the same version.
If you are using security software that detects files that have been changed when compared with the original files in that version, you will get a warning that can be ignored.
I would suggest that the manual installation and subsequent warning could have been avoided by raising the version number, which would have triggered a normal update.
To Malae:
Thanks but this not takes any effect. I deleted whole plugin and install again – image still resized. Than deleted owl.carousel.css via FTP and uploaded new files from SA website. Still no effect… Any idea?
Thanks
Thread Starter
Malae
(@malae)
@michaelamelia
Do you have any cache issues?
I reverted to the old version until I downloaded the plugin with the correct owl.carousel.css file in zip format directly from the plugin website. After extracting from the zip file, I used FTP to install the slide-anything folder into the plugins folder. It worked and all my settings were preserved.
I also have this problem. I’ve reinstalled several times. I still have a problem
Did version 2.1.16 fix the reported issue? I’m wondering if it’s safe to update. Thanks!