Author Topic: [SOLVED] Upgrade to 4.4.beta4 fails on 'Migrate custom word-replacements' (Read 5749 times)

Generic · October 31, 2013, 10:36:00 am

Hi nickholden, I've written up what to do in the upgrading forum.

http://forum.civicrm.org/index.php/topic,30497.0.html

totten · October 31, 2013, 12:02:17 pm

As Generic suggests, it's probably OK to replace the FourFour.php file in this case. As a general matter, it's not always safe, and (in this case, without doing extensive testing/verification) I'd give it a 2/3 chance of working OK. It should be safe to try on your dev/test environment, but for a production environment it would be better to wait for 4.4.1. (IIRC, 4.4.1 will go out next week.)

Aside: The "xml" directory is in the source-code repository (github), but it's generally omitted from tarballs - the "xml" directory is a "code-generator" used by developers when they prepare the tarball, but it isn't needed at runtime.

nickholden · November 01, 2013, 03:27:55 am

Thanks, totten! I've been able to upgrade by applying just the element of the patch which related to the FourFour.php file (and only the fresh update version, not the 4.4.0 - 4.4.1 version), and it upgraded cleanly.

Manish · November 21, 2013, 06:24:16 am

This must be Error of Multi Languages so first of all remove your all Words Admin -> customize Data and Screens ->Word Replacements remove all your data first and then try to upgrade Civi Crm to newer Version on Joomla or Drupal

CiviCRM Community Forums (archive)

News:

Author Topic: [SOLVED] Upgrade to 4.4.beta4 fails on 'Migrate custom word-replacements' (Read 5749 times)

Generic

Re: [SOLVED] Upgrade to 4.4.beta4 fails on 'Migrate custom word-replacements'

totten

Re: [SOLVED] Upgrade to 4.4.beta4 fails on 'Migrate custom word-replacements'

nickholden

Re: [SOLVED] Upgrade to 4.4.beta4 fails on 'Migrate custom word-replacements'

Manish

Re: [SOLVED] Upgrade to 4.4.beta4 fails on 'Migrate custom word-replacements'