I suspect that another package has also registered an angular resource called settingsResource. As the name is a bit generic I think conflicts have arisen between one or more instances where the definitions differ. When angular is calling 'settingsResource' it is in fact somewhere within another package which does not have a get profile function and is therefore causing the error.

In order to try and confirm this try putting a js breakpoint on the dashboardcontroller js in Analytics 1.2.0 say on line 4. If in chrome this might show in the sources tab in /App_Plugins/Analytics/backOffice/AnalyticsTree/controllers/Dashboard.Controller.js. Inspecting the settingsResource argument of the main function may give you an idea which definition of settingsResource is being picked up and to which package that belongs.

Ultimately if that is the problem one or each of the plugin authors involved would need to rename their resource to something less generic e.g wbAnalyticsSettingsResource and issue an update

Thanks @Ian.

I've run a Find and Replace for /App_Plugins/Analytics and changed settingsResource to AnalyticsSettingsResource and it fixed it.

The conflict was between Merchello and Analytics.

It would be worth dropping a line or pull request to the developers of these two packages to highlight the conflict so that if they do any updates in the future it doesn't break your site and you don't have to keep hacking there code.

is working on a reply...