Is it me or has the Site Mapper action stopped working with the upgrade to 5.5.2?
When I try to apply it, I’m getting a message in the actions window saying: “Cannot use this action - Apply the site mapper file location action to a page in the site.”
I’m not sure what the site mapper file location action is, but it doesn’t seem to solve the problem.
Thanks for the suggestion, Tom. This is a website I’ve been running for some time, so all those upload details are in place, but I’ve just realised that by following the instructions and applying “the site mapper file location action to a page in the site”, the site mapper folder action then starts working.
Incidentally, I have the same problem as someone on another thread about submitting the site map to Yahoo using Firefox.
Except that I tried adding the site mapper to a page as it suggested and it still didn’t work.
Removed the action from the site folder and reapplied it - still refuses to be used.
I also use showcase action in my site and have only just got over problems with an unwanted interaction with Anti-Spam action - is this another unexpected issue or something a little bigger?
There are now Site Mapper and a Site Mapper File Location Page Actions. the one that is required is the File Location one (though you should really use the Site Mapper Page Action on almost all your pages to give them a different priority too).
If i still doesn’t work after doing this then let us know exactly what the message in the Action palette is.
Joe
On 2 Nov 2010, at 11:01, reab wrote:
Well . . me too!
Except that I tried adding the site mapper to a page as it suggested and it still didn’t work.
Removed the action from the site folder and reapplied it - still refuses to be used.
I also use showcase action in my site and have only just got over problems with an unwanted interaction with Anti-Spam action - is this another unexpected issue or something a little bigger?
Site Mapper action applied to Site Folder
Site Mapper File Location action applied to a page within the site
Site Mapper Page action applied to each individual page
There are now Site Mapper and a Site Mapper File Location Page Actions. the one that is required is the File Location one (though you should really use the Site Mapper Page Action on almost all your pages to give them a different priority too).
If i still doesn’t work after doing this then let us know exactly what the message in the Action palette is.
Joe
On 2 Nov 2010, at 11:01, reab wrote:
Well . . me too!
Except that I tried adding the site mapper to a page as it suggested and it still didn’t work.
Removed the action from the site folder and reapplied it - still refuses to be used.
I also use showcase action in my site and have only just got over problems with an unwanted interaction with Anti-Spam action - is this another unexpected issue or something a little bigger?
The sitemap will be generated alongside the page the File Location Action is applied to. So if you want the map to be in your root folder then apply it to any page at root level (i.e. in the Site Folder and not a subfolder). If you want it to be published in a subfolder then apply it to a page in a subfolder.
Hope this helps,
Joe
On 2 Nov 2010, at 13:57, Julie Maxwell Allen wrote:
Thank you!
does it matter what page the file location goes to or if it is the index.html page
THank you Joe!
Julie
On Nov 2, 2010, at 9:53 AM, Joe Billings wrote:
Yep, that’s it.
On 2 Nov 2010, at 13:46, Julie Maxwell Allen wrote:
so the file location is only to 1 page.
and page action is to each page that we feel is a main page
sorry just want to be clear
J
On Nov 2, 2010, at 8:57 AM, Joe Billings wrote:
On 2 Nov 2010, at 12:02, Nathan Garner wrote:
So…
Site Mapper action applied to Site Folder
Yep.
Site Mapper File Location action applied to a page within the site
Yep.
Site Mapper Page action applied to each individual page…
… of importance. Without doing this all pages will have the same priority.
it does - thank you - sorry for sounding blond. but i wanted to ensure I understood!
J
On Nov 2, 2010, at 10:04 AM, Joe Billings wrote:
The sitemap will be generated alongside the page the File Location Action is applied to. So if you want the map to be in your root folder then apply it to any page at root level (i.e. in the Site Folder and not a subfolder). If you want it to be published in a subfolder then apply it to a page in a subfolder.
Hope this helps,
Joe
On 2 Nov 2010, at 13:57, Julie Maxwell Allen wrote:
Thank you!
does it matter what page the file location goes to or if it is the index.html page
THank you Joe!
Julie
On Nov 2, 2010, at 9:53 AM, Joe Billings wrote:
Yep, that’s it.
On 2 Nov 2010, at 13:46, Julie Maxwell Allen wrote:
so the file location is only to 1 page.
and page action is to each page that we feel is a main page
sorry just want to be clear
J
On Nov 2, 2010, at 8:57 AM, Joe Billings wrote:
On 2 Nov 2010, at 12:02, Nathan Garner wrote:
So…
Site Mapper action applied to Site Folder
Yep.
Site Mapper File Location action applied to a page within the site
Yep.
Site Mapper Page action applied to each individual page…
… of importance. Without doing this all pages will have the same priority.
Hmm . . well I applied the site mapper action (only appears in the folder actions to choose from) to my site folder (worked ok in previous version of FW) and get an error message.
Made another folder and tried to apply the folder action with failure again.
Error message in the site mapper tab is:
Cannot use this action.
Apply the site mapper file location action to a page in the site.
I can apply individual page actions for site mapping without a problem but the file location action tab is totally blank when applied!
The same thing happened to me, but I’m assuming the file location action tab is supposed to be blank and it’s just a way of telling the other action where to place the site map information. This is only a guess and I could be wrong.
I’m not convinced that having to use three actions where one used to do is much of a time-saver. My old method of creating a sitemap at www.xml-sitemaps.com, putting it on the server, then telling Google about it seems only marginally more of a fuss.
We know it takes more steps but the old method was prone to breaking. Now when you change anything in the Site Mapper Page Action the main Site Mapper Action will publish the changes correctly. Also, the file is now always guaranteed to be called the same thing whereas previously it would get generated as sitemapa.xml, sitemapb.xml etc. This would cause Google to lose the file because it wouldn’t know the filename had changed.
Hope that clear things up.
Joe
On 2 Nov 2010, at 16:16, Mark F Fisher wrote:
Hi Roger,
The same thing happened to me, but I’m assuming the file location action tab is supposed to be blank and it’s just a way of telling the other action where to place the site map information. This is only a guess and I could be wrong.
I’m not convinced that having to use three actions where one used to do is much of a time-saver. My old method of creating a sitemap at www.xml-sitemaps.com, putting it on the server, then telling Google about it seems only marginally more of a fuss.
OK - however it doesn’t help me at all - once again I can’t rely on the site map to be generated as the folder action no longer works and I also will drop back to www.xml-sitemaps.com
Its a pain to go to each page and I reiterate - this worked ok previously and now doesn’t after a minor upgrade!
Just tried adding a page site mapper action and uploaded it - no site map!