<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1226" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2><SPAN
class=439135311-13102003>Hi,</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN
class=439135311-13102003> </SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=439135311-13102003> I am
new to Opencms and facing some issues with static export.</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2><SPAN class=439135311-13102003>Can somebody please
help with this?</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV><FONT face=Arial
size=2></FONT><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT>
<DIV><FONT face=Arial size=2></FONT><FONT face=Arial size=2></FONT><BR><SPAN
class=439135311-13102003><FONT face=Arial size=2>1) </FONT></SPAN><FONT
face=Arial><FONT size=2>I am <SPAN class=439135311-13102003>unable
</SPAN>to <SPAN class=439135311-13102003>export</SPAN>
projects:</FONT></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2>Publishing project ...<BR>No static
export required<BR>Checking filesystem links ...<BR>.. filesystem link check
finished<BR>... the project has been published</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=439135311-13102003><FONT face=Arial size=2>Should it be enabled
somewhere?</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2><SPAN
class=439135311-13102003> </SPAN></FONT></DIV>
<DIV><FONT face=Arial><FONT size=2><SPAN class=439135311-13102003>2)
</SPAN>When I publish the resources directly, the resource is not found in the
</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2>folder mentioned in the static export
path.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2>Publishing resource ...<BR>Publishing
/release/installation.html<BR>Publishing
/system/bodies/release/installation.html<BR>Static export, number of starting
links is: 2<BR>Skipping /release/installation.html<BR>Skipping
/system/bodies/release/installation.html<BR>... static export
finished<BR>Checking filesystem links ...<BR>.. filesystem link check
finished<BR>... the resource has been published</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2><SPAN class=439135311-13102003>3) </SPAN>The
static export icon in the administration appears grey.</FONT></FONT></DIV>
<DIV><SPAN class=439135311-13102003><FONT face=Arial size=2>
How can I enable it?</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial><FONT size=2><SPAN class=439135311-13102003>4) </SPAN>Also
can I specify absolute path such as C:\export?<BR>It does not seem to work for
me.</FONT></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff><SPAN
class=439135311-13102003>opencms.properties file</SPAN></FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2># Parameters for static
export<BR>#################################################################################</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2># if static export is disabled
nothing is exported and the rules are not used.<BR># For the handeling of the
link tags one standard rule is generated with the<BR># url_prefix_http value. So
you can still configure the
servletpath.<BR>staticexport.enabled=true</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2># the static export is controlled by
the resource property export. It has 6 possible<BR># values: true, false,
dynamic, https, https_enabled and dynamic_https_enabled.<BR># With the property
staticexport.default.export you can decide whitch value is used if<BR># a
resource and all parentfolders don't have the the property export set.<BR># If
your site shoud be exported except a few resources you set the default to
true<BR># and add the export=dynamic property to the folder where the dynamic
pages are. If<BR># your site is mostly dynamic you set the default to dynamic
and add the export= true<BR># property to the pics and the download folder.<BR>#
Only the values 'true' and 'dynamic' are
allowed.<BR>staticexport.default.export=true</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2># the path where to save the exported
pages. This path may be relative or
absolute.<BR>staticexport.path=export/</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial size=2><FONT color=#0000ff># Prefix variables. The export
prefix defines where to find the static reources.<BR># The http prefix defines
the way to the dynamic resources in OpenCms. The https and<BR># the servername
are used only for ssl. (If you use ssl you have to set the values like:<BR>#
</FONT><A
href="https://server.de/${WEB_APP_NAME}/opencms">https://server.de/${WEB_APP_NAME}/opencms</A><FONT
color=#0000ff> for the https prefix and </FONT><A
href="http://server.de">http://server.de</A><BR><FONT color=#0000ff># for the
servername)<BR># The String ${WEB_APP_NAME} will be replaced by the name of<BR>#
the webapplication. These variables can also be used in the
rulesets.<BR>url_prefix_export=/${WEB_APP_NAME}/export<BR>url_prefix_http=/${WEB_APP_NAME}/opencms<BR>url_prefix_https=<BR>url_prefix_servername=</FONT></FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2># the name of the ruleset used to
replace links while exporting, in the online project,<BR># in the offlineproject
and for the name in the extern file system. There are two sets<BR># of rules.
Depending of the staticexport.default.export parameter the linkrules.true
or<BR># the linkrules.dynamic are
used.<BR>linkrules.true.export=exportrules<BR>linkrules.true.online=exportrules<BR>linkrules.true.offline=offlinerules<BR>linkrules.true.extern=externrules<BR>linkrules.dynamic.export=dynamic_exportrules<BR>linkrules.dynamic.online=dynamic_exportrules<BR>linkrules.dynamic.offline=dynamic_offlinerules<BR>linkrules.dynamic.extern=dynamic_externrules</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2># the start rule used for extern and
export (not for online and offline).<BR># (the rules are regular expressions in
perl5
standard)<BR>#exportfirstrule=s#.([^&\?]*)=([^&\?]*)#_$1$2#g<BR>#<BR>#
The start rule feature is removed. Instead there is a new feature: While
exporting<BR># if after the dynamic rueles nothing has changed the parameters of
the link will be<BR># decoded in the name. so
"/index.html?newsid=27&size=100" is replaced by "/index_402.html"<BR># where
402 is the id of the link in the database. Further rules (after the dynamic
ones)<BR># will be processed with the new link.</FONT></DIV>
<DIV><FONT color=#0000ff></FONT> </DIV>
<DIV><BR><FONT face=Arial color=#0000ff size=2># The rulesets for
linkreplacement as comma seperated lists<BR># You can use the ${WEB_APP_NAME}
variable for the webapplication name and the<BR># four prefix variables defined
above (${url_prefix_export}, ${url_prefix_http},...).<BR># They will be replaced
befor using the regular expression.<BR># In addition to this it is possible to
define the place where the dynamic<BR># generated rules should be used instead
of a rule use the expression<BR># *dynamicRules* (including the *'s). OpenCms
replaces this with the dynamic<BR># generated rules.<BR># There are two types of
dynamic rules. The first one is generated with the<BR># resourceproperty
"exportname". For each resouce with this property a rule<BR># will be generated
that replaces the absolute path of this resource with the<BR># value of the
property. It is principally used to get nice short foldernames<BR># on the
disc.<BR># The second kind of dynamic rules are generated with the property
"export".<BR># The possible values are explained below.<BR>#<BR># Possible
values for the "export" property are:<BR>#<BR># export=true<BR># The
marked resource is exported.<BR># For the online project, all links
that point to this resource are<BR># build according to the
"linkrules.true.extern" (see above) ruleset.<BR># All links found on
the marked resource that have been<BR># marked with the
<link/> tag are followed and also checked for export.<BR>#
Example:<BR># VFS
=/index.html<BR># RFS
=${webapp_path}/opencms/export/index.html<BR>#
Link=<a href="${url_prefix_export}/index.html"/><BR>#<BR>#
export=false<BR># The marked resource is not
exported.<BR># For the online project, all links that point to this
resource are<BR># build according to the "linkrules.true.online"
(see above) ruleset.<BR># Links on the marked resource that are
marked with the <link/> tag are<BR># NOT followed and
therefore not exported.<BR>#
Example:<BR># VFS
=/index.html<BR># RFS
=(none)<BR># Link=<a
href="${url_prefix_http}/index.html"/><BR>#<BR>#
export=dynamic<BR># The marked resource is not
exported.<BR># For the online project, all links that point to this
resource are<BR># build according to the "linkrules.dynamic.online"
(see above) ruleset.<BR># All links found on the marked resource
that have been<BR># marked with the <link/> tag are followed
and also checked for export.<BR>#
Example:<BR># VFS
=/index.html<BR># RFS
=(none)<BR># Link=<a
href="${url_prefix_http}/index.html"/><BR>#<BR># Static exort and
https:<BR># If you intent to use https settings with the
export,<BR># you must extend the ${url_prefix_http} to include the
http protocol,<BR># and also set the ${url_prefix_https} and the
${url_prefix_servername}.<BR># In this case, all links will be
absolute links that contain server name<BR># and protocol (but see
also the resource setting "export=https_enabled"<BR># explained
below).<BR>#<BR># export=https<BR># The marked resource is not
exported, but treated as a https resource.<BR># For the online
project, all links that point to this resource are<BR># build
according to the "linkrules.true.online" (see above) ruleset,<BR>#
using the "url_prefix_https" Prefix.<BR># All access to this
resource that is NOT using the https protocol<BR># is
forbidden!<BR># All links found on the marked resource that have
been<BR># marked with the <link/> tag are followed and also
checked for export.<BR># Example:<BR>#
VFS =/index.html<BR># RFS
=(none)<BR># Link=<a
href="${url_prefix_https}/index.html"/><BR>#<BR>#
export=https_enabled<BR># The marked resource is not
exported.<BR># For the online project, all links that point to this
resource are<BR># build according to the "linkrules.true.extern"
(see above) ruleset.<BR># No protocol will be used for the link, so
that a browser that<BR># was in https mode will be staying in https,
while a http request<BR># will stay in http mode.<BR>#
Use this parameter esp. for images to prevent the dreaded webbrowser
warning<BR># that tells you something like "The page you are
about<BR># to view uses secure and unsecure data".<BR>#
All links found on the marked resource that have been<BR># marked
with the <link/> tag are followed and also checked for
export.<BR># Example:<BR># VFS
=/index.html<BR># RFS
=(none)<BR># Link=<a
href="/${web_app_name}/${opencms_servlet_name}/index.html"/><BR>#<BR>#
export=dynamic_https_enabled<BR># The marked resource is not
exported, but treated as a https resource.<BR># This is like
"export=dynamic" with the addition that the resource<BR># will only
be delivered if the request is a https request,<BR>#
Example:<BR># VFS
=/index.html<BR># RFS
=(none)<BR># Link=<a
href="${url_prefix_https}/index.html"/><BR>#<BR># The dynamic rules are only
for export, online and extern rules. Don't use them in<BR># the
offlineruleset.<BR># The parameterreplacement is done in the dynamic rules. So
it works together with<BR># the exportname rule. If you have a rule befor the
dynamic rules that is triggered<BR># the parameterreplacement will not
happen.<BR>ruleset.offlinerules=s#^#${url_prefix_http}#<BR>ruleset.exportrules=*dynamicRules*,
\
<BR>s#^#${url_prefix_export}#<BR>ruleset.externrules=*dynamicRules*</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff
size=2>ruleset.dynamic_offlinerules=s#^#${url_prefix_http}#<BR>ruleset.dynamic_exportrules=*dynamicRules*,
\ <BR>s#(.*\.gif$)#${url_prefix_export}$1#, \
<BR>s#(.*\.jpg$)#${url_prefix_export}$1#, \
<BR>s#(.*\.pdf$)#${url_prefix_export}$1#, \
<BR>s#(.*\.css$)#${url_prefix_export}$1#, \
<BR>s#(.*\.doc$)#${url_prefix_export}$1#, \
<BR>s#(.*\.exe$)#${url_prefix_export}$1#, \
<BR>s#(.*\.xls$)#${url_prefix_export}$1#, \
<BR>s#(.*\.js$)#${url_prefix_export}$1#, \
<BR>s#(.*\.zip$)#${url_prefix_export}$1#, \
<BR>s#(.*\.jpeg$)#${url_prefix_export}$1#, \
<BR>s#(.*\.txt$)#${url_prefix_export}$1#, \
<BR>s#^#${url_prefix_http}#<BR>ruleset.dynamic_externrules=*dynamicRules*, \
<BR>s#(.*\.gif$)#$1#, \ <BR>s#(.*\.jpg$)#$1#, \ <BR>s#(.*\.pdf$)#$1#, \
<BR>s#(.*\.css$)#$1#, \ <BR>s#(.*\.doc$)#$1#, \ <BR>s#(.*\.exe$)#$1#, \
<BR>s#(.*\.xls$)#$1#, \ <BR>s#(.*\.js$)#$1#, \ <BR>s#(.*\.zip$)#$1#, \
<BR>s#(.*\.jpeg$)#$1#, \ <BR>s#(.*\.txt$)#$1#, \ <BR>s#.*##</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2># When set to true the links in the
static export that refer to pages in the static export<BR># will be relative
instead of absolute. Enable this feature only if you use the standard<BR>#
ruleset.<BR>#<BR>relativelinks_in_export=false</FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=439135311-13102003><FONT face=Arial color=#0000ff
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=439135311-13102003><FONT face=Arial color=#0000ff
size=2>Raghu</FONT></SPAN></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> </DIV></BODY></HTML>