nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Validating basic content component

chrishardie

Hello,

I have create a template that implements a custom fixed-area layout and contains a basic content component.

When a user creates a page in SitePublisher using this template, I wish to perform some validation on the contents of the basic content component. If there are errors, I wish the user to be notified by writing the errors to the page and not to a javascript alert box.

The documentation indicates building a controller would be the best route, but when the user submits the page, where would I forward the user? Is it possible to present the user with the errors on the page editor interface?

Regards,

Chris

Chris

Find more posts tagged with

Comments

vpatel

Hello,

I have create a template that implements a custom fixed-area layout and contains a basic content component.

When a user creates a page in SitePublisher using this template, I wish to perform some validation on the contents of the basic content component. If there are errors, I wish the user to be notified by writing the errors to the page and not to a javascript alert box.

The documentation indicates building a controller would be the best route, but when the user submits the page, where would I forward the user? Is it possible to present the user with the errors on the page editor interface?

Regards,

Chris

Chris

Are you talking about handling *warnings/errors* during the authoring time to CMS authors? Or during preview time (still in authoring TS environment)? Or are you talking about handling page *warnings/errors* at render time on the end website?

chrishardie

I'd like to present authors with any errors during authoring time, just after they attempt to submit the page. I'd like for authors to correct any errors before the page is submitted to a reviewer to obviate the need to have it sent back down the publishing process.

Regards,

Chris

vpatel

I am still not very clear on where you are wanting to validate the content and warn authors. Component datums provide some basic validation mechanism. In addition, if you have DCT datums then you can have FormAPI validations and warn the user. Not sure if that is what you are after.

chrishardie

Thanks for your response.

Let's say a user builds a page, and enters content into the basic content component. Now, for accessibility reasons, I want to check to ensure headers are properly ordered:

<h1> -> <h2> -> <h3> -> <h2> **VALID**

<h1> -> <h4> -> <h1> -> <h3> **INVALID**

How can I parse the content for validation errors like this, present the error to the author in the content creation stage and ensure the author corrects the error before saving or submitting the page?

I'm unsure what you mean by DCT datum type, I didn't see that in the documentation. Do you mean the DCR datum type?

Regards,

Chris

vpatel

I'm unsure what you mean by DCT datum type, I didn't see that in the documentation. Do you mean the DCR datum type?

Yes I meant DCR Datum type.

For the kind of stuff that you want to do -- you'd have to come up with custom solution. You could evaluate each and every field in a DCT on save or something. Alternatively you could do some logic at WF time and run the entire page through some sort of validator.

chrishardie

Ok, I'll explore that, many thanks for your help.

Chris