Sanitizer issue on product description edits with embedded images
I'm using a little right chevron ► in the product description that shows up correctly on preview but is saved as ? in the database. This used to work.
Re: Sanitizer issue on product description edits with embedded images
Re: Sanitizer issue on product description edits with embedded images
No, I have the latest Trustwave updates + 155a.
Re: Sanitizer issue on product description edits with embedded images
Oh well, I had this issue and replacing these files corrected it for my install
/admin/includes/classes/AdminRequestSanitizer.php
/admin/includes/init_includes/init_sanitize.php
Re: Sanitizer issue on product description edits with embedded images
To what charset is the database set? Template?
Re: Sanitizer issue on product description edits with embedded images
Hmmm
product description is probably the most permissive field as far as admin sanitizer is concerned.
How do you enter the chevron. As an html entity ?
Re: Sanitizer issue on product description edits with embedded images
Did a quick test on my v155 branch.
Copy/pasted a chevron into a description.
saved OK and displays OK in admin/catalog
Re: Sanitizer issue on product description edits with embedded images
Thanks for confirming, @wilt.
Did some digging and found the root cause was that the database was latin1. Converted to UTF8 using Andrew's script:
https://www.zen-cart.com/downloads.php?do=file&id=1318
and the problem was resolved.
Re: Sanitizer issue on product description edits with embedded images
Quote:
Originally Posted by
swguy
@swguy, I've got to disagree that the problem was resolved by converting the database to utf8. Isn't Zen Cart supposed to operate properly on latin1/iso-8559-1 setups, too? If so, you've found a work-around for the problem, but not the solution.
Re: Sanitizer issue on product description edits with embedded images
It does but the charset (in the configure files) and database have to agree - I had set the charset to utf8 but failed to update the database accordingly. Prior incarnations of this system had charset iso-8859-1, so it all worked.