Nabble - Bitflux - General

twitter feeds

2009-11-17T14:07:04Z

Hi bitflux developers,

How can the twitter plugin get running?

I now have a clean setup, but the error raises.

Strict[2048] Non-static method DOMDocument::loadXML() should not be
called statically, assuming $this from incompatible context in
/data/tiri/fluxcms/inc/popoon/components/serializers/xhtml.php at line
59

Thomas.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:53:53Z

How can caching been disabled ?
I did

rm -rf tmp/*

But my wget is still transitional.

I greped the themes directories: (only admin is transitional).

wiki:/data/tiri/fluxcms/themes# grep -ri "Transitional" * | grep -v \.svn
standard/admin/plugins/properties.xsl: <xsl:output encoding="utf-8"
method="xml" indent="yes"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
standard/admin/plugins/dbforms2.xsl: <xsl:output encoding="utf-8"
method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
standard/admin/plugins/history.xsl: <xsl:output encoding="utf-8"
method="xml" indent="yes"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
standard/admin/admin.xsl: <xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN"/>
standard/admin/navi.xsl:
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
standard/admin/navi.xsl: doctype-public="-//W3C//DTD XHTML 1.0
Transitional//EN"
standard/admin/delete.xsl:
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"
standard/admin/delete.xsl: doctype-public="-//W3C//DTD XHTML 1.0
Transitional//EN"
standard/admin/login.html:<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0
Transitional//EN"
standard/admin/login.html:
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

Thanks for your help in advance.

Tomorrow I try a completely fresh installation.

Thanks again.

Thomas.

Zitat von Philipp Stucki <philipp@...>:

> list.fluxcms wrote:
>> And this is the problem :-(
>
> Caching is turned off as well? If not: disable it or erase all contents
> of the tmp folder.
>
> Philipp
>
>
> --
> Philipp Stucki
> Eibenstrasse 5
> 8045 Zürich
>
> philipp@...
> http://qwert.ch
>
>

Thomas.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:41:14Z

list.fluxcms wrote:
> And this is the problem :-(

Caching is turned off as well? If not: disable it or erase all contents
of the tmp folder.

Philipp

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:36:22Z

Go scientific : search for the string "Transitional" in the whole flux
CMS Folder...

list.fluxcms a écrit :

> And this is the problem :-(
>
> Zitat von florent Claude <florent@...>:
>
>> If you don't mention XHTML Transitional nowhere but still see it
>> generated, then it is a supernatural...
>> Nothing I can do for that ;-)
>>
>>
>> list.fluxcms a écrit :
>>> OK. But my mytheme/staticl.xsl starts:
>>>
>>> <?xml version="1.0"?>
>>> <xsl:stylesheet version="1.0"
>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>> xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="xhtml">
>>> <xsl:import href="../standard/common.xsl"/>
>>> <xsl:import href="master.xsl"/>
>>>
>>> <xsl:output encoding="utf-8" method="xml"
>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>
>>>
>>> And my ../standard/common.xsl:
>>>
>>> <?xml version="1.0"?>
>>> <xsl:stylesheet version="1.0"
>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>> xmlns="http://www.w3.org/1999/xhtml"
>>> xmlns:php="http://php.net/xsl"
>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>> xmlns:blog="http://bitflux.org/doctypes/blog"
>>> exclude-result-prefixes="xhtml php blog i18n"
>>> >
>>>
>>> <xsl:output encoding="utf-8" method="xml"
>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>
>>>
>>>
>>> Thomas.
>>>
>>> Zitat von florent Claude <florent@...>:
>>>
>>>> I meant : By default, the first xsl to be called is
>>>> /themes/your_theme/static.xsl
>>>>
>>>>
>>>>
>>>> list.fluxcms a écrit :
>>>>> And that, what my standard/static.xsl is looking:
>>>>>
>>>>>
>>>>> <?xml version="1.0"?>
>>>>> <xsl:stylesheet version="1.0"
>>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>>> xmlns="http://www.w3.org/1999/xhtml">
>>>>> <xsl:output encoding="utf-8" method="xml"
>>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>>> <xsl:template match="/">
>>>>>
>>>>> <html>
>>>>>
>>>>> <xsl:call-template name="htmlhead"/>
>>>>>
>>>>> But the result: still: transitional :-/
>>>>>
>>>>> Thomas.
>>>>>
>>>>>
>>>>> Zitat von florent Claude <florent@...>:
>>>>>
>>>>>> By default, the first xsl to be called is static.xsl
>>>>>>
>>>>>>
>>>>>> list.fluxcms a écrit :
>>>>>>> I use following code in my xsl-stylesheets: (this is master.xsl)
>>>>>>>
>>>>>>> <xsl:stylesheet version="1.0"
>>>>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>>>>> xmlns="http://www.w3.org/1999/xhtml"
>>>>>>> xmlns:forms="http://bitflux.org/forms"
>>>>>>> xmlns:php="http://php.net/xsl"
>>>>>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>>>>>> exclude-result-prefixes="xhtml forms php i18n"
>>>>>>>
>>>>>>> >
>>>>>>> <xsl:import href="../standard/mastercommon.xsl" />
>>>>>>> <xsl:output encoding="utf-8" method="xml"
>>>>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>>>>>
>>>>>>> And I added to ../standard/mastercommon.xsl:
>>>>>>>
>>>>>>> <xsl:stylesheet version="1.0"
>>>>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>>>>> xmlns="http://www.w3.org/1999/xhtml"
>>>>>>> xmlns:forms="http://bitflux.org/forms"
>>>>>>> xmlns:php="http://php.net/xsl"
>>>>>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>>>>>> exclude-result-prefixes="xhtml forms php i18n"
>>>>>>>
>>>>>>> >
>>>>>>> <xsl:output encoding="utf-8" method="xml"
>>>>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>>>>>
>>>>>>>
>>>>>>> But still -- Transitional :-(
>>>>>>>
>>>>>>> Thomas.
>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Thomas.
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> This message was sent using IMP, the Internet Messaging Program.
>>>>>
>>>
>>>
>>>
>>> Thomas.
>>>
>>> ----------------------------------------------------------------
>>> This message was sent using IMP, the Internet Messaging Program.
>>>
>
>
>
> Thomas.
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:34:39Z

And this is the problem :-(

Zitat von florent Claude <florent@...>:

> If you don't mention XHTML Transitional nowhere but still see it
> generated, then it is a supernatural...
> Nothing I can do for that ;-)
>
>
> list.fluxcms a écrit :
>> OK. But my mytheme/staticl.xsl starts:
>>
>> <?xml version="1.0"?>
>> <xsl:stylesheet version="1.0"
>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>> xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="xhtml">
>> <xsl:import href="../standard/common.xsl"/>
>> <xsl:import href="master.xsl"/>
>>
>> <xsl:output encoding="utf-8" method="xml"
>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>
>>
>> And my ../standard/common.xsl:
>>
>> <?xml version="1.0"?>
>> <xsl:stylesheet version="1.0"
>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>> xmlns="http://www.w3.org/1999/xhtml"
>> xmlns:php="http://php.net/xsl"
>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>> xmlns:blog="http://bitflux.org/doctypes/blog"
>> exclude-result-prefixes="xhtml php blog i18n"
>> >
>>
>> <xsl:output encoding="utf-8" method="xml"
>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>
>>
>>
>> Thomas.
>>
>> Zitat von florent Claude <florent@...>:
>>
>>> I meant : By default, the first xsl to be called is
>>> /themes/your_theme/static.xsl
>>>
>>>
>>>
>>> list.fluxcms a écrit :
>>>> And that, what my standard/static.xsl is looking:
>>>>
>>>>
>>>> <?xml version="1.0"?>
>>>> <xsl:stylesheet version="1.0"
>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>> xmlns="http://www.w3.org/1999/xhtml">
>>>> <xsl:output encoding="utf-8" method="xml"
>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>> <xsl:template match="/">
>>>>
>>>> <html>
>>>>
>>>> <xsl:call-template name="htmlhead"/>
>>>>
>>>> But the result: still: transitional :-/
>>>>
>>>> Thomas.
>>>>
>>>>
>>>> Zitat von florent Claude <florent@...>:
>>>>
>>>>> By default, the first xsl to be called is static.xsl
>>>>>
>>>>>
>>>>> list.fluxcms a écrit :
>>>>>> I use following code in my xsl-stylesheets: (this is master.xsl)
>>>>>>
>>>>>> <xsl:stylesheet version="1.0"
>>>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>>>> xmlns="http://www.w3.org/1999/xhtml"
>>>>>> xmlns:forms="http://bitflux.org/forms"
>>>>>> xmlns:php="http://php.net/xsl"
>>>>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>>>>> exclude-result-prefixes="xhtml forms php i18n"
>>>>>>
>>>>>> >
>>>>>> <xsl:import href="../standard/mastercommon.xsl" />
>>>>>> <xsl:output encoding="utf-8" method="xml"
>>>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>>>>
>>>>>> And I added to ../standard/mastercommon.xsl:
>>>>>>
>>>>>> <xsl:stylesheet version="1.0"
>>>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>>>> xmlns="http://www.w3.org/1999/xhtml"
>>>>>> xmlns:forms="http://bitflux.org/forms"
>>>>>> xmlns:php="http://php.net/xsl"
>>>>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>>>>> exclude-result-prefixes="xhtml forms php i18n"
>>>>>>
>>>>>> >
>>>>>> <xsl:output encoding="utf-8" method="xml"
>>>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>>>>
>>>>>>
>>>>>> But still -- Transitional :-(
>>>>>>
>>>>>> Thomas.
>>>>>>
>>>>
>>>>
>>>>
>>>> Thomas.
>>>>
>>>> ----------------------------------------------------------------
>>>> This message was sent using IMP, the Internet Messaging Program.
>>>>
>>
>>
>>
>> Thomas.
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:31:10Z

If you don't mention XHTML Transitional nowhere but still see it generated, then it is a supernatural...
Nothing I can do for that ;-)

list.fluxcms a écrit :

OK. But my mytheme/staticl.xsl starts:

<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:i18n="http://apache.org/cocoon/i18n/2.1" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="xhtml">
    <xsl:import href="../standard/common.xsl"/>
    <xsl:import href="master.xsl"/>

    <xsl:output encoding="utf-8" method="xml"
    doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
    doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

And my ../standard/common.xsl:

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:xhtml="http://www.w3.org/1999/xhtml"
    xmlns="http://www.w3.org/1999/xhtml"
    xmlns:php="http://php.net/xsl"
    xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
    xmlns:blog="http://bitflux.org/doctypes/blog"
    exclude-result-prefixes="xhtml php blog i18n"
    >

    <xsl:output encoding="utf-8" method="xml"
    doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
    doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

Thomas.

Zitat von florent Claude florent@...:

I meant : By default, the first xsl to be called is
/themes/your_theme/static.xsl

list.fluxcms a écrit :

And that, what my standard/static.xsl is looking:

<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns="http://www.w3.org/1999/xhtml">
   <xsl:output encoding="utf-8" method="xml"
   doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
   doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
   <xsl:template match="/">

       <html>

           <xsl:call-template name="htmlhead"/>

But the result: still: transitional :-/

Thomas.

Zitat von florent Claude florent@...:

By default, the first xsl to be called is static.xsl

list.fluxcms a écrit :

I use following code in my xsl-stylesheets: (this is master.xsl)

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
      xmlns:xhtml="http://www.w3.org/1999/xhtml"
      xmlns="http://www.w3.org/1999/xhtml"
      xmlns:forms="http://bitflux.org/forms"
      xmlns:php="http://php.net/xsl"
      xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
      exclude-result-prefixes="xhtml forms php i18n"

      >
<xsl:import href="../standard/mastercommon.xsl" />
<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

And I added to ../standard/mastercommon.xsl:

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
      xmlns:xhtml="http://www.w3.org/1999/xhtml"
      xmlns="http://www.w3.org/1999/xhtml"
      xmlns:forms="http://bitflux.org/forms"
      xmlns:php="http://php.net/xsl"
   xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
      exclude-result-prefixes="xhtml forms php i18n"

      >
<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

But still -- Transitional :-(

Thomas.

Thomas.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

Thomas.

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:16:13Z

OK. But my mytheme/staticl.xsl starts:

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml" exclude-result-prefixes="xhtml">
<xsl:import href="../standard/common.xsl"/>
<xsl:import href="master.xsl"/>

<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

And my ../standard/common.xsl:

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:php="http://php.net/xsl"
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
xmlns:blog="http://bitflux.org/doctypes/blog"
exclude-result-prefixes="xhtml php blog i18n"
>

<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

Thomas.

Zitat von florent Claude <florent@...>:

> I meant : By default, the first xsl to be called is
> /themes/your_theme/static.xsl
>
>
>
> list.fluxcms a écrit :
>> And that, what my standard/static.xsl is looking:
>>
>>
>> <?xml version="1.0"?>
>> <xsl:stylesheet version="1.0"
>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>> xmlns="http://www.w3.org/1999/xhtml">
>> <xsl:output encoding="utf-8" method="xml"
>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>> <xsl:template match="/">
>>
>> <html>
>>
>> <xsl:call-template name="htmlhead"/>
>>
>> But the result: still: transitional :-/
>>
>> Thomas.
>>
>>
>> Zitat von florent Claude <florent@...>:
>>
>>> By default, the first xsl to be called is static.xsl
>>>
>>>
>>> list.fluxcms a écrit :
>>>> I use following code in my xsl-stylesheets: (this is master.xsl)
>>>>
>>>> <xsl:stylesheet version="1.0"
>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>> xmlns="http://www.w3.org/1999/xhtml"
>>>> xmlns:forms="http://bitflux.org/forms"
>>>> xmlns:php="http://php.net/xsl"
>>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>>> exclude-result-prefixes="xhtml forms php i18n"
>>>>
>>>> >
>>>> <xsl:import href="../standard/mastercommon.xsl" />
>>>> <xsl:output encoding="utf-8" method="xml"
>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>>
>>>> And I added to ../standard/mastercommon.xsl:
>>>>
>>>> <xsl:stylesheet version="1.0"
>>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>>> xmlns="http://www.w3.org/1999/xhtml"
>>>> xmlns:forms="http://bitflux.org/forms"
>>>> xmlns:php="http://php.net/xsl"
>>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>>> exclude-result-prefixes="xhtml forms php i18n"
>>>>
>>>> >
>>>> <xsl:output encoding="utf-8" method="xml"
>>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>>
>>>>
>>>> But still -- Transitional :-(
>>>>
>>>> Thomas.
>>>>
>>
>>
>>
>> Thomas.
>>
>> ----------------------------------------------------------------
>> This message was sent using IMP, the Internet Messaging Program.
>>

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:14:14Z

My pipeline is start.xsl.

Zitat von Philipp Stucki <philipp@...>:

> list.fluxcms wrote:
>
>> How can I see which stylesheet is invoked first?
>
> By default this is static.xsl, but this can be changed in .configxml
> using the xslt parameter:
>
> <parameter name="xslt" type="pipeline" value="start.xsl"/>
>
>> Is there a way to see this with FirePHP or another debug-snippet?
>> (Please send us a hint how to invoke FirePHP in xxx.xsl).
>
> No AFAIK.
>
>> I verify the doctype currently only with
>>
>> wget 'http://fluxcms/' -O - 2>/dev/null | head -1
>
> That's good because browsers tend to screw this up.
>
>
> Philipp
>
> --
> Philipp Stucki
> Eibenstrasse 5
> 8045 Zürich
>
> philipp@...
> http://qwert.ch
>
>

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:12:46Z

I meant : By default, the first xsl to be called is
/themes/your_theme/static.xsl

list.fluxcms a écrit :

> And that, what my standard/static.xsl is looking:
>
>
> <?xml version="1.0"?>
> <xsl:stylesheet version="1.0"
> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> xmlns:xhtml="http://www.w3.org/1999/xhtml"
> xmlns="http://www.w3.org/1999/xhtml">
> <xsl:output encoding="utf-8" method="xml"
> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
> <xsl:template match="/">
>
> <html>
>
> <xsl:call-template name="htmlhead"/>
>
> But the result: still: transitional :-/
>
> Thomas.
>
>
> Zitat von florent Claude <florent@...>:
>
>> By default, the first xsl to be called is static.xsl
>>
>>
>> list.fluxcms a écrit :
>>> I use following code in my xsl-stylesheets: (this is master.xsl)
>>>
>>> <xsl:stylesheet version="1.0"
>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>> xmlns="http://www.w3.org/1999/xhtml"
>>> xmlns:forms="http://bitflux.org/forms"
>>> xmlns:php="http://php.net/xsl"
>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>> exclude-result-prefixes="xhtml forms php i18n"
>>>
>>> >
>>> <xsl:import href="../standard/mastercommon.xsl" />
>>> <xsl:output encoding="utf-8" method="xml"
>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>
>>> And I added to ../standard/mastercommon.xsl:
>>>
>>> <xsl:stylesheet version="1.0"
>>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>>> xmlns="http://www.w3.org/1999/xhtml"
>>> xmlns:forms="http://bitflux.org/forms"
>>> xmlns:php="http://php.net/xsl"
>>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>>> exclude-result-prefixes="xhtml forms php i18n"
>>>
>>> >
>>> <xsl:output encoding="utf-8" method="xml"
>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>
>>>
>>> But still -- Transitional :-(
>>>
>>> Thomas.
>>>
>
>
>
> Thomas.
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:11:24Z

list.fluxcms wrote:

> How can I see which stylesheet is invoked first?

By default this is static.xsl, but this can be changed in .configxml
using the xslt parameter:

<parameter name="xslt" type="pipeline" value="start.xsl"/>

> Is there a way to see this with FirePHP or another debug-snippet?
> (Please send us a hint how to invoke FirePHP in xxx.xsl).

No AFAIK.

> I verify the doctype currently only with
>
> wget 'http://fluxcms/' -O - 2>/dev/null | head -1

That's good because browsers tend to screw this up.

Philipp

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:11:10Z

And that, what my standard/static.xsl is looking:

<?xml version="1.0"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml">
<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
<xsl:template match="/">

<html>

<xsl:call-template name="htmlhead"/>

But the result: still: transitional :-/

Thomas.

Zitat von florent Claude <florent@...>:

> By default, the first xsl to be called is static.xsl
>
>
> list.fluxcms a écrit :
>> I use following code in my xsl-stylesheets: (this is master.xsl)
>>
>> <xsl:stylesheet version="1.0"
>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>> xmlns="http://www.w3.org/1999/xhtml"
>> xmlns:forms="http://bitflux.org/forms"
>> xmlns:php="http://php.net/xsl"
>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>> exclude-result-prefixes="xhtml forms php i18n"
>>
>> >
>> <xsl:import href="../standard/mastercommon.xsl" />
>> <xsl:output encoding="utf-8" method="xml"
>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>
>> And I added to ../standard/mastercommon.xsl:
>>
>> <xsl:stylesheet version="1.0"
>> xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
>> xmlns:xhtml="http://www.w3.org/1999/xhtml"
>> xmlns="http://www.w3.org/1999/xhtml"
>> xmlns:forms="http://bitflux.org/forms"
>> xmlns:php="http://php.net/xsl"
>> xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
>> exclude-result-prefixes="xhtml forms php i18n"
>>
>> >
>> <xsl:output encoding="utf-8" method="xml"
>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>
>>
>> But still -- Transitional :-(
>>
>> Thomas.
>>

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:07:09Z

By default, the first xsl to be called is static.xsl

list.fluxcms a écrit :

I use following code in my xsl-stylesheets: (this is master.xsl)

<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
        xmlns:xhtml="http://www.w3.org/1999/xhtml"
        xmlns="http://www.w3.org/1999/xhtml"
        xmlns:forms="http://bitflux.org/forms"
        xmlns:php="http://php.net/xsl"
        xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
        exclude-result-prefixes="xhtml forms php i18n"

        >
    <xsl:import href="../standard/mastercommon.xsl" />
    <xsl:output encoding="utf-8" method="xml"
    doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
    doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

And I added to ../standard/mastercommon.xsl:

<xsl:stylesheet version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
        xmlns:xhtml="http://www.w3.org/1999/xhtml"
        xmlns="http://www.w3.org/1999/xhtml"
        xmlns:forms="http://bitflux.org/forms"
        xmlns:php="http://php.net/xsl"
     xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
        exclude-result-prefixes="xhtml forms php i18n"

        >
    <xsl:output encoding="utf-8" method="xml"
    doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
    doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>


But still -- Transitional :-(

Thomas.

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T13:02:55Z

I use following code in my xsl-stylesheets: (this is master.xsl)

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:forms="http://bitflux.org/forms"
xmlns:php="http://php.net/xsl"
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
exclude-result-prefixes="xhtml forms php i18n"

>
<xsl:import href="../standard/mastercommon.xsl" />
<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

And I added to ../standard/mastercommon.xsl:

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:forms="http://bitflux.org/forms"
xmlns:php="http://php.net/xsl"
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
exclude-result-prefixes="xhtml forms php i18n"

>
<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

But still -- Transitional :-(

Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T12:55:22Z

Hi Philipp,

Thanks for your answer.
How can I see which stylesheet is invoked first?
Is there a way to see this with FirePHP or another debug-snippet?
(Please send us a hint how to invoke FirePHP in xxx.xsl).

I verify the doctype currently only with

wget 'http://fluxcms/' -O - 2>/dev/null | head -1

Thomas.

On Tue, 17 Nov 2009 21:46:34 +0100, Philipp Stucki <philipp@...>
wrote:

> Hi thomas
>
>
> The doctype is generated by libxslt using the xsl:output element of the
> stylesheet invoked first (might be different from master.xsl)
>
> I shortly checked this with one of my projects and it works without any
> problems.
>
> How do you verify if the doctype is correct?
>
>
> Philipp
>
>
> http://www.w3.org/TR/xslt#output
>
> list.fluxcms wrote:
>> Hi developers,
>>
>> I'm on the end.
>> I nearly updated all files which contained "Transitional" to "Strict"

but
>> still the first line in the source code is DOCTYPE html PUBLIC
>> "-//W3C//DTD XHTML 1.0 Transitional//EN"
>>
>> WHERE is this line created?
>> HOW can I change the DOCTYPE to Strict???
>>
>> Thanks for your reply in advance.
>>
>> Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T12:46:34Z

Hi thomas

The doctype is generated by libxslt using the xsl:output element of the
stylesheet invoked first (might be different from master.xsl)

I shortly checked this with one of my projects and it works without any
problems.

How do you verify if the doctype is correct?

Philipp

http://www.w3.org/TR/xslt#output

list.fluxcms wrote:

> Hi developers,
>
> I'm on the end.
> I nearly updated all files which contained "Transitional" to "Strict" but
> still the first line in the source code is DOCTYPE html PUBLIC
> "-//W3C//DTD XHTML 1.0 Transitional//EN"
>
> WHERE is this line created?
> HOW can I change the DOCTYPE to Strict???
>
> Thanks for your reply in advance.
>
> Thomas.

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT - question to the developers

2009-11-17T12:23:35Z

Hi developers,

I'm on the end.
I nearly updated all files which contained "Transitional" to "Strict" but
still the first line in the source code is DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN"

WHERE is this line created?
HOW can I change the DOCTYPE to Strict???

Thanks for your reply in advance.

Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: extending options to admin interface (dbform)

2009-11-17T11:36:46Z

Hi Thomas,

[by the way, my name is florent , not Claude :-) ]

I made an update on 'my' plugin : http://dl.dropbox.com/u/1274719/maxtree.php

With this, you can specify the starting point of the returned tree :

Use the plugin like that :
<plugin type="maxtree">
<parameter name="rootpath" value="/path/to/folder/" />
</plugin>

If no rootpath is mentionned, it will build the whole tree.

Hope it suits your needs,
florent/.

list.fluxcms a écrit :

Great work. Thanks Claude.
Is it possible (and how) to extend the plugin to use
a parameter (xpath query for example) to get with a
plugin like this all information and only the information 
really needed?

Thanks for your reply.

Thomas.

On Tue, 17 Nov 2009 16:52:31 +0100, florent Claude florent@...
wrote:

I am not a great at php but you should be able to get only part of the 
fulltree by editing correctly the plugin.

By the way, I have updated this plugin (which I called maxtree now) : 
http://dl.dropbox.com/u/1274719/maxtree.php
I added the root collection as first node and, following your remark on 
the information been too big, I removed the fulltext properties.
It works fine for me ONLY IF I don't use the sitemap plugin.
Is this because I used the original sitemap php code in the maxtree

plugin?

florent/.


list.fluxcms a écrit :

This works. Thank you - but makes the Information bigger.
Is there a possibility how to combine this with a xpath query 
to get e.g. only the current node and its neighbours and not the
fulltree? (I know the name is fulltree and it works like this).

Thanks for your reply in advance.

Thomas.

On Sun, 15 Nov 2009 13:26:30 +0100, florent Claude florent@...
wrote:

I also wondered how to get any property value from anywhere on the

site?

To do so, I created the fulltree2 plugin by tweaking the sitemap

plugin

    
        

Want to try? Download fulltree2.php at 
http://dl.dropbox.com/u/1274719/fulltree2.php
and place it in in /localinc/bx/plugins/

then edit your site configs :
 - http://yoursite.com/admin/edit/.configxml?editor=oneform
 - http://yoursite.com/admin/edit/.configxml.children?editor=oneform

in each file, add this line  :
    <plugin type="fulltree2"></plugin>

Voilà! That's it. You should be able to access all properties from the

public interface of your site. (http://yoursite.com/?XML=1 for

example).

florent/.


list.fluxcms a écrit :

Hmmm. Not so easy :-(

My custom field for my resource is shown in the Admin Interface, and

is

shown in the database as well. 
But it is not shown when I perform the XML=1 view of my page.
Is there sitll anything to extend?
I thought the XML view shows all the database, and even the empty
elements?

How can I either check, if my custom-field is useable in my XSL?

Thanks for your help in advance.

Thomas.

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: extending options to admin interface (dbform)

2009-11-17T11:07:50Z

Great work. Thanks Claude.
Is it possible (and how) to extend the plugin to use
a parameter (xpath query for example) to get with a
plugin like this all information and only the information
really needed?

Thanks for your reply.

Thomas.

On Tue, 17 Nov 2009 16:52:31 +0100, florent Claude <florent@...>
wrote:
> I am not a great at php but you should be able to get only part of the
> fulltree by editing correctly the plugin.
>
> By the way, I have updated this plugin (which I called maxtree now) :
> http://dl.dropbox.com/u/1274719/maxtree.php
> I added the root collection as first node and, following your remark on
> the information been too big, I removed the fulltext properties.
> It works fine for me ONLY IF I don't use the sitemap plugin.
> Is this because I used the original sitemap php code in the maxtree
plugin?

>
> florent/.
>
>
> list.fluxcms a écrit :
>> This works. Thank you - but makes the Information bigger.
>> Is there a possibility how to combine this with a xpath query
>> to get e.g. only the current node and its neighbours and not the
>> fulltree? (I know the name is fulltree and it works like this).
>>
>> Thanks for your reply in advance.
>>
>> Thomas.
>>
>> On Sun, 15 Nov 2009 13:26:30 +0100, florent Claude <florent@...>
>> wrote:
>>
>>> I also wondered how to get any property value from anywhere on the

site?
>>> To do so, I created the fulltree2 plugin by tweaking the sitemap
plugin

>>>
>> :
>>
>>> Want to try? Download fulltree2.php at
>>> http://dl.dropbox.com/u/1274719/fulltree2.php
>>> and place it in in /localinc/bx/plugins/
>>>
>>> then edit your site configs :
>>> - http://yoursite.com/admin/edit/.configxml?editor=oneform
>>> - http://yoursite.com/admin/edit/.configxml.children?editor=oneform
>>>
>>> in each file, add this line :
>>> <plugin type="fulltree2"></plugin>
>>>
>>> Voilà! That's it. You should be able to access all properties from the

>>> public interface of your site. (http://yoursite.com/?XML=1 for
example).
>>>
>>> florent/.
>>>
>>>
>>> list.fluxcms a écrit :
>>>
>>>> Hmmm. Not so easy :-(
>>>>
>>>> My custom field for my resource is shown in the Admin Interface, and
is

>>>> shown in the database as well.
>>>> But it is not shown when I perform the XML=1 view of my page.
>>>> Is there sitll anything to extend?
>>>> I thought the XML view shows all the database, and even the empty
>>>> elements?
>>>>
>>>> How can I either check, if my custom-field is useable in my XSL?
>>>>
>>>> Thanks for your help in advance.
>>>>
>>>> Thomas.
>>>>
>>>>

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT

2009-11-17T08:17:35Z

Sorry I don't have the answer just like that.
I remember changing that before although...

list.fluxcms a écrit :

> Hi Claude,
>
> I still changed all in themes/standard/*.xsl with output, but still my
> HTML Source Code shows
>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <html xmlns="http://www.w3.org/1999/xhtml" lang="de" xml:lang="de">
>
> But I need it to XHTML 1.0 Strict!! I even performed a grep through the
> filesystem.
> I dont know which process creates the 1st DOCTYPE line in fluxcms.
>
> Do you have any other ideas?
>
> Thanks for your reply in advance.
>
> Thomas.
>
> btw. the mastercommon.xsl doesnt contain any output information in my svn
> core.
>
> On Tue, 17 Nov 2009 16:54:58 +0100, florent Claude <florent@...>
> wrote:
>
>> maybe look in /themes/standard/mastercommon.xsl ?
>>
>>
>>
>> list.fluxcms a écrit :
>>
>>> Hi,
>>>
>>> I changed all lines in themes/mytheme/*.xsl to
>>>
>>> <xsl:output encoding="utf-8" method="xml"
>>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>>
>>> but the Browser's show HTML Source still shows
>>>
>>> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>>> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>>>
>>> What else has to be changed to get strict 1.0 working ?
>>>
>>> Thanks for your reply in advance.
>>>
>>> Thomas.
>>>
>> >

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: change doctype to XHTML1.0 STRICT

2009-11-17T08:09:19Z

Hi Claude,

I still changed all in themes/standard/*.xsl with output, but still my
HTML Source Code shows

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="de" xml:lang="de">

But I need it to XHTML 1.0 Strict!! I even performed a grep through the
filesystem.
I dont know which process creates the 1st DOCTYPE line in fluxcms.

Do you have any other ideas?

Thanks for your reply in advance.

Thomas.

btw. the mastercommon.xsl doesnt contain any output information in my svn
core.

On Tue, 17 Nov 2009 16:54:58 +0100, florent Claude <florent@...>
wrote:

> maybe look in /themes/standard/mastercommon.xsl ?
>
>
>
> list.fluxcms a écrit :
>> Hi,
>>
>> I changed all lines in themes/mytheme/*.xsl to
>>
>> <xsl:output encoding="utf-8" method="xml"
>> doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
>> doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>
>>
>> but the Browser's show HTML Source still shows
>>
>> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>> "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>>
>> What else has to be changed to get strict 1.0 working ?
>>
>> Thanks for your reply in advance.
>>
>> Thomas.
>>

<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns="http://www.w3.org/1999/xhtml"
xmlns:forms="http://bitflux.org/forms"
xmlns:php="http://php.net/xsl"
xmlns:i18n="http://apache.org/cocoon/i18n/2.1"
exclude-result-prefixes="xhtml forms php i18n"

>
<xsl:param name="webroot"/>

<xsl:template name="html_head_scripts">
<xsl:call-template name="html_head_scripts_default"/>
</xsl:template>

<xsl:template name="html_head_scripts_default">
<xsl:text>
</xsl:text>
<xsl:for-each select="/bx/javascripts/src">
<script type="text/javascript" src="{$webroot}{text()}"></script>
<xsl:text>
</xsl:text>
</xsl:for-each>
</xsl:template>

<xsl:template name="html_head_custom">
</xsl:template>

</xsl:stylesheet>

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: extending options to admin interface (dbform)

2009-11-17T07:52:31Z

I am not a great at php but you should be able to get only part of the fulltree by editing correctly the plugin.

By the way, I have updated this plugin (which I called maxtree now) : http://dl.dropbox.com/u/1274719/maxtree.php
I added the root collection as first node and, following your remark on the information been too big, I removed the fulltext properties.
It works fine for me ONLY IF I don't use the sitemap plugin.
Is this because I used the original sitemap php code in the maxtree plugin?

florent/.

list.fluxcms a écrit :

This works. Thank you - but makes the Information bigger.
Is there a possibility how to combine this with a xpath query 
to get e.g. only the current node and its neighbours and not the
fulltree? (I know the name is fulltree and it works like this).

Thanks for your reply in advance.

Thomas.

On Sun, 15 Nov 2009 13:26:30 +0100, florent Claude florent@...
wrote:

I also wondered how to get any property value from anywhere on the site?
To do so, I created the fulltree2 plugin by tweaking the sitemap plugin

Want to try? Download fulltree2.php at 
http://dl.dropbox.com/u/1274719/fulltree2.php
and place it in in /localinc/bx/plugins/

then edit your site configs :
 - http://yoursite.com/admin/edit/.configxml?editor=oneform
 - http://yoursite.com/admin/edit/.configxml.children?editor=oneform

in each file, add this line  :
    <plugin type="fulltree2"></plugin>

Voilà! That's it. You should be able to access all properties from the 
public interface of your site. (http://yoursite.com/?XML=1 for example).

florent/.


list.fluxcms a écrit :

Hmmm. Not so easy :-(

My custom field for my resource is shown in the Admin Interface, and is
shown in the database as well. 
But it is not shown when I perform the XML=1 view of my page.
Is there sitll anything to extend?
I thought the XML view shows all the database, and even the empty
elements?

How can I either check, if my custom-field is useable in my XSL?

Thanks for your help in advance.

Thomas.

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

twitter feeds not working

2009-11-16T13:42:59Z

Hi,

Did sb get
https://fosswiki.liip.ch/display/FLX/Display+your+Twitter+tweets
working?

I got the same problems as anonymous in the WIKI.

What has to be enabled to get the cache module working?

Thanks for your reply in advance.

Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: conditional IE stylesheets in master.xsl

2009-11-15T23:59:18Z

list.fluxcms wrote:
> What is the correct syntax to get this comments appear in the HTML source
> code? Or do I really have to take a CDATA?

Here's an example. You will have to replace all XSL variables inside the
CDATA section with their respective values.

<xsl:comment>
<![CDATA[[if gte IE 6]>
<link rel="stylesheet" type="text/css" media="screen"
href="/themes/mytheme/css/ie.css" />
<![endif]]]>
</xsl:comment>

Philipp

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: conditional IE stylesheets in master.xsl

2009-11-15T23:36:04Z

list.fluxcms schrieb 2009-11-14 23:00:

> <!--[if lte IE 6]>
> What is the correct syntax to get this comments appear in the HTML source
> code? Or do I really have to take a CDATA?

The way to go is xsl:comment + CDATA, yes.

Don't forget to show us what you're working on when done :)

Hannes

--
Liip AG // Agile Web Development // T +41 43 500 39 82
Feldstrasse 133 // CH - 8004 Zürich // GPG 0x9EA04604
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

change doctype to XHTML1.0 STRICT

2009-11-15T13:26:03Z

Hi,

I changed all lines in themes/mytheme/*.xsl to

<xsl:output encoding="utf-8" method="xml"
doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"
doctype-public="-//W3C//DTD XHTML 1.0 Strict//EN"/>

but the Browser's show HTML Source still shows

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

What else has to be changed to get strict 1.0 working ?

Thanks for your reply in advance.

Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: extending options to admin interface (dbform)

2009-11-15T05:30:59Z

This works. Thank you - but makes the Information bigger.
Is there a possibility how to combine this with a xpath query
to get e.g. only the current node and its neighbours and not the
fulltree? (I know the name is fulltree and it works like this).

Thanks for your reply in advance.

Thomas.

On Sun, 15 Nov 2009 13:26:30 +0100, florent Claude <florent@...>
wrote:
> I also wondered how to get any property value from anywhere on the site?
> To do so, I created the fulltree2 plugin by tweaking the sitemap plugin
:

>
> Want to try? Download fulltree2.php at
> http://dl.dropbox.com/u/1274719/fulltree2.php
> and place it in in /localinc/bx/plugins/
>
> then edit your site configs :
> - http://yoursite.com/admin/edit/.configxml?editor=oneform
> - http://yoursite.com/admin/edit/.configxml.children?editor=oneform
>
> in each file, add this line :
> <plugin type="fulltree2"></plugin>
>
> Voilà! That's it. You should be able to access all properties from the
> public interface of your site. (http://yoursite.com/?XML=1 for example).
>
> florent/.
>
>
> list.fluxcms a écrit :
>> Hmmm. Not so easy :-(
>>
>> My custom field for my resource is shown in the Admin Interface, and is
>> shown in the database as well.
>> But it is not shown when I perform the XML=1 view of my page.
>> Is there sitll anything to extend?
>> I thought the XML view shows all the database, and even the empty
>> elements?
>>
>> How can I either check, if my custom-field is useable in my XSL?
>>
>> Thanks for your help in advance.
>>
>> Thomas.
>>

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

conditional IE stylesheets in master.xsl

2009-11-14T14:00:09Z

Hi,

i tried to get the conditional stylesheets working with modifying my
master.xsl like this:

....
<xsl:text>

</xsl:text>
...

But when showing the source code there no IE6 comment/conditional is
shown.

What is the correct syntax to get this comments appear in the HTML source
code? Or do I really have to take a CDATA?

Thanks for your reply in advance.

Thomas.

--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

LiveSearch throws error

2009-11-12T23:06:29Z

Hi,

when I perform a Livesearch, the Livesearch is OK but the following error
is shown.

BXCMSNG Errors:
Notice[8] Uninitialized string offset: 1 in
[BX_PROJECT_DIR]/inc/bx/plugins/blog/categories.php at line 62.

What does this mean -- and how can this error been suppressed?

Thanks for your reply in advance.

Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: tidying HTML output

2009-11-12T15:05:04Z

list.fluxcms wrote:
> Question: How can the HTML Source Code being shrinked, i.e. the other way,
> just remove all spaces and line-breaks?

AFAIK this is not possible with tidy. However if tidy is disabled in
sitemap.xml no extra whitespace will be added.

Philipp

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: redirect of a resource

2009-11-12T14:46:02Z

Setting @relink or @redirect on resources is not currently possible.
I'd opt for mod_rewrite in this case but don't remember the actual rules
right now.

HTH
Philipp

list.fluxcms wrote:

> Hi
>
> is it possible (and how) to perform a redirect of a resource to another
> resource,
> e.g.
>
> I have /contact/impressum.html and want this URL redirected to
> /imprint/index.html
>
> (Due to old fragments in search-engines I want to redirect old pages to
> the new ones,
> if possible with sending a 301 moved permanently).
>
> Thanks for your reply in advance.
>
> Thomas.

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: redirect/relink question

2009-11-12T14:43:06Z

These properties depend on the theme you're using and whether it has
been modified or not.

@relink is resolved at XSL level in the master stylesheet:
http://fisheye.liip.ch/browse/PUB/fluxcms_demo/trunk/themes/3-cols/master.xsl?r=HEAD#l181

To link a resource to an external link set @relink to http://othersite.com

@redirect is handled at request level in the cms and does not change the
href attribute. e.g.: let /abc, /def be collections, setting @redirect
on /abc to "/def/index.html" would make /abc an alias of /def/index.html

HTH
Philipp

list.fluxcms wrote:

> I need to realize a redirect of the collection named "stellenanzeigen" to
> the collection "jobs" which already has content and resources in it.
> So I created the collection and edited the properties of collection
> "stellenanzeigen", and put in
>
> bx::redirect -- /jobs
>
> But the system answers with "/stellenanzeigen/ not found" but "/jobs/" is
> working.
>
> Can you give me a hint why it is not working? (I tried the same with
> bx::relink which was not working as well).
>
> Second question:
>
> Is it possible to let a collection or resource point to an external URL,
> e.g. I create a collection "fluxcms" with properties
>
> bx::redirect -- http://www.liip.ch
>
> and want to redirect all to liip.ch ?
>
> Thanks for your help in advance.
>
> Thomas.

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: tidying HTML output

2009-11-12T14:29:08Z

OK, Thanks, Philipp,
I just want It for easier debugging, not for the live site.

Question: How can the HTML Source Code being shrinked, i.e. the other way,
just remove all spaces and line-breaks?
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

redirect of a resource

2009-11-12T14:26:50Z

Hi

is it possible (and how) to perform a redirect of a resource to another
resource,
e.g.

I have /contact/impressum.html and want this URL redirected to
/imprint/index.html

(Due to old fragments in search-engines I want to redirect old pages to
the new ones,
if possible with sending a 301 moved permanently).

Thanks for your reply in advance.

Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: XSL Snippet just for displaying level=2

2009-11-12T14:24:13Z

This should be working for only the second level.

<xsl:value-of
select="/bx/plugin[@name='navitree']/collection/items/collection[@selected='selected']/uri"
/>

Thomas.
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms

Re: tidying HTML output

2009-11-12T14:17:15Z

To enable tidy on the standard output pipeline you need to uncomment the
according section in sitemap/sitemap.xml (about line 261)

Set "indent" to "yes" if you need indenting on the source.

Keep in mind enabling this will process every request using tidy which
might have drawbacks on performance. If your main intention is to make
the source readable consider using a add-on in your browser like html
validator or something equivalent.

HTH
Philipp

list.fluxcms wrote:
> Hi,
>
> is there an easy way to tidy HTML output?
> Currently the code is valid but not readeable.
> php5-tidy is available on my server.
>
> Thanks for your reply in advance.
>
> Thomas.

--
Philipp Stucki
Eibenstrasse 5
8045 Zürich

philipp@...
http://qwert.ch
--
bitflux-cms mailing list
bitflux-cms@...
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms