CRM_Upgrade_Incremental_php_FiveTwenty
class CRM_Upgrade_Incremental_php_FiveTwenty extends CRM_Upgrade_Incremental_Base
Upgrade logic for FiveTwenty
Constants
| BATCH_SIZE |
|
Properties
| static protected | $relationshipTypes |
Methods
Compute any messages which should be displayed beforeupgrade.
Compute any messages which should be displayed after upgrade.
Syntactic sugar for adding a task.
Remove a payment processor if not in use
No description
Add a column to a table if it doesn't already exist
Do any relevant message template updates.
Re-save any valid values from contribute settings into the normal setting format.
Drop a column from a table if it exist.
Add a index to a table column.
Drop a index from a table if it exist.
Rebuild Multilingual Schema.
Upgrade function.
Change direction of activity autoassignees in case type xml for bidirectional relationship types if they point the other way. This is mostly a visual issue on the case type edit screen and doesn't affect normal operation, but could lead to confusion and a future mixup.
Process a single case type
Change labels in case type xml definition back to names. (dev/core#1046) ONLY for ones using database storage - don't want to "fork" case types that aren't currently forked.
Change labels in case type xml definition back to names. (dev/core#1046) ONLY for ones using database storage - don't want to "fork" case types that aren't currently forked.
Details
in CRM_Upgrade_Incremental_Base at line 41
bool
verifyPreDBstate($errors)
Verify DB state.
at line 48
setPreUpgradeMessage($preUpgradeMessage, string $rev, null $currentVer = NULL)
Compute any messages which should be displayed beforeupgrade.
Note: This function is called iteratively for each upcoming revision to the database.
at line 75
setPostUpgradeMessage(string $postUpgradeMessage, string $rev)
Compute any messages which should be displayed after upgrade.
in CRM_Upgrade_Incremental_Base at line 78
static bool
runSql(CRM_Queue_TaskContext $ctx, string $rev)
(Queue Task Callback)
in CRM_Upgrade_Incremental_Base at line 96
protected
addTask(string $title, string $funcName)
Syntactic sugar for adding a task.
Task is (a) in this class and (b) has a high priority.
After passing the $funcName, you can also pass parameters that will go to the function. Note that all params must be serializable.
in CRM_Upgrade_Incremental_Base at line 121
static bool
removePaymentProcessorType(CRM_Queue_TaskContext $ctx, string $name)
Remove a payment processor if not in use
in CRM_Upgrade_Incremental_Base at line 140
static bool
checkFKExists(string $table_name, string $constraint_name)
in CRM_Upgrade_Incremental_Base at line 156
static bool
addColumn(CRM_Queue_TaskContext $ctx, string $table, string $column, string $properties, bool $localizable = FALSE, string|null $version = NULL)
Add a column to a table if it doesn't already exist
in CRM_Upgrade_Incremental_Base at line 194
static
updateMessageTemplates(CRM_Queue_TaskContext $ctx, string $version)
Do any relevant message template updates.
in CRM_Upgrade_Incremental_Base at line 213
static bool
updateContributeSettings($ctx)
Re-save any valid values from contribute settings into the normal setting format.
We render the array of contribution_invoice_settings and any that have metadata defined we add to the correct key. This is safe to run even if no settings are to be converted, per the test in testConvertUpgradeContributeSettings.
in CRM_Upgrade_Incremental_Base at line 231
bool
updateSmartGroups(CRM_Queue_TaskContext $ctx, array $actions)
Do any relevant smart group updates.
in CRM_Upgrade_Incremental_Base at line 245
static bool
dropColumn(CRM_Queue_TaskContext $ctx, string $table, string $column)
Drop a column from a table if it exist.
in CRM_Upgrade_Incremental_Base at line 261
static bool
addIndex(CRM_Queue_TaskContext $ctx, string $table, string|array $column)
Add a index to a table column.
in CRM_Upgrade_Incremental_Base at line 276
static bool
dropIndex(CRM_Queue_TaskContext $ctx, string $table, string $indexName)
Drop a index from a table if it exist.
in CRM_Upgrade_Incremental_Base at line 289
static bool
dropTableIfEmpty(CRM_Queue_TaskContext $ctx, string $table)
Drop a table.
.. but only if it's empty.
in CRM_Upgrade_Incremental_Base at line 309
static bool
rebuildMultilingalSchema(CRM_Queue_TaskContext $ctx, string|null $version = NULL)
Rebuild Multilingual Schema.
at line 97
upgrade_5_20_alpha1(string $rev)
Upgrade function.
at line 156
static
templateStatus(CRM_Queue_TaskContext $ctx)
at line 186
static bool
changeCaseTypeAutoassignee()
Change direction of activity autoassignees in case type xml for bidirectional relationship types if they point the other way. This is mostly a visual issue on the case type edit screen and doesn't affect normal operation, but could lead to confusion and a future mixup.
(dev/core#1046) ONLY for ones using database storage - don't want to "fork" case types that aren't currently forked.
Earlier iterations of this used the api and array manipulation and then another iteration used SimpleXML manipulation, but both suffered from weirdnesses in how conversion back and forth worked.
Here we use SQL and a regex. The thing we're changing is pretty
well-defined and unique:
at line 206
static
processCaseTypeAutoassignee($caseTypeId, $definition)
Process a single case type
at line 264
static bool
changeCaseTypeLabelToName()
Change labels in case type xml definition back to names. (dev/core#1046) ONLY for ones using database storage - don't want to "fork" case types that aren't currently forked.
at line 279
static array
_changeCaseTypeLabelToName($isDryRun = FALSE)
Change labels in case type xml definition back to names. (dev/core#1046) ONLY for ones using database storage - don't want to "fork" case types that aren't currently forked.