Pierre Smits created OFBIZ-7941:
-----------------------------------
Summary: Have more flexibility regarding setting SeoConfig
parameters
Key: OFBIZ-7941
URL: https://issues.apache.org/jira/browse/OFBIZ-7941
Project: OFBiz
Issue Type: Improvement
Components: specialpurpose/cmssite, specialpurpose/ecommerce
Affects Versions: Trunk
Reporter: Pierre Smits
Currently when deploying mutilple cmssite and ecommerce based sites and the
adopter wants to have some kind of url shortening, the adopter must adjust the
SeoConfig.xml file manually.
The following needs to be adjusted in the file to include other componentIds:
{code}
<allowed-context-paths>/:/ecomseo</allowed-context-paths>
{code}
Also, differentiation regarding multiple site components is not obvious (can't
be achieved?) in:
{code}
<category-name>disable</category-name>
{code}
Furthermore, for each new addition (to allowed-contex-paths) requires the
addition of:
{code}
<url-config>
<description>sample: remove /ecomseo/main</description>
<url-pattern>^/ecomseo/main$</url-pattern>
<seo>
<replacement>/ecomseo/</replacement>
</seo>
<forward>
<replacement>/ecomseo/</replacement>
<responsecode>301</responsecode>
</forward>
</url-config>
{code}
At the moment I haven't found a work-around to have it configurable through
data (visavis multi-tenancy).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
