AC2 triggering reloading of script

@George @patrick

Has something changed from AC1 to AC2 in terms of internal link event triggers?

Here’s what I’m seeing.

The following script is on the layout:

    <script type="text/javascript">
        !function(e,t,n){function a(){var e=t.getElementsByTagName("script")[0],n=t.createElement("script");n.type="text/javascript",n.async=!0,n.src="https://beacon-v2.helpscout.net",e.parentNode.insertBefore(n,e)}if(e.Beacon=n=function(t,n,a){e.Beacon.readyQueue.push({method:t,options:n,data:a})},n.readyQueue=[],"complete"===t.readyState)return a();e.attachEvent?e.attachEvent("onload",a):e.addEventListener("load",a,!1)}(window,document,window.Beacon||function(){});
    </script>

It is a vendor provided script. Under AC1, this runs once when the full page is loaded and generates some script entries. It creates one set of script tags.

With AC2, the function executes every time I navigate to a new content page.

Screenshot 2024-02-20 at 4.10.05 PM

Thoughts on this?

It should only evaluate script tags that are within the content page, not the ones on the layout page. Can you tell me where the script tag is located within the layout, I assume you didn’t put it inside the view component.

Thanks Patrick, it is loading just after the boostrap.bundle.min.js…and no, not inside the view component.

Could you test if this update fixes it: dmxRouting.zip (8.6 KB)

Yes, that takes care of it!

Fixed in Wappler 6.3.3