[jira] [Commented] (OFBIZ-5312) Proposal: URL-Generation Changes (mostly for SEO reasons but not only)

2017-01-24 Thread Paul Foxworthy (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837156#comment-15837156
 ] 

Paul Foxworthy commented on OFBIZ-5312:
---

With the recent discussion on ecomseo on the dev mailing list, I'd like to make 
some observations here.

Good, clean URLs are good for human beings, not just for SEO. .../control/... 
is definitely not a good, clean URL.

Good, clean URLs are beneficial for all of OFBiz, not just e-commerce, not just 
product information.

Several times in the discussion on this issue, people have said different URLs 
should not lead to the same content. It is true duplicate content will 
disadvantage you with Google and other search engines. The solution is *not* 
one unique URL for given content. The solution is to add a canonical URL link 
(https://en.wikipedia.org/wiki/Canonical_link_element) to the content, to make 
clear the primary URL and to make clear alternative URLs are just that, 
alternative paths to the same thing.

One of the strengths of OFBiz is that a product can belong to more than one 
category. If we have URLs containing categories, naturally there will be more 
than one URL for a product. For example

https://mysite.com/products/SKU-1234
https://mysite.com/products/christmas-hat
https://mysite.com/products/christmas/christmas-hat
https://mysite.com/products/hats/christmas-hat

might all get you to the same page. 

That's a good thing not a bad thing, provided we get the canonical URL right.

> Proposal: URL-Generation Changes (mostly for SEO reasons but not only)
> --
>
> Key: OFBIZ-5312
> URL: https://issues.apache.org/jira/browse/OFBIZ-5312
> Project: OFBiz
>  Issue Type: New Feature
>  Components: specialpurpose/ecommerce
>Affects Versions: Trunk
>Reporter: Jacques Le Roux
>Assignee: Jacques Le Roux
>Priority: Minor
>  Labels: changes, ecommerce, friendly, seo, url
> Fix For: 16.11.01
>
> Attachments: classloaderpatch.txt, 
> OFBiz-5312-allowpaths-email-jsp-patch-20140625.patch, 
> OFBIZ-5312-infinite-loop-20141209.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 - 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 

[jira] [Commented] (OFBIZ-8316) Update Apache Solr/Lucene to release 6.2.1

2017-01-24 Thread Shi Jinghai (JIRA)

[ 
https://issues.apache.org/jira/browse/OFBIZ-8316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15837120#comment-15837120
 ] 

Shi Jinghai commented on OFBIZ-8316:


A temp fix is submitted in rev. 1780133.

To caopengan:

Hi Pengan,

It would be great if you can change the products and content indexes folder 
structure like:
runtime/indexes/products/index
runtime/indexes/products/snapshot_metadata
runtime/indexes/products/tlog

runtime/indexes/content/index
runtime/indexes/content/snapshot_metadata
runtime/indexes/content/tlog

TIA,


> Update Apache Solr/Lucene to release 6.2.1
> --
>
> Key: OFBIZ-8316
> URL: https://issues.apache.org/jira/browse/OFBIZ-8316
> Project: OFBiz
>  Issue Type: Improvement
>  Components: specialpurpose/lucene, specialpurpose/solr
>Affects Versions: Trunk
>Reporter: Michael Brohl
>Assignee: Shi Jinghai
>Priority: Minor
> Attachments: OFBIZ-8316_corrected.patch, 
> ofbiz-truck-lucene-6.2.1.patch, ofbiz-truck-solr-6.2.1.patch, 
> solr6.2.1_1.patch
>
>
> According to the announcements in 
> https://lists.apache.org/thread.html/5d2cb1ecbe04c6c40b8eeba3b7f8da586d1271af98c9b07ceee8ada2@%3Cannounce.apache.org%3E
>  and 
> https://lists.apache.org/thread.html/c1269b52229f6bce68399e813b7c6b79eb3f6283ae21bde11c82fc7c@%3Cannounce.apache.org%3E
>  there is a new Solr/Lucene release available.
> This issue takes care of the update.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)