Hello,
using zenphoto version 1.2.4 [3716] | zenpage Version 1.1.1, zenpage_default theme, we encountered some issues which seem to deal with localization.
Chosen language for alleries is "German"
Clicking on Zenpage, text is German, but all German umlauts are displayed quite... broken. You know, this ü instead of ü and so on. This is only in the zenpage area of the admin panel.
On the other hand, the article_edit.php has an input field with the name title_en_US, but the function process_language_string_save seems to change it to something different, so any adding or updating articles/pages will send an "no title" error. We hotfixed that by exchanging a line in zenpage_admin_functions.php:
//$result['title'] = mysql_real_escape_string(process_language_string_save("title",2));
$result['title'] = sanitize($_POST['title_en_US']); / FIX /
which is of course only quite a dirty hack ;-)
Somehow both seems to deal with localisation. In general, I haven't yet understood the concept where localisation takes place. There is only one place inside the gallery administration where I can choose a language.
Any ideas what's going wrong here?
thx, ella
You should really consider to update to the current Zenphoto 1.2.5 instead hacking an older version (Zenpage version of 1.2.5 is 1.1.1 , too, but actually it is 1.2 as we forgot to update the version number.... It can't be installed with earlier version). Or even wait until 1.2.6 is released (scheduled August 1st).
No, the problems are only with the system texts in Zenpage. Any Content is rendered properly.
For example, the first tab in Zenphoto says "Übersicht" (Overview). This is ok in Zenphoto. When I click on one of the Zenpage tabs (News, Pages), the "Übersicht" tab is changed to "Überblick". And so are all Zenphoto explanatory texts screwed up...
e.
Update: I checked again the delivered code of the pages. The zenphoto pages were delivered correctly in utf-8, the zenpage admin stuff was delivered in ISO-xxx which apparently caused the error. I took a whip and went to my server admin before checking more code, and - he somehow managed to force-deliver the whole stuff in utf-8. The web server should have been fully delivered in utf-8, so I don't exactly know what happened here.
Thanks for your patience. I btw re-updated to 1.2.5 again. Localisation files in this version are not yet completed...? ;-) (If I only slightly understood how to edit these .mo/.po stuff, I could help out, but it costs too much time... :-()
Thanks again,
best wishes,
e.