-
Notifications
You must be signed in to change notification settings - Fork 45
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
Database error upgrading to 3.15 #224
Comments
@mwestergaard are you able to get a full backtrace on that error? |
Does this help? I'm seeing the same issue.
|
|
I don't know if this is related, but I found one error in my web log at the time I upgraded:
Thinking it might be an extension conflict, I turned on debug, disabled both extensions, and then uninstalled omnipaymultiprocessor. When I reinstalled, I didn't get the DB_DataObject Error. I re-enabled lineitemedit and both seem to be working. Oddly, I now receive an error on any extension I enable:
I got that when I upgraded the mosaico extension earlier today. |
I also ran into some issues with a clean install of Civi. The issue is that my gateway project files contains a copy of the *.mgd.php file in a Support folder for the First Atlantic Commerce Gateway. During installation of the plugin I believe the plugin loads all files it can find using the "*.mgd.php" pattern. $mgdFiles = _omnipaymultiprocessor_civix_find_files(__DIR__, '*.mgd.php'); Since this file is also in the Metadata folder of the plugin it loads twice which is causing the issues. There are two proposed solutions:
Another release is required to avoid "out of the box" issues. As a workaround for those affected:
|
@cloudcogsio I suspect BOTH 1 & 2 should probably be done.... |
An alternative route to the above if you are not using FirstAtlanticCommerce payment processor is to remove the .mgd.php file from both locations and just cv flush - at least I think this works! I couldn't get the above steps to work without hitting other problems. (uninstalling resulted in other errors.) |
@eileenmcnaughton FAC lib was updated. (v1.0.2.1) Removed the mgd from the vendor folder. |
I just did ^^ & tagged 3.16 |
I received this error going from 3.16 to 3.18 today. $backTrace = #0 .../public_html/sites/all/modules/civicrm/CRM/Core/Error.php(954): CRM_Core_Error::backtrace("backTrace", TRUE) #1 .../public_html/sites/all/modules/civicrm/vendor/pear/pear-core-minimal/src/PEAR.php(922): CRM_Core_Error::exceptionHandler(Object(DB_Error)) #2 .../public_html/sites/all/modules/civicrm/vendor/pear/db/DB.php(997): PEAR_Error->__construct("DB Error: already exists", -5, 16, (Array:2), "INSERT INTO |
@timatidg it implies that for some reason you have omnipay_FirstAtlanticCommerce in your payment processor type table (civicrm_payment_processor_type) but not in civicrm_managed - so it is trying to add it |
@eileenmcnaughton, Thank you! I deleted it from the database table (civicrm_payment_processor_type), disabled and re-enabled the (already upgraded) extension and did not receive further error messages. |
yay! |
I upgraded my dev system (CiviCRM 5.46.0) to 3.15 and received:
DB_DataObject Error: update: trying to perform an update without the key set, and argument to update is not DB_DATAOBJECT_WHEREADD_ONLY Array ( [seq] => Array ( [0] => id [1] => 1 ) [keys] => Array ( [0] => id ) )
Test transactions (PayPal CheckOut) seem to completing successfully and I don't see anything fishy in the log. I tried updating a second system (CiviCRM 5.46.2) and received the same error. Again, test transactions appear to be working.
The error might be thrown here: https://github.com/civicrm/civicrm-packages/blob/master/DB/DataObject.php
The text was updated successfully, but these errors were encountered: