Description
The SlingPostServlet supports a :savePrefix parameter which may be set to indicate which fields should actually be stored as content and which should just be ignored. The main use case is to use existing forms and to be able to explicitly tell which parameters should be saved or not.
In the meantime we realized, that either the prefix is not used at all or it will always be the same "./", "../" or "/". So the :savePrefix parameter is removed and content modification/creation operation just scans the parameters:
- If no parameters have either of the prefixes, all parameters not prefixed with the colon ( used as the command prefix are stored
- If at least parameter has either of the prefix, only parameters with either of the prefixes will be stored
- Parameters prefixed with the colon ( will never be stored as they are intended as processing parameters
Attachments
Issue Links
- duplicates
-
SLING-394 Remove ":savePrefix" support
- Closed