On fresh install I'm getting the following error when trying to clone the default optionset:

Error: Call to undefined function _slick_typecast_optionset() in SlickUi->edit_form_submit() (line 455 of SlickUi.class.php).

Possibly related, when I add a slick_entityreference field formatter and attempt to edit its settings, I get the following error:

Call to undefined function slick_optionset_options() in slick_entityreference_field_formatter_settings_form() in slick_entityreference.module

Comments

inteja created an issue. See original summary.

inteja’s picture

Title: Error: Call to undefined function _slick_typecast_optionset() in SlickUi->edit_form_submit() (line 455 of SlickUi.class.php). » Error: Call to undefined function _slick_typecast_optionset() in SlickUi
inteja’s picture

Issue summary: View changes
gausarts’s picture

Category: Bug report » Support request
Status: Active » Postponed (maintainer needs more info)

Thanks 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.

inteja’s picture

I'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

gausarts’s picture

I 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.php was 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!

gausarts’s picture

gausarts’s picture

Status: Postponed (maintainer needs more info) » Fixed

This 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!

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.