[MAGNOLIA-6360] Cannot select node from Inbox to publish / delete or cancel action. Created: 27/Aug/15 Updated: 28/Aug/15 Resolved: 28/Aug/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 4.2.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Critical |
| Reporter: | Steven Gatt | Assignee: | Unassigned |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
After publishing a node using Magnolia, a yellow highlighted error with red text is showing when trying to publish the same node from the Inbox saying "FreeMarker template error!". We are unable to publish any other nodes before we can delete or activate the current node which is causing other nodes not showing under the Inbox section when published. Reported error from the machine running Magnolia: Method public java.lang.String info.magnolia.cms.gui.controlx.impl.AbstractControl.render() threw an exception when invoked on info.magnolia.cms.gui.controlx.list.ListColumn@1baef5 |
| Comments |
| Comment by Jan Haderka [ 28/Aug/15 ] |
|
Could you please provide version of Magnolia on which you have encountered this problem? Guessing from the error message it's 4.5.x or older. |
| Comment by Steven Gatt [ 28/Aug/15 ] |
|
Hi Jan, thanks a lot for replying. We are running a relatively old version - 4.2.2 |
| Comment by Jan Haderka [ 28/Aug/15 ] |
|
Hi Steven, yeah, sorry, that branch is not maintained for quite few years already. I'm pretty sure if you upgrade to something more recent the issue was fixed in the mean time. |
| Comment by Steven Gatt [ 28/Aug/15 ] |
|
Thank you Jan. |