Hey Thor,
I’m not able to reproduce this. Do you know what plugin/post type specifically this is happening with?
Thank you for your fast reply!
Of course I should have done the usual “disable all plugins” first 🙂 I have narrowed it down to one plugin – piklist, unfortunately it is a must use plugin for me.
Definitely some metabox clash between these two. Happens on a simple custompost when editing or adding new post.
Hmm… I have a fix in place for the next version that should take care of the error, but it sounds like you might end up with no ability to control the lightbox on those posts when that plugin is active.
I’ll do some testing and see if I can get a workaround that will work correctly in all circumstances.
I’m waiting for an accessibility fix to come through in the Featherlight script, but it looks like that will happen pretty soon so I expect to publish the next version sometime today or tomorrow.
I was able to track down the conflict and opened a ticket on Piklist’s support forum about it.
Since it’s possible that other plugins might do something similar, I’ve also implemented a patch in Featherlight to attempt to work around it. It’s working correctly with the latest version of Piklist on my development server, so I think you should be good to go when I push the next version.
Awesome. Thank you very much!
any news on a new (development) version? (piklist hasn’t fixed it yet)
Hey Thor,
I’ve been delaying the next update due to some accessibility changes that were supposed to be made in the Featherlight script not working quite right. It looks like the rest of the changes have been delayed though, so I’ll most likely go ahead and tag a new release early next week.
could you point me into the direction of what I need to change, to remove the error?
Hey Thor,
I’ve published version 1.1.0 to the plugin repo which I think should resolve your issue. If not, please let me know!
awesome – works perfect! thank you very much.
