Skip to content

Dropping a log on which part of the XML file triggers the error #37

@shahroq

Description

@shahroq

When installing a theme with sample content, and something goes wrong, the log only shows the php error. Yet in most cases is not possible to get which part of the content.xml triggers that error. Is it possible to drop something in the log about that? Something that gives the theme developer a clue about the troublesome node in the XML file?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions