Answers.Body: <p>Finally, i have found out that the disabling of Logging is caused by one of two things :</p>
  
  <ul>
  <li>Trigger permissions is not available on your instance (thanks Parvez for spotting that)</li>
  <li>You are in a multilingual configuration</li>
  </ul>
  
  <p>In my cases, all our sites are multilingual so that's why i can't add the logging functionnality. For the site i was asking, the site was first monolingual and became multilingual which explain why i have been able to enable it and why i can't anymore.</p>
  
  <p>I guess the multilingual triggers don't play nicely with logging triggers.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-20T20:14:44.337Z
Answers.Text: Just find out that there is an issue and a patch for it for 4.7 ! see https://issues.civicrm.org/jira/browse/CRM-12658
Answers.UserDisplayName: samuelsov
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-20T20:08:59.570Z
Answers.LastActivityDate: 2015-11-20T20:08:59.570Z
Answers.UserDisplayName: samuelsov
Answers.Body: <p>I don't have an idea why it got turned off; perhaps an upgrade cleared it?</p>
  
  <p>At any rate, a fresh install does not set a default selection on these radio buttons. You should be able to simply select <code>Yes</code> and then save.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T14:30:06.250Z
Answers.Text: Thanks, but there is no way in the UI to do so as shown in the screenshot i've just added
Answers.UserDisplayName: samuelsov
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T14:33:28.373Z
Answers.Text: Ah, the picture helps!  So the logging question is completely disabled.   It does appear that upgrades to CiviCRM do disable logging when an upgrade is done, and should then reenable them upon completion of the upgrade.  I am wondering if one of your upgrades never fully completed.
Answers.UserDisplayName: DaveD
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T14:46:37.393Z
Answers.Text: I would recommend running the CiviCRM upgrade script to see if it resets things correctly.  For Drupal: `/?q=civicrm/upgrade&reset=1`
Answers.UserDisplayName: DaveD
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T14:47:08.217Z
Answers.Text: I think it might be checking that you have permissions on the DB before it lets you enable? (Assuming the upgrade is showing as cleanly completed)
Answers.UserDisplayName: Parvez Saleh
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T16:17:38.827Z
Answers.Text: We've had a quick look at the code behind the radio option and its checking if the database user has Trigger permissions on the database. My suspicion is that you don't have that permission on this particular database. It may be that you've moved it to test the upgrade or something hence not all permissions as they should be.
Answers.UserDisplayName: Parvez Saleh
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-19T21:40:30.130Z
Answers.LastActivityDate: 2015-10-19T21:40:30.130Z
Answers.UserDisplayName: DaveD
Answers.Body: <p>We use the logging functions for most of our clients. Really depends on what version of CiviCRM your on as to what the problem might be so if you could share that I may be able to point you in the right direction.</p>
  
  <p>Also theres no danger in trying to turn it back on, it wont drop the old logging tables, it'll check for their existence prior to doing anything. If they exist then triggers will simply be added to the base CiviCRM tables.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T14:31:09.853Z
Answers.Text: Just added the version of CiviCRM in the post
Answers.UserDisplayName: samuelsov
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T14:22:21.103Z
Answers.LastActivityDate: 2015-10-20T14:22:21.103Z
Answers.UserDisplayName: Parvez Saleh
Body: <p>I used to have Logging functionnality activated on one of my civicrm instance but when i look at <code>log_civicrm_address</code>, nothing seems to be logged since quite a while.</p>
  
  <p>When i look at the config screen <code>Administer -&gt; System settings -&gt; Misc (Undelete, PDFs, Limits, Logging, Captcha, etc.)</code>, the logging functionnality is disabled and neither set to <code>Yes</code> or <code>No</code>.</p>
  
  <p><a href="https://i.sstatic.net/Bo2Fi.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Bo2Fi.png" alt="enter image description here"></a></p>
  
  <p>How can i re-enable this (and any idea why it's like that) ?</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>CiviCRM is in version 4.6.5 and logging was activated in 4.2 (or maybe before).</p>
  
Tags: <logging>
Title: Logging functionnality disabled
ThreadText: # Logging functionnality disabled
  
  (Asked by: username_0 on 2015-10-19)
  
  I used to have Logging functionnality activated on one of my civicrm instance but when i look at `log_civicrm_address`, nothing seems to be logged since quite a while.
  
  When i look at the config screen `Administer -> System settings -> Misc (Undelete, PDFs, Limits, Logging, Captcha, etc.)`, the logging functionnality is disabled and neither set to `Yes` or `No`.
  
  [![enter image description here](https://i.sstatic.net/Bo2Fi.png)](https://i.sstatic.net/Bo2Fi.png)
  
  How can i re-enable this (and any idea why it's like that) ?
  
  **EDIT**
  
  CiviCRM is in version 4.6.5 and logging was activated in 4.2 (or maybe before).
  
  **Tags:** logging
  
  
  ---
  
  ## 3 answers
  
  ### Answer by username_0 on 2015-11-20. Score: 1 | Accepted answer
  
  Finally, i have found out that the disabling of Logging is caused by one of two things :
  
  * Trigger permissions is not available on your instance (thanks username_2 for spotting that)
  * You are in a multilingual configuration
  
  In my cases, all our sites are multilingual so that's why i can't add the logging functionnality. For the site i was asking, the site was first monolingual and became multilingual which explain why i have been able to enable it and why i can't anymore.
  
  I guess the multilingual triggers don't play nicely with logging triggers.
  
  > **Comments:**
  > **username_0**: Just find out that there is an issue and a patch for it for 4.7 ! see https://issues.civicrm.org/jira/browse/CRM-12658  
  
  ---
  
  ### Answer by username_1 on 2015-10-19. Score: 1
  
  I don't have an idea why it got turned off; perhaps an upgrade cleared it?
  
  At any rate, a fresh install does not set a default selection on these radio buttons. You should be able to simply select `Yes` and then save.
  
  > **Comments:**
  > **username_0**: Thanks, but there is no way in the UI to do so as shown in the screenshot i've just added  
  > **username_1**: Ah, the picture helps!  So the logging question is completely disabled.   It does appear that upgrades to CiviCRM do disable logging when an upgrade is done, and should then reenable them upon completion of the upgrade.  I am wondering if one of your upgrades never fully completed.  
  > **username_1**: I would recommend running the CiviCRM upgrade script to see if it resets things correctly.  For Drupal: `/?q=civicrm/upgrade&reset=1`  
  > **username_2**: I think it might be checking that you have permissions on the DB before it lets you enable? (Assuming the upgrade is showing as cleanly completed)  
  > **username_2**: We've had a quick look at the code behind the radio option and its checking if the database user has Trigger permissions on the database. My suspicion is that you don't have that permission on this particular database. It may be that you've moved it to test the upgrade or something hence not all permissions as they should be.  
  
  ---
  
  ### Answer by username_2 on 2015-10-20. Score: 0
  
  We use the logging functions for most of our clients. Really depends on what version of CiviCRM your on as to what the problem might be so if you could share that I may be able to point you in the right direction.
  
  Also theres no danger in trying to turn it back on, it wont drop the old logging tables, it'll check for their existence prior to doing anything. If they exist then triggers will simply be added to the base CiviCRM tables.
  
  > **Comments:**
  > **username_0**: Just added the version of CiviCRM in the post  
  
  ---
  
  