This content has been marked as final. Show 2 replies
This is due to a change that was made to the Dynamic Actions framework in 4.2. The workaround for now is to change your event to resource load on the DOM window object.
It's working now. In the next release of the plug-in you'll be able to go back to the Page Load (ready) event.