[opencms-dev] mod_proxy and workspace.css

[Jonathan Woods]

Hope this works for you.  I do remember it took me ages to figure out...
 
Jon

  _____  

From: opencms-dev-bounces at opencms.org
[mailto:opencms-dev-bounces at opencms.org] On Behalf Of Marc Johnen
Sent: 06 June 2006 12:27
To: opencms-dev at opencms.org
Subject: Re: [opencms-dev] mod_proxy and workspace.css


Hi Jon,

sorry for my late response and thanks for your answer!

I'm starting to understand how it works, but my problem

is not yet solved. I followed your instructions, but without

effect. Probably I made a mistake somewhere, for now I don't 

have any time to check it. My plan is to configure only the

exported page with mod_jk (which seems more flexible to me) and

leave the workspace-access at port 8080.

Greetings

Marc, Berlin







Like some other system resources, workspace.css is 'statically exported'

(written from VFS to RFS) on demand; and the RFS location it's written to

will be <opencms root>/WEB-INF/export/system/work......  So clearly the

stsatic export part of your set-up isn't working.  This may be linked to the

missing step re the workspace JSP, which is this: edit

/system/workplace/views/top_js.jsp (for 6.2.x) or

/system/workplace/views/top_fs.jsp (for 6.0.4) and locate the line which

says



	this.servpath="<%= OpenCms.getSystemInfo().getOpenCmsContext() %>";



to say



	this.servpath="<%= OpenCms.getStaticExportManager().getVfsPrefix()

%>";



This says to OpenCms that it should regard OpenCms-managed URIs as beginning

with the VFS prefix configured in opencms-importexport.xml (which, slightly

misleadingly, also controls URI generation for non-exported resources.



Hope this helps.



Jon



-----Original Message-----

From: opencms-dev-bounces at opencms.org
<http://lists.opencms.org/mailman/listinfo/opencms-dev> 

[mailto:opencms-dev-bounces at opencms.org
<http://lists.opencms.org/mailman/listinfo/opencms-dev> ] On Behalf Of Marc
Johnen

Sent: 27 May 2006 13:55

To: opencms-dev at opencms.org
<http://lists.opencms.org/mailman/listinfo/opencms-dev> 

Subject: [opencms-dev] mod_proxy and workspace.css



hello everyone,



i (carefully) followed the instructions of the documentation to "cut off"

the "opencms/opencms" and it is working fine so far. i'm only encountering

one problem. the workspace.css can not be found at

"/export/system/workplace/commons/style/workplace.css",

after the modifications

it should be "/system/workplace/commons/style/workplace.css", if i'm

correct.

also i think in earlier versions of the documentation there was some kind of

reference of changing one of the workspace-jsps, i can't find that anymore

though.

the workspace is not really usable without the correct css and my

understanding of opencms is not sufficient to correct the problem. hope

someone knows what to do.

thanks and greetings

marc, berlin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://webmail.opencms.org/pipermail/opencms-dev/attachments/20060606/7ad39917/attachment.htm>