[MAGNOLIA-3528] RenderException: Can't find renderable definition Created: 24/Jan/11  Updated: 01/Feb/11  Resolved: 01/Feb/11

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 4.3.7
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Ondrej Chytil Assignee: Ondrej Chytil
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File stacktrace.txt    
Issue Links:
causality
caused by MAGNOLIA-3292 Forced setting of paragraph name fiel... Closed
relation
is related to MAGNOLIA-3280 RenderException: Can't find renderabl... Closed
is related to MAGNOLIA-3245 Paragraph does not render after faili... Closed
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

 Description   

This issue was fixed by MAGNOLIA-3245 but introduced again with MAGNOLIA-3292/MGNLDATA-103.

Coppied description:

Occurs in conjunction with adding new links (external-link, internal-link, ...) to the "LinkList" paragraph.

New link dialog:

1) Click "Save" without providing any field data
(leads to an error message popup, saying that input values of mandatory fields are missing)

2) Provide data for mandatory fields

3) Click "Save" again

4) Reloading the page containing the linklist-paragraph, which in turn contains the new link, throws the
following exception. Additionally the added link is not shown in the list of links.



 Comments   
Comment by Ondrej Chytil [ 31/Jan/11 ]

Not able to reproduce this issue again.
In case of SUPPORT-858 probably old nodes created with 4.3.2 version are causing issue. For now we are waiting for reply from that ticket.

Comment by Ondrej Chytil [ 01/Feb/11 ]

Confirmed on SUPPORT-858 ticket, not an issue.

Generated at Mon Feb 12 03:47:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.