Search Results
Search type | Search syntax |
---|---|
Tags | [tag] |
Exact | "words here" |
Author |
user:1234 user:me (yours) |
Score |
score:3 (3+) score:0 (none) |
Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
Views | views:250 |
Code | code:"if (foo != bar)" |
Sections |
title:apples body:"apples oranges" |
URL | url:"*.example.com" |
Saves | in:saves |
Status |
closed:yes duplicate:no migrated:no wiki:no |
Types |
is:question is:answer |
Exclude |
-[tag] -apples |
For more details on advanced search visit our help page |
Questions related to civicrm upgrades or updates
1
vote
Accepted
Error after upgrading from v5.22.0 to v5.29.1 in WordPress
Just adding an answer - which is actually from the comments - since I think stackexchange doesn't like answers in the comments - anyway - the issue was an extra copy of the codebase
2
votes
How long should a CiviCRM / Drupal upgrade take?
4.2 is not heinously old - but the older the DB the more risk of something that won't upgrade smoothly. … I would be nervous about saying I could upgrade an unknown database in 4 hours as sometimes just getting the right site access can take that long! …
6
votes
What can I do to fix my database that has been partially upgraded?
You basically need to identify whereabouts in the upgrade it failed. … Once you have done all the things the upgrade script would have done to get to the next point version you can alter the value in civicrm_domain.version to the next point version & remove the upgrade & …
2
votes
Accepted
Upgrade error = API error: Value already exists in the database on ReportTemplate.create
If you are on a recent version of CiviCRM you can run the Managed.reconcile api through the api explorer - in this instance I'm running it to reconcile extended reports - you can do all extensions at …
0
votes
Errors like "Missing case type defintion" and "Invalid case type name" on upgrade to 5.75.0
Thank you for reporting this - the issue will be resolved in 5.75.1+
2
votes
Cannot change cases via Drupal Webform after CiviCRM update
Note that the issue has now been reported as a gitlab and that is the place to follow along with it https://lab.civicrm.org/dev/core/-/issues/3671