#6069 - messages_to_render's r_message did not get promoted to a Comcode field in 11.beta5
-
By Adam Edington
- Added
- 12 views
| Identifier | #6069 |
|---|---|
| Issue type | Trivial issue (does not break functionality) |
| Title | messages_to_render's r_message did not get promoted to a Comcode field in 11.beta5 |
| Status | Completed |
| Tags |
Roadmap: v11 (custom) |
| Handling member | PDStig |
| Addon | General / Uncategorised |
| Description | A query has failed [INSERT INTO cms_messages_to_render (r_session_id, r_type, r_time, r_message, r_message__text_parsed, r_message__source_user) VALUES ('xh3ddhncmry3t', 'inform', 1732627755, 'Your action was successful.', 'return unserialize(\"a:5:{i:0;a:1:{i:0;a:1:{i:0;a:5:{i:0;s:39:\\\"string_attach_6745cd2b4d4144.90676273_1\\\";i:1;a:0:{}i:2;i:1;i:3;s:0:\\\"\\\";i:4;s:0:\\\"\\\";}}}i:1;a:0:{}i:2;s:10:\\\":container\\\";i:3;b:0;i:4;a:1:{s:39:\\\"string_attach_6745cd2b4d4144.90676273_1\\\";s:95:\\\"\\$tpl_funcs[\'string_attach_6745cd2b4d4144.90676273_1\']=\\\"echo \\\\\\\"Your action was successful.\\\\\\\";\\\";\\n\\\";}}\");\n', 2)] [Unknown column 'r_message__text_parsed' in 'field list'] (version: 11 beta5, PHP version: 8.3.13, URL: https://dev.mediafeeder.net:80/v2/beta4/vanilla/cms/index.php?page=cms-galleries&type=__edit_other&id=2&redirect=https-cms%3Aindex.php%3Fpage%3Dgalleries%26type%3Dvideo%26id%3D5tK8pVaxZCo%26sort%3Drecent%2BDESC&uploading=1) |
| Steps to reproduce | |
| Additional information | The edit was successful. Still not sure where this port 80 reference is coming from, I removed it from the installer. |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments
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.