Upgrade failure "codingerror"

Upgrade failure "codingerror"

by Dani Kaplan -
Number of replies: 2

Upgrading from 2.7 to 2.8.3 after replacing the files and running the command line upgrade:


-->tool_messageinbound

Database transaction aborted automatically in /home/mdas/public_html/admin/cli/upgrade.php

Default exception handler: Coding error detected, it must be fixed by a programmer: Unknown message processor type moodletxtplus Debug: 

Error code: codingerror

* line 2508 of /message/lib.php: coding_exception thrown

* line 2555 of /message/lib.php: call to get_message_processor()

* line 356 of /lib/messagelib.php: call to translate_message_default_setting()

* line 275 of /lib/messagelib.php: call to message_set_default_message_preference()

* line 521 of /lib/upgradelib.php: call to message_update_providers()

* line 1626 of /lib/upgradelib.php: call to upgrade_plugins()

* line 171 of /admin/cli/upgrade.php: call to upgrade_noncore()


!!! Coding error detected, it must be fixed by a programmer: Unknown message processor type moodletxtplus !!!

!! 

Error code: codingerror !!

!! Stack trace: * line 2508 of /message/lib.php: coding_exception thrown

* line 2555 of /message/lib.php: call to get_message_processor()

* line 356 of /lib/messagelib.php: call to translate_message_default_setting()

* line 275 of /lib/messagelib.php: call to message_set_default_message_preference()

* line 521 of /lib/upgradelib.php: call to message_update_providers()

* line 1626 of /lib/upgradelib.php: call to upgrade_plugins()

* line 171 of /admin/cli/upgrade.php: call to upgrade_noncore()


What should I do next ?


Average of ratings: -
In reply to Dani Kaplan

Re: Upgrade failure "codingerror"

by Michael Aherne -
Picture of Core developers Picture of Peer reviewers Picture of Plugin developers

At a guess, it sounds as if you have a record in your message_processors database table for a plugin called moodletxtplus, but don't have the code for this in /message/output. If that's the case, you might be best to get the code for the plugin if you can, just to get through the upgrade. If that's not possible, you could consider deleting the row in the database, but I don't really know what side-effects that might have.

Average of ratings: Useful (1)
In reply to Michael Aherne

Re: Upgrade failure "codingerror"

by Dani Kaplan -

Thanks for replying, It looks like the upgrade worked at least to a stage the site was accessible. But several plugin s failed. 

Needed to fix them manually.

If something needs to be fixed in future versions is the upgrade process....

Dani