Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve errors on failed db updates #67

Open
lynxlynxlynx opened this issue Mar 26, 2020 · 0 comments
Open

Improve errors on failed db updates #67

lynxlynxlynx opened this issue Mar 26, 2020 · 0 comments

Comments

@lynxlynxlynx
Copy link
Contributor

lynxlynxlynx commented Mar 26, 2020

Doing:

$ 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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant