Today I checked a policy in the policy portal and was wondering why the table I expected to see there towards the end of the policy content was so short.
I assumed the last reviewer might have only pasted half the table, so I created a new review, pasted the full table, saved and checked again in the policy portal, and it’s been cut off again.
I went back to create a new review and its missing there too so it’s not a display problem but rather some limits being exceeded when saving a policy review.
It would be nice to know which data types have which limits. Imagine when you save a policy, and it is too long, you get a warning along the lines: Your content is X characters longer than the max of Y characters.
Wouldn’t that be pleasant? I expected some kind of input validation to be happening before Eramba saves anything to the DB instead of silently truncating my content.
Email with relevant information just sent to support.
Thanks for all the information. The policy content is limited to 65,535 characters.
And yes, you’re right — we will add validation to inform users about this.
I thought so too. Then I became curious what is happening here and had a look, purely a look at the DB. The field for this policy was indeed “full” at 65,535 characters.
I extracted the content and asked ChatGPT to prettify the content, remove styling, empty spans and divs etc. and the result which wasn’t actually pretty weighed in at approx. 12.000 characters.
I am sure that with a proper HTML editor I could cut that down even more. Next I did a review of this policy and pasted this HTML into the “code view” of the WYSIWYG editor (see screenshot), saved, checked the output in the policy portal and it looks good.
Double-checked the entry in the DB and there it now shows about 12,800 characters - this overhead is totally OK.
I am now busy double-checking about 20 translated policies as there we simply appended the English translation below the German content and saved to make sure I do not have any content which got lost when saving due to excessive lengths.
Anyway, I am pointing my finger (as usual) at the WYSIWYG editor and really hoping for improvement with the new version you guys promised.
And one more question, will the new editor possibly support markdown? I think the whole mess with the WYSIWYG editor is that its using HTML in the background and its prettifying capabilities seem lacking.
