XML Sitemap & Google News feeds - Version 4.5.1

Version Description

Fix Persistent/Stored XSS vulnerability on admin page, thanks to Sneha Rajguru @Sneharajguru

=

Download this release

Release Info

Developer RavanH
Plugin Icon 128x128 XML Sitemap & Google News feeds
Version 4.5.1
Comparing to
See all releases

Code changes from version 4.5 to 4.5.1

Files changed (2) hide show
  1. readme.txt +34 -31
  2. xml-sitemap.php +2 -2
readme.txt CHANGED
@@ -3,14 +3,14 @@ Contributors: RavanH
3
  Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=ravanhagen%40gmail%2ecom&item_name=XML%20Sitemap%20Feed&item_number=3%2e8&no_shipping=0&tax=0&bn=PP%2dDonationsBF&charset=UTF%2d8&lc=us
4
  Tags: sitemap, xml sitemap, news sitemap, sitemap.xml, robots.txt, Google, Google News, Yahoo, Bing, , Yandex, Baidu, seo, feed, polylang, image sitemap
5
  Requires at least: 3.2
6
- Tested up to: 4.4
7
- Stable tag: 4.5
8
 
9
  XML and Google News Sitemaps to feed the hungry spiders. Multisite, WP Super Cache and Polylang compatible.
10
 
11
  == Description ==
12
 
13
- This plugin dynamically creates feeds that comply with the **XML Sitemap** and the **Google News Sitemap** protocol. **Multisite** and **Polylang** compatible and there are no files created. Options can be found on **Settings > Reading** to control which sitemaps, which post and taxonomy types are included, how priority is calculated, who to ping and set additional robots.txt rules.
14
 
15
  The main advantage of this plugin over other XML Sitemap plugins is **simplicity**. No need to change file or folder permissions, move files or spend time tweaking difficult plugin options.
16
 
@@ -22,13 +22,13 @@ Please read the FAQ's for info on how to get your articles listed on Google News
22
 
23
  **Compatible with caching plugins** like WP Super Cache, W3 Total Cache and Quick Cache that cache feeds, allowing a faster serving to the impatient (when hungry) spider.
24
 
25
- **NOTES:**
26
 
27
  1. If you _do not use fancy URL's_ or you have WordPress installed in a _subdirectory_, a dynamic **robots.txt will NOT be generated**. You'll have to create your own and upload it to your site root! See FAQ's.
28
 
29
  2. On large sites, it is advised to use a good caching plugin like **WP Super Cache**, **Quick Cache** or **W3 Total Cache** to improve your site _and_ sitemap performance.
30
 
31
- = Features =
32
 
33
  **XML Sitemap**
34
 
@@ -36,7 +36,7 @@ Please read the FAQ's for info on how to get your articles listed on Google News
36
  * Sitemap with custom URLs optional.
37
  * Custom/static sitemaps can be added to the index.
38
  * Completely **automatic** post URL _priority_ and _change frequency_ calculation based on post age and comment and trackback activity.
39
- * Works out-of-the-box, even on **Multisite** installations.
40
  * Optionally include Image tags with caption and title for featured images or attached images.
41
  * Pings Google, Bing & Yahoo, Yandex and Baidu on new post publication.
42
  * Options to define which post types and taxonomies get included in the sitemap and automatic priority calculation rules.
@@ -62,9 +62,9 @@ Please read the FAQ's for info on how to get your articles listed on Google News
62
  - **French** * R.A. van Hagen http://status301.net (version 4.2) (improved translation or suggestions needed!)
63
  - **Indonesian** * Nasrulhaq Muiz http://al-badar.net/ (version 4.2)
64
  - **Italian** * Raffaello Tesi http://www.raffaellotesi.com (version 4.3.2)
65
- - **Serbian** * WPdiscounts http://wpdiscounts.com/ (version 4.1)
66
  - **Spanish** * Andrew Kurtis - WebHostingHub Support http://www.webhostinghub.com/ (version 4.3.2)
67
- - **Ukrainian** * Cmd Software http://www.cmd-soft.com/ (version 4.0)
68
 
69
  New transtations will be accepted and listed here. See translation instructions under [Other Notes](http://wordpress.org/plugins/xml-sitemap-feed/other_notes/).
70
 
@@ -133,7 +133,7 @@ Yes. You can find default settings for priority, changefreq and lastmod on **Set
133
 
134
  = Do I need to submit the sitemap to search engines? =
135
 
136
- No. In normal circumstances, your site will be indexed by the major search engines before you know it. The search engines will be looking for a robots.txt file and (with this plugin activated) find a pointer in it to the XML Sitemap on your blog. The search engines will return on a regular basis to see if your site has updates.
137
 
138
  Besides that, Google and Bing are pinged upon each new publication.
139
 
@@ -147,7 +147,7 @@ Yes, Google and Bing are pinged upon each new publication. Unless you disable th
147
 
148
  That depends. In normal circumstances, if you have no physical robots.txt file in your site root, the new sitemap url will be automatically added to the dynamic robots.txt that is generated by WordPress. But in some cases this might not be the case.
149
 
150
- If you use a static robots.txt file in your website root, you will need to open it in a text editor. If there is already a line with `Sitemap: http://yourblogurl.tld/sitemap.xml` you can just leave it like it is. But if there is no sitemap referrence there, add it (adapted to your site url) to make search engines find your XML Sitemap.
151
 
152
  Or if you have WP installed in a subdirectory, on a server without rewrite_rules or if you do not use fancy URLs in your Permalink structure settings. In these cases, WordPress will need a little help in getting ready for XML Sitemap indexing. Read on in the **WordPress** section for more.
153
 
@@ -156,15 +156,15 @@ Or if you have WP installed in a subdirectory, on a server without rewrite_rules
156
  That depends on where the index.php and .htaccess of your installation reside. If they are in the root while the rest of the WP files are installed in a subdir, so the site is accessible from your domain root, you do not have to do anything. It should work out of the box. But if the index.php is together with your wp-config.php and all other WP files in a subdir, meaning your blog is only accessible via that subdir, you need to manage your own robots.txt file in your **domain root**. It _has_ to be in the root (!) and needs a line starting with `Sitemap:` followed by the full URL to the sitemap feed provided by XML Sitemap Feed plugin. Like:
157
  `
158
  Sitemap: http://yourblogurl.tld/subdir/sitemap.xml
159
- `
160
 
161
  If you already have a robots.txt file with another Sitemap reference like it, just add the full line below or above it.
162
 
163
  = Do I need to use a fancy Permalink structure? =
164
 
165
- No. While I would advise you to use any one of the nicer Permalink structures for better indexing, you might not be able to (or don't want to) do that. If so, you can still use this plugin:
166
 
167
- Check to see if the URL yourblog.url/?feed=sitemap does produce a feed. Now manually upload your own robots.txt file to your website root containing:
168
  `
169
  Sitemap: http://yourblog.url/?feed=sitemap
170
 
@@ -197,20 +197,20 @@ If that's not the case, you are probably using a caching plugin or your browser
197
 
198
  = I use a caching plugin but the sitemap is not cached =
199
 
200
- Some caching plugins have the option to switch on/off caching of feeds. Make sure it is turned on.
201
 
202
  Frederick Townes, developer of **W3 Total Cache**, says: "There's a checkbox option on the page cache settings tab to cache feeds. They will expire according to the expires field value on the browser cache setting for HTML."
203
 
204
  The Google News sitemap is designed to NOT be cached.
205
 
206
- = I get an ERROR when opening the sitemap or robots.txt! =
207
 
208
  The absolute first thing you need to check is your blogs privacy settings. Go to **Settings > Privacy** and make sure you are **allowing search engines to index your site**. If they are blocked, your sitemap will _not_ be available.
209
 
210
  Then, you might want to make sure that there is at least ONE post published. WordPress is known to send 404 status headers with feed requests when there are NO posts. Even though the plugin tries to prevent that, in some cases the wrong status header will get sent anyway and Google Webmaster Tools will report a vague message like:
211
 
212
- We encountered an error while trying to access your Sitemap.
213
- Please ensure your Sitemap follows our guidelines and can be
214
  accessed at the location you provided and then resubmit.
215
 
216
  If that did not solve the issue, check the following errors that might be encountered along with their respective solutions:
@@ -221,16 +221,16 @@ Try to refresh the Permalink structure in WordPress. Go to Settings > Permalinks
221
 
222
  **404 page instead of both sitemap.xml and robots.txt**
223
 
224
- There are plugins like Event Calendar (at least v.3.2.beta2) known to mess with rewrite rules, causing problems with WordPress internal feeds and robots.txt generation and thus conflict with the XML Sitemap Feed plugin. Deactivate all plugins and see if you get a basic robots.txt file showing:
225
  `
226
  User-agent: *
227
  Disallow:
228
  `
229
- Reactivate your plugins one by one to find out which one is causing the problem. Then report the bug to the plugin developer.
230
 
231
  **404 page instead of robots.txt while sitemap.xml works fine**
232
 
233
- There is a know issue with WordPress (at least up to 2.8) not generating a robots.txt when there are _no posts_ with _published_ status. If you use WordPress as a CMS with only _pages_, this will affect you.
234
 
235
  To get around this, you might either at least write one post and give it _Private_ status or alternatively create your own robots.txt file containing:
236
  `
@@ -243,7 +243,7 @@ and upload it to your web root...
243
 
244
  **Error loading stylesheet: An unknown error has occurred**
245
 
246
- On some setups (usually using the WordPress MU Domain Mapping plugin) this error occurs. The problem is known, the cause is not... Until I find out why this is happening, please take comfort in knowing that this only affects reading the sitemap in normal browsers but will NOT affect any spidering/indexing on your site. The sitemap is still readable by all search engines!
247
 
248
  **XML declaration allowed only at the start of the document**
249
 
@@ -259,7 +259,7 @@ A. If you see strange output in the first few lines (head tags) of the source, t
259
 
260
  B. If the source is empty or incomplete then you're probably experiencing an issue with your servers PHP memory limit. In those cases, you should see a messages like `PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted.` in your server/account error log file.
261
 
262
- This can happen on large sites. To avoid these issues, there is an option to split posts over different sitemaps on Settings > Reading. Try different settings, each time revisiting the main sitemap index file and open different sitemaps listed there to check.
263
 
264
  Read more on [Increasing memory allocated to PHP](http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP) (try a value higher than 256M) or ask your hosting provider what you can do.
265
 
@@ -273,7 +273,7 @@ Yes. In fact, it has been designed for it. Tested on WPMU 2.9.2 and WPMS 3+ both
273
  1. Install PoEdit on your computer.
274
  1. Go to this plugins /languages/ directory.
275
  1. If there is no .po file that corresponds with your language yet, rename the template translation database xml-sitemap-feed-xx_XX.po by replacing the xx with your language code and XX with your country code.
276
- 1. Open the .po file of your language with PoEdit.
277
  1. Go to Edit > Preferences and on the tab Editor check the option to compile a .mo database on save automatically. Close with OK.
278
  1. Go to Catalog > Settings and set your name, e-mail address, language and country. Close with OK.
279
  1. Go to Catalog > Update from POT-file and select the main xml-sitemap-feed.pot file. Then accept all new and removed translation strings with OK.
@@ -293,11 +293,14 @@ Thanks for sharing your translation :)
293
 
294
  == Upgrade Notice ==
295
 
296
- = 4.5 =
297
- Set access or exclude individual posts from Google News sitemap. Improved cache handling and Nginx Helper compatibility.
298
 
299
  == Changelog ==
300
 
 
 
 
301
  = 4.5 =
302
  * Set Google News access tag per post
303
  * Exclude posts from Google News sitemap
@@ -320,7 +323,7 @@ Set access or exclude individual posts from Google News sitemap. Improved cache
320
  * Optionally limit posts to certain categories in News Sitemap
321
  * Noindex response header for sitemaps to keep them out of search results
322
  * Static sitemap stylesheets
323
- * Controversial default robots.txt rules removed
324
  * DB query streamlining
325
  * BUGFIX: fatal error on . (dot) as category base in permalinks
326
  * BIGFIX: PHP Strict notices
@@ -353,14 +356,14 @@ Set access or exclude individual posts from Google News sitemap. Improved cache
353
  * Rearranged settings section
354
  * FIX: replace permalink, title and bloginfo rss filter hooks with own
355
 
356
- = 4.2.3 =
357
  * BUGFIX: Empty ping options after disabling the main sitemap
358
  * BUGFIX: Empty language tag for Google News tags in posts sitemap
359
  * Small back end changes
360
  * NEW: Custom post types split by year/month
361
 
362
  = 4.2 =
363
- * NEW: Image & News tags
364
  * NEW: Exclude pages/posts
365
 
366
  = 4.1.4 =
@@ -373,7 +376,7 @@ Set access or exclude individual posts from Google News sitemap. Improved cache
373
  = 4.1 =
374
  * NEW: Ping Google and Bing on new publications
375
  * NEW: Set priority per post
376
- * NEW: Priority calculation options
377
  * NEW: Option to split posts by year or month for faster generation of each sitemap
378
  * Reduced queries to increase performance
379
  * Improved Lastmod and Changefreq calculations
@@ -420,7 +423,7 @@ Set access or exclude individual posts from Google News sitemap. Improved cache
420
  = 3.8.5 =
421
  * **xLanguage support** based on code and testing by **Daniele Pelagatti**
422
  * new FILTER HOOK `robotstxt_sitemap_url` for any translate and url changing plugins.
423
- * BUGFIX: Decimal separator cannot be a comma!
424
 
425
  = 3.8.3 =
426
  * filter out external URLs inserted by plugins like Page Links To (thanks, Francois)
@@ -472,7 +475,7 @@ Set access or exclude individual posts from Google News sitemap. Improved cache
472
 
473
  = 2.0 =
474
  * priority calculation based on comments and age
475
- * changefreq based on comments
476
 
477
  = 1.0 =
478
  * changed feed template location to avoid the need to relocate files outside the plugins folder
3
  Donate link: https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=ravanhagen%40gmail%2ecom&item_name=XML%20Sitemap%20Feed&item_number=3%2e8&no_shipping=0&tax=0&bn=PP%2dDonationsBF&charset=UTF%2d8&lc=us
4
  Tags: sitemap, xml sitemap, news sitemap, sitemap.xml, robots.txt, Google, Google News, Yahoo, Bing, , Yandex, Baidu, seo, feed, polylang, image sitemap
5
  Requires at least: 3.2
6
+ Tested up to: 4.5
7
+ Stable tag: 4.5.1
8
 
9
  XML and Google News Sitemaps to feed the hungry spiders. Multisite, WP Super Cache and Polylang compatible.
10
 
11
  == Description ==
12
 
13
+ This plugin dynamically creates feeds that comply with the **XML Sitemap** and the **Google News Sitemap** protocol. **Multisite** and **Polylang** compatible and there are no files created. Options can be found on **Settings > Reading** to control which sitemaps, which post and taxonomy types are included, how priority is calculated, who to ping and set additional robots.txt rules.
14
 
15
  The main advantage of this plugin over other XML Sitemap plugins is **simplicity**. No need to change file or folder permissions, move files or spend time tweaking difficult plugin options.
16
 
22
 
23
  **Compatible with caching plugins** like WP Super Cache, W3 Total Cache and Quick Cache that cache feeds, allowing a faster serving to the impatient (when hungry) spider.
24
 
25
+ **NOTES:**
26
 
27
  1. If you _do not use fancy URL's_ or you have WordPress installed in a _subdirectory_, a dynamic **robots.txt will NOT be generated**. You'll have to create your own and upload it to your site root! See FAQ's.
28
 
29
  2. On large sites, it is advised to use a good caching plugin like **WP Super Cache**, **Quick Cache** or **W3 Total Cache** to improve your site _and_ sitemap performance.
30
 
31
+ = Features =
32
 
33
  **XML Sitemap**
34
 
36
  * Sitemap with custom URLs optional.
37
  * Custom/static sitemaps can be added to the index.
38
  * Completely **automatic** post URL _priority_ and _change frequency_ calculation based on post age and comment and trackback activity.
39
+ * Works out-of-the-box, even on **Multisite** installations.
40
  * Optionally include Image tags with caption and title for featured images or attached images.
41
  * Pings Google, Bing & Yahoo, Yandex and Baidu on new post publication.
42
  * Options to define which post types and taxonomies get included in the sitemap and automatic priority calculation rules.
62
  - **French** * R.A. van Hagen http://status301.net (version 4.2) (improved translation or suggestions needed!)
63
  - **Indonesian** * Nasrulhaq Muiz http://al-badar.net/ (version 4.2)
64
  - **Italian** * Raffaello Tesi http://www.raffaellotesi.com (version 4.3.2)
65
+ - **Serbian** * WPdiscounts http://wpdiscounts.com/ (version 4.1)
66
  - **Spanish** * Andrew Kurtis - WebHostingHub Support http://www.webhostinghub.com/ (version 4.3.2)
67
+ - **Ukrainian** * Cmd Software http://www.cmd-soft.com/ (version 4.0)
68
 
69
  New transtations will be accepted and listed here. See translation instructions under [Other Notes](http://wordpress.org/plugins/xml-sitemap-feed/other_notes/).
70
 
133
 
134
  = Do I need to submit the sitemap to search engines? =
135
 
136
+ No. In normal circumstances, your site will be indexed by the major search engines before you know it. The search engines will be looking for a robots.txt file and (with this plugin activated) find a pointer in it to the XML Sitemap on your blog. The search engines will return on a regular basis to see if your site has updates.
137
 
138
  Besides that, Google and Bing are pinged upon each new publication.
139
 
147
 
148
  That depends. In normal circumstances, if you have no physical robots.txt file in your site root, the new sitemap url will be automatically added to the dynamic robots.txt that is generated by WordPress. But in some cases this might not be the case.
149
 
150
+ If you use a static robots.txt file in your website root, you will need to open it in a text editor. If there is already a line with `Sitemap: http://yourblogurl.tld/sitemap.xml` you can just leave it like it is. But if there is no sitemap referrence there, add it (adapted to your site url) to make search engines find your XML Sitemap.
151
 
152
  Or if you have WP installed in a subdirectory, on a server without rewrite_rules or if you do not use fancy URLs in your Permalink structure settings. In these cases, WordPress will need a little help in getting ready for XML Sitemap indexing. Read on in the **WordPress** section for more.
153
 
156
  That depends on where the index.php and .htaccess of your installation reside. If they are in the root while the rest of the WP files are installed in a subdir, so the site is accessible from your domain root, you do not have to do anything. It should work out of the box. But if the index.php is together with your wp-config.php and all other WP files in a subdir, meaning your blog is only accessible via that subdir, you need to manage your own robots.txt file in your **domain root**. It _has_ to be in the root (!) and needs a line starting with `Sitemap:` followed by the full URL to the sitemap feed provided by XML Sitemap Feed plugin. Like:
157
  `
158
  Sitemap: http://yourblogurl.tld/subdir/sitemap.xml
159
+ `
160
 
161
  If you already have a robots.txt file with another Sitemap reference like it, just add the full line below or above it.
162
 
163
  = Do I need to use a fancy Permalink structure? =
164
 
165
+ No. While I would advise you to use any one of the nicer Permalink structures for better indexing, you might not be able to (or don't want to) do that. If so, you can still use this plugin:
166
 
167
+ Check to see if the URL yourblog.url/?feed=sitemap does produce a feed. Now manually upload your own robots.txt file to your website root containing:
168
  `
169
  Sitemap: http://yourblog.url/?feed=sitemap
170
 
197
 
198
  = I use a caching plugin but the sitemap is not cached =
199
 
200
+ Some caching plugins have the option to switch on/off caching of feeds. Make sure it is turned on.
201
 
202
  Frederick Townes, developer of **W3 Total Cache**, says: "There's a checkbox option on the page cache settings tab to cache feeds. They will expire according to the expires field value on the browser cache setting for HTML."
203
 
204
  The Google News sitemap is designed to NOT be cached.
205
 
206
+ = I get an ERROR when opening the sitemap or robots.txt! =
207
 
208
  The absolute first thing you need to check is your blogs privacy settings. Go to **Settings > Privacy** and make sure you are **allowing search engines to index your site**. If they are blocked, your sitemap will _not_ be available.
209
 
210
  Then, you might want to make sure that there is at least ONE post published. WordPress is known to send 404 status headers with feed requests when there are NO posts. Even though the plugin tries to prevent that, in some cases the wrong status header will get sent anyway and Google Webmaster Tools will report a vague message like:
211
 
212
+ We encountered an error while trying to access your Sitemap.
213
+ Please ensure your Sitemap follows our guidelines and can be
214
  accessed at the location you provided and then resubmit.
215
 
216
  If that did not solve the issue, check the following errors that might be encountered along with their respective solutions:
221
 
222
  **404 page instead of both sitemap.xml and robots.txt**
223
 
224
+ There are plugins like Event Calendar (at least v.3.2.beta2) known to mess with rewrite rules, causing problems with WordPress internal feeds and robots.txt generation and thus conflict with the XML Sitemap Feed plugin. Deactivate all plugins and see if you get a basic robots.txt file showing:
225
  `
226
  User-agent: *
227
  Disallow:
228
  `
229
+ Reactivate your plugins one by one to find out which one is causing the problem. Then report the bug to the plugin developer.
230
 
231
  **404 page instead of robots.txt while sitemap.xml works fine**
232
 
233
+ There is a know issue with WordPress (at least up to 2.8) not generating a robots.txt when there are _no posts_ with _published_ status. If you use WordPress as a CMS with only _pages_, this will affect you.
234
 
235
  To get around this, you might either at least write one post and give it _Private_ status or alternatively create your own robots.txt file containing:
236
  `
243
 
244
  **Error loading stylesheet: An unknown error has occurred**
245
 
246
+ On some setups (usually using the WordPress MU Domain Mapping plugin) this error occurs. The problem is known, the cause is not... Until I find out why this is happening, please take comfort in knowing that this only affects reading the sitemap in normal browsers but will NOT affect any spidering/indexing on your site. The sitemap is still readable by all search engines!
247
 
248
  **XML declaration allowed only at the start of the document**
249
 
259
 
260
  B. If the source is empty or incomplete then you're probably experiencing an issue with your servers PHP memory limit. In those cases, you should see a messages like `PHP Fatal error: Allowed memory size of xxxxxx bytes exhausted.` in your server/account error log file.
261
 
262
+ This can happen on large sites. To avoid these issues, there is an option to split posts over different sitemaps on Settings > Reading. Try different settings, each time revisiting the main sitemap index file and open different sitemaps listed there to check.
263
 
264
  Read more on [Increasing memory allocated to PHP](http://codex.wordpress.org/Editing_wp-config.php#Increasing_memory_allocated_to_PHP) (try a value higher than 256M) or ask your hosting provider what you can do.
265
 
273
  1. Install PoEdit on your computer.
274
  1. Go to this plugins /languages/ directory.
275
  1. If there is no .po file that corresponds with your language yet, rename the template translation database xml-sitemap-feed-xx_XX.po by replacing the xx with your language code and XX with your country code.
276
+ 1. Open the .po file of your language with PoEdit.
277
  1. Go to Edit > Preferences and on the tab Editor check the option to compile a .mo database on save automatically. Close with OK.
278
  1. Go to Catalog > Settings and set your name, e-mail address, language and country. Close with OK.
279
  1. Go to Catalog > Update from POT-file and select the main xml-sitemap-feed.pot file. Then accept all new and removed translation strings with OK.
293
 
294
  == Upgrade Notice ==
295
 
296
+ = 4.5.1 =
297
+ Fix Persistent/Stored XSS vulnerability on admin page, thanks to Sneha Rajguru @Sneharajguru
298
 
299
  == Changelog ==
300
 
301
+ = 4.5.1 =
302
+ * fix Persistent/Stored XSS vulnerability on admin page, thanks to Sneha Rajguru @Sneharajguru
303
+
304
  = 4.5 =
305
  * Set Google News access tag per post
306
  * Exclude posts from Google News sitemap
323
  * Optionally limit posts to certain categories in News Sitemap
324
  * Noindex response header for sitemaps to keep them out of search results
325
  * Static sitemap stylesheets
326
+ * Controversial default robots.txt rules removed
327
  * DB query streamlining
328
  * BUGFIX: fatal error on . (dot) as category base in permalinks
329
  * BIGFIX: PHP Strict notices
356
  * Rearranged settings section
357
  * FIX: replace permalink, title and bloginfo rss filter hooks with own
358
 
359
+ = 4.2.3 =
360
  * BUGFIX: Empty ping options after disabling the main sitemap
361
  * BUGFIX: Empty language tag for Google News tags in posts sitemap
362
  * Small back end changes
363
  * NEW: Custom post types split by year/month
364
 
365
  = 4.2 =
366
+ * NEW: Image & News tags
367
  * NEW: Exclude pages/posts
368
 
369
  = 4.1.4 =
376
  = 4.1 =
377
  * NEW: Ping Google and Bing on new publications
378
  * NEW: Set priority per post
379
+ * NEW: Priority calculation options
380
  * NEW: Option to split posts by year or month for faster generation of each sitemap
381
  * Reduced queries to increase performance
382
  * Improved Lastmod and Changefreq calculations
423
  = 3.8.5 =
424
  * **xLanguage support** based on code and testing by **Daniele Pelagatti**
425
  * new FILTER HOOK `robotstxt_sitemap_url` for any translate and url changing plugins.
426
+ * BUGFIX: Decimal separator cannot be a comma!
427
 
428
  = 3.8.3 =
429
  * filter out external URLs inserted by plugins like Page Links To (thanks, Francois)
475
 
476
  = 2.0 =
477
  * priority calculation based on comments and age
478
+ * changefreq based on comments
479
 
480
  = 1.0 =
481
  * changed feed template location to avoid the need to relocate files outside the plugins folder
xml-sitemap.php CHANGED
@@ -4,7 +4,7 @@ Plugin Name: XML Sitemap & Google News feeds
4
  Plugin URI: http://status301.net/wordpress-plugins/xml-sitemap-feed/
5
  Description: Feed the hungry spiders in compliance with the XML Sitemap and Google News protocols. Happy with the results? Please leave me a <strong><a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=ravanhagen%40gmail%2ecom&item_name=XML%20Sitemap%20Feed&item_number=4%2e0&no_shipping=0&tax=0&bn=PP%2dDonationsBF&charset=UTF%2d8&lc=us">tip</a></strong> for continued development and support. Thanks :)
6
  Text Domain: xml-sitemap-feed
7
- Version: 4.5
8
  Author: RavanH
9
  Author URI: http://status301.net/
10
  */
@@ -47,7 +47,7 @@ if(!empty($_SERVER['SCRIPT_FILENAME']) && 'xml-sitemap.php' == basename($_SERVER
47
  * CONSTANTS
48
  * -------------------- */
49
 
50
- define('XMLSF_VERSION', '4.5');
51
 
52
  define('XMLSF_PLUGIN_BASENAME', plugin_basename(__FILE__));
53
 
4
  Plugin URI: http://status301.net/wordpress-plugins/xml-sitemap-feed/
5
  Description: Feed the hungry spiders in compliance with the XML Sitemap and Google News protocols. Happy with the results? Please leave me a <strong><a href="https://www.paypal.com/cgi-bin/webscr?cmd=_donations&business=ravanhagen%40gmail%2ecom&item_name=XML%20Sitemap%20Feed&item_number=4%2e0&no_shipping=0&tax=0&bn=PP%2dDonationsBF&charset=UTF%2d8&lc=us">tip</a></strong> for continued development and support. Thanks :)
6
  Text Domain: xml-sitemap-feed
7
+ Version: 4.5.1
8
  Author: RavanH
9
  Author URI: http://status301.net/
10
  */
47
  * CONSTANTS
48
  * -------------------- */
49
 
50
+ define('XMLSF_VERSION', '4.5.1');
51
 
52
  define('XMLSF_PLUGIN_BASENAME', plugin_basename(__FILE__));
53