XML Sitemap for XenForo 1.3 [Not needed, included in 1.4]

get this message in webmaster tools


http://www.opelteams.de/: Increase in authorization permission errors
8. Juli 2013
Google detected a significant increase in the number of URLs we were blocked from crawling due to authorization permission errors.



Recommended action

  • Check the Crawl Errors page in Webmaster Tools.
  • Check if your server or host is blocking Googlebot.
  • If you don't want Google to crawl these pages, consider adding them to your robots.txt.
 
Is it including forums not viewable by guests?
I personally checked our sitemaps and made sure this is not happening. It will not show up, but make sure that you do use usergroup based permission blocking, and not just invisibility on the node.
 
guests can see me at all

my Robots
User-agent: *
Disallow: /account*
Disallow: /help*
Disallow: /misc/style*
Disallow: /misc/quick-navigation-menu*
Disallow: /login*
Disallow: /logout*
Disallow: /lost-password*
Disallow: /register*
Disallow: /reports*
Disallow: /search*
Disallow: /conversations*
Disallow: /css.php
Disallow: /cron.php
Disallow: /admin.php
Disallow: /js
Disallow: /styles
Disallow: /attachments/*
Disallow: /members/*
Disallow: /profile-posts/*
Disallow: /online/*
Disallow: /recent-activity/*

Sitemap: http://www.opelteams.de/sitemap/sitemap.xml.gz
 
get this message in webmaster tools


http://www.opelteams.de/: Increase in authorization permission errors
8. Juli 2013
Google detected a significant increase in the number of URLs we were blocked from crawling due to authorization permission errors.



Recommended action

  • Check the Crawl Errors page in Webmaster Tools.
  • Check if your server or host is blocking Googlebot.
  • If you don't want Google to crawl these pages, consider adding them to your robots.txt.

Me too :(
 
This doesn't mean anything. It means Googlebot can't get to every single location, including locations blocked in robots.txt. You can edit robots in your Options once this add-on is installed. There is no reason Google needs to index, or try to access, cron.php, for example. Webmaster Tools is telling you it can't gain access to certain stuff because its blocked, intentionally. The intentional blocking of content is usually to protect it from public disclosure and to prevent junk from getting in the index. This is not a penalization of your account, its just a notification that you've disallowed some locations to be indexed.
 
Rigel Kentaurus updated Sitemap for XenForo [1.2 compatible] with a new update entry:

1.3.1 Fix for Route Filters

If you like this add-on, please post a review. It takes 1 minute and I enjoy the feedback! :)

Bug fixes
  • The generated sitemap was not taking into consideration the route filters. This change will take whatever configuration you set for outgoing filters and will use that when generating the threads, forums, and everything else
 
Thanks for building this.

Unfortunately I got an error when I attempted to run it, which I assume is due to my server's configuration.

Any help would be much appreciated.

*********************************************
Server Error
gzopen(sitemap/sitemap.xml.gz) [function.gzopen]: failed to open stream: Permission denied

  1. XenForo_Application::handlePhpError()
  2. gzopen() in XfAddOns/Sitemap/Sitemap/Base.php at line 93
  3. XfAddOns_Sitemap_Sitemap_Base->save() in XfAddOns/Sitemap/Sitemap/Index.php at line 53
  4. XfAddOns_Sitemap_Sitemap_Index->generate() in XfAddOns/Sitemap/Model/Sitemap.php at line 148
  5. XfAddOns_Sitemap_Model_Sitemap->runAllAvailableSiteMaps() in XfAddOns/Sitemap/CronEntry/RebuildSitemap.php at line 40
  6. XfAddOns_Sitemap_CronEntry_RebuildSitemap::run()
  7. call_user_func() in XenForo/Model/Cron.php at line 356
  8. XenForo_Model_Cron->runEntry() in XenForo/ControllerAdmin/Cron.php at line 213
  9. XenForo_ControllerAdmin_Cron->actionRun() in XenForo/FrontController.php at line 337
  10. XenForo_FrontController->dispatch() in XenForo/FrontController.php at line 134
  11. XenForo_FrontController->run() in /home/useraccountname/public_html/admin.php at line 13
 
I did the directory but maybe it didn't do the contents. I'll try again.

BTW, do I leave them all at 777 or should I change any back to more secure settings?

Thanks for the help.
 
That was it. Thanks.

I Chmoded the sitemap folder and all recursive files and directories to 777. Can I keep it that way or should I change anything else to more secure settings?
 
Back
Top Bottom