@aembler
If there is a problem in the content.xml, concrete produces an error that in most cases is generic and would not point out to the node in XML that caused the error.
Is there a way to log the problematic node? Or is there a way to trace it through the error page?
I usually find the problematic node by just trying and error and removing nodes one by one, which takes lots of effort.
@aembler
If there is a problem in the content.xml, concrete produces an error that in most cases is generic and would not point out to the node in XML that caused the error.
Is there a way to log the problematic node? Or is there a way to trace it through the error page?
I usually find the problematic node by just trying and error and removing nodes one by one, which takes lots of effort.