SaaS CMS has officially launched! Learn more now.

Google Analytics gadget breaking dashboard (DXC)

Vote:
 

We are using the latest EPiServer.GoogleAnalytics v2.2.1 and, in our DXC environments, the whole dashboard breaks and is completely blank if we add the Google Analytics gadget. It has the console error "GET https://integ.eboshealthcare.co.nz/EPiServer/Shell/11.6.0/ClientResources/epi-googleanalytics/components/GaDashboardComponent.js 404 ()" - from looking through the network requests this does look like the first thing to go wrong.

I might be on the wrong track, but I’m trying to figure out why our loca requests this seemingly correct URL (which works):

http://sitenz.local/EPiServer/EPiServer.GoogleAnalytics/2.2.1/ClientResources/Scripts/components/GaDashboardComponent.js

Whilst the DXC environments end up requesting this URL instead (and gets a 404):

https://integ.mydomain.co.nz/EPiServer/Shell/11.6.0/ClientResources/epi-googleanalytics/components/GaDashboardComponent.js

The root of those paths differs from “/EPiServer.GoogleAnalytics/2.2.1/ClientResources/Scripts/” to “/EPiServer/Shell/11.6.0/ClientResources/epi-googleanalytics/” – so it seems that the DXC environments are going relative to the CMS UI shell’s ClientResources, whereas our locals go to the GA package’s own ClientResources path.

There's nothing I can think the Azure (DXC) environment would affect this - but I also can't see anything we're doing with the deployment that should mess with the package.. Perhaps if there's anything specific I should check for let me know so I can nosey around what we actually have deployed - I just don't know what to look for yet.

Packages we’re using:

EPiServer.CMS v11.9.4

EPiServer.CMS.UI v11.6.0

EPiServer.GoogleAnalytics v2.2.1

#196288
Edited, Aug 24, 2018 9:00
Vote:
 

Have fixed this issue in our DXC environment by simply deleting the protected modules folder for the GoogleAnalytics plugin. Noticed an extra module.config file outside the zip file, which mismatched what was on my local environment - so that led me to believe we had some old files that hadn't been cleaned up on deploy probably during a newer version of the plugin being deployed.

#196323
Aug 27, 2018 2:35
This topic was created over six months ago and has been resolved. If you have a similar question, please create a new topic and refer to this one.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.