Backbone conflict
-
Hi,
Simple History
Version: 2.37.2A site that I use this on has displayed a console error “Backbone history has already started”. This is derived from a conflicting plugin already starting the Backbone history. They also use the
wp-backbonedependency handle rather than thebackbone. The conflicting plugin is brightcove player.Would it be possible if your team updated the JS, first stop Backbone history before the start? Updating
plugins/simple-history/js/scripts.jsline 608Backbone.history.start()to first runBackbone.history.stop()worked for me but I reverted that to make a workaround without having to edit a plugin.At the moment I dequeue all conflicting plugins on the “Simple History dashboard” only if they contain a dependency of
wp-backboneorbackbone.Thanks
Anthony
The topic ‘Backbone conflict’ is closed to new replies.