Barbara Slupik wrote:
> Hello
>
> The problem is caused by a license statement in blocks/forms/resources/
> org/apache/cocoon/forms/resources/js/templates/InfoPopup.html which
> has been added in Cocoon-2.1.12. The fix is to remove the license.
> Perhaps it is possible to move it inside the
Daniel Schmidt wrote:
> Hi Thorsten,
>
> Thanks for pointing out actions. I will have a closer look at them.
>
> Setting the status code is no problem, we already do that. The problem is
> that we only know within the XSLT code if a page is available in a certain
> country, because this is defi
Hi Thorsten,
Thanks for pointing out actions. I will have a closer look at them.
Setting the status code is no problem, we already do that. The problem is that
we only know within the XSLT code if a page is available in a certain country,
because this is defined in XML.
Thanks.
From: Thorst
On 12/12/2013 02:21 PM, Daniel Schmidt wrote:
>
> Hi,
>
>
>
> In our project we have multiple languages and some pages are not
> available in a certain country. If that is the case, we just output a
> message. For Search engines it would be good to respond with a
> different status code then 200.
Hi,
In our project we have multiple languages and some pages are not available in a
certain country. If that is the case, we just output a message. For Search
engines it would be good to respond with a different status code then 200.
The question is: Is it possible to trigger a different http s
Thanks for clarifying, Thorsten.
I did a workaround and created my own formatNumber EXSLT function which just
replaces , and . in a number (10,000.00) with the correct localisation for a
certain country.
Cheers,
Daniel
From: Thorsten Scherler [mailto:scher...@gmail.com]
Sent: Mittwoch, 11. Dez
