[
https://issues.apache.org/jira/browse/OFBIZ-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811298#comment-13811298
]
Paul Piper commented on OFBIZ-5312:
-----------------------------------
{quote}
1. Url contains category/ or product/ as prefix - Is it posible to remove this
prefix from the category and product url? Although I know these prefix is used
to differanciate the category and product request at filtration level, I'm
asking these for posiblity, and if yes then what should the best approch?{quote}
You do need to have "some" prefix to work your way around one or the other, so
removing it entirely is not really an option at this moment. Otherwise you risk
problems when a category "shoe" also happens to be in the identifier for a
product of sorts. From a SEO perspective, an identifier doesn't hurt, more
importantly you have to make sure that the urls are unique and contain some of
the keywords connected to the page they deliver. So I would say: let's focus on
the proper url structure frist, before moving on.
{quote}
2. Changing the url pattern of category is configurable using config files or
it require customization at code level?
eg. - Current url for category contains the name of current category only
er-respective of category level, but in my comment the pattern contains
parent/child hierarchy including level. So is it configurable using config file?
{quote}
I am uncertain I understand correctly. What is the behavior you want to
achieve? It should be configurable in most cases...
{quote}
3. Adding the productId/categoryId in url should be configurable, so that
business can take decision on the basis of there requiement and intrest.
{quote}
Unless we add a new entity that maps Ids to paths, there is currently no way to
go without the ids. From a SEO perspective, it doesn't hurt, however and is
probably the best way to keep urls unique. Even with auto-generated full urls,
it may be that you have to add a number to keep urls unique, so I say it isn't
really a necessity anyway.
{quote}
4. How the content url can be configured? - For the seo perspective I feel the
url should be Domain_Name/content/content_name.
{quote}
We focused on most of the other aspects of the auto-generated urls. I do agree
that we may want to take a second look at the cms implementation for ofbiz...
{quote}
5. Similarly the url for search should be Domain_Name/search/keyword - so these
urls can be configured?
{quote}
In addition to 4. I think that both could be implemented without too much
effort. Take a look at how the products / categories were handled. Perhaps you
can supply a patch?
{quote}
6. Configuration files and its utility class contains various configuration
parameters and there respective effect in url, but I think most of us don't
know about all parameters. So it will be really helpful if at lease these
paramerers can be defined.
{quote}
What would be the benefit? Shouldn't we rather begin documenting the parameters
we use within ofbiz applications?
> 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)
