You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ cv upgrade:db --dry-run
Found CiviCRM database version 5.17.4.
Found CiviCRM code version 5.23.4.
...
found no problems. Running the upgrade for real failed (not sure if dry-run could catch that) and dumped a webpage with this text:
<span class="status-fatal">Sorry, due to an error, we are unable to fulfill your request at the
moment. You may want to contact your administrator or service provider with more details about
what action you were performing when this occurred.</span>
<div class="crm-section crm-error-message"></div>
<hr style="solid 1px" />
<div class="crm-section crm-error-message">DB Error: no such field</div>
DB Error: no such field is almost useless, but -vv at least provides a clue where to start looking, in this case: CRM_Upgrade_Incremental_php_FiveEighteen::runSql(5.18.alpha1)
Is there no way to make the default reported error be more verbose, in this case printing the field name and/or dumping the query (debug_info member) and/or filename?
(not important, but the actual problem seems to have been in the later steps, since .20 introduced frontend_title to civicrm_contribution_page, which was missing the localized columns)
The text was updated successfully, but these errors were encountered:
Doing:
found no problems. Running the upgrade for real failed (not sure if dry-run could catch that) and dumped a webpage with this text:
DB Error: no such field is almost useless, but -vv at least provides a clue where to start looking, in this case:
CRM_Upgrade_Incremental_php_FiveEighteen::runSql(5.18.alpha1)
Is there no way to make the default reported error be more verbose, in this case printing the field name and/or dumping the query (debug_info member) and/or filename?
(not important, but the actual problem seems to have been in the later steps, since .20 introduced frontend_title to civicrm_contribution_page, which was missing the localized columns)
The text was updated successfully, but these errors were encountered: