AW: AW: [opencms-dev] Opencms6.0 beta2, microsite, _configuration
patrick
pat at www.monmien.com
Fri Apr 8 16:09:18 CEST 2005
Thanks Andreas, it is working now.
I spent some time trying to understand what happened, and I found the
following reproductible behaviour, which I think is not normal.
Here is how you can reproduce it (I did it twice):
- I create a microsite ('test' is his name) and do NOT fill in the
style_main_configpath field
- I create an index.html in the microsite root folder and fill dummy
content.
- I publish the site, background color is white. Normal.
- I edit the microsite's 'style_main_configpath' to
'/test/_configuration/' (with a '/' at the end as per your email)
- I publish it
- Background color is still white. Normal this is the default value of
the _configuration/configuration_css file.
- I change the value of the _configuration/configuration_css file
(property 'content background') of the microsite folder.
- I publish it.
- the changes do NOT appear! Neither in Offline nor in Online mode.
Background is still white. Oups...
now the fun part:
- I replace in the microsite folder 'style_main_configpath' property
'/test/_configuration/' by the full path:
'/sites/default/test/_configuration/'.
- I publish
- In OFFLINE mode: I do see my changes! Background is blue.
- In ONLINE mode: I still do NOT see the changes! Background is white.
- I re-edit the 'style_main_configpath' property of the microsite folder
to '/test/_configuration'
- I publish
- In OFFLINE mode: the background has reverted to white. (!)
- In ONLINE mode: the backgournd is blue. (!)
I hope this helps.
I do have a question though: is there a link in the documentation with
the effect of each property on the template one demo? (some properties
are pretty self explanatory, but... not all of them :=))
OpenCms Rocks!! and Microsites are killers!
Vielen Dank!
Patrick
>Patrick,
>
>be sure that the property value of your path ends with a slash "/", and do
>not use the full root resource path. So use "/Microsite/_configuration/" as
>property value without including the site folder prefix.
>
>Regards,
>
>Andreas Zahner
>Alkacon Software - The OpenCms Experts
>http://www.alkacon.com
>
>-----Ursprüngliche Nachricht-----
>Von: opencms-dev-bounces at opencms.org
>[mailto:opencms-dev-bounces at opencms.org] Im Auftrag von patrick
>Gesendet: Freitag, 8. April 2005 13:25
>An: The OpenCms mailing list
>Betreff: Re: AW: [opencms-dev] Opencms6.0 beta2, microsite, _configuration
>
>Hi Andreas, thanks for the quick answer!
>
>-I have added in the microsite property 'style_main_configpath' the full
>path '/sites/default/mymicrosite/_configuration/' (with just
>'/mymicrosite/_configuration', as stated in your email, it was not working),
>and when viewing inthe page in OFFLINE mode, I do see my changes. Cool!
>- Now I publish my site.
>- The changes do NOT appear! It is not a browser cache problem (cache
>emptied and put to 0 + browser restarted).
>- In the ONLINE site, the poperty for the 'style_main_configpath' is
>correctly set.
>- The html that OpenCms generates for the css is the folowing (the name of
>the microsite is 'Microsite'): <link
>href="/opencms/opencms/system/modules/org.opencms.frontend.templateone/resou
>rces/style.css?respath=/opencms/export/templateone/resources/&config=/sites/
>default/Microsite/_configuration/configuration_css&site=/sites/default&__loc
>ale=en" rel="stylesheet" type="text/css">
>I have no idear if this is valid.
>
>So... I am sorry... did I miss something again?
>
>Thanks,
>
>Patrick
>
>
>
>
>
>
>Andreas Zahner wrote:
>
>
>
>>Patrick,
>>
>>you have to set a property value at the microsite folder, too. The property
>>"style_main_configpath" must point to the configuration folder, e.g.
>>"/mymicrosite/_configuration/". This is necessary because each page can
>>
>>
>have
>
>
>>individual configuration settings even for one microsite.
>>In the current CVS head, I fixed this problem by attaching the property
>>value on microsite folder creation. To do so, you have to adjust the
>>manifest.xml file of the template one module zip and add the following
>>property nodes to the microsite folder definition:
>>
>><type class="org.opencms.file.types.CmsResourceTypeFolderExtended"
>>name="microsite" id="19">
>> <properties>
>> <property>
>> <name>style_main_configpath</name>
>>
>><value><![CDATA[${resource.folder.path}_configuration/]]></value>
>> </property>
>> </properties>
>> <copy-resources>
>> <copy-resource
>>source="/system/modules/org.opencms.frontend.templateone/copyresources/_con
>>
>>
>f
>
>
>>iguration" target="${resource.folder.path}" type="new"/>
>> </copy-resources>
>> </type>
>>
>>Hth!
>>Regards,
>>
>>Andreas Zahner
>>Alkacon Software - The OpenCms Experts
>>http://www.alkacon.com
>>
>>-----Ursprüngliche Nachricht-----
>>Von: opencms-dev-bounces at opencms.org
>>[mailto:opencms-dev-bounces at opencms.org] Im Auftrag von patrick
>>Gesendet: Freitag, 8. April 2005 12:29
>>An: opencms-dev at opencms.org
>>Betreff: [opencms-dev] Opencms6.0 beta2, microsite, _configuration
>>
>>Hi!
>>The microsite functionality new from b2 seems extremely interesting for
>>me! I do have problems making it work though: I cannot configure it
>>properly on a per-microsite basis.
>>
>>What I did:
>>- in the Default web site, I create 2 microsites (m1 and m2). I am
>>always using the Template One demo as a template.
>>- In each microsite folder, I do have a _configuration folder which
>>contains various configuration elements
>>- I would like to have a blue text background on microsite m1 and a gray
>>one on m2. So I go to the m1/_configuration/configuration_css and change
>>the appropriate value (content-background) and do the same with m2.
>>- I am still having the default white background; in other words, the
>>values are not taking into accounts.
>>- This happens wether I publish or not.
>>
>>What I am missing?
>>
>>OpenCms6.0 beta 2, tomcat 5.5.9, jdk1.5, mysql 4.1.11, slackware.
>>
>>Thanks,
>>
>>Patrick
>>
>>
>>
>>_______________________________________________
>>This mail is send to you from the opencms-dev mailing list
>>To change your list options, or to unsubscribe from the list, please visit
>>http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>>
>>
>>_______________________________________________
>>This mail is send to you from the opencms-dev mailing list
>>To change your list options, or to unsubscribe from the list, please visit
>>http://mail.opencms.org/mailman/listinfo/opencms-dev
>>
>>
>>
>>
>
>
>
>_______________________________________________
>This mail is send to you from the opencms-dev mailing list
>To change your list options, or to unsubscribe from the list, please visit
>http://mail.opencms.org/mailman/listinfo/opencms-dev
>
>
>
>_______________________________________________
>This mail is send to you from the opencms-dev mailing list
>To change your list options, or to unsubscribe from the list, please visit
>http://mail.opencms.org/mailman/listinfo/opencms-dev
>
>
More information about the opencms-dev
mailing list