pastvne
Bruce Decker
Hi All:
Happy holidays.
I'm working on a project where I have a field/text element with no WYSIWYG. I set the element access to allow one viewlevel to edit and another to display (no edit). If I login with user that carries the edit access, I can enter text including apostrophe and it stores correctly into the database with the unencoded string (in this case containing an unencoded, liter apostophe) store liternally (no encoding).
But if I login with another user that does not have edit access rights on that element, it will properly display the text but if I save the record, the database ends up with encoded entities in the stored record (#39).
I'm looking now at using a form plug-in to cleanse the field before Fabrik updates the field. But, I'm wondering why it should behave this way and whether I've either caused the issue by the way I've defined the element or if there is another approach that is cleaner than using a form plug-in to cleans the field value.
Thanks,
Bruce
Happy holidays.
I'm working on a project where I have a field/text element with no WYSIWYG. I set the element access to allow one viewlevel to edit and another to display (no edit). If I login with user that carries the edit access, I can enter text including apostrophe and it stores correctly into the database with the unencoded string (in this case containing an unencoded, liter apostophe) store liternally (no encoding).
But if I login with another user that does not have edit access rights on that element, it will properly display the text but if I save the record, the database ends up with encoded entities in the stored record (#39).
I'm looking now at using a form plug-in to cleanse the field before Fabrik updates the field. But, I'm wondering why it should behave this way and whether I've either caused the issue by the way I've defined the element or if there is another approach that is cleaner than using a form plug-in to cleans the field value.
Thanks,
Bruce