Admin editing in frontend - markup will be changed

Lilly

Hi!
As you already know there are some problems concerning charsets. For example I can enter "ß" just in the admin-backend and if I write it like this: `

Lilly

Sorry, `

acrylian

Thanks for reporting. I can reproduce it and I wonder why that escaped us or probably more exactly me since I am German, too. Probably I am a little english focussed with Zenphoto (or its because of our "neue Rechtschreibung" where ß is less often used..:-)).

Generally, if you use UTF-8 on your theme files there is actually no need to turn "ß" into ' ß' . It should display fine directly.

Anyway, we will take a look at it.

Lilly

Thank you very much for your quick reply, Acrylian!

I have UTF-8 everywhere, in themes, in database fields, but I cannot use "ß" directly, "Hauptstraße" would turn into "Hauptstraf#376;e".
I always have to write for example "& b u l l ;" or "& e u r o ;" or "& m i d d o t ;", or the sentence will be cut at this char. In admin this is done directly after save. In frontend it first shows up like "Hauptstraf#376;e", if you leave the page and come back it is "Hauptstra".

And I could do this only in textboxes in admin backend but not in textareas (I guess this is what you missed) before I changed admin-functions.php.

Funny is that there is no problem to type äöü or even <> directly from keyboard.

Just what I would like to know from you is where I can find the code which is responsible for textboxes and textareas in frontend when logged in as admin and how to change the code. Because if I type "& e u r o ;" in any of the input fields it will be shown as € in frontend next time I edit it.
If I save that, the sentence will be cut before this char.

May be like this: '.html_encode($UnknownVariable_WhereDoIFindIt, $striptags=false).'?

Yours,
Lilly

acrylian

The front end code is within several template functions that you will find within zp-core/template-functions.php. But that "editable if logged in" is tied in with some Ajax-Javascript and that may be picky beast.

Our JS/encoding expert is not available currently (I think), but all I can say is we will try to solve this problem as soon a possible.
Meanwhile, It is of course not recommend to hack any core files because of problems with further updates...:-)

Lilly

Okay! It's not so urgent, I can wait until it's fixed. Main thing is that you know about it. Thanks for the information!

Btw, I'm curious, do you paint acrylics, Acrylian?

acrylian

Alright. Sort of, I am also an illustrator and I do use acrylics. But the "Acrylian" actually refers to my logo figure.

sbillard

I think we have found both the problem and the fix.

Seems the database was not considering ß a valid UTF-8 character and truncating the string at that character. The fix is to convert ß to ß before it is stored in the database. There are a few other characters with the same [unfortunate] properties. Mostly accented capital letters. These have been converted as well.

There may be other characters as well with the property. If so, the user base will have to let us know which they are.

Lilly

Hi SBillard,

if I type a text directly into a database field with phpmyadmin, I can type anything I like. For a test I put in the whole charset into a description field. It shows up completely on the website.

I made now several tests to find the concerning chars, but I'm afraid they are too much. Other users who want to help can find a complete list of all named entities here:
http://de.selfhtml.org/html/referenz/zeichen.htm

Here are them in short:
`"` `&` `<` `>`   ` ` `¡` `¢` `£` `¤` `¥` `¦` `§` `¨` `©` `ª` `«` `¬` `­` `®` `¯` `°` `±` `²` `³` `´` `µ` `¶` `·` `¸` `¹` `º` `»` `¼` `½` `¾` `¿` `À` `Á` `Â` `Ã` `Ä` `Å` `Æ` `Ç` `È` `É` `Ê` `Ë` `Ì` `Í` `Î` `Ï` `Ð` `Ñ` `Ò` `Ó` `Ô` `Õ` `Ö` `×` `Ø` `Ù` `Ú` `Û` `Ü` `Ý` `Þ` `ß` `à` `á` `â` `ã` `ä` `å` `æ` `ç` `è` `é` `ê` `ë` `ì` `í` `î` `ï` `ð` `ñ` `ò` `ó` `ô` `õ` `ö` `÷` `ø` `ù` `ú` `û` `ü` `ý` `þ` `ÿ`   `Α` `α` `Β` `β` `Γ` `γ` `Δ` `δ` `Ε` `ε` `Ζ` `ζ` `Η` `η` `Θ` `θ` `Ι` `ι` `Κ` `κ` `Λ` `λ` `Μ` `μ` `Ν` `ν` `Ξ` `ξ` `Ο` `ο` `Π` `π` `Ρ` `ρ` `Σ` `ς` `σ` `Τ` `τ` `Υ` `υ` `Φ` `φ` `Χ` `χ` `Ψ` `ψ` `Ω` `ω` `ϑ` `ϒ` `ϖ`   `∀` `∂` `∃` `∅` `∇` `∈` `∉` `∋` `∏` `∑` `−` `∗` `√` `∝` `∞` `∠` `∧` `∨` `∩` `∪` `∫` `∴` `∼` `≅` `≈` `≠` `≡` `≤` `≥` `⊂` `⊃` `⊄` `⊆` `⊇` `⊕` `⊗` `⊥` `⋅` `◊`   `⌈` `⌉` `⌊` `⌋` `〈` `〉`   `←` `↑` `→` `↓` `↔` `↵` `⇐` `⇑` `⇒` `⇓` `⇔`   `•` `′` `″` `‾` `⁄` `℘` `ℑ` `ℜ` `™` `€` `ℵ` `♠` `♣` `♥` `♦`   `Œ` `œ` `Š` `š` `Ÿ` `ƒ`   ` ` ` ` ` ` `‌` `‍` `‎` `‏` `–` `—` `‘` `’` `‚` `“` `”` `„` `†` `‡` `…` `‰` `‹` `›`   `ˆ` `˜`

They should appear like this:
" & < > ¡ ¢ £ ¤ ¥ ¦ § ¨ © ª « ¬ ­ ® ¯ ° ± ² ³ ´ µ ¶ · ¸ ¹ º » ¼ ½ ¾ ¿ À Á Â Ã Ä Å Æ Ç È É Ê Ë Ì Í Î Ï Ð Ñ Ò Ó Ô Õ Ö × Ø Ù Ú Û Ü Ý Þ ß à á â ã ä å æ ç è é ê ë ì í î ï ð ñ ò ó ô õ ö ÷ ø ù ú û ü ý þ ÿ Α α Β β Γ γ Δ δ Ε ε Ζ ζ Η η Θ θ Ι ι Κ κ Λ λ Μ μ Ν ν Ξ ξ Ο ο Π π Ρ ρ Σ ς σ Τ τ Υ υ Φ φ Χ χ Ψ ψ Ω ω ϑ ϒ ϖ ∀ ∂ ∃ ∅ ∇ ∈ ∉ ∋ ∏ ∑ − ∗ √ ∝ ∞ ∠ ∧ ∨ ∩ ∪ ∫ ∴ ∼ ≅ ≈ ≠ ≡ ≤ ≥ ⊂ ⊃ ⊄ ⊆ ⊇ ⊕ ⊗ ⊥ ⋅ ◊ ⌈ ⌉ ⌊ ⌋ 〈 〉 ← ↑ → ↓ ↔ ↵ ⇐ ⇑ ⇒ ⇓ ⇔ • ′ ″ ‾ ⁄ ℘ ℑ ℜ ™ € ℵ ♠ ♣ ♥ ♦ Œ œ Š š Ÿ ƒ       ‌ ‍ ‎ ‏ – — ‘ ’ ‚ “ ” „ † ‡ … ‰ ‹ › ˆ ˜

Kind regards,
Lilly

sbillard

Of course typing the HTML representation of the character will work. It is just the direct UTF-8 code that seems to fail. In fact, what you have done is exactly the fix we have made. The problem characters are converted to their HTML representations before being saved to the database.

Have you tried last night's build?

Lilly

Thanks for your efforts, you both! I will try the latest night's build on Monday. During the weekend I will be a "pastelian" and try to keep away from the computer.

Have a nice weekend!

Lilly

Hi there,
I tried the SVN (2601). Even though I did that before without any problem I made a copy of my installation on another subdomain and made the update there. That was a good idea. The problem with the input of ß is now gone and at the first glance everthing seems to be okay. But the search brings funny results now concerning the pagination. I don't have enough time to test everything and give you my feedback, so I will wait a week or two and then try another SVN again or 1.2.1.