View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 6069 | Composr alpha bug reports | General / Uncategorised | public | 2024-11-26 13:31 | 2024-12-03 00:12 |
| Reporter | Adam Edington | Assigned To | PDStig | ||
| Priority | normal | Severity | trivial | ||
| Status | resolved | Resolution | fixed | ||
| Summary | 6069: messages_to_render's r_message did not get promoted to a Comcode field in 11.beta5 | ||||
| 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) | ||||
| Additional Information | The edit was successful. Still not sure where this port 80 reference is coming from, I removed it from the installer. | ||||
| Tags | Roadmap: v11 | ||||
| Attach Tags | |||||
| Sponsorship open | |||||
|
|
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. |
|
|
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. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-11-26 13:31 | Adam Edington | New Issue | |
| 2024-11-26 13:31 | Adam Edington | Additional Information Updated | |
| 2024-11-26 13:32 | Adam Edington | Summary | Updated to beta 5, happened changing title of gallery video => Updated to beta5, happened changing title of gallery video |
| 2024-11-26 13:35 | Adam Edington | Additional Information Updated | |
| 2024-11-26 16:17 | PDStig | Tag Attached: Roadmap: v11 | |
| 2024-11-26 16:20 | PDStig | Note Added: 0009682 | |
| 2024-11-28 17:37 | PDStig | Summary | Updated to beta5, happened changing title of gallery video => messages_to_render did not get promoted to a Comcode field in 11.beta5 |
| 2024-11-28 17:38 | PDStig | Assigned To | => user4172 |
| 2024-11-28 17:38 | PDStig | Status | Not Assigned => Resolved |
| 2024-11-28 17:38 | PDStig | Resolution | open => fixed |
| 2024-11-28 17:39 | PDStig | Summary | messages_to_render did not get promoted to a Comcode field in 11.beta5 => messages_to_render's r_message did not get promoted to a Comcode field in 11.beta5 |
| 2024-12-03 00:12 | PDStig | Note Added: 0009694 | |
| 2024-12-03 00:12 | PDStig | Note Edited: 0009694 |
