<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Gerhard,<br>
<br>
Am 03.09.2014 11:17, schrieb Gerhard:<br>
</div>
<blockquote cite="mid:5406DCB4.3060207@archeron.de" type="cite"><script
type="text/javascript"
src="/../../configuration/js/javascriptfile3.js"></script>
<br>
</blockquote>
This is not a typical OpenCms link. Do you make use of the
<cms:link /> tag?<br>
Can you further post how a link to another OpenCms hosted page looks
like?<u><br>
<br>
</u>Thanks,<br>
<br>
\Fabian<br>
<u><br>
</u><u><br>
</u>
<blockquote cite="mid:5406DCB4.3060207@archeron.de" type="cite"><u></head>
</u><u><br>
</u><u>
</u><u><br>
</u><u>We include all static files like pictures, CSS,
JavaScript-files like this:
</u><u><br>
</u><u>
</u><u><br>
</u><u><div class="icon">
</u><u><br>
</u><u> <img
src="<cms:link>/common/../../picture.png</cms:link>">
</u><u><br>
</u><u></div>
</u><u><br>
</u><u>
</u><u><br>
</u><u>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.
</u><u><br>
</u><u>
</u><u><br>
</u><u>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.
</u><u><br>
</u><u>
</u><u><br>
</u><u>Concerning that Nginx our service provider said that it is
only proxying but doesn't cache anything.
</u><u><br>
</u><u>
</u><u><br>
</u><u>Thanks&Regards,
</u><u><br>
</u><u>Gerhard
</u><u><br>
</u><u>
</u><u><br>
</u><u>Am 03.09.2014 10:20, schrieb Schliemann, Kai:
</u><u><br>
</u>
<blockquote type="cite"><u>Hi Gerhard,
</u><u><br>
</u><u>from inside OpenCms you can only influence, if
files/folders should be statically exported or not. This is
what Fabian already described.
</u><u><br>
</u><u>Is it possible for you to send a part of the browser
generated html source?
</u><u><br>
</u><u>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.
</u><u><br>
</u>
<u><br>
</u><u>One other thing. Is it possible, that Nginx is working as
a proxy server and thus caching the mentioned files?
</u><u><br>
</u>
<u><br>
</u><u>Best regards
</u><u><br>
</u><u>Kai
</u><u><br>
</u>
<u><br>
</u><u>-----Ursprüngliche Nachricht-----
</u><u><br>
</u><u>Von: <a class="moz-txt-link-abbreviated" href="mailto:opencms-dev-bounces@opencms.org">opencms-dev-bounces@opencms.org</a>
[<a class="moz-txt-link-freetext" href="mailto:opencms-dev-bounces@opencms.org">mailto:opencms-dev-bounces@opencms.org</a>] Im Auftrag von
Gerhard
</u><u><br>
</u><u>Gesendet: Mittwoch, 3. September 2014 09:53
</u><u><br>
</u><u>An: The OpenCms mailing list
</u><u><br>
</u><u>Betreff: Re: [opencms-dev] Publishing problems
</u><u><br>
</u>
<u><br>
</u><u>Hi Fabian,
</u><u><br>
</u>
<u><br>
</u><u>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?
</u><u><br>
</u>
<u><br>
</u><u>Thanks,
</u><u><br>
</u><u>Gerhard
</u><u><br>
</u>
<u><br>
</u><u>Am 02.09.2014 12:26, schrieb
<a class="moz-txt-link-abbreviated" href="mailto:fhsubscriptions@componio.net">fhsubscriptions@componio.net</a>:
</u><u><br>
</u>
<blockquote type="cite"><u>Well, usually this is available via
context menu of the resource
</u><u><br>
</u><u>(right
</u><u><br>
</u><u>click) -> Advanced -> Secure/Export and then see
the radio button yes
</u><u><br>
</u><u>| no | not set Otherwise I understood that your
provider has
</u><u><br>
</u><u>introduced its own static cache mechanism which will
surely be
</u><u><br>
</u><u>configured differently.
</u><u><br>
</u>
<u><br>
</u><u>\Fabian
</u><u><br>
</u>
<u><br>
</u><u>Am 02.09.2014 12:16, schrieb Gerhard:
</u><u><br>
</u>
<blockquote type="cite"><u>Hi Fabian,
</u><u><br>
</u>
<u><br>
</u><u>ah seems to be complicated :-)
</u><u><br>
</u>
<u><br>
</u><u>So, where can I find this static logic? (Not sure if
you mentioned
</u><u><br>
</u><u>already)
</u><u><br>
</u>
<u><br>
</u><u>Cheers,
</u><u><br>
</u><u>Gerhard
</u><u><br>
</u>
<u><br>
</u><u>Am 02.09.2014 11:48, schrieb
<a class="moz-txt-link-abbreviated" href="mailto:fhsubscriptions@componio.net">fhsubscriptions@componio.net</a>:
</u><u><br>
</u>
<blockquote type="cite"><u>Hi Gerhard,
</u><u><br>
</u>
<u><br>
</u><u>again - hard to tell :-)
</u><u><br>
</u>
<u><br>
</u><u>If A is the root node and the static logic from the
provider does
</u><u><br>
</u><u>not check if B is related to A then yes, you would
have to publish both.
</u><u><br>
</u><u>However this is very simple to verify:
</u><u><br>
</u>
<u><br>
</u><u>Create a template A which outputs the current time
and create a JSP
</u><u><br>
</u><u>B which is included by the template A (via the tag
<cms:include />)
</u><u><br>
</u><u>which also outputs the current time.
</u><u><br>
</u><u>Publish both, request template A and both time
stamps should be
</u><u><br>
</u><u>identically.
</u><u><br>
</u><u>Then change template B and publish again.
</u><u><br>
</u>
<u><br>
</u><u>Depending on how the static logic from your
provider works you will
</u><u><br>
</u><u>most likely have one of the following results when
calling template A again:
</u><u><br>
</u>
<u><br>
</u><u>- timestamp A = timestamp B = the timestamp from
the first template
</u><u><br>
</u><u>call (Logic did not detect a change)
</u><u><br>
</u><u>- timestamp A = timestamp B = the current timestamp
(Logic detected
</u><u><br>
</u><u>change and recompiled template)
</u><u><br>
</u>
<u><br>
</u>
<u><br>
</u><u>Kind regards
</u><u><br>
</u>
<u><br>
</u><u>\Fabian
</u><u><br>
</u>
<u><br>
</u>
<u><br>
</u>
<u><br>
</u>
<u><br>
</u>
<u><br>
</u>
<u><br>
</u></blockquote>
</blockquote>
</blockquote>
</blockquote>
<u>
</u><u><br>
</u><u>
</u><u><br>
</u><u>_______________________________________________
</u><u><br>
</u><u>This mail is sent to you from the opencms-dev mailing list
</u><u><br>
</u><u>To change your list options, or to unsubscribe from the
list, please visit
</u><u><br>
</u><u><a class="moz-txt-link-freetext" href="http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev">http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev</a>
</u><u><br>
</u><u>
</u><u><br>
</u><u>
</u><u><br>
</u><u>
</u><br>
</blockquote>
<br>
</body>
</html>