Closed (fixed)
Project:
Slick Carousel
Version:
7.x-2.1
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Mar 2019 at 03:27 UTC
Updated:
11 May 2019 at 23:14 UTC
Jump to comment: Most recent
Comments
Comment #2
inteja commentedComment #3
inteja commentedComment #4
gausarts commentedThanks for the report.
Sounds like versions mismatch, please ensure you are using Slick 2.x, not 3.x, for now.
I may have removed one of the mentioned functions from the latest 3.x.
In such cases I will see to putting them back.
Comment #5
inteja commentedI'm using slick 7.x-2.1, slick views 7.x-2.1 & slick entity reference 7.x-1.1. I'm now suspecting this has nothing to do with slick as I was able to copy across the contrib modules and libraries from the broken site to another and it worked just fine. Something has been corrupted in the database but no amount of cache clearing has helped and the system table slick entries look identical between the 2 sites, so next I'll try https://www.drupal.org/project/registry_rebuild
Comment #6
gausarts commentedI am not sure if it is relevant, as I haven't tried it, but likely a problem when we place the new Slick folder on top of the old one.
I haven't verified this but likely some old files are still there while the new Slick has removed them.
In this case old
SlickUi.class.phpwas still there, while it should not be.This file was removed at 3.x for the namespace base.
And likely the class registry still loads it.
For such a case, the best way is to remove the entire old Slick folder, and place the new one, and run /update.php, or
drush cc all.I will see if I can provide solutions in such a case.
In the mean time, registry_rebuild or
drush cc all, and removing old Slick folder, should hopefully solve the issues with class registry.That is why I put a disclaimer at home page that 2.x to 3.x upgrade path is NOT supported, yet, as to be honest I haven't investigated potential issues with the new changes except for few. This one is likely one of them.
Thanks for bringing this to attention!
Comment #7
gausarts commentedComment #8
gausarts commentedThis should not happen at 2.x. However the relevant above-mentioned measures were provided at 3.x for just in case.
Feel free to re-open if any issue. Thanks for the report!