Still get 404-not-found-error [#857108]

Comment	File	Size	Author
#23	drupal-modules.png	724.46 KB	Witch
#6	sitemap1.png	23.48 KB	Witch
#4	xml.png	43.25 KB	Witch
	sitemap.png	23.42 KB	Witch

Comment #1

Witch commented 18 July 2010 at 23:46

Anybody?

Log in or register to post comments

Comment #2

Witch commented 20 July 2010 at 15:17

Ok, i have no idea why i get this 404 error, but a simple Rewrite

RewriteRule ^sitemap\.xml$ sites/default/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/index.xml [NC,L]

should be a temporary solution.

Hope we can find a better way :(

Log in or register to post comments

Comment #3

Anonymous (not verified) commented 20 July 2010 at 16:51

Why isn't your Drupal finding /sitemap.xml as a page to serve without the rewrite? What permissions have you assigned to the anonymous user? What modules do you have enabled? What aliases do you have assigned? Do you have a sitemap.xml file in your DocumentRoot?

Log in or register to post comments

Comment #4

Witch commented 20 July 2010 at 17:03

Status	File	Size
new	xml.png	43.25 KB

Hi Earnie,

anonymous user have no permissions, because you can only assign "Administer xmlsitemap".

I have a lots of modules enabled. I attached a screen with xmlsitemaps enabled modules. I have no idea which module could interact with xmlsitemap module.

Maybe boost or pathauto?

I have no aliases assigned to sitemap.xml or same and there is no sitemap.xml in my document root folder.

Log in or register to post comments

Comment #5

dave reid

he/him

English

Nebraska USA

commented 20 July 2010 at 17:15

The anonymous user should have the 'access content' permission in order to view the sitemap.

Log in or register to post comments

Comment #6

Witch commented 20 July 2010 at 19:07

Status	File	Size
new	sitemap1.png	23.48 KB

Cant see that permissionpoint. But i know that it existed in earlier version 0o. I thought the developer changed this point.

Log in or register to post comments

Comment #7

dave reid

he/him

English

Nebraska USA

commented 20 July 2010 at 19:20

It's not an xmlsitemap permission. It's a node.module permission found higher up in the page.

Log in or register to post comments

Comment #8

Witch commented 20 July 2010 at 22:33

no chance. i cant find it. :(

Log in or register to post comments

Comment #9

Witch commented 23 July 2010 at 10:01

I uninstalled the module completely and reinstalled it. The permission still wont appear.

What went wrong? Where can i have a look into to solve this?

I appreciate your help.

Log in or register to post comments

Comment #10

Anonymous (not verified) commented 23 July 2010 at 14:02

You still don't understand that the permission is located with the node module's set of permissions. If you don't have 'access content' at all on the permissions page then something is wrong with your installation of Drupal. Don't look under "xmlsitemap module", look under "node module".

Log in or register to post comments

Comment #11

Witch commented 23 July 2010 at 14:16

Hi earnie,

I missunderstood you in prior posts. Sorry for that :(

"access content" were and is activated for anonymous users but you cant access the sitemap it will return a 404.

Log in or register to post comments

Comment #12

coloryan commented 26 July 2010 at 09:31

Same problem here. Upgraded, purged caches, uninstalled/reinstalled, still no love.

Log in or register to post comments

Comment #13

coloryan commented 26 July 2010 at 09:33

Correction: I just rebuild (sitename.com/admin/settings/xmlsitemap/rebuild) and it magically appeared.

Also note that on the page it did advise me that 'Your sitemap is up to date and does not need to be rebuilt.'

Fixed for me.

Log in or register to post comments

Comment #14

fleshgrinder commented 26 July 2010 at 12:10

I also got the “Page not found” error. I use a multi-domain configuration and I rebuild the sitemap as mentioned in #13. It worked for one language, the other keeps returning “Page not found”. This is a really annoying error. Hopefully a fix is coming soon.

Subscribing!

Edit: Completely uninstalled the module. Only generating errors and creating problems. This isn't a beta for me, this is a development build.

Log in or register to post comments

Comment #15

Witch commented 26 July 2010 at 13:25

Fleshgrinder, you dont should have any problems if you test any changes offline. Always make backups. Dont get developers with such unqualified comments on their nerves.

Log in or register to post comments

Comment #16

Witch commented 26 July 2010 at 13:35

Very strange is that drupal does not handle the 404. The Browser says "The file were nout found on the server". I checked the htaccess but there is no hint.

Log in or register to post comments

Comment #17

fleshgrinder commented 26 July 2010 at 21:41

I don't have problems, the module has. I'm always trying to help, but in this case I can't see any land – it's just not working. Which, for me, is really sad and I don't know how I could help to solve those issues.

Log in or register to post comments

Comment #18

dave reid

he/him

English

Nebraska USA

commented 26 July 2010 at 21:49

@Witch If you're not getting a Drupal 404 message then something else is going wrong and not letting Drupal load when using the path 'sitemap.xml'. Check server/cache/etc configurations.

@Fleshgrinder: Did you go through all your re-save all your sitemaps at admin/settings/xmlsitemap/list (click edit link for each one and just press Save on the edit sitemap page)?

Log in or register to post comments

Comment #19

coloryan commented 27 July 2010 at 05:40

@Fleshgrinder: Try using the 6.x-1.2 build. As I said, my sitemap was being produced, but Google Webmaster Tools wouldn't accept it. I noticed that it was being accepted for two other sites and they're both using that branch with no issues. It doesn't have 100% of the functionality as the latest dev, but the Google Gods seem to approve.

Log in or register to post comments

Comment #20

fleshgrinder commented 27 July 2010 at 08:39

@Dave Reid: Definitely not, but I'm going to reinstall the module and then I will give it a try also with your advices. Thanks for your input.

@coloryan: Thanks for your input but the 6.x-1.2 build isn't suitable for my website. Because I need to create different sitemaps for all subdomains (languages).

Log in or register to post comments

Comment #21

coloryan commented 27 July 2010 at 10:47

Understood. I'm having issues with submitting the sitemaps to Google Webmaster Tools. I'm using multiple sites via the domain module, and when I checked this morning Google gave me the red 'X' and didn't accept the sitemaps for some reason. domain_xmlsitemap is current, as is xmlsitemap.

All other sites, even a multiple language site, are responding in Google.

I can provide URLs if anyone wants to see an example.

Log in or register to post comments

Comment #22

Anonymous (not verified) commented 27 July 2010 at 12:08

Status:

Active

» Postponed (maintainer needs more info)

@coloryan:

I checked this morning Google gave me the red 'X' and didn't accept the sitemaps

is a different issue than 404-not-found-error. Do not hijack this issue with a different problem.

@Witch: Can you please provide a list of enabled modules?

Log in or register to post comments

Comment #23

Witch commented 27 July 2010 at 16:15

Status	File	Size
new	drupal-modules.png	724.46 KB

Hi earnie,

i attached a screenshot with all enabled modules. Maybe you can find something. I will check the apache and serverlogs for hints.

Log in or register to post comments

Comment #24

kingofsevens commented 9 August 2010 at 06:26

I had the same problem. I have 3 languages with different domain names. First there was the default english map, then I have added the other languages first disabled the human readable format, changed the lifetime to 1 day. The module said running cron is enough but it didn't worked so I rebuilt to create the maps. It worked and I have changed back to the human readable format. Also, a simple question but did you specify in the settings of the module what pages to include?

Log in or register to post comments

Comment #25

Ingumsky commented 18 August 2010 at 12:52

coloryan
Thanks mate. Your solution (#13) works for me too.

Log in or register to post comments

Comment #26

WebWalker3D commented 21 August 2010 at 16:22

Solution (#13) worked for me as well... It appears that the sitemap is not getting built until you "rebuild" it.

Log in or register to post comments

Comment #27

Witch commented 22 August 2010 at 18:34

My problem is that drupal does not handle the 404. May there be an error in my htaccess file? Can i post it?

Log in or register to post comments

Comment #28

alex.skrypnyk

he/him

English

Melbourne

commented 10 September 2010 at 04:45

I Have similar problem.

But in my case a sitename.com/sitemap.xml is accessible, but www.sitename.com/sitemap.xml - page not found.
I use 3 languages.

Update: when I changed base XML Sitemap->Settings->Advanced Settings->Default base URL: to www.sitename.com -> www.sitename.com/sitemap.xml became accesible, but sitename.com/sitemap.xml - page not found.

Is it possible to fix this?

Log in or register to post comments

Comment #29

firex commented 1 October 2010 at 08:26

I have the same problem

404 error for requesting sitemap.xml with or without Friendly Url enabled.

Rebuilt links and in my file folder i can see only the file "1.xml"

Solutions?

Log in or register to post comments

Comment #30

cookiesunshinex commented 16 October 2010 at 02:42

I had to disable, un-install, and re-install this module to get it working with a 6.x-2.0-dev to 6.x-2.0-beta1 upgrade.

I had 404 not found and lots of PHP errors otherwise.

Log in or register to post comments

Comment #31

jisuo commented 26 October 2010 at 12:59

Post #13 fixed this problem for me too. Thanks.

Log in or register to post comments

Comment #32

Witch commented 8 February 2011 at 13:44

Hi,

in the very beginning of my project where the error occurs i used the following code in settings.php

// List of extensions for static files
$exts = 'txt|png|gif|jpe?g|shtml?|css|js|ico|swf|flv|cgi|bat|pl|dll|exe|asp|xml';

// It is not an imagecache path, which we allow to go through Drupal
if (!strpos($_SERVER['QUERY_STRING'], 'imagecache')) {
  // It is not our main feed page
  if ($_SERVER['QUERY_STRING'] != 'rss.xml') {
    // Is it a static file?
    if (preg_match('/\.(' . $exts . ')$/', $_SERVER['QUERY_STRING']))
      // Just send a 404 right now ...
      {
      header('HTTP/1.0 404 Not Found');
      print '<html>';
      print '<head><title>404 Not Found</title></head>';
      print '<body><h1>Not Found</h1>';
      print '<p>The requested URL was not found on this server.</p>';
      print '</body></html>';
      exit();
    }
  }
}

Removing xml solved this issue.

Thank you :)

Log in or register to post comments

Comment #33

Michsk commented 25 October 2011 at 19:32

@#32: you saved me! I started looking if boost didn't cache anything untill i saw your post. Thanks!

Log in or register to post comments

Comment #34

Witch commented 29 October 2011 at 10:56

I am glad to see you happy with this :) This issue blowed my head up for many months....

Log in or register to post comments

Comment #35

aronne commented 10 November 2011 at 10:14

Hi all, i had the same problem and i solved it following these steps:

navigate to admin/config/search/xmlsitemap
delete all your sitemaps
Add new XML sitemap
navigate to admin/reports/status and run cron
navigate back to admin/config/search/xmlsitemap
select all your sitemaps listed into the table and click on the Update button (Update cached files)

After these steps you should be able to see again all of your sitemaps.

Hope it helps!

Fixed for me.

Log in or register to post comments

Comment #36

dave reid

he/him

English

Nebraska USA

commented 29 November 2011 at 00:16

Status:

Postponed (maintainer needs more info)

» Fixed

Log in or register to post comments

Comment #37

13 December 2011 at 00:21

Status:

Fixed

» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Log in or register to post comments

Comment #38

asb commented 5 December 2014 at 18:55

Version:	6.x-2.0-beta1	» 6.x-2.x-dev
Issue summary:	View changes
Status:	Closed (fixed)	» Active

Sorry guys, this issue is not fixed. By default, this module seems to generate a bogus sitemap.xml on i18n sites. This sitemap.xml simply won't be accessible whatever you do. Especially the steps provided in #13 do not work on those sites.

#35 is a partial workaround. The sitemap.xml file generated by defaul has to be manually deleted and then manually configured. On a i18n site, you'll get a dropdown when creating the new sitemaps where you can choose the language. The sitemaps created by this method will be accessible. So there is a workaround available to fix the broken default behaviour, but still there is is no fix for the code.

However, what makes this issue complicated: The seemingly language-specific sitemap files do not honor the selected language. This is another issue, but it's probably connected to the broken default behaviour.

Steps to reproduce:

* recent version of Pressflow/D6
* i18n, language subdomains, translated content

foo.mysite.org has "foo" content, bar.mysite.org has "bar" language content. Translated content is marked as "foo" respectively "bar". By default, the module will create an inaccessible fake sitemap.xml at the site's default language, e.g. foo.mysite.org/sitemap.xml.

Manually created sitemaps will be created at foo.mysite.org/sitemap.xml respectively bar.mysite.org/sitemap.xml. These sitemaps are accessible, but contain a mixture of content in the languages "foo" and "bar".

The expected behaviour would be: The module honors the language settings chosen when creating the sitemap.

An pragmatic approach might be to not fake i18n support and by default just create one sitemap at mysite.org/sitemap.xml that contains the mixture of language content that is in foo.mysite.org/sitemap.xml nad bar.mysite.org/sitemap.xml anyway.

An even more pragmatic approach would be to make a note on the project page that this module las none or limited support for localized sites/i18n.

Log in or register to post comments

Comment #39

dave reid

he/him

English

Nebraska USA

commented 13 December 2014 at 04:03

Version:	6.x-2.x-dev	» 6.x-2.0-beta1
Status:	Active	» Closed (fixed)

@asb Unless you turn on the xmlsitemap_i18n sub-module, this is the expected behavior. Since you never mentioned you have that module enabled, I assume it isn't. Either way, it's nice etiquette to not re-open issues that have been closed for over three years and instead file a new bug report for your issues.

Log in or register to post comments

Comment #40

asb commented 13 December 2014 at 19:20

Follow-up issue: #2392849: Still get 404-not-found-error

Log in or register to post comments

Still get 404-not-found-error

Comments