I generated one and uploaded it as a card. I know you guys said the site doesn't really rename files, but google can't find the file I uploaded unless I give it the renamed filename with the numbers in it. I don't know if that actually matters in whether or not it will serve its purpose once I give google the URL. But... shouldn't I be able to sitemap.xml on my site AS sitemap.xml somehow?
The idea is that you would upload it as a File card named "sitemap". If you have a Wagn request in the form of /x.y, then x is the card name and y is the format. So if you want /sitemap.xml to work, you need a card named sitemap.
It doesn't actually work at present, because wagn has special xml handling and tries to process the content when you go to .xml. What needs to happen is that it gets smart about recognizing that it doesn't actually have to convert anything when it's already an XML file.
If you did the File card thing, you could do this: /sitemap.xml?explicit_file=true
I think you'll be able to get Google to work regardless.
So the explicit_file=true tells it to not do any processing based on the file extension?
It appears that Google doesn't care what the filename is so long as it's an actual sitemap. Should I rename the card now so it doesn't have any extension in the cardname, so that when you fix this XML handling it'll work?
John: yes, essentially. it tells it to look for a file rather than process a card from the database.
Lora: sure, why not :)