[
https://issues.apache.org/jira/browse/OFBIZ-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823583#comment-13823583
]
Parimal Gain edited comment on OFBIZ-5312 at 11/15/13 11:43 AM:
----------------------------------------------------------------
Hi Jacques,
You have consolidate all thing very well, I don't think there is any point
missing or wrong. While looking and testing more I found one more additional
point to discussed here with respect to OOTB and that is making the product url
as business defined. In OOTB there is facility to define alternate url with
respect to locale in Product Content section. This is very good functionality
in perspective of internationalization of product url. This facility enable
business user to define product url for a product according to the business
requirement and locality of the business. So while creating SEO friendly url
for product this feature should pick up with high priority in comparison with
product name, But in current SEO implementation while making product url
'alternate url' from Product Content is picked up if product do not have
defined product name with it.
In my opinion product name from alternate url should picked up first and if
alternate url is not defined then should look for product name. Also to get the
product name, system should not only check for product.productName but it
should look for PRODUCT_NAME from product content and product.internalName as
well, as the name can be defined any where of the three places. What do you
think ????
was (Author: parimal):
Hi Jacques,
You have consolidate all thing very well, I don't think there is any point
missing or wrong. While looking and testing more I found one more additional
point to discussed here with respect to OOTB and that is making the product url
as business defined. In OOTB there is facility to define alternate url with
respect to local in Product Content section. This is very good functionality in
perspective of internationalization of product url. This facility enable
business user to define product url for a product according to the business
requirement and locality of the business. So while creating SEO friendly url
for product this feature should pick up with high priority in comparison with
product name, But in current SEO implementation while making product url
'alternate url' from Product Content is picked up if product do not have
defined product name with it.
In my opinion product name from alternate url should picked up first and if
alternate url is not defined then should look for product name. Also to get the
product name, system should not only check for product.productName but it
should look for PRODUCT_NAME from product content and product.internalName as
well, as the name can be defined any where of the three places. What do you
think ????
> Proposal: URL-Generation Changes
> --------------------------------
>
> Key: OFBIZ-5312
> URL: https://issues.apache.org/jira/browse/OFBIZ-5312
> Project: OFBiz
> Issue Type: New Feature
> Components: specialpurpose/ecommerce
> Affects Versions: SVN trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Minor
> Labels: changes, ecommerce, friendly, seo, url
> Fix For: SVN trunk
>
> Attachments: OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 -
> ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312
> - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch,
> OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 -
> ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312
> - ofbiz-ecommerce-seo.patch, OFBIZ-5312 - ofbiz-ecommerce-seo.patch,
> OFBIZ-5312 - ofbiz-ecommerce-seo.patch, OFBIZ-5312 -
> ofbiz-ecommerce-seo.patch, OFBiz-5312-product-ecommerce-seo-20131031.patch,
> OFBiz-5312-product-ecommerce-seo-for-seo-branch.patch,
> OFBiz-5312-product-ecommerce-seo.patch, SeoContextFilter.java.patch
>
>
> [This was proposed by Paul Piper in Nabble 7 months
> ago|http://ofbiz.135035.n4.nabble.com/Proposal-URL-Generation-Changes-td4639289.html].
> Here is quoted Paul's proposal
> {quote}
> Hey Everyone,
> over at ilscipio (www.ilscipio.com) we developed a set of functional OFBiz
> changes that we believe the entire community could benefit from. The changes
> have been implemented in parts in Syracus (www.syracus.net) for a while now,
> but we figured that some of which are too crucial for ofbiz' success in the
> long run, so we are considering the contribution (as we did with the SOLR
> component).
> As you are probably aware, OFBiz has a pretty uncommon way of generating
> URLs. Most of this has to do with the fact that OFBiz uses a servlet
> (ControlServlet) to handle all requests. The servlet is mounted at /control,
> so that it won't interfere with other servlets. Though functionally valid,
> this has the sideeffect that all urls are actually created on /control, which
> is neither pretty, nor good by any measures of SEO. It also means that a few
> 302 redirects are necessary to forward the user from / to /control/main. It
> also makes requests more complicated, since many forwards are necessary
> whenever somebody wants to move away from this implementation.
> Since this is hurtful to many of the implementers, I wanted to discuss
> whether or not you guys would be interested in the changes we have made. The
> functional changes contain:
> * Removal of /control out of all the urls
> * SEO-friendly URLS
> * Configurable product/category and other URLs
> * Frontpage mapping from /main to /
> It was tested on our end and contains all necessary improvements (Transforms,
> Sample Configuration, Servlets & Filters) for it to be applicable.
> If interested, I would create a new JIRA ticket for this and after a few
> minor internal discussions, we will gladly provide the rest of you with it.
> Regards,
> Paul
> {quote}
> There is even a patch, mostly done by Jinghai Shi, that I attach here. Even
> if it has been already used in [Syracus|http://syracus.net/] since early this
> year, some help would be needed to test it thoroughly in OFBiz.
> Then we should discuss if it's the way to go. I believe it is. Who needs a
> /control/ or /main by default in ecommerce urls? Would you not prefer
> http://localhost:8080/ecommerce/ over
> http://localhost:8080/ecommerce/control/main ?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
