[opencms-dev] Publishing problems

Discussion:

Gerhard

2014-08-26 13:23:45 UTC

Hello,

we are currently facing some larger issues with OpenCMS and I hope
someone can help us out here.

The situation is as follows: We use templates which include some common
parts with the help of the <cms:include/>-element and which are then
used by a set of localized pages. So far so good. Now we did some
changes in a JavaScript-file used by our templates. This change made it
necessary to adapt the <cms:include/>d code as well. We published both
the JavaScript-file and the <cms:include/>d code and it is working as
intended inside OpenCMS.

The problem is now that when we open one of these pages outside of
OpenCMS e.g. over an external domain we get the old page (with the old
include-code). Yes, it looks strongly like a cache issue, however,
deleting all browser caches+all OpenCMS caches does not help. The only
two things we found working are either touching all pages
(right-click->advanced->touch) or opening the _online_ version inside
OpenCMS. After that opening the page over an external domains works
flawlessly. What causes this behaviour? How can we solve this?

We have no access to the underlying servers, so I can't tell much about
configuration parameters etc. The only thing I know is that Nginx,
Apache and Tomcat are used.

Any help is appreciated.

Kind regards,
Gerhard

fhsubscriptions

2014-08-26 13:31:20 UTC

Permalink

Hi Gerhard,

do you statically export the html pages? If so, then you have to touch
and re-publish all pages which have a last-modified timestamp older than
the date and time of your applied changes.

Regards

\Fabian

Post by Gerhard
Hello,
we are currently facing some larger issues with OpenCMS and I hope
someone can help us out here.
The situation is as follows: We use templates which include some
common parts with the help of the <cms:include/>-element and which are
then used by a set of localized pages. So far so good. Now we did some
changes in a JavaScript-file used by our templates. This change made
it necessary to adapt the <cms:include/>d code as well. We published
both the JavaScript-file and the <cms:include/>d code and it is
working as intended inside OpenCMS.
The problem is now that when we open one of these pages outside of
OpenCMS e.g. over an external domain we get the old page (with the old
include-code). Yes, it looks strongly like a cache issue, however,
deleting all browser caches+all OpenCMS caches does not help. The only
two things we found working are either touching all pages
(right-click->advanced->touch) or opening the _online_ version inside
OpenCMS. After that opening the page over an external domains works
flawlessly. What causes this behaviour? How can we solve this?
We have no access to the underlying servers, so I can't tell much
about configuration parameters etc. The only thing I know is that
Nginx, Apache and Tomcat are used.
Any help is appreciated.
Kind regards,
Gerhard
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please
visit
http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev

Sudheendra Singh

2014-08-26 13:43:41 UTC

Permalink

Hi Gerhard,
Did you publish the pages? Try restarting server as well.

On 26 August 2014 14:31, fhsubscriptions at componio.net <

Post by fhsubscriptions
Hi Gerhard,
do you statically export the html pages? If so, then you have to touch
and re-publish all pages which have a last-modified timestamp older than
the date and time of your applied changes.
Regards
\Fabian

--
Regards,
Sudheendra.N.Singh
07872067281
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140826/23e9432f/attachment.html>

Gerhard

2014-08-26 13:52:20 UTC

Permalink

Hello Sudheendra,

thanks for these tips, we tried that but unfortunately it didn't help.

Cheers,
Gerhard

Post by fhsubscriptions
Hi Gerhard,
Did you publish the pages? Try restarting server as well.
On 26 August 2014 14:31, fhsubscriptions at componio.net
<mailto:fhsubscriptions at componio.net> <fhsubscriptions at componio.net
Hi Gerhard,
do you statically export the html pages? If so, then you have to touch
and re-publish all pages which have a last-modified timestamp older than
the date and time of your applied changes.
Regards
\Fabian

which are

Post by Gerhard
then used by a set of localized pages. So far so good. Now we

did some

Post by Gerhard
changes in a JavaScript-file used by our templates. This change made
it necessary to adapt the <cms:include/>d code as well. We published
both the JavaScript-file and the <cms:include/>d code and it is
working as intended inside OpenCMS.
The problem is now that when we open one of these pages outside of
OpenCMS e.g. over an external domain we get the old page (with

the old

Post by Gerhard
include-code). Yes, it looks strongly like a cache issue, however,
deleting all browser caches+all OpenCMS caches does not help.

The only

Post by Gerhard
two things we found working are either touching all pages
(right-click->advanced->touch) or opening the _online_ version

inside

Post by Gerhard
OpenCMS. After that opening the page over an external domains works
flawlessly. What causes this behaviour? How can we solve this?
We have no access to the underlying servers, so I can't tell much
about configuration parameters etc. The only thing I know is that
Nginx, Apache and Tomcat are used.
Any help is appreciated.
Kind regards,
Gerhard
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev

_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev
--
Regards,
Sudheendra.N.Singh
07872067281
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140826/39ead2a2/attachment.html>

Gerhard

2014-08-26 13:50:30 UTC

Permalink

Hi Fabian,

we publish all pages via right-click->publish directly. I am not sure if
this means a static export is done as well, but I think not. Where can I
see if a static export occurs?

Anyway touching all files like you described does work, the only problem
is that this takes extremely long because we have several thousands of
pages.

Kind regards,
Gerhard

fhsubscriptions

2014-08-26 14:07:23 UTC

Permalink

How does a page URL look like?
If it contains .../export/... the pages are statically exported. This
means that they are precompiled and are statically served from the disk.
Thus OpenCms will never apply your changes unless you touch an republish
the page(s) in question (which triggers the static export).

\Fabian

Post by Gerhard
Hi Fabian,
we publish all pages via right-click->publish directly. I am not sure
if this means a static export is done as well, but I think not. Where
can I see if a static export occurs?
Anyway touching all files like you described does work, the only
problem is that this takes extremely long because we have several
thousands of pages.
Kind regards,
Gerhard

Post by Gerhard
Hello,
we are currently facing some larger issues with OpenCMS and I hope
someone can help us out here.
The situation is as follows: We use templates which include some
common parts with the help of the <cms:include/>-element and which are
then used by a set of localized pages. So far so good. Now we did some
changes in a JavaScript-file used by our templates. This change made
it necessary to adapt the <cms:include/>d code as well. We published
both the JavaScript-file and the <cms:include/>d code and it is
working as intended inside OpenCMS.
The problem is now that when we open one of these pages outside of
OpenCMS e.g. over an external domain we get the old page (with the old
include-code). Yes, it looks strongly like a cache issue, however,
deleting all browser caches+all OpenCMS caches does not help. The only
two things we found working are either touching all pages
(right-click->advanced->touch) or opening the _online_ version inside
OpenCMS. After that opening the page over an external domains works
flawlessly. What causes this behaviour? How can we solve this?
We have no access to the underlying servers, so I can't tell much
about configuration parameters etc. The only thing I know is that
Nginx, Apache and Tomcat are used.
Any help is appreciated.
Kind regards,
Gerhard
_______________________________________________
This mail is sent to you from the opencms-dev mailing list
To change your list options, or to unsubscribe from the list, please visit
http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev

Gerhard

2014-08-27 12:19:58 UTC

Permalink

Hi Fabian,

the URLs contain no ../export/.. :-/

Our service provider for the servers on which OpenCMS is running spoke
about "statification" yesterday which sounded pretty much like a static
export. That would explain the fact that we get old pages as long as we
don't republish the content. But one thing is weird: When the people at
the service provider open the pages, they don't have any problems at
all, the most current version is loaded. And when I open the very same
page _after that_ I get the correct page too! Do you have any idea how
this can happen?

Thanks,
Gerhard

Post by fhsubscriptions
How does a page URL look like?
If it contains .../export/... the pages are statically exported. This
means that they are precompiled and are statically served from the disk.
Thus OpenCms will never apply your changes unless you touch an republish
the page(s) in question (which triggers the static export).
\Fabian

fhsubscriptions

2014-08-27 13:25:30 UTC

Permalink

Hi Gerhard,

without knowing the infrastructure hard to tell. My best guess would be
that the service provider accesses directly OpenCms whereas you access
the statically "cached" version.

Kind regards

\Fabian

Post by Gerhard
Hi Fabian,
the URLs contain no ../export/.. :-/
Our service provider for the servers on which OpenCMS is running spoke
about "statification" yesterday which sounded pretty much like a
static export. That would explain the fact that we get old pages as
long as we don't republish the content. But one thing is weird: When
the people at the service provider open the pages, they don't have any
problems at all, the most current version is loaded. And when I open
the very same page _after that_ I get the correct page too! Do you
have any idea how this can happen?
Thanks,
Gerhard

Gerhard

2014-09-02 08:24:43 UTC

Permalink

Hi Fabian,

does that mean that when I have a file A which uses a file B that I
always have to republish A manually when B changes?

Thanks,
Gerhard

Post by fhsubscriptions
Hi Gerhard,
without knowing the infrastructure hard to tell. My best guess would be
that the service provider accesses directly OpenCms whereas you access
the statically "cached" version.
Kind regards
\Fabian

fhsubscriptions

2014-09-02 09:48:48 UTC

Permalink

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

Post by Gerhard
Hi Fabian,
does that mean that when I have a file A which uses a file B that I
always have to republish A manually when B changes?
Thanks,
Gerhard

Gerhard

2014-09-02 10:16:09 UTC

Permalink

Hi Fabian,

ah seems to be complicated :-)

So, where can I find this static logic? (Not sure if you mentioned already)

Cheers,
Gerhard

Post by fhsubscriptions
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.
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
- 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

Post by Gerhard
Hi Fabian,
does that mean that when I have a file A which uses a file B that I
always have to republish A manually when B changes?
Thanks,
Gerhard

fhsubscriptions

2014-09-02 10:26:09 UTC

Permalink

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

Post by Gerhard
Hi Fabian,
ah seems to be complicated :-)
So, where can I find this static logic? (Not sure if you mentioned already)
Cheers,
Gerhard

Post by Gerhard
Hi Fabian,
does that mean that when I have a file A which uses a file B that I
always have to republish A manually when B changes?
Thanks,
Gerhard

Gerhard

2014-09-03 07:53:06 UTC

Permalink

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

Post by fhsubscriptions
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

Post by Gerhard
Hi Fabian,
ah seems to be complicated :-)
So, where can I find this static logic? (Not sure if you mentioned already)
Cheers,
Gerhard

Post by Gerhard
Hi Fabian,
does that mean that when I have a file A which uses a file B that I
always have to republish A manually when B changes?
Thanks,
Gerhard

Schliemann, Kai

2014-09-03 08:20:42 UTC

Permalink

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

Post by fhsubscriptions
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

Post by Gerhard
Hi Fabian,
ah seems to be complicated :-)
So, where can I find this static logic? (Not sure if you mentioned already)
Cheers,
Gerhard

Post by fhsubscriptions
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.
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
- 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

Post by Gerhard
Hi Fabian,
does that mean that when I have a file A which uses a file B that I
always have to republish A manually when B changes?
Thanks,
Gerhard

Post by fhsubscriptions
Hi Gerhard,
without knowing the infrastructure hard to tell. My best guess
would be that the service provider accesses directly OpenCms
whereas you access the statically "cached" version.
Kind regards
\Fabian

Gerhard

2014-09-03 09:17:40 UTC

Permalink

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

Post by fhsubscriptions
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

Post by fhsubscriptions
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

Post by Gerhard
Hi Fabian,
ah seems to be complicated :-)
So, where can I find this static logic? (Not sure if you mentioned already)
Cheers,
Gerhard

Post by fhsubscriptions
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.
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
- 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

fhsubscriptions

2014-09-03 09:29:33 UTC

Permalink

Hi Gerhard,

Post by 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
_
__
_

Post by Gerhard
_</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 __
_ _
_ _
_ _
_ _
_ _
_ _
_

___
____
_________________________________________________ __
__This mail is sent to you from the opencms-dev mailing list __
__To change your list options, or to unsubscribe from the list, please
visit __
__http://lists.opencms.org/cgi-bin/mailman/listinfo/opencms-dev __
____
____
___

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140903/0a8f9803/attachment.html>

Gerhard

2014-09-03 09:31:54 UTC

Permalink

Hi Fabian,

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

Cheers,
Gerhard

Post by fhsubscriptions
Hi Gerhard,

Post by 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
_
__
_

_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: __
_

_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: __
_

___
____
_________________________________________________ __
_

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140903/eff51af8/attachment.html>

fhsubscriptions

2014-09-03 09:55:14 UTC

Permalink

Hi Gerhard,

let me clarify :-)

<script type="text/javascript"
src="/../../configuration/js/javascriptfile3.js"></script>

If this is the link in the online generated HTML then the template makes
no use of the static export feature.
However if this is the link generated while in the offline project it
still is not a typical OpenCms link thus I guess that your template does
not look like this:

<script type="text/javascript"
src="<cms:link>/path/to/the/proper/directory/configuration/js/javascriptfile3.js</cms:link>"></script>

And again:

Can you further post how a link to another OpenCms hosted page is
generated._
_

\Fabian

Post by Gerhard
Hi Fabian,
yes this is the browser generated HTML, the template code is below that ;-)
Cheers,
Gerhard

Post by fhsubscriptions
Hi Gerhard,

Post by 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
_
__
_

_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 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: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140903/f6d2ddaa/attachment.html>

Gerhard

2014-09-03 10:23:56 UTC

Permalink

Hi Fabian,

ok now I am a bit confused, seems I still have to learn a lot about
OpenCMS haha. I will try to answer:

<script type="text/javascript"
src="/pathTo/commonStuff/configuration/js/javascriptfile3.js"></script>

This is indeed the form which appears in the online version. In the
offline there is an additional prefix in front:

<script type="text/javascript"
src="/aPrefix/pathTo/commonStuff/configuration/js/javascriptfile3.js"></script>

then the template makes no use of the static export feature.

How do you see this? Ok, we have no "export" in the URL. But is "export"
the unique sign for static exports?

<script type="text/javascript"
src="<cms:link>/pathTo/commonStuff/configuration/js/javascriptfile3.js</cms:link>"></script>

This is exactly the form we use in our templates.

Can you further post how a link to another OpenCms hosted page is

Hi Gerhard,
let me clarify :-)
<script type="text/javascript"
src="/../../configuration/js/javascriptfile3.js"></script>
If this is the link in the online generated HTML then the template
makes no use of the static export feature.
However if this is the link generated while in the offline project it
still is not a typical OpenCms link thus I guess that your template
<script type="text/javascript"
src="<cms:link>/path/to/the/proper/directory/configuration/js/javascriptfile3.js</cms:link>"></script>
Can you further post how a link to another OpenCms hosted page is
generated._
_
\Fabian

Post by Gerhard
Hi Fabian,
yes this is the browser generated HTML, the template code is below that ;-)
Cheers,
Gerhard

Post by fhsubscriptions
Hi Gerhard,

Post by 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
_
__
_

Post by Gerhard
_</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 __
_

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140903/e3f4e9ba/attachment.html>

Schliemann, Kai

2014-09-03 13:45:39 UTC

Permalink

Hi Gerhard,
I try to answer for Fabian again.
The additional prefix seems to be the OpenCms servlet name. In a standard installation it is "opencms".
How do you see this? Ok, we have no "export" in the URL. But is "export" the unique sign for static exports?
Because it seemed to be a relative link (/../../blablabla/). I didn't see the leading / at first, so I thought that as well.
And it must not be "export" in the URL for statically exported pages. This is again the standard config.

Can you further post how a link to another OpenCms hosted page is generated.

It is just a link from one page to another within OpenCms. For example a link generated for the navigation, the sitemap or a link within your content.

BR
Kai

Von: opencms-dev-bounces at opencms.org [mailto:opencms-dev-bounces at opencms.org] Im Auftrag von Gerhard
Gesendet: Mittwoch, 3. September 2014 12:24
An: The OpenCms mailing list
Betreff: Re: [opencms-dev] Publishing problems

Hi Fabian,

ok now I am a bit confused, seems I still have to learn a lot about OpenCMS haha. I will try to answer:

<script type="text/javascript" src="/pathTo/commonStuff/configuration/js/javascriptfile3.js"></script>

This is indeed the form which appears in the online version. In the offline there is an additional prefix in front:

<script type="text/javascript" src="/aPrefix/pathTo/commonStuff/configuration/js/javascriptfile3.js"></script>

then the template makes no use of the static export feature.

How do you see this? Ok, we have no "export" in the URL. But is "export" the unique sign for static exports?

<script type="text/javascript" src="<cms:link>/pathTo/commonStuff/configuration/js/javascriptfile3.js</cms:link>"></script>

This is exactly the form we use in our templates.

Can you further post how a link to another OpenCms hosted page is generated.

Not sure if I got you right here. We have an Util-class which converts OpenCmsVfsFile-values into a link in OpenCMS which can be used with a simple <a/> tag. Is that what you mean?

Thanks&Regards,
Gerhard

Am 03.09.2014 11:55, schrieb fhsubscriptions at componio.net<mailto:fhsubscriptions at componio.net>:
Hi Gerhard,

let me clarify :-)

<script type="text/javascript" src="/../../configuration/js/javascriptfile3.js"></script>

If this is the link in the online generated HTML then the template makes no use of the static export feature.
However if this is the link generated while in the offline project it still is not a typical OpenCms link thus I guess that your template does not look like this:

<script type="text/javascript" src="<cms:link>/path/to/the/proper/directory/configuration/js/javascriptfile3.js</cms:link>"></script>

And again:

Can you further post how a link to another OpenCms hosted page is generated.

\Fabian

Am 03.09.2014 11:31, schrieb Gerhard:
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<mailto: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> [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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140903/1b587709/attachment.html>

Gerhard

2014-09-03 14:55:49 UTC

Permalink

Hi Kai,

hm does that mean that if I am using relative links instead, I can avoid
the static export? Just an idea ...

Concerning links: We only have two kinds of links

1. Links that are handled by JavaScript. These don't link to other pages
but are for events etc., so not interesting here.
2. Links specified with OpenCmsVfsFile-fields or via properties. The
code for the generation of these links is pretty long so I fear I can't
post the whole code here. What I can post is the result: When I open an
offline page in OpenCMS the links have the form

/servlet-prefix/path/to/some/interesting/page.html

online pages looks equal but without the servlet-prefix. Does that help?

Thanks&Regards,
Gerhard

Post by fhsubscriptions
Hi Gerhard,
I try to answer for Fabian again.
The additional prefix seems to be the OpenCms servlet name. In a
standard installation it is "opencms".
How do you see this? Ok, we have no "export" in the URL. But is
"export" the unique sign for static exports?
Because it seemed to be a relative link (/../../blablabla/). I didn't
see the leading / at first, so I thought that as well.
And it must not be "export" in the URL for statically exported pages.
This is again the standard config.

Can you further post how a link to another OpenCms hosted page is generated.

It is just a link from one page to another within OpenCms. For example
a link generated for the navigation, the sitemap or a link within your
content.
BR
Kai
*Von:*opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] *Im Auftrag von *Gerhard
*Gesendet:* Mittwoch, 3. September 2014 12:24
*An:* The OpenCms mailing list
*Betreff:* Re: [opencms-dev] Publishing problems
Hi Fabian,
ok now I am a bit confused, seems I still have to learn a lot about
<script type="text/javascript"
src="/pathTo/commonStuff/configuration/js/javascriptfile3.js"></script>
This is indeed the form which appears in the online version. In the
<script type="text/javascript"
src="/aPrefix/pathTo/commonStuff/configuration/js/javascriptfile3.js"></script>

then the template makes no use of the static export feature.

How do you see this? Ok, we have no "export" in the URL. But is
"export" the unique sign for static exports?
<script type="text/javascript"
src="<cms:link>/pathTo/commonStuff/configuration/js/javascriptfile3.js</cms:link>"></script>
This is exactly the form we use in our templates.

Can you further post how a link to another OpenCms hosted page is

generated.
Not sure if I got you right here. We have an Util-class which converts
OpenCmsVfsFile-values into a link in OpenCMS which can be used with a
simple <a/> tag. Is that what you mean?
Thanks&Regards,
Gerhard
Am 03.09.2014 11:55, schrieb fhsubscriptions at componio.net
Hi Gerhard,
let me clarify :-)
<script type="text/javascript"
src="/../../configuration/js/javascriptfile3.js"></script>
If this is the link in the online generated HTML then the template
makes no use of the static export feature.
However if this is the link generated while in the offline project
it still is not a typical OpenCms link thus I guess that your
<script type="text/javascript"
src="<cms:link>/path/to/the/proper/directory/configuration/js/javascriptfile3.js</cms:link>"></script>
Can you further post how a link to another OpenCms hosted page is
generated._
_
\Fabian
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,
<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,
<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
_

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opencms.org/pipermail/opencms-dev/attachments/20140903/510135e6/attachment.html>

Gerhard

2014-09-03 09:29:43 UTC

Permalink

Hi Kai,

I forgot one thing: We include common elements on all pages like footer,
navigation etc. by referencing a jsp

<cms:include page="/system/modules/mysite/../../basicElements.jsp"
element="footer"/>

and "footer" is defined in basicElements.jsp like this:

<cms:template element="footer">
--footer-html--
</cms:template>

This exactly the point where our initial problem occurs: When we change
the footer in "basicElements.jsp" all pages which include this jsp don't
"see" the change until they are republished. But republishing all sites
would take days for us, so a better solution is welcome. :-)

Thanks,
Gerhard

Post by Gerhard
Hi Kai,
<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>
<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

Post by fhsubscriptions
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

Post by fhsubscriptions
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

Post by Gerhard
Hi Fabian,
ah seems to be complicated :-)
So, where can I find this static logic? (Not sure if you mentioned already)
Cheers,
Gerhard

Post by fhsubscriptions
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.
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
- 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

Continue reading on narkive:

Search results for '[opencms-dev] Publishing problems' (Questions and Answers)

replies

Urgent help with school!!?

started 2011-09-11 06:19:46 UTC

primary & secondary education

replies

Windows Movie Maker Publishing Problems?

started 2008-08-21 20:31:29 UTC

software

replies

Front Page publishing problems uploading images?