Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi all,

I have changed the parameters to have LO in front of them (so for
example LOlocale) so they shouldn't interfere with silverstripe.

Can the parameters LOlocale, LOmodule and LOVersion be passed from
silverstripe to the BSA?

- --
Greetings,
Rob Snelders

Op 18-12-12 15:47, Christian Lohmaier schreef:
Hi Rob, Flo, *,

On Mon, Dec 17, 2012 at 1:30 PM, Florian Effenberger 
<floeff@documentfoundation.org> wrote:
Rob Snelders wrote on 2012-12-16 23:23:

For expanding the "Send Feedback" option in LibreOffice we
added some parameters to the link it opens. One of the
parameters is locale. But there is a bug[1] posted that using a
locale that's not US then the website doesn't load anymore.

locale is a parameter used by silverstripe - so it is a bad idea to
use.

It is uses to manually switch between translations of a site - and
as you noticed creates an error when a non-existing locale is used

see http://donate.libreoffice.org/?locale=de_DE 
http://donate.libreoffice.org/?locale=he_IL 
http://donate.libreoffice.org/?locale=invalid for example.

And non-existing doesn't mean non-existing translation, but when
the locale-identifier itself is unknown to silverstripe/the
zend-framework silverstripe uses.

I tried a link[2] and then the website doesn't load anymore.

it is "invalid" locale as described above. correct one would be
nl_NL instead of just nl:

http://www.libreoffice.org/?locale=nl_NL

correct in the sense that it is a valid locale in
silverstripe's/Zends opinion. When there is no translated page, it
will hand out the subsite's default langauge.

But when I try with the US-locale[3] then the page works. Can
this be easily solved in the website? Or would it be better if
I use another parameter-name?

If you want to keep the locale parameter, you need to make sure
you're using the ones that silverstripe likes. i.e. the long
versions.

I lack the technical details on how the BSA is implemented.

This has nothing to do with the BSA itself. BSA ist just displayed 
within an iframe. It is already silverstripe's zend-cache that
fails because of the invalid parameter.

Probably Christian Lohmaier, our Silverstripe expert, knows
things best here. What I can offer from the server side is to
write a mod_rewrite rule. However, this is always the least
preferred option, since it IMHO would then break some 
Silverstripe functionality.

mod rewrite to change a query parameter is madness :-)

ciao Christian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJQ0ORWAAoJEGs78UIq7mKy6NYH/3PE168ITxmHnrKXlvc3Jmkt
9aGWFyhKYFPC9PJwlied2mHOUktNuRN7xc4Fb63EfSk55BBdQ9iE4U6wedNB5UzQ
Z1Oyk6QYVBAb209Q40Q7mPxeCKAvOcRiDqnsspFCU+juLtpiHlzzLDBWz7dNWf+6
B+IQAyTz52lq77ZP1kfm6bI3PcoVWddkfi9XtoKlmIeqqdgaSeb1cqyoqcFxPEj1
Ccj4T8AvmBlMs2TSTD3E75VR35zZsndfh0UlPbqWLlmod3gyNvlywevjWjD9kSNJ
675rDFs2tr0RNOY5vlKvuGOKO3D2CLI7+vldzHb2cvCc61Dv4UU0iMYR7XgvzK4=
=FQMc
-----END PGP SIGNATURE-----

-- 
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.