Problem/Motivation
...as per issue's title. See original report for more information.
Proposed resolution
Latest workaround (August 2011, post #101 by Willynux):
When you have xmlsitemap i18n module enabled, you have to create one sitemap for each language and hit save with a given language selected (hit save even if you don't do any modification, in the case of the English sitemap), then update the caches and it should be ok. You only need to rebuild links if you actually change links to be included or excluded.
Remaining tasks
???
User interface changes
???
API changes
???
Original report by Phil23798 on May 4, 2010 at 3:15am:
I installed xml sitemap 6.x-2.0-beta1 and now I get a "page not found" error when opening www.domain.com/sitemap.xml.
1) I have used a older 6.x-2.x-dev (from early April) until today
2) I deleted the old xml sitemap - folder and copied the new 6.x-2.0-beta1 folder to my modules folder
3) I ran update.php -> no errors
4) all the settings and options pages of xml sitemap are working
5) opening www.domain.com/sitemap.xml brings the "page not found" error
I have
- cleared my caches several times
- restarted apache
- rerun update.php
There are no errors in my apache logs.
In the drupal log:
Type: Page not found
User: Admin
Place: http://www.domain.com/sitemap.xml
Referrer: http://www.domain.com/admin/settings/xmlsitemap
The only thing that helped me was to go back to the older 6.x-2.x-dev (april 8 works). All the newer xml sitemap brought the same problem.
What could be the reason for this problem? How can I solve this to install the new 6.x-2.0-beta1?
Comment | File | Size | Author |
---|---|---|---|
#52 | sitemap1.JPG | 4.85 KB | lionking7 |
#52 | sitemap2.JPG | 7.38 KB | lionking7 |
#21 | xmls.JPG | 24.01 KB | Vacilando |
#10 | Screen shot 2010-05-12 at 11.44.28 PM.png | 22.31 KB | Ben Finklea |
Comments
Comment #1
Dave ReidHave you run cron to regenerate the sitemap files? What do you see in your sites/default/files/xmlsitemap or sites/mysite.com/files/xmlsitemap directories?
Comment #2
Phil23798 CreditAttribution: Phil23798 commented> Have you run cron to regenerate the sitemap files?
Yes, I have run cron about 20 time after installing the beta1. I even have rebuild the sitemaps manually.
> What do you see in your sites/default/files/xmlsitemap or sites/mysite.com/files/xmlsitemap directories?
de41357168acf4797d3100599697fdb2-1.xml - 792 kB
de41357168acf4797d3100599697fdb2-2.xml - 83 kB
de41357168acf4797d3100599697fdb2-3.xml - 165 B
de41357168acf4797d3100599697fdb2-index.xml - 401 B
The files have the regular sitemap entries.
To me it seems that xml sitemap generally works, but the connection between the path sitemap.xml and the files is somehow broken or there is perhaps a rights problems or a problem with another modules that causes this. But I am no expert in these things.
All that helps is to go back to the older releases.
Comment #3
Dave ReidHmm, if you're using the beta1 you should actually see something like this:
Did you see any watchdog messages for XML sitemap or file system not being able to write to directories?
Comment #4
Phil23798 CreditAttribution: Phil23798 commented> Did you see any watchdog messages for XML sitemap or file system not being able to write to directories?
No, there were none of the messages.
But I got beta1 working in the mean time:
I uninstalled the old dev completely, deleted the file-folders of xml sitemap and then installed beta1. Now it works.
Comment #5
Dave ReidOk. /me shrugs. :)
Comment #6
Vacilando CreditAttribution: Vacilando commentedSame problem here, so re-opening.
Properly uninstalled old v1, deleted the module folder, deleted the old sitemap files from /files, downloaded 6.x-2.x-dev of May 9th, configured, ran sitemap rebuild.
There is one file in the auto-created directory, i.e. /files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml and it looks OK.
However, http://www.mysite.tld/sitemap.xml returns "The page you requested does not exist."
What can be the problem - where should I look?
Comment #7
Vacilando CreditAttribution: Vacilando commentedAdjusting the title and version.
Comment #8
Anonymous (not verified) CreditAttribution: Anonymous commentedDo you have a file in your DocumentRoot that is named sitemap.xml? If so remove it.
Comment #9
Vacilando CreditAttribution: Vacilando commentedGood point, earnie, but no, I've just checked, there is no other sitemap.xml file anywhere.
What else can I check?
Comment #10
Ben Finklea CreditAttribution: Ben Finklea commentedSame problem. The List shows a sitemap but when you click on it, it is not found.
I see nothing in the two directories you asked about, Dave.
Comment #11
Ben Finklea CreditAttribution: Ben Finklea commentedOK, I was just dinking around and found the fix.
1. Install the elements module: http://drupal.org/project/elements
2. Turn it on.
3. Go to the admin xml sitemaps module page: /admin/settings/xmlsitemap
4. Select the (new) ticbox next to your sitemap that isn't showing up.
5. From the dropdown, select "Update cached files" and click the Update button.
I got a message that said "blah, blah directory as been created". Now, when I visit sitemap.xml, I have a sitemap. It's still a bug that I should have to do all this but at least we have a workaround.
Comment #12
Vacilando CreditAttribution: Vacilando commentedI've installed the elements module, did "Update cached files", all looks fine - /sitemap.xml updated today, 98069 links, 2 pages, cleared all Drupal caches, went to http://mysite.tld/sitemap.xml ... page still not found!
In /files/xmlsitemap/ there is a directory with a code name, then there are 3 files with today's date: 1.xml, 2.xml, index.xml. The first is large, the second smaller, the third just a little index. All looks perfectly well.
Interestingly, even when I try to access one of the partial files (as listed in index.xml), e.g. http://mysite.tld/sitemap.xml?page=1, that page is not found either.
What do you think should I check / look at?
Comment #13
Dave ReidEnable the developer mode at admin/settings/xmlsitemap/settings and then add ?debug to your sitemaps's URL (e.g. http://example.com/sitemap.xml?debug) to see what's going on. You can paste that output here in this issue that would be very helpful too.
Comment #14
Vacilando CreditAttribution: Vacilando commentedCleared all caches, enabled developer mode, accessed /sitemap.xml?debug ... same deal, Drupal returns "Page not found".
Where else (in the database) can I check why /sitemap.xml is not redirecting to the right location, what other tests can I do?
Comment #15
Anonymous (not verified) CreditAttribution: Anonymous commentedIs it possible you have an alias assigned for sitemap.xml either as the Drupal path or the alias path?
Comment #16
Vacilando CreditAttribution: Vacilando commentedHi,
I've checked both /admin/build/path-redirect/list and /admin/build/path but there is nothing assigned for sitemap.xml
I did have old versions of XML Sitemap installed, but I had uninstalled everything properly, as mentioned in #6. I can imagine it is possible that the uninstall script did not remove some remnants in the db that are now posing this problem. Where else can I check? What exactly is responsible for resolving sitemap.xml to the files that I know exist in /files/xmlsitemap/ (see #12)?
Thanks!
Comment #17
Anonymous (not verified) CreditAttribution: Anonymous commentedMarked #803206: Update from 6.x-2.0-alpha2 to 6.x-2.0-beta1 and now sitemap.xml 404's as duplicate of this issue.
Comment #18
mdlueck CreditAttribution: mdlueck commented@Dave Reid #13
I enabled the debug mode, and here is the adjusted output:
So I went to verify the file should exist since it said it did not exist.
In the .../drupal_files/xmlsitemap dir I found:
So it looks like a "-" char is where the "/" char making a directory should be.
I made the "40cd750bba9870f18aada2478b24840a" directory by hand, ran cron, etc... no files in that dir, no sitemap still.
Perhaps this info will help.
Comment #19
Dave ReidThe upgrade puts the files in the hash/chunk.xml path instead of hash-chunk.xml file. To manually regenerate the files, you can do it three ways:
1. (highly recommended) Download the Elements module and then select the sitemaps to regenerate on admin/settings/xmlsitemap.
2. Adjust your sitemap's minimum lifetime to 'No minimum' on admin/settings/xmlsitemap/settings, and then run cron, and then adjust the setting back to where you had it.
3. Use the 'Rebuild links' tab if it is available.
Comment #20
mdlueck CreditAttribution: mdlueck commented@Dave Reid #19
That worked! It created the "40cd750bba9870f18aada2478b24840a" directory, "1.xml" showed up in that dir, and the sitemap appears properly.
I will remove the old "40cd750bba9870f18aada2478b24840a-1.xml" by hand.
Looks like this was a sharp spot migrating from alpha2 to beta1 at the very least.
Comment #21
Vacilando CreditAttribution: Vacilando commentedI checked the generated files in my case again, but they are all right - just the hash folder and the xml plus index files in it. (See attached screenshot.)
I have Elements installed, just re-ran the update, all went OK, but clicking /sitemap.xml still returns 404.
Comment #22
Dave Reid@vacilando I may have to help you debug this one-on-one and not through the issue queue since all my other suggestions that should work haven't. Find me on IRC or e-mail me through my contact tab to figure out when we can debug.
Comment #23
Dave ReidWith help from vocilando I found out what happened in his case. Basically it's this issue that I'm working on: #768182: Handle context changes. At some point he enabled the xmlsitemap_i18n which adds an additional 'language' context for sitemaps. But his default sitemap doesn't define a language context value (typically the default language, English) because that sitemap was saved prior to the module being enabled. When the request to view the sitemap happens, the module doesn't find a sitemap that has the English language context and returns a 404.
What you need to do if you enable/disable the context-providing modules (like xmlsitemap_i18n or domain_xmlsitemap) is make sure you go through and re-edit your sitemaps on admin/settings/xmlsitemap/list and just press 'Save'.
Comment #24
Vacilando CreditAttribution: Vacilando commentedExcellent, Dave, thanks!
I've just done this on two sites and the sitemaps are now accessible!
To clarify, I installed the main module and all sub-modules at once, as I described in #6. But it is true that whilst I use pages translated in various languages, that is done using locale, not i18n, so I shouldn't have enabled xmlsitemap_i18n.
Comment #26
Hardrocker CreditAttribution: Hardrocker commentedI was having the same problem too. I disabled the xmlsitemap_i18n module and it finally worked.
Comment #27
klonosThis is surely not fixed, so please keep it open till it is.
In my case I enabled all submodules (including xmlsitemap_i18n) at once. I visited the sitemaps' list page (../admin/settings/xmlsitemap) and after reading the note I installed Elements. At this point, I still hadn't have checked the generated sitemap.
After installing the Elements module I went on and checked the link to the default sitemap created (was the only one) and I then realized the issue. I then checked the module's issue queue and found myself reading this issue's posts. So, I basically tried everything. What seemed to do the job in the end was the suggestion in #26 to disable the xmlsitemap_i18n submodule. That didn't of course do the job instantly. I had to use the 'Update cached files' option provided by the installed Elements module (perhaps also do the edit -> save thing suggested in #23 - but I honestly can't recall).
This is not a solid solution, rather than a simple workaround to get things halfway done. I cannot tell what will happen if I enable the xmlsitemap_i18n submodule again. So, as I said please keep this issue open till we figure it out. I am willing to help with tests etc. Let me know.
PS: ...unless #768182: Handle context changes is definitely the cause of this. In that case perhaps we should mark this duplicate? ...since there is no way in drupal.org to set issues as depended to others :(
Comment #28
Dave ReidYes, #768182: Handle context changes is where this is properly being handled. Marking as a duplicate of that issue.
Until then your solution should always be to:
1. Go through and edit & save each sitemap (this helps clear out any abandoned or add newly-found contexts which is the key here).
2. Use the elements module and perform the 'update cached files' operation on all sitemaps.
Comment #29
klonosThank you Dave for taking the time to clear this out for us.
...I think there should be a 3rd thing to do:
3. Disable xmlsitemap_i18n submodule.
Having it enabled will always produce a 'page not found' error.
Comment #30
ckreutz CreditAttribution: ckreutz commentedSame here. Worked only if I disabled xmlsitemap_i18n submodule. Otherwise page not found.
Comment #31
AdamKlein CreditAttribution: AdamKlein commentedI'm having the issue described above - /sitemap.xml returns "page not found"
Here's what I've got configured:
*I don't have il8n submodule installed (not even on server, shows missing on module admin page)
*Element Module Installed
*I've tried rebuilding and updating cache pages
Debug at /sitemap?debug
Current context: Array ( )
Sitemap: Array ( [smid] => 1 [context_hash] => 40cd750bba9870f18aada2478b24840a [context] => Array ( ) [updated] => 1284493398 [links] => 0 [chunks] => 0 [uri] => Array ( [path] => sitemap.xml [options] => Array ( [absolute] => 1 [base_url] => http://pacificadvisors.com ) ) )
Chunk: 1
Cache file location: sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml
Cache file exists: No
After I rebuild or update Cache:
warning: fopen() [function.fopen]: Unable to access sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml in /var/www/vhosts/pacificadvisors.com/httpdocs/sites/all/modules/xmlsitemap/xmlsitemap.generate.inc on line 190.
warning: fopen(sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml) [function.fopen]: failed to open stream: Success in /var/www/vhosts/pacificadvisors.com/httpdocs/sites/all/modules/xmlsitemap/xmlsitemap.generate.inc on line 190.
user notice: Could not open file sites/pacificadvisors.com/files/xmlsitemap/40cd750bba9870f18aada2478b24840a/1.xml for writing. in /var/www/vhosts/pacificadvisors.com/httpdocs/sites/all/modules/xmlsitemap/xmlsitemap.generate.inc on line 191.
There are no files located at /files/xmlsitemap/
Please help!
Comment #32
AdamKlein CreditAttribution: AdamKlein commentedone more thing - if I try to add a new sitemap I get:
There are currently no XML sitemap contexts available
Comment #33
ressa CreditAttribution: ressa commentedThanks Volacci! (in post #11) ..."Update cached files" with Elements module did the trick.
Just remember to disable the XML sitemap internationalization module before using the 'Update cached files' option provided by the Elements module.
Comment #34
japanitrat CreditAttribution: japanitrat commentedhm but i18n is needed in my case .. :(
subscribe
Comment #35
Vote_Sizing_Steve CreditAttribution: Vote_Sizing_Steve commentedNeeded by me too - subscribing.
Comment #36
cookiesunshinex CreditAttribution: cookiesunshinex commentedI 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.
Comment #37
ealfert CreditAttribution: ealfert commentedThank you Dave!
#23 worked for me.
Just wanted to place a message here that this issue is not limited to 6.x-2.0 because I was experiencing the same problem with D7-Beta2 and xmlsitemap 7.x-2.x-dev.
In my case I also had "domain_xmlsitemap" module that I enabled after enabling and configuring "xmlsitemap" module. Going back to the list page and clicking on "save" button fixed my "page not found" problem.
Comment #38
ThePickwickProject CreditAttribution: ThePickwickProject commentedI had the same "page not found" issue until I clicked "Rebuild links".
Comment #39
Tatta CreditAttribution: Tatta commentedHi guys
i had the same problem. and was running around to fix it. The way i did was simply delete the sitemap at ?q=admin/settings/xmlsitemap and create a new one. now i can see my site map.
cheers
Comment #40
eescape CreditAttribution: eescape commentedsame versions/issue, it worked this way:
I didn't switch off i18n - simply (after uninstalling and reinstalling Sitemaps and its i18n submodule) for each language and once per time I added the respective xml sitemap and regenerated the cache. It works now. Ok, I actually have 2 sitemaps with the same url (the default sitemap - generated by Sitemaps for the default language), and the new one I added for the default language, mydomain.com/en/sitemap.xml) and other 2 for the remaining languages... I wont't delete the default sitemap: when I did it, I had to uninstall evertything... hope this help.
Comment #41
mattwmc CreditAttribution: mattwmc commentedOK, I'm lost, lol.
My sitemap for the main domain was working just fine.
I installed this mod and followed #11 to get it to work for my subdomains. Subdomain sitemaps work.
However, now the main domain (www.example.com/sitemap.xml) returns a "Page Not Found Error."
I've rebuilt the links, Updated Cache Files, deleted and saved the sitemap a few times and run cron. Nothing.
It does show the sitemap to be present on the XML Sitemap page with the correct number of links and pages. When going to the link it is not there.
In files/xmlsitemap, the folders are there. Not sure which one is for which, but I think for the main site it has files: 1.xml, 2.xml and index.xml.
Any ideas?
*uninstalled Domain Sitemap and reinstalled. All seems to be working - for now!
Comment #42
klonos...back to the branch it was set to before then ;)
Comment #43
mattwmc CreditAttribution: mattwmc commentedJust checked it again.
The sitemap is now NOT being found again - the main site that is. The subdomains are there.
The folder is present in the XML folder.
Not sure what the heck is up.
Is there any Drupal Mod that doesn't take days of configuring to work? Frustrating as ****!
Comment #44
FlemmingLeer CreditAttribution: FlemmingLeer commentedJust wondering.
Maybe permissions is not granted to anomyous users to the beta2 ?
Comment #45
mattwmc CreditAttribution: mattwmc commentedIt wasn't being found because as soon as I enabled the Domain Sitemap Mod it conflicts.
(My browser cache just needed to be cleared - then it was showing not found.)
The only permission I have found for any sitemap module is to administer.
Comment #46
Anonymous (not verified) CreditAttribution: Anonymous commentedInstalled 6.x-2.0-beta1 version + i18n extension. When navigating to www.website.com/sitemap.xml it said "File Not Found". Can't see the file in my terminal although the cache files/directory seem to have been created.
I followed the suggestions above but they didn't work for me (incl. installing Elements).
I uninstalled 6.x-2.0-beta1 completely and installed 6.x-1.2 version. That didn't work either.
Would love to have this module working. Any guidance would be greatly appreciated.
Cheers
Comment #47
Anonymous (not verified) CreditAttribution: Anonymous commentedFurther to #46 solved by installing the dev version (which isn't ideal). But thanks for this module. 6.x-2.0 is excellent.
Comment #48
tm01xx CreditAttribution: tm01xx commentedI have installed element and disabled XML sitemap internationalization module and the sitemap is working now. It means that my site is now able to provide only one sitemap for one default language only. Cannot generate for other languages.
Then I tried to remove one of the sitemaps. I got this error:
user warning: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1 query: DELETE FROM xmlsitemap_sitemap WHERE smid IN () in /home/davcomv1/public_html/ebos.vn/sites/all/modules/xmlsitemap/xmlsitemap.module on line 197.
The sitemap is still there in the list.
Have any ideas?
Comment #49
Bartezz CreditAttribution: Bartezz commentedAlso getting page not found with beta1 and i18n... will try dev next week...
Cheers
Comment #50
Bartezz CreditAttribution: Bartezz commentedUninstalled beta-1, installed latest .dev and still nothing.
Not getting any errors other than page not found.
When looking in the xmlsitemap dir on the server all there is is a directory named NXhscRe0440PFpI5dSznEVgmauL25KojD7u4e9aZwOM with a file in it called 1.xml
Sever is shared but have LOADS of resources, not getting any timeout issues as far as I see.
Website is on sub.domain.com, could this be a problem?
Cheers
Comment #51
Bartezz CreditAttribution: Bartezz commentedDone some debugging...
Uninstalled dev again and reinstalled beta-1 on my multilingual website on a subdomain.
I've only installed XML sitemap and none of the submodules (not even XML sitemap internat.)
Install runs fine, domain.com/en/sitemap.xml gives 404 not found.
Then click to rebuild sitemap, get warning this is not necessary, do it anyway, then /en/sitemap.xml is available.
Then installing XML sitemap internationalization I can add a sitemap for each language, and rebuild links.
This works for all languages but breaks default language sitemap, and ofcourse only adds the homepage to multilingual sitemaps.
Enabling XML Sitemap Node kills all functionality. Sitemaps are not created and the url returns a 404.
Do I need to reconfigure anything?
Cheers
Comment #52
lionking7 CreditAttribution: lionking7 commentedam using D7 sitemap 7.x-2.0-beta2 and it does not work
Image Attached.
Please help me.
Comment #53
tm01xx CreditAttribution: tm01xx commentedI think the 6.x-2.0-beta2 has fixed everything now.
Comment #54
newmediaist CreditAttribution: newmediaist commentedJust a heads up, I'm on 6.x-2.0-beta2 and still experiencing this issue -
Comment #55
Stekkie CreditAttribution: Stekkie commentedJust had the same problem in version 6.x-2.0-beta2.
What the problem was;
- The directory, sites/default/files/xmlsitemap/[hash] was created by Drupal, Linux owner was set to "apache"
How to fix it;
- Log in to your hosting administration panel (eg. DirectAdmin), go to the file manager, and reset the owner of this [hash]-directory.
- Chmod the directory (eg. 777, UNSAFE! Check the manual)
- Rebuild your sitemap
Comment #56
tky CreditAttribution: tky commentedI had similar problem but little different.
xml file in dictionary has been generated, xmlsitemap setting page show it has indexed 1083 links.
When I click http://localhost/sitemap.xml, it shows a page but without any links on it.
I have already installed the element module, but nothing changed.
Any idea?
Comment #57
Anonymous (not verified) CreditAttribution: Anonymous commented@tky:
This isn't the same as the titled issue so you should have used a different issue to report your problem. I'm guessing your issue to be that you've not enabled the content type for use by xmlsitemap.
Comment #58
tky CreditAttribution: tky commented@earnie
Thank you for your reply. You are right, I should post another issue.
I am sure I enabled the content types in xmlsitemap control panel and it show xmlsitemap already indexed more than 1800 nodes. But the sitemap.xml still shows nothing there.
Comment #59
miaoulafrite CreditAttribution: miaoulafrite commentedhello,
i just dowloaded the 2.0-beta2 and get also a 404
in the folder sites/default/files/xmlsitemap i have a folder generated by the module, but NO file!
i do not get any error message
what shall i do?
edit: on the admin/settings/xmlsitemap page i get the following:
URL Last updatedsort icon Links Pages Operations
http://localhost/nmr/sitemap.xml Fri, 06/03/2011 - 10:01 1077 1 edit delete
so content seems to be indexed...
it should be some permission or?
Comment #60
mdlueck CreditAttribution: mdlueck commented@miaoulafrite #59: If you did not have an earlier version of the mod on this Drupal installation, perhaps did you not enable content types to be access via this module? Edit the various content types you want included in the site map. And do not forget about Taxonomy if you use that.
Comment #61
miaoulafrite CreditAttribution: miaoulafrite commented@mdlueck: thanks, i did include types & taxonomy as well as users
i know this module, i have it installed on several sites, but in that particular case it does not work...
Comment #62
Anonymous (not verified) CreditAttribution: Anonymous commentedYou must allow cron to run (multiple times perhaps). I recommend Elysia Cron module for controlling the individual hook_cron implementations. Give xmlsitemap more time in cron and control which hook_cron implementations are allowed to run when.
Comment #63
miaoulafrite CreditAttribution: miaoulafrite commented@earnie: yes cron ran several times
all content is marked as "included available indexed and visible"
all seems fine in the module's configuration pages
but still 404, and i repeat, there is no file in the sites/all/files/xmlsitemap. only an empty directory '40cd750bba9870f18aada2478b24840a'
Comment #64
Anonymous (not verified) CreditAttribution: Anonymous commentedWhat is your domain name? I'll give it a try. BTW, you should try to access /sitemap.xml as an anonymous user.
Comment #65
Dave ReidAlso make sure to always check your status report page (admin/reports/status) for any errors or warnings which might need to be reported back into this issue.
Comment #66
miaoulafrite CreditAttribution: miaoulafrite commented@earnie > it is on localhost so far sorry
@Dave Reid > The XML cached files are out of date and need to be regenerated. You can run cron manually to regenerate the sitemap files.
> XML sitemap cache directory : Writable
> XML sitemap maximum file size 0 octets
0 bytes?!
could it be the reason?
after running cron, i got a lot of errors
and so on
i did not copy everything
and sitemap.xml is still unavailable
all info from xml sitemap here is checked as OK
Comment #67
Anonymous (not verified) CreditAttribution: Anonymous commentedSee #920062: XMLWriter::openUri(): Unable to resolve file path as returned from xmlsitemap_sitemap_get_file.
Comment #68
Sylvain Lecoy CreditAttribution: Sylvain Lecoy commentedGot this bug as well:
http://new.lcclub.fr/sitemap.xml
Subscribing
Comment #69
antiorario CreditAttribution: antiorario commentedSubscribing.
Comment #70
arija CreditAttribution: arija commentedI have the same problem - on http://mysite/sitemap.xml page not found. I deleted and rebuilt it a few times but without any positive results
Comment #71
Shven CreditAttribution: Shven commentedsubscribing (using 6.x-2.0-beta2)
Comment #72
tahiticlic CreditAttribution: tahiticlic commentedsubscribe, same here
Edit : as stated in #26, disabling xmlsitemap i18n submodule solved the problem
Comment #73
antiorario CreditAttribution: antiorario commentedI disabled xmlsitemap i18n but still get the same error.
Since the module used to work a few months ago, I've been moving back and forth through different versions, but I can't seem to find the one that works. Is it possible that the error depend on changes in Drupal core? (I'm just trying to guess here.)
Comment #74
websage_gr CreditAttribution: websage_gr commentedI added the elements module as proposed, it wouldn't work.
I could get it working disabling the option "Include a stylesheet in the sitemaps for humans".
Comment #75
Anonymous (not verified) CreditAttribution: Anonymous commentedComment #76
Anonymous (not verified) CreditAttribution: Anonymous commentedCan we please give the 6.x-2.x-dev version a try to see if the problem is resolved by recent modifications to fix similar issues?
Comment #77
websage_gr CreditAttribution: websage_gr commentedHi earnie,
I downloaded the 6.x-2.x-dev, ran update.php.
Then I switched on the stylesheets and updated the cache files with the elements module's update function.
It works and displays the info correctly with the stylesheet.
Comment #78
Anonymous (not verified) CreditAttribution: Anonymous commentedThanks for the report back.
Comment #79
klonos...fixed in dev then.
Comment #80
Sylvain Lecoy CreditAttribution: Sylvain Lecoy commentedI'm using the 7.x version, the bug occur in this one as well.
Comment #81
Sylvain Lecoy CreditAttribution: Sylvain Lecoy commentedDon't know if I need to open a new ticket or edit this one...
Comment #82
Anonymous (not verified) CreditAttribution: Anonymous commentedIt is generally best to open a new ticket for differing versions but it would be flagged as a duplicate because the issue is fixed in the -dev version unless of course you happen to be using the -dev version.
Comment #83
antiorario CreditAttribution: antiorario commentedI don't think it's completely fixed. Please see my comment and patch at #920062: XMLWriter::openUri(): Unable to resolve file path as returned from xmlsitemap_sitemap_get_file. (#33).
Comment #84
storytellerjeff CreditAttribution: storytellerjeff commentedSubscribing - I've tried pretty much everything above, using the newest -dev and I'm still getting Not Found. The 1.xml file is being created in the folder under default/files/xmlsitemap, but the URL link under the List tab can't find it. And neither can Google. Please let me know if I've just missed something obvious. For now I'm putting the file manually into the root folder and Google is happy, but obviously that's not ideal.
Comment #85
antiorario CreditAttribution: antiorario commented@storytellerjeff Have you patched the latest dev as I suggest in #83?
Comment #86
storytellerjeff CreditAttribution: storytellerjeff commented@antiorario - Yes, I tried that patch just before my previous post, but I'm still getting the Not Found.
Comment #87
antiorario CreditAttribution: antiorario commentedAny issues with your file system path and download method?
Comment #88
storytellerjeff CreditAttribution: storytellerjeff commentedDoesn't appear to be. When I rename the 1.xml file and place it in the root folder, everything works - when I click on the URL link it pops up with the correct sitemap and Google recognizes it. When I remove the file I've manually placed in the root directory, I just get the Not Found.
And the Sitemap Cache Directory I have set up is accurate and the 1.xml file is being created correctly and is showing up in the site/default/files/xmlsitemap folder as expected.
Comment #89
antiorario CreditAttribution: antiorario commentedMay I have a link to the website?
Comment #90
storytellerjeff CreditAttribution: storytellerjeff commentedSure, the site is www.catdoctorko.com.
Comment #91
Anonymous (not verified) CreditAttribution: Anonymous commented@storytellerjeff: When I go to your site and add sitemap.xml I see 378 links. I don't see an issue.
Comment #92
storytellerjeff CreditAttribution: storytellerjeff commentedYup, because I've manually lifted the 1.xml file from the site/default/files/xmlsitemap folder, renamed it to sitemap.xml and placed it into my root folder to keep Google happy. If I delete the file I have manually placed into the root, the xmlsitemap module gives me the Not Found message. When I first set up the module, many months ago, it was working as expected. It's very possible that I'm overlooking something obvious, but as far as I can tell, the module isn't pointing to the 1.xml file that it creates.
Comment #93
Anonymous (not verified) CreditAttribution: Anonymous commented@storytellerjeff: You need to rename the file you called sitemap.xml in your root directory and go to your Google admin UI and give it the modified file name. The xmlsitemap module will never work if you have a file named sitemap.xml in your root directory. Once your problem with xmlsitemap is resolved then you can go back to your Google admin UI and change back to using sitemap.xml.
Comment #94
storytellerjeff CreditAttribution: storytellerjeff commented@earnie: I understand that placing the sitemap file in the root directory manually will stop xmlsitemap from working. But this was done as a temporary solution because it wasn't previously working on it's own.
I've just followed your instructions (great idea) and have ensured that there's no sitemap.xml file in my root directory. Google now has the name of my renamed sitemap. And, after flushing caches, and rebuilding the XML sitemap, as expected, the Link tab URL is leading me to NOT FOUND when it looks for sitemap.xml in the root directory. Is XML sitemap supposed to create a sitemap.xml file and place it there, or simply redirect to the 1.xml file in the default/files/xmlsitemap/... directory?
For now, I'm still having to manually take the 1.xml file this module is creating, rename it to my new sitemap name and place it in the root directory. I have looked through all the documentation I could find, which is a little outdated, but didn't find anything that could be the problem.
I appreciate the help everyone and if I'm missing anything obvious, please let me know.
Comment #95
antiorario CreditAttribution: antiorario commented@storytellerjeff Instead of copying the file every time the site map is updated you could simply create a symbolic link to it (only as a temporary workaround until you find a solution to the problem).
About the problem, have you tried setting up a clean install to see if the module works on that one?
Comment #96
storytellerjeff CreditAttribution: storytellerjeff commented@antiorario I did try a clean install, as that was suggested somewhere above. I still got the same result. The symbolic link is a good idea. I'll do that. thanks!
Comment #97
Anonymous (not verified) CreditAttribution: Anonymous commented@storytellerjeff: Tell me more about your server. Do you have any server side cache involved? Maybe boost? I see information in the chrome developer tools that leads me to believe so. This is known to cause issues with xmlsitemap, IIRC.
Also you have a sites/all/modules/better_messages/skins/default/images/b1.png that is giving an error in the resource data.
Comment #98
storytellerjeff CreditAttribution: storytellerjeff commented@earnie: I'm hosted by the Hot Drupal team. I just had a look and it doesn't look like there's any server-side caching. But, I am running Boost on my end. And that might be the culprit. I'll look into that more and report back if I find a solution.
And thanks for catching that error in the resource data. I haven't used Chrome Web Developer Tools, I'll check it out.
Comment #99
Anonymous (not verified) CreditAttribution: Anonymous commentedThe Chrome Developer tools come embedded in the standard browser install. I'm just learning it myself but was nice to have looking at your site.
Comment #100
tomsm CreditAttribution: tomsm commentedPatch mentioned in #83 works great. Solved my "page not found" problem. I also use i18n.
Webserver: IIS 7.5
XML sitemap 6.x-2.0-beta2
Drupal 6.22
Comment #101
wranvaud CreditAttribution: wranvaud commentedI can confirm that when you have xmlsitemap i18n module on you have to create one sitemap for each language and hit save with a given language selected (hit save even if you don't do any modification, in the case of the english sitemap), then update the caches and it should be ok. You only need to rebuild links if you actually change links to be included or excluded.
Comment #101.0
klonos...updated with latest workaround + conforming to issue summary standards.
Comment #102
klonosHey William, thanx for the feedback. I updated the issue's summary with your findings ...and gave you credit too ;)
Comment #103
Michsk CreditAttribution: Michsk commentedI read this whole threat. I even got to the point that i have uninstalled v2, removed everything i could find of xmlsitemap. re-downloaded v2, installed, again the whole settings done.
And... you guessed it, again no sitemap. I do not run a multilingual site.
Comment #104
Michsk CreditAttribution: Michsk commentedDebug:
The location: sites/default/files/xmlsitemap/NXhscRe0440PFpI5dSznEVgmauL25KojD7u4e9aZwOM does exist
Comment #105
cookiesunshinex CreditAttribution: cookiesunshinex commentedIasac,
Are you sure that you deleted EVERYTHING. Try these steps:
1) disable module
2) uninstall module
3) delete module files under /sites/all/modules/
4) delete the /sites/default/xmlsitemap directory completely
Flush caches (not sure if this is necessary)
Run update.php (not sure if this is necessary either)
Then download and re-install the latest version of the module.
Comment #106
Michsk CreditAttribution: Michsk commentedJap, done all of that.
Comment #107
Michsk CreditAttribution: Michsk commentedAnd this is happening with 6.2beta3. Nothing in my watchdog.
Comment #108
mdlueck CreditAttribution: mdlueck commentedDid you mark content types as needing to show up on the sitemap? Did you do the same with Taxonomy, if any?
Then after that did you flag that all nodes should show up on the site map?
Then finally did you re-run cron? Do you use Drush to run cron and have it verbosely log what is happening?
Comment #109
Michsk CreditAttribution: Michsk commentedDid you mark content types as needing to show up on the sitemap? Did you do the same with Taxonomy, if any?
>> Yes and Yes, also set menu's to show up.
Then after that did you flag that all nodes should show up on the site map?
>>uhhh..? i have set them upt to show in the sitemap.xml
Then finally did you re-run cron? Do you use Drush to run cron and have it verbosely log what is happening?
>>Yes, not trough drush.
Comment #110
Anonymous (not verified) CreditAttribution: Anonymous commentedHow many times? Note that all hook_cron jobs get are 240 seconds of execution time. The more modules you have with a hook_cron the more times it may take. Look into installing the Elysia Cron module which can help control which modules are getting time in cron and give more to xmlsitemap.
Comment #111
Michsk CreditAttribution: Michsk commentedearnie: haven't tried / nore looked at that. Will do and report back.
Comment #112
mdlueck CreditAttribution: mdlueck commented>>>>Then after that did you flag that all nodes should show up on the site map?
>>uhhh..? i have set them upt to show in the sitemap.xml
Forgetting if it is necessary in this latest build of this mod... At one point you had to flag all nodes that the sitemap needed to consider placing them on the sitemap. That UI was found at the admin page listing all nodes on the site. Drop down pick list choice to mark selected nodes as needed to show up on the sitemap.
Also, is this a brand new mod install, or has a prior version been on this site ever? Thinking perhaps some cludge in the mod's temp files, stored in the Drupal temp area. If prior versions have been on, consider wacking the xmlsitemap temp dirs / files and then go though the cron gyrations again.
Comment #113
Michsk CreditAttribution: Michsk commentedWell there has been an xmlsitemap installed, but i removed it and removed all the temp files and folder. In thuis build you don't have to flag nodes.
Comment #114
Michsk CreditAttribution: Michsk commentedThis is getting anoying. I again removed the module / unstalled, removed all it's files, cleared cache etcetc blabla. Reinstalled, run cron now about for the sixth time, and still a 404.
Comment #115
Michsk CreditAttribution: Michsk commentedCurrent context: Array ( )
Sitemap: stdClass Object ( [smid] => NXhscRe0440PFpI5dSznEVgmauL25KojD7u4e9aZwOM [context] => Array ( ) [updated] => 1319546260 [links] => 30 [chunks] => 1 [max_filesize] => 2689 [uri] => Array ( [path] => sitemap.xml [options] => Array ( [absolute] => 1 [base_url] => http://domain.nl ) ) )
Chunk: 1
Cache file location: sites/default/files/xmlsitemap/NXhscRe0440PFpI5dSznEVgmauL25KojD7u4e9aZwOM/1.xml
Cache file exists: Yes
Could this have to do with boost?
Comment #116
Michsk CreditAttribution: Michsk commentedi am also using the elements module to clear the form's cache, but withouth result.
Comment #117
Anonymous (not verified) CreditAttribution: Anonymous commentedAbsolutely positively yes.
http://drupal.org/project/issues/xmlsitemap?text=boost&status=All
Comment #118
Michsk CreditAttribution: Michsk commentedNot boost. But fast 404's http://drupal.org/node/857108#comment-4063752
Comment #119
wellyas CreditAttribution: wellyas commentedSame problem. 404.
Comment #120
atilla CreditAttribution: atilla commentedIn my case the cron job did not run. When I tried the /cron.php it gave me this error
translation_management/icl_core/icl_core.module on line 191
Because the Content module under translation management was not enabled. I enabled it and went through #19. It worked for me.
www.gokhancanpolat.com
Comment #121
Anonymous (not verified) CreditAttribution: Anonymous commentedRe: #120
You need to file an issue with the translation_management module. It seems some dependencies are missed.
Comment #122
thedrupalguy CreditAttribution: thedrupalguy commentedHi All,
Please make sure of the PHP version you're using. I added one more PHP v 5.2.5 addon to my wamp server and it worked. Previously I was using PHP v5.3.5 and I had issue with running cron and opening sitemap.xml file but now it is a thing of the past.
Please respond if this trick works for you too.
Comment #123
Anonymous (not verified) CreditAttribution: Anonymous commentedPlease do not change titles of an issue unless it is for clarification of the issue.
Comment #124
Kodyn CreditAttribution: Kodyn commentedHi all!
I've the same problem. I've tried to uninstall it, reinstall it. But still I'm not able to run the http://sudokucup.com/sitemap.xml. I've 9 language versions and I'm able to see the 1.xml file and to access it. For English there is this xml file and I'm able to see it http://sudokucup.com/sites/default/files/xmlsitemap/g3XYqcXbSKPVBDODwnT6...
The debug gives me this information (this works - http://sudokucup.com/sitemap.xml?debug):
Current context: Array ( [language] => en )
Sitemap: stdClass Object ( [smid] => g3XYqcXbSKPVBDODwnT6pq7oqhCFkPryj4vVqrl_Kfc [context] => Array ( [language] => en ) [updated] => 1370542730 [links] => 345 [chunks] => 1 [max_filesize] => 42961 [uri] => Array ( [path] => sitemap.xml [options] => Array ( [language] => stdClass Object ( [language] => en [name] => English [native] => English [direction] => 0 [enabled] => 1 [plurals] => 0 [formula] => [domain] => http://sudokucup.com [prefix] => [weight] => -10 [javascript] => ) [absolute] => 1 [base_url] => http://sudokucup.com ) ) )
Chunk: 1
Cache file location: sites/default/files/xmlsitemap/g3XYqcXbSKPVBDODwnT6pq7oqhCFkPryj4vVqrl_Kfc/1.xml
Cache file exists: Yes
Does anyone have any idea?
I've Drupal 6.28. I use version 6.x-2.0-rc2. I've installed Elements.
Comment #125
klonosPlease assign issues to yourself only when you intent to work on them (as in actually writing code that fixes things).
Comment #125.0
klonos...fix original report section.
Comment #126
joco_sp CreditAttribution: joco_sp commentedThis worked for me:
the difference was only, that I didn't need to hit save on every language. It was enough to make two different sitemaps (one English and the other with the second language) and then rebuilt links.
Comment #127
smartmark CreditAttribution: smartmark commentedI am using i12n and although I've followed the recommended steps
- disabling and deleting old version of xmlsitemap module
- installed new xmlsitemap and elements modules, and enabled them with xmlsitemap i18n submodule
- included nodes into sitemap
- deleted predefined sitemap and created separate sitemaps for each language (default Czech and English)
- "updated cached files" at admin/settings/xmlsitemap
- set high limit for cron (1000 pages) and run cron manualy
- clicked "rebuild links" at admin/settings/xmlsitemap
- "updated cached files" once again
I still cannot see /sitemap.xml in Czech language - debug:
The weird thing is that the english sitemap works: http://en.skkp.cz/sitemap.xml, although its reports in DB and in debug seems very similar. Debug:
The sitemap is well generated, but I am frustrated that I cannot access it from /sitemap.xml (and the lengthy adress is not a good idea to submit to search engine)
Comment #128
smartmark CreditAttribution: smartmark commentedI haven't been able to resolve the problem of "sitemap not found" with reinstaling, updating, or regenerating xmlsitemaps (which apparently worked for others, but not for me). Since I am more of a PHP programmer than Drupal developer, I created a "hack" that works for me.
I created the following PHP script:
You may upload this file wherever you want. The important thing is to direct the browsers to this file. This can be done in two ways:
1. robots.txt
2. .htaccess
Either one should be sufficient.
I know that PHP out of modules in Drupal is depreciated, but this issue with xmlsitemap made me mad... I spent hours by clicking and reinstalling and trying, while I made this workaround in less than 45 minutes.
I guess for desperate people like me this might be a reasonable way to go.
Comment #129
ktmwebhosting CreditAttribution: ktmwebhosting commentedplease help me
http://www.ktmwebhosting.com/sitemap.xml
give me 404 error
i read all above support but i can't find solution
plz help me
Comment #130
jgardezi CreditAttribution: jgardezi as a volunteer commentedHi @ktmwebhosting,
I see you were able to solve the issue. Please let me know the steps you have taken to solve the issue.
Comment #131
gobinathmConsidering D6 already in EOL, shouldn't this issue also be in Closed status ?
Comment #132
tedwyer CreditAttribution: tedwyer commentedThis issue still exists in D7. Looking for a solution at this moment
Comment #133
karlkablisk CreditAttribution: karlkablisk commentedUsing D7, this is what I did and got it working after it stopped working for some reason.
In the xml sitemap settings tab, I checked
"Enable developer mode to expose additional settings."
And then the rebuild page lets you separate which you rebuild.Nodes, users, menu_links etc. I then rebuilt each one by one and saw only MENU was causing an issue. So I excluded all menus (I saw some errors that referred to superfish etc so maybe that is what did it.) Now Menu_link didn't appear in the rebuild page at all. You can also try making the "Number of links in each sitemap page" and "Maximum number of sitemap links to process at once" are at the lowest numbers. Less than 1000 pages still goes very fast even at those low settings. Good if your php and my.cnf settings aren't very high.
After that I was able to run a rebuild. You could also just not select menu when you rebuild even if its included that worked too. I tested this after disabling xml internationalization.
URL worked too. I tried using a custom URL also in the settings page under, "Default base URL". That didn't work so well so I went back to putting the site's url. Rebuilt and with the elements module installed updated the cache.
Now that it worked and the xml file appears. Though without xml internationalization, all languages were appearing although not as orderly as before.
I am 90% sure these are the settings I started with before I changed anything, but doing it like this one by one and adding to it seems to have gotten it back in order and now I understand the components a bit better.
Lastly, I put internationalization back and still having issues with the language and tweaking but at least the xml pages are showing up again reliably. Now I just need to get it to recognize both languages are separate. Worst case I'll have both languages show up in the same xml though I don't know if that is an effective solution it does get both languages seen.