Changeset 3497 in products
- Timestamp:
- Aug 13, 2012 12:35:20 PM (12 years ago)
- Location:
- quintagroup.plonegooglesitemaps/branches/sitemap_date
- Files:
-
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
quintagroup.plonegooglesitemaps/branches/sitemap_date/README.txt
r3325 r3497 2 2 ============ 3 3 4 Plone Google Sitemaps product allows Plone websites to get better visibility forGoogle search engine5 by providing it with complete listing of URLs to website content.4 Plone Google Sitemaps product allows Plone websites to get better visibility on Google search engine 5 by providing it with a complete listing of content URLs to website. 6 6 7 7 .. figure:: http://quintagroup.com/services/plone-development/products/google-sitemaps/plone-google-sitemaps.png … … 15 15 16 16 * ``Content Sitemap`` - is a regular list of pages on your website. Creating and submitting such a Sitemap 17 lets Google know about all the pages on your Plone web 17 lets Google know about all the pages on your Plone website, including URLs that may not be discoverable 18 18 by Google's normal crawling process. 19 * ``Mobile Sitemap`` - is a specific type of Sitemap, that indexes all site URLs that serve content for 20 mobile devices. 19 * ``Mobile Sitemap`` - is a specific type of Sitemap, that indexes all site URLs that serve mobile-oriented content. 21 20 * ``News Sitemap`` - is different from regular Sitemaps, since it is specific to Google News only. 22 It uses the Sitemap protocol, with additional News-specific tags, defined by Google. The package brings 23 additional Google Sitem pas tab to News Item content type for defining NewsSitemap-specific meta tags.21 It uses the Sitemap protocol, with additional News-specific tags, defined by Google. The package brings protocol with 22 additional Google Sitemaps tab to News Item content type for defining NewsSitemap-specific meta tags. 24 23 25 Different Sitemap types index their own content and do not depend on other Sitemaps. 24 Different Sitemap types index their own content and do not depend on other Sitemaps. 26 25 27 26 Usage … … 39 38 ========= 40 39 41 If you UPGRADE older version of quintagroup.plonegooglesitemaps package to newer:42 --------------------------------------------------------------------------------- 40 If you UPGRADE an older version of quintagroup.plonegooglesitemaps package to a newer one: 41 ------------------------------------------------------------------------------------------ 43 42 44 * In your zope instance configuration or buildout -replace old package version with a new one.43 * In your zope instance configuration or buildout replace old package version with a new one. 45 44 * Run plone instance and reinstall package with Quickinstaller tool ("Add-on Products" in plone control panel). 46 45 47 If you rMIGRATE from Products.qPloneGoogleSitemaps to quintagroup.plonegooglesitemaps:48 ------------------------------------------------------------------------------------- -46 If you MIGRATE from Products.qPloneGoogleSitemaps to quintagroup.plonegooglesitemaps: 47 ------------------------------------------------------------------------------------- 49 48 50 * Add to new plone instance/buildout both qPloneGoogleSitemaps product and last version quintagroup.plonegooglesitemaps package.49 * Add to a new Plone instance/buildout both qPloneGoogleSitemaps product and last version quintagroup.plonegooglesitemaps package. 51 50 * Copy Data.fs from old Plone instance to new one. 52 * Start your new zope instance/buildout.51 * Start your new Zope instance/buildout. 53 52 54 53 The following steps are performed in the plone instance: -
quintagroup.plonegooglesitemaps/branches/sitemap_date/docs/HISTORY.txt
r3413 r3497 2 2 ========= 3 3 4 1. 7.1 - unreleased4 1.8.0 (2012-08-13) 5 5 ------------------ 6 6 7 * Updated modification date in Sitemaps for folderish objects which have 8 default pages. 9 Sitemap types have their own index (sitemap_date) 10 which helps to generate Sitemaps without default pages. 11 Index contains the last modification date from this object or 12 from default page. As а result you will not see default pages 13 in sitemap types. 14 [potar] 15 * Added tests for index (sitemap_date), updated tests. 16 [potar] 7 17 * Added deleting (button) the verification file 8 18 [potar] 9 10 19 * Updated view quintagroup.plonegooglesitemaps (tabs) 11 20 [potar] 21 12 22 13 23 1.7.0 (2011-10-28) -
quintagroup.plonegooglesitemaps/branches/sitemap_date/quintagroup/plonegooglesitemaps/filters.txt
r3494 r3497 103 103 form, it should be empty by default settings. 104 104 105 >>> file("/tmp/browser. 0.html","wb").write(browser.contents)105 >>> file("/tmp/browser.test.html","wb").write(browser.contents) 106 106 >>> blackout_list = browser.getControl("Blackout entries") 107 107 >>> blackout_list … … 143 143 144 144 >>> browser.open(smview_url) 145 >>> file("/tmp/browser. 1.html","wb").write(browser.contents)145 >>> file("/tmp/browser.test.html","wb").write(browser.contents) 146 146 >>> no_filters_content = browser.contents 147 147
Note: See TracChangeset
for help on using the changeset viewer.