[opencms-dev] Publishing problems

Gerhard opencms at archeron.de
Tue Sep 2 10:24:43 CEST 2014


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

Am 27.08.2014 15:25, schrieb fhsubscriptions at componio.net:
> 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
>
>
>
> Am 27.08.2014 14:19, schrieb 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
>>
>>
>> Am 26.08.2014 16:07, schrieb fhsubscriptions at componio.net:
>>> 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
>>>
>>>




More information about the opencms-dev mailing list