Hi- this came up again, likely due to an update. The gutentor folks pointed out that this is because Salient is using an old version of Isotope. Can you update to the newest version? Otherwise I have to keep doing this or use some deregister script that I'm not really sure how to do.
The isotope used in Salient has a different feature set than the latest release, so updating it would take some time. I've noted to investigate this further, however, you can handle this compatibility issue via a child theme by adding the following snippet to your child functions.php file:
Sorry for all of the questions!
My search results are blank. There are so many style sheets that I just can't figure out where to look.
I see from the inspector tool that they are there, but I don't know what setting to adjust or where they might be being hidden. Thanks!
Hey Again,
The Plugin "Gutentor" is likely causing the conflict. Try deactivating it and check.
Thanks
ThemeNectar Support Team
That did the trick, thanks!
Is there any other way to make this functionality work? I'd really like to keep Gutenberg as my post editing tool if possible.
Hey Again,
Try using this plugin to remove the conflicting scripts on the particular page: https://wordpress.org/plugins/gonzales/ .
Thanks
ThemeNectar Support Team
Got the answer here from the folks at gutenberg. In case others run into this, I had to comment out Isotope JS on the Gutentor hooks.php.
Hello There,
Thanks for pointing it out.
This will surely help users with similar issues.
Thanks.
Hi- this came up again, likely due to an update. The gutentor folks pointed out that this is because Salient is using an old version of Isotope. Can you update to the newest version? Otherwise I have to keep doing this or use some deregister script that I'm not really sure how to do.
Hey Again,
Escalating this to the developer so this can be added in updated in upcoming Theme Updates.
Thanks
ThemeNectar Support Team
Hey themacinator,
The isotope used in Salient has a different feature set than the latest release, so updating it would take some time. I've noted to investigate this further, however, you can handle this compatibility issue via a child theme by adding the following snippet to your child functions.php file:
add_action( 'wp_enqueue_scripts', 'salient_child_iostope', 100); function salient_child_iostope() { if( is_search() ) { wp_deregister_script( 'isotope' ); wp_enqueue_script( 'isotope', get_template_directory_uri() . '/js/build/third-party/isotope.min.js', array( 'jquery' ), '7.6', true ); } }That will handle the deregistering and allow the change to persist through future updates of the plugin/theme.
Kind regards,