Details
-
Type: Bug
-
Status: Done/Fixed
-
Priority: Blocker
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.7.11
-
Fix Version/s: 4.7.13
-
Component/s: Core CiviCRM, Internationalisation
-
Documentation Required?:None
-
Funding Source:Contributed Code
Description
After working around https://issues.civicrm.org/jira/browse/CRM-19341, I tried to re-enable logging. However, I then get the issue of:
[debug_info] => ALTER TABLE `civicrm`.log_civicrm_contribution_page_en_US ADD `adjust_recur_start_date` tinyint(4) DEFAULT '0' COMMENT 'If true - user is able to adjust payment start date.' [nativecode=1146 ** Table 'civicrm.log_civicrm_contribution_page_en_US' doesn't exist]
This seems to be an issue with the combination of logging and l10n. There are no "log_" views or "log_"*"_en_US" tables listed in MySQL.
Logging had been turned on in 4.7.10 before upgrading, and after a successful upgrade, and clearing of the Cache, then this error cropped up when attempting to re-enable logging directly after the upgrade.
In Incremental/sql/4.7.10.mysql.tpl, there is a change made to the table. However, I don't see changes made to 4.7.11 to that table. Ideas?