[opencms-dev] Publishing problems

Wed Sep 3 11:17:40 CEST 2014

Hi Kai,

thanks for your message. A typical browser generated head looks like this:

<head>
--lots of metadata--

<link type="text/css" rel="stylesheet" href="/common/css/aCss.css"/>
<script type="text/javascript" src="/../../javascriptfile1.js"></script>
<script type="text/javascript" src="/common/js/javascriptfile2.js"></script>
<script type="text/javascript" src="/common/js/common.js"></script>
<script type="text/javascript" 
src="/../../configuration/js/javascriptfile3.js"></script>
</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
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>