Re: Multilingual site options?

Simon Rönnqvist <[email protected]>
Newsgroups gmane.comp.cms.bitflux.general
Message-ID <[email protected]>
On Oct 3, 2005, at 21:28, Simon Rönnqvist wrote:

> I tried something similar to what you suggested
> In config.xml:
>     <sitedescription_en allowFromDB="true">This is my Flux CMS  
> Site</sitedescription_en>
>     <sitedescription_sv allowFromDB="true">Detta ar min Flux CMS  
> Site</sitedescription_sv>
>     <sitedescription_fi allowFromDB="true">Tama on Flux CMS  
> sivustoni</sitedescription_fi>
> (Couldn't btw. find out how to get umlaut characters accepted in  
> the config.xml tags above.)
>
> And then this in master.xsl:
>     <xsl:variable name="sitedescription" select="php:functionString 
> ('bx_helpers_config::getOption',concat('sitedescription_',$lang))"/>
>
> Then when I tried to add new dbform options I get the following  
> (but I can change the names of existing variables though):
> The given query was not valid in file /home/streng/www/inc/XML/ 
> xml2db.php at line 226
> [Last query: insert into bxcms_options (name, value, isarray, id)  
> values ('sitedescription_en', 'trubadour, singer, entertainer &  
> conferencier', '0', '13')] [Native code: 1062] [Native message:  
> Duplicate entry '13' for key 1]
> MDB2 Error: already exists

   I noticed that this has been fixed now, thankyou!

> However, when I changed the sitedescription variable to  
> sitedescription_fi I find another problem... all the scandinavian  
> characters come out encoded on the webpage.
> Or let's say ä comes out as &amp;#228; in the XHTML code and  
> therefore the browser views &#228; instead of having it in the  
> code... ;-)
> (I remember some problem like this with the standard usage of  
> sitename, etc. some time earlier on, but that one got fixed.)

   But do you have any suggestion on a solution for this?

> Is it btw. possible to edit the standard site-options form so that  
> one could add variables of one's own (and take away those which one  
> doesn't want to let the customer touch), so that the customer  
> wouldn't have to dig through the dbforms?

And possibly for this?

   cheers, Simon

-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.