Details
-
New Feature
-
Status: Closed
-
Low
-
Resolution: Outdated
-
None
-
None
-
None
Description
According to business rules, content should be validated both in the front-end through template editing as well as in the repository according to rules.
Attachments
Issue Links
1.
|
Be more selective when and what to save in cms | Closed | Unassigned |
|
|||||||
2.
|
Define API for content validation modules | Closed | Berry van Halderen (Inactive) | ||||||||
3.
|
Write simple content validation according to JCR CND itself | Closed | Berry van Halderen (Inactive) |
|
|||||||
4.
|
Integrate content validation in front-end template engine | Closed | Unassigned | ||||||||
5.
|
Integrate content validation in repository save hook. | Closed | Berry van Halderen (Inactive) |
|
|||||||
6.
|
Verify if constraints are checked before publishing a document | Closed | Unassigned | ||||||||
7.
|
Validation does not work for nested nodes | Closed | Frank van Lankvelt (Inactive) |