Changes between Version 82 and Version 83 of qPloneGoogleSitemaps


Ignore:
Timestamp:
Feb 15, 2011 12:04:30 PM (10 years ago)
Author:
olha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • qPloneGoogleSitemaps

    v82 v83  
    8989== FAQs == 
    9090 
    91 === 1. Why the generated sitemap.xml displays URLs with the IP address like this: ''999.999.999.999:8080/myplonesite'' instead of the URL ''www.plonesite.com''? === 
     91=== 1. Why the generated sitemap.xml displays URLs with the IP address like this: ''999.999:8080/myplonesite'' instead of the URL ''www.plonesite.com''? === 
    9292 
    93 quintagroup.plonegooglesitemaps uses 'canonical_url' catalog metadata field while building the sitemap.xml. You might get wrong values cataloged when creating sitemap through internal URL. To fix this - login to your Plone site via your site's real URL (''www.plonesite.com'') and update portal_catalog to fix the cataloged values. 
     93'''Method 1.''' 
    9494 
    95 Also, to fix the above-mentioned issue - insert the following line into '''URL processing Regular Expressions''' on a sitemap edit form: 
     95To fix this issue - insert the following line into '''URL processing Regular Expressions''' on a sitemap edit form: 
    9696 
    9797{{{ 
     
    101101where ''[you_site\/internal\/path]'' - is URL via which you edit your site, and ''[domain]'' - is site production URL. 
    102102 
    103 '''Example''': for our site ''http://quintagroup.com'' we use ''!http://www.quinta.qg:8080/www/www'' internal URL, so, to configure right sitemap URLs we insert: 
     103For example: for the site ''!http://plonesite.com'' we use ''!http://999.999:8080/myplonesite'' internal URL, so, to configure right sitemap URLs we insert: 
    104104 
    105105[[Image(url-processing.png, nolink)]]   
     106 
     107'''Method 2.''' 
     108 
     109quintagroup.plonegooglesitemaps uses 'canonical_url' catalog metadata field while building the sitemap.xml. You might get wrong values cataloged when creating sitemap through internal URL. To fix this - login to your Plone site via your site's real URL (''www.plonesite.com'') and update portal_catalog to fix the cataloged values. 
     110 
     111