Skip to content

Issues with validation on Dataverse Page #6472

@scolapasta

Description

@scolapasta

While working on the glassfish upgrade (specifically issue #6447), I noticed some issues with validation. However trying on our demo and production sites, they are not specific to the upgrade.

• Validation messages don't appear - this one is what #6447 is about. It's strange because I see the same behavior in production, but not in demo (i.e. demo works properly). This should be fixed by changing the update attribute from "@ALL" to "@Form :messagePanel". I've merged this into 6230 branch, but we should consider making this change for develop so we can fix our production.
• (I would be curious to understand why it does work correctly in demo and have some others try it to see if demo is the only outlier)
• Dataverse name does not have a <p:message> tag so if you leave it blank you don't get a validation message.
• validation messages know show a lot of extra text (jsf component ids) at the beginning - not sure which version this got in, but checking Odum production, it was not an issue in 4.11. My guess is that it happened during the recent changes related to accessibility.

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