Colossus and SearchSpring

[netblazon]

On category pages, sometimes the "sort by" dropdown from SearchSpring is empty. If I inspect the source code, the actual select tag has the appropriate options, so I think it's that the custom-select.js process needs to run again after the SearchSpring content loads. I have no idea how to do that. Calling $.loadScript again throws an error "Uncaught SyntaxError: Identifier 'changes' has already been declared", and trying to call publicAPIs.init() directly throws "publicAPIs is not defined".

[Matt Zimmermann]

Hi Susan,

Currently, there is no way to destroy nor reinitialize the custom-select extension. I will look into adding those methods for a future update. You might try adding, if you can, the data-no-custom attribute to the select elements. This will make the extension ignore them.

[netblazon]

Matt, thank you for replying. I did try that, and also removed u-hidden from the <select> and it worked, but of course we lost the nicer display. I'll let the client know that we may have to go this route, however.