Add UI to Manage Google Analytic Tracking Code

[mikesmeltzer]

Closes #2129

Summary

Added a new Connector extension project to the solution called DNN.GoogleAnalyticsConnector.

The connector adds the previously removed fields for managing the Google Analytic fields that were previously exposed in the Platform in prior versions of DNN. The fields should match the fields that were in DNN 8.0.4.

The connector also adds a new button for deactivating the analytic codes. This button is visible only when an analytics code is saved. Behind the scenes, this behaviour only clears the fields for the GA provider which is turn prevents the provider from writing code to the page. This isn't, however, a true deactivation of the GA Http Module and site analytics config.

Validation was added to verify that the Google Analytics tracking code is not empty.

How to Test

On an existing site that is using the core Google Analytics provider, you should be able to view and edit the previously defined tracking code settings. These settings are stored at the root of each portal folder within the GoogleAnalytics.config file.

On a new installation, you should be able to fill out the tracking code details and have them reflected within the page source after saving the screen. Additionally, the GoogleAnalytics.config file should now be visible on the root of the portal in question with the proper settings added to it.

After saving the tracking code, try deleting it and re-adding,etc.

Known Issues

1. What I perceive to be a workaround for the showing/hiding the Delete Connection button was implemented due to some shortcomings in the connectors extension. This has been indicated with comments in both the C# and JS.

2. Pressing cancel after the connector has been saved will make it appear that it is no longer saved. This appears to be an issue with the core connectors extension. Another issue will be created to review the connectors extension in general.

[dnfclas]

All CLA requirements met.

[mitchelsellers]

@mikesmeltzer Quick question on this, it looks good, but is there any ability to "disable" this once configured. The existing platform was limited as well, but if you wanted to disable tracking would it be possible to support that as well?

[mikesmeltzer]

Mitch,

In its current state, and with DNN 8.0.4, you could remove the tracking code and save which would essentially disable the functionality.

To make that more clear, we could add some messaging to the screen to indicate how to disable it.

Thoughts?

[mitchelsellers]

@mikesmeltzer THat might be good enough, I guess from what I remember if you remove the code, the script is still rendered on-page which is what I was hoping to avoid.

[mikesmeltzer]

Let me double check if that completed removes it. If not, maybe I can add a checkbox or something else to disable it entirely.

My intent was like for like with what we had in the last version but if we can do a bit of a value add to then that is great.

[pjkruger]

@mikesmeltzer and @mitchelsellers, are there any plans to integrate Google Tag Manager (GTM) as well?

[mitchelsellers]

This appears to be working as the old one was working

[mikesmeltzer]

Mitchel, I have some pending changes that I haven't committed yet based on the last round of feedback. Please hold off on merging this until I push those.  I'm currently out of the country and will touch base in a few days.

[ohine]

@mikesmeltzer No worries, we will hold off on merging till you let us know it's all set. Hopefully we can get it merged in before the first week of October so it can make it into the v9.3.0 release.

[mitchelsellers]

@mikesmeltzer Do you have an ETA on the final changes?

[mikesmeltzer]

I anticipate doing another commit today. The delete / remove analytics functionality has been added and now I'm just in the process of some final testing.

[mitchelsellers]

@mikesmeltzer Awesome!

[mikesmeltzer]

@mitchelsellers I've pushed another change and edited the initial description. Should be ready for another review.