[opencms-dev] Publishing problems

Wed Sep 3 11:31:54 CEST 2014

Hi Fabian,

yes this is the browser generated HTML, the template code is below that ;-)

Cheers,
Gerhard

Am 03.09.2014 11:29, schrieb fhsubscriptions at componio.net:
> Hi Gerhard,
>
> Am 03.09.2014 11:17, schrieb Gerhard:
>> <script type="text/javascript" 
>> src="/../../configuration/js/javascriptfile3.js"></script>
> This is not a typical OpenCms link. Do you make use of the <cms:link 
> /> tag?
> Can you further post how a link to another OpenCms hosted page looks 
> like?_
>
> _Thanks,
>
> \Fabian
> _
> __
> _
>> _</head> __
>> ____
>> __We include all static files like pictures, CSS, JavaScript-files 
>> like this: __
>> ____
>> __<div class="icon"> __
>> __    <img src="<cms:link>/common/../../picture.png</cms:link>"> __
>> __</div> __
>> ____
>> __Files which are specified as content when editing in OpenCMS are 
>> accessed via the I_CmsXmlDocument Interface but I am not sure if you 
>> meant that too. __
>> ____
>> __I am not sure what exactly gets statically exported. I read about 
>> static export "on demand" and I guess this is the mechanism used 
>> because we never do a manual static export in the administration 
>> panel. __
>> ____
>> __Concerning that Nginx our service provider said that it is only 
>> proxying but doesn't cache anything. __
>> ____
>> __Thanks&Regards, __
>> __Gerhard __
>> ____
>> __Am 03.09.2014 10:20, schrieb Schliemann, Kai: __
>> _
>>> _Hi Gerhard, __
>>> __from inside OpenCms you can only influence, if files/folders 
>>> should be statically exported or not. This is what Fabian already 
>>> described. __
>>> __Is it possible for you to send a part of the browser generated 
>>> html source? __
>>> __The <head> section with the css / js files would be interesting. 
>>> And a part of the source, where an image, a download file and an 
>>> OpenCms internal link (to another page in OpenCms) is contained. You 
>>> could change the file names, if you do not want to name them here. I 
>>> am only interested in the path and if the files are statically 
>>> exported or not. __
>>> _ _
>>> __One other thing. Is it possible, that Nginx is working as a proxy 
>>> server and thus caching the mentioned files? __
>>> _ _
>>> __Best regards __
>>> __Kai __
>>> _ _
>>> __-----Ursprüngliche Nachricht----- __
>>> __Von: opencms-dev-bounces at opencms.org 
>>> [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Gerhard __
>>> __Gesendet: Mittwoch, 3. September 2014 09:53 __
>>> __An: The OpenCms mailing list __
>>> __Betreff: Re: [opencms-dev] Publishing problems __
>>> _ _
>>> __Hi Fabian, __
>>> _ _
>>> __ok to get some more light in the dark (for me :-): Is there a 
>>> possibility to influence the static export mechanism directly within 
>>> OpenCMS? I mean is there a place where I can plug in my own code for 
>>> the static export? __
>>> _ _
>>> __Thanks, __
>>> __Gerhard __
>>> _ _
>>> __Am 02.09.2014 12:26, schrieb fhsubscriptions at componio.net: __
>>> _
>>>> _Well, usually this is available via context menu of the resource __
>>>> __(right __
>>>> __click) -> Advanced -> Secure/Export and then see the radio button 
>>>> yes __
>>>> __| no | not set Otherwise I understood that your provider has __
>>>> __introduced its own static cache mechanism which will surely be __
>>>> __configured differently. __
>>>> _ _
>>>> __\Fabian __
>>>> _ _
>>>> __Am 02.09.2014 12:16, schrieb Gerhard: __
>>>> _
>>>>> _Hi Fabian, __
>>>>> _ _
>>>>> __ah seems to be complicated :-) __
>>>>> _ _
>>>>> __So, where can I find this static logic? (Not sure if you 
>>>>> mentioned __
>>>>> __already) __
>>>>> _ _
>>>>> __Cheers, __
>>>>> __Gerhard __
>>>>> _ _
>>>>> __Am 02.09.2014 11:48, schrieb fhsubscriptions at componio.net: __
>>>>> _
>>>>>> _Hi Gerhard, __
>>>>>> _ _
>>>>>> __again - hard to tell :-) __
>>>>>> _ _
>>>>>> __If A is the root node and the static logic from the provider 
>>>>>> does __
>>>>>> __not check if B is related to A then yes, you would have to 
>>>>>> publish both. __
>>>>>> __However this is very simple to verify: __
>>>>>> _ _
>>>>>> __Create a template A which outputs the current time and create a 
>>>>>> JSP __
>>>>>> __B which is included by the template A (via the tag <cms:include 
>>>>>> />) __
>>>>>> __which also outputs the current time. __
>>>>>> __Publish both, request template A and both time stamps should be __
>>>>>> __identically. __
>>>>>> __Then change template B and publish again. __
>>>>>> _ _
>>>>>> __Depending on how the static logic from your provider works you 
>>>>>> will __
>>>>>> __most likely have one of the following results when calling 
>>>>>> template A again: __
>>>>>> _ _
>>>>>> __- timestamp A = timestamp B = the timestamp from the first 
>>>>>> template __
>>>>>> __call (Logic did not detect a change) __
>>>>>> __- timestamp A = timestamp B = the current timestamp (Logic 
>>>>>> detected __
>>>>>> __change and recompiled template) __
>>>>>> _ _
>>>>>> _ _
>>>>>> __Kind regards __
>>>>>> _ _
>>>>>> __\Fabian __
>>>>>> _ _
>>>>>> _ _
>>>>>> _ _
>>>>>> _ _
>>>>>> _ _
>>>>>> _ _
>>>>>> _
>> ___
>> ____
>> _________________________________________________ __
>> _ 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20140903/eff51af8/attachment.htm>