Answers.Body: <p>The issue got fixed in release 5.15.0 (see <a href="https://lab.civicrm.org/dev/financial/issues/54" rel="nofollow noreferrer">here</a>). Thanks a lot to everyone who contributed!</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-11-01T08:06:36.873Z
Answers.LastActivityDate: 2019-11-01T08:06:36.873Z
Answers.UserDisplayName: Joachim
Body: <p>I have been wondering for a while, why two settings for CiviContribute did never have any effect on the created financial transactions:</p>
  
  <ul>
  <li><p>Always post to Accounts Receivable?</p></li>
  <li><p>Enable Deferred Revenue?</p></li>
  </ul>
  
  <p>Since I am beginning to become more familiar with Civi, I tried to dig a bit deeper into the internals of the system, and I might have found the cause.</p>
  
  <p>In general, all settings for all components are stored in the table civicrm_setting, one row per setting. </p>
  
  <p>BUT: There is one exception. All settings for CiviContribute get stored combined within one single row. Looking into the source code, all relevant settings are then pulled out of this single row. And this is also true for the read access to the two settings I mentioned above.</p>
  
  <p>HOWEVER: It seems that when the settings of these two entries get stored, they are indeed written in distinct rows within the settings table. This would be ok for all other settings, except those for CiviContribute. While the system tries to  read the (non existing) values out of the combined row, it always assumes, those values have never been set.</p>
  
  <p>I manually fiddled with this ominous CiviContribute data row and placed a value for deferred_revenue_enabled==true:</p>
  
  <blockquote>
    <p>a:10:{s:24:"deferred_revenue_enabled";s:1:"1";...</p>
  </blockquote>
  
  <p>and voila, now the expected financial transactions all get generated.</p>
  
  <p>I would like to ask some of the more experienced CiviCRM guys to have a look at this phenomenon, since I am not quite sure yet about the correct way for a bug report.</p>
  
  <p>(My current version of Civi is 5.13.2 in combination with Wordpress 5.2, but this bug exists already for some time, at least since 5.11.)</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-08T15:56:08.907Z
Comments.Text: Good work tracking it down. You can go to the financial section at gitlab and create a new issue there, linking back to this question. https://lab.civicrm.org/dev/financial/issues
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-05-08T16:42:50.337Z
Comments.Text: Done (https://lab.civicrm.org/dev/financial/issues/54).
Comments.UserDisplayName: Joachim
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-09-26T19:57:41.887Z
Comments.Text: Ughh... I have the same version of Civi and WP.  CiviContribute disappeared.  It doesn't show in the Components.  Can't enable or disable it.  Any hope for this?
Comments.UserDisplayName: Gary Zimmerman
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-10-02T13:08:06.517Z
Comments.Text: Sorry, but I think your issue is completely unrelated to the discribed bug.
Comments.UserDisplayName: Joachim
Tags: <civicontribute><bug-reporting>
Title: Bug in settings for CiviContribute Component?
ThreadText: # Bug in settings for CiviContribute Component?
  
  (Asked by: username_0 on 2019-05-08)
  
  I have been wondering for a while, why two settings for CiviContribute did never have any effect on the created financial transactions:
  
  * Always post to Accounts Receivable?
  * Enable Deferred Revenue?
  
  Since I am beginning to become more familiar with Civi, I tried to dig a bit deeper into the internals of the system, and I might have found the cause.
  
  In general, all settings for all components are stored in the table civicrm\_setting, one row per setting.
  
  BUT: There is one exception. All settings for CiviContribute get stored combined within one single row. Looking into the source code, all relevant settings are then pulled out of this single row. And this is also true for the read access to the two settings I mentioned above.
  
  HOWEVER: It seems that when the settings of these two entries get stored, they are indeed written in distinct rows within the settings table. This would be ok for all other settings, except those for CiviContribute. While the system tries to read the (non existing) values out of the combined row, it always assumes, those values have never been set.
  
  I manually fiddled with this ominous CiviContribute data row and placed a value for deferred\_revenue\_enabled==true:
  
  > a:10:{s:24:"deferred\_revenue\_enabled";s:1:"1";...
  
  and voila, now the expected financial transactions all get generated.
  
  I would like to ask some of the more experienced CiviCRM guys to have a look at this phenomenon, since I am not quite sure yet about the correct way for a bug report.
  
  (My current version of Civi is 5.13.2 in combination with Wordpress 5.2, but this bug exists already for some time, at least since 5.11.)
  
  **Tags:** civicontribute, bug-reporting
  
  > **Comments:**
  > **username_1**: Good work tracking it down. You can go to the financial section at gitlab and create a new issue there, linking back to this question. https://lab.civicrm.org/dev/financial/issues  
  > **username_0**: Done (https://lab.civicrm.org/dev/financial/issues/54).  
  > **username_2**: Ughh... I have the same version of Civi and WP.  CiviContribute disappeared.  It doesn't show in the Components.  Can't enable or disable it.  Any hope for this?  
  > **username_0**: Sorry, but I think your issue is completely unrelated to the discribed bug.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-11-01. Score: 1 | Accepted answer
  
  The issue got fixed in release 5.15.0 (see [here](https://lab.civicrm.org/dev/financial/issues/54)). Thanks a lot to everyone who contributed!
  
  
  ---
  
  