Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Error reporting #103

Open
shahroq opened this issue Nov 1, 2023 · 0 comments
Open

Error reporting #103

shahroq opened this issue Nov 1, 2023 · 0 comments

Comments

@shahroq
Copy link
Contributor

shahroq commented Nov 1, 2023 •
edited
Loading

@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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@shahroq