#6069 - messages_to_render's r_message did not get promoted to a Comcode field in 11.beta5

This is a spacer post for a website comment topic. The content this topic relates to: #6069 - messages_to_render's r_message did not get promoted to a Comcode field in 11.beta5
By Guest posted
I have no idea why port 80 keeps getting in there either. I wonder if your web host is messing around with your environment variables.

As for this issue specifically, I changed a field type for beta5 in site messages. It looks like Composr did not properly update the database to accommodate.

Workaround for those with database access: In the *_messages_to_render table, create a column r_message__text_parsed with type longtext, and another column r_message__source_user with type int(11) / integer. In theory, this should make the errors go away. I have not tested this workaround.
By Guest posted
Promote message to Comcode will not work; NTS edit upgrade code for 11.beta6 to fix this. We may just have to use raw queries to create these tables manually.

0 guests and 0 members have recently viewed this.