Yes, there is a compatibility issue with Avada. I’m sorry, but the only solution at this time is to use an alternate TOC plugin.
Note to self, related:
– https://wordpress.org/support/topic/plugin-vs-avada-theme/
– https://wordpress.org/support/topic/activating-easy-toc-breaks-features-of-avada-theme/
Same problem here and after a little digging: For the general functionality the plugin doesn’t need the waypoint library, does it?
Removing the two waypoint functions from front.js and preventing enqueuing the library solved it for me.
Maybe you can consider adding an option to deactivate these features.
@marc_j
The widget relies on the Waypoints library and I rely on the widget for my use. A future version will have Waypoints removed.
That should solve the issue as well. Thank you very much!
Hi Steven! Thanks for your great plugin! 🙂
Versión 1.7 of the plugin is still having conflicts with Avada. Let us know when you find a workaround! Thanks!
