Allow empty Web Property ID via Variable module integration.

I suggest to set the value via drush in DEV. You need to change a lot of settings in dev and this is just one. We already have domain and i18n support. Not validating the UA code sounds like no option at all to me as this caused a LOT of support issues in past.

Hm... Should take a look to the patch first. Allowing an empty value sound useful to me, but removing validation completly not.

#1: variable_empty_id-1964052-1.patch queued for re-testing.

Since variable module may not exists in D8 moving back to D7. But why are we only changing this on variables form and not also on admin form?

Any news?

Or use a fake ID like UA-1234567-89 (I hope it's fake ;-)

I typically use UA-1234-1 as it's used in references and docs. It allows a test.

No update for an extended period of time. Closing because of inactivity.

Broken re-role

Not identical. Review the patch, please.

+++ b/googleanalytics.admin.inc
@@ -305,7 +304,7 @@ function googleanalytics_admin_settings_form($form_state) {
-    '#description' => t('You can set values for Google Analytics <a href="@custom_var_documentation">Custom Dimensions</a> here. You must have already configured your custom dimensions in the <a href="@setup_documentation">Google Analytics Management Interface</a>. You may use tokens. Global and user tokens are always available; on node pages, node tokens are also available. A dimension <em>value</em> is allowed to have a maximum length of 150 bytes. Expect longer values to get trimmed.', array('@custom_var_documentation' => 'https://developers.google.com/analytics/devguides/collection/analyticsjs/custom-dims-mets', '@setup_documentation' => 'https://support.google.com/analytics/answer/2709829')),
+    '#description' => t('You can set values for Google Analytics <a href="@custom_var_documentation">Custom Dimensions</a> here. You must have already configured your custom dimensions in the <a href="@setup_documentation">Google Analytics Management Interface</a>. You may use tokens. Global and user tokens are always available; on node pages, node tokens are also available. A dimension <em>value</em> is allowed to have a maximum lenght of 150 bytes. Expect longer values to get trimmed.', array('@custom_var_documentation' => 'https://developers.google.com/analytics/devguides/collection/analyticsjs/custom-dims-mets', '@setup_documentation' => 'https://support.google.com/analytics/answer/2709829')),

Fault

No update for an extended period of time. Closing because of inactivity.

Yes, GA D8 is ready for prime time. You can rerole, but it also requires a D8 patch first.

Additionally I'm still not sure how we can solve the usability issue. I'd like to have form validation and show the red star to imply this is a must value. If I only think about the number of issues we had before I introduced the validation/requirement compared to today I'm still not convinced this helps users except for edge cases. I wish we could do some comparison to core or other modules how they handle such form settings.

It is sooo easy to delete this variable via drush...

I always put the drush commands in a script. This easily allows me to backup live systems, restore them scripted on test/staging and then run a bunch of drush commands to correct all variables that need to be changed to the system.

These are at least:

drush vset file_private_path C:/hiddenpath/foo
drush vset file_directory_temp C:/xampp/tmp
drush vdel googleanalytics_account
drush vdel piwik_site_id

How do you change the paths from production to dev without drush?

I do not like to waste both of our time, but I think we lose more than we win. At least 1-2 useless support cases per week is what I will get here.

With the sunset of legacy google analytics, the 8.x-2.x module is now unsupported. If this is still an issue with the 4.x version, please file a new issue in the queue.