WordPress.org

Ready to get started?Download WordPress

Forums

Better WordPress Google XML Sitemaps (with sitemapindex, multi-site and Google News sitemap support)
[resolved] [Plugin: Better WordPress Google XML Sitemaps (with sitemapindex and Multi-site support)] 404 Error (26 posts)

  1. robnalexpress
    Member
    Posted 2 years ago #

    2 site multisite Running W3TC 0.9.2.4. I get 404 error when trying to open sitemapindex (http://mysite.com/sitemapindex.xml).

    I've tried the suggestions here and here, and cannot solve it.

    I don't have this in my .htaccess file:

    RewriteCond %{REQUEST_URI} !(robots\.txt|sitemap(_index|[0-9]+)?\.xml(\.gz)?)

    I have this on 2 lines of each W3TC Page Cache Core:

    RewriteCond %{REQUEST_URI} (sitemap\.xml(\.gz)?) [NC]

    Tried to change it as suggested in the links above and it caused an internal server error and crashed the sites. Replaced the original code and all is well, but I'm uninstalling for now. There really isn't very much help for multisite with W3TC, and I've spent WAY too many hours already.

  2. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    Changing .htaccess file should be done with caution, you can't just copy / paste and hope it work instantly. Please use the contact form: http://betterwp.net/contact/ to send me your .htaccess file, and I will see if there's anything I can do.

  3. robnalexpress
    Member
    Posted 2 years ago #

    @OddOneOut- Thanks- will do- greatful for any assistance!

    Also, even if I get the code right, W3TC is going to change it every time i make any settings changes....

  4. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    I've received the message. It seems that you're using an old version of W3TC. Anyway, if you want to keep the settings, go to Performance > Browser Cache, and then go to '404 error exception list:' in the General option block, find this line:

    sitemap\.xml(\.gz)?

    and change it to:

    (sitemapindex|[a-z0-9_-]+)\.xml)

    Please tell me if it works for you.

  5. robnalexpress
    Member
    Posted 2 years ago #

    @OddOneOut- Thanks. As stated on the 1st line of my first post, I'm using the latest Version 0.9.2.4 of W3TC. I will try the change you suggest and let you know.....

  6. robnalexpress
    Member
    Posted 2 years ago #

    Which activation is preferred: network or individual sites? Unless I hear otherwise, I'm activating per site.

  7. robnalexpress
    Member
    Posted 2 years ago #

    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, webmaster@trianglehomesuccess.com and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.
    Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at trianglehomesuccess.com Port 80

  8. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    Okay please don't revert the change, and send me your new .htaccess file (after you changed that line, you told W3TC to put new rules in .htaccess right?)

    Btw, you can safely activate the plugin network-wide, it doesn't matter.

  9. robnalexpress
    Member
    Posted 2 years ago #

    Sending now- Thanks!

  10. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    Hi, that was my mistake, sorry. Now you should manually edit your .htaccess file, and then find the part you just added, which is:

    (sitemapindex|[a-z0-9_-]+)\.xml)

    and then replace it with (actually, just remove the last parenthesis):

    (sitemapindex|[a-z0-9_-]+)\.xml

    Once you get back to the site, go to the Browser Cache tab again and make the same change ;).

  11. robnalexpress
    Member
    Posted 2 years ago #

    I already changed the .htaccess line to:
    RewriteCond %{REQUEST_URI} !(robots\.txt|sitemap\.xml(\.gz)?)
    so I could get back in.

    Should I now go to browser cache settings and make the change?

    Also, page cache settings contains the following under Non-trailing slash pages: sitemap\.xml(\.gz)? Should I change that as well?

  12. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    Of course.

    Also, page cache settings contains the following under Non-trailing slash pages: sitemap\.xml(\.gz)? Should I change that as well?

    That will allow you to cache sitemaps produced by BWP GXS, but since my plugin already has its own caching mechanism, it's up to you.

  13. robnalexpress
    Member
    Posted 2 years ago #

    New settings works and works.

    Should I do anything with that page cache setting? Also, not exactly sure how to 'submit' after configuring?

    Thanks so very much for taking the time to help. I wish I'd thought to look at W3TC browser cache yesterday while fretting over this. This would be a really simple addition/change for you to make in your FAQs for the many W3TC users, when you get a chance. Thank you so much!

  14. robnalexpress
    Member
    Posted 2 years ago #

    That will allow you to cache sitemaps produced by BWP GXS, but since my plugin already has its own caching mechanism, it's up to you.

    What do you recommend? Can I just take that out of the exceptions field and let your plugin handle it?

    Also, under W3TC page cache settings, cache preload,Sitemap URL: what link should I put here? The W3TC default is http://mysite.com/sitemap.xml

  15. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    Glad it's working!

    This would be a really simple addition/change for you to make in your FAQs for the many W3TC users, when you get a chance.

    What you read in the FAQ is correct, I really don't know why it didn't work for you though.

    What do you recommend? Can I just take that out of the exceptions field and let your plugin handle it?

    Well, if you use BWP GXS's caching mechanism, sitemaps will be cached independently with its own expiry time, which is basically the main benefit. To avoid unnecessary issues that might arise, I suggest using mine.

    Also, under W3TC page cache settings, cache preload,Sitemap URL: what link should I put here? The W3TC default is http://mysite.com/sitemap.xml

    That is for the old sitemap thing, where all URLs are listed there. I'm not sure if that feature works with a sitemap index, but you can leave it as is.

  16. robnalexpress
    Member
    Posted 2 years ago #

    What you read in the FAQ is correct, I really don't know why it didn't work for you though.

    Because I was changing the code in the W3TC Page cache Core rules instead of the 404 rules. Maybe I missed that in the FAQ.

    Thanks for all your help, and for making the plugin available. Still not clear on how to 'submit' to search engines. Do I go to their sites for that?

  17. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    Of course, that's the best way. You only need to submit the main sitemap, i.e. sitemapindex.xml. I've actually put some links in the Sitemap Statistics tab (right in the Submit sitemap section), just follow them to submit your sitemap.

    Have fun with BWP GXS ;).

  18. robnalexpress
    Member
    Posted 2 years ago #

    You only need to submit the main sitemap, i.e. sitemapindex.xml.

    For each site, or does the main index cover all sites? Re-read it and still not sure. For instance, there is an index mysite1 and another index for mysite2. Do I need to submit an index for each site?

  19. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    The main site's sitemapindex does not cover all sites, and it can't either, you can't put a URL that has a different domain in another domain's sitemap. Fortunately, there's an option in Generator tab to include all sitemaps' URL in the main site's robots.txt, so you can use that instead. You only have two sites, so I guess submitting both isn't a pain at all ;-).

  20. robnalexpress
    Member
    Posted 2 years ago #

    Nope- already submitted both to google- will do the others this afternoon. Still no Basic information on my sub-site dashboard:

    "Nothing here... yet! Try submitting your sitemapindex first!"

    I guess maybe it takes a while....?

  21. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    Do you see anything in Sitemap Generator's Log?

  22. robnalexpress
    Member
    Posted 2 years ago #

    Sep 11, 2011 : 16:13:21 — taxonomy_ngg_tag.xml does not have any item. The plugin has fired a 404 header to the search engine that requests it. You should check the module that generates that sitemap (taxonomy.php).
    Sep 11, 2011 : 16:13:21 — Sub-module file: taxonomy_ngg_tag.php is not available in both default and custom module directory. The plugin will now try loading the parent module instead.
    Sep 11, 2011 : 16:13:21 — Cache file for module taxonomy_ngg_tag is not found and will be built right away.
    Sep 11, 2011 : 16:05:08 — Successfully served a cached version of sitemapindex.xml.
    Sep 11, 2011 : 16:05:02 — Successfully served a cached version of sitemapindex.xml.
    Sep 11, 2011 : 16:02:32 — taxonomy_ngg_tag.xml does not have any item. The plugin has fired a 404 header to the search engine that requests it. You should check the module that generates that sitemap (taxonomy.php).
    Sep 11, 2011 : 16:02:32 — Sub-module file: taxonomy_ngg_tag.php is not available in both default and custom module directory. The plugin will now try loading the parent module instead.
    Sep 11, 2011 : 16:02:32 — Cache file for module taxonomy_ngg_tag is not found and will be built right away.
    Sep 11, 2011 : 15:51:54 — taxonomy_ngg_tag.xml does not have any item. The plugin has fired a 404 header to the search engine that requests it. You should check the module that generates that sitemap (taxonomy.php).
    Sep 11, 2011 : 15:51:54 — Sub-module file: taxonomy_ngg_tag.php is not available in both default and custom module directory. The plugin will now try loading the parent module instead.
    Sep 11, 2011 : 15:51:54 — Cache file for module taxonomy_ngg_tag is not found and will be built right away.
    Sep 11, 2011 : 15:41:17 — taxonomy_ngg_tag.xml does not have any item. The plugin has fired a 404 header to the search engine that requests it. You should check the module that generates that sitemap (taxonomy.php).
    Sep 11, 2011 : 15:41:17 — Sub-module file: taxonomy_ngg_tag.php is not available in both default and custom module directory. The plugin will now try loading the parent module instead.
    Sep 11, 2011 : 15:41:17 — Cache file for module taxonomy_ngg_tag is not found and will be built right away.
    Sep 11, 2011 : 15:34:49 — Successfully served a cached version of sitemapindex.xml.
    Sep 11, 2011 : 15:33:35 — Successfully served a cached version of taxonomy_category.xml.
    Sep 11, 2011 : 15:30:04 — taxonomy_ngg_tag.xml does not have any item. The plugin has fired a 404 header to the search engine that requests it. You should check the module that generates that sitemap (taxonomy.php).
    Sep 11, 2011 : 15:30:04 — Sub-module file: taxonomy_ngg_tag.php is not available in both default and custom module directory. The plugin will now try loading the parent module instead.
    Sep 11, 2011 : 15:30:04 — Cache file for module taxonomy_ngg_tag is not found and will be built right away.
    Sep 11, 2011 : 15:29:50 — Successfully served a cached version of post.xml.
    Sep 11, 2011 : 15:27:50 — Successfully served a cached version of page.xml.
    Sep 11, 2011 : 15:27:21 — Successfully served a cached version of sitemapindex.xml.
    Sep 11, 2011 : 15:26:42 — Successfully served a cached version of sitemapindex.xml.
    Sep 11, 2011 : 15:10:24 — Successfully served a cached version of sitemapindex.xml.
    Sep 11, 2011 : 14:44:42 — Successfully served a cached version of sitemapindex.xml.

    Enable logging?

  23. robnalexpress
    Member
    Posted 2 years ago #

    I'm now seeing Basic Information about your sitemaps:

    page has been successfully built on Sep 11, 2011 : 16:27:31.
    post has been successfully built on Sep 11, 2011 : 16:27:31.
    taxonomy_category has been successfully built on Sep 11, 2011 : 16:27:31.
    sitemapindex has been successfully built on Sep 11, 2011 : 16:27:30.

    Latest log entries:

    Sep 11, 2011 : 16:48:02 — Successfully served a cached version of sitemapindex.xml.
    Sep 11, 2011 : 16:47:45 — Successfully served a cached version of taxonomy_category.xml.
    Sep 11, 2011 : 16:47:34 — Successfully served a cached version of post.xml.
    Sep 11, 2011 : 16:47:20 — Successfully served a cached version of page.xml.

  24. Khang Minh
    Member
    Plugin Author

    Posted 2 years ago #

    It's working as expected ;).

  25. ulhack
    Member
    Posted 2 years ago #

    i have same problem with @robnalexpress, to some one please

  26. robnalexpress
    Member
    Posted 2 years ago #

    @OddOneOut- Thanks so much for the "above and beyond" support! I'll mark this thread resolved.

    I've unchecked the include taxonomy archives' sitemaps, including custom taxonomies.

    If you find you're running into this issue a lot with new users who also use W3TC, you might want to expand a little in the FAQ and include the easier method of adding (sitemapindex|[a-z0-9_-]+)\.xml to the W3TC browser cache page 404 error exception list and replacing the new rules in .htaccess. The way it currently reads, dummies like me are going to be in there changing the page cache core, since that's the first place one sees any reference to .txt|sitemap.

    many thanks!

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic