asy_sitemap: Google-Sitemap (as-is/for developers)

Dawk · 2007-12-26 22:25:56

Is this 4.05 ready?

Thanks ;)

els · 2007-12-26 23:45:50

It’s working for me in 4.0.5 :)

SebastianS · 2007-12-31 12:08:57

Hi,
I uploaded Sencers ‘asy_sitemap: Google-Sitemap’ to install plugins created a folder in webdevelopmentnotes.com/public_html/sitemap.xml.gz , changed CHOMD to 666. amd get the message

Can’t write to file.

Filename: /home/loginname/domains/webdevelopmentnotes.com/public_html/sitemap.xml.gz

Using Textpattern 4.05.
be nice if all pages could be indexed by google not just home page.
What am I doing wrong?

iblastoff · 2007-12-31 12:49:58

its supposed to be a file, not a folder.

SebastianS · 2007-12-31 20:37:06

Steve thank you for your help,
Sencers ‘asy_sitemap: Google-Sitemap’ works fine with Textpattern 4.05.

kevinpotts · 2008-01-05 19:52:49

I will happily donate to the person who can take this plugin to the next level, meaning iron out the bugs and being able to select what sections are included. Consider me your patron.

TNT · 2008-01-14 19:41:51

I second the request by kevinpotts: this plugin deserves a second life!

But in the meantime: does anyone have the raw version of this plugin, modified by GeertAki? That file is no longer online, but I would like to have it since I would like to exclude some sections from the sitemap.

Thanks in advance.

LeeUmm · 2008-01-14 19:49:36

I would third the request. I think this is a simple, but much needed plugin.

Here is the version you’re after which allows sections to be excluded:

http://www.shiftideas.com/stuff/asy_sitemaps.org.txt

GeertAki · 2008-01-14 19:59:26

Thanks for adding it again LeeUmm. I lost the original version after server crash and the hosting company did not have a backup (though they promised to take backups)…

els · 2008-01-14 20:15:11

+ 1. If I could code I’d do it myself, but what I’d really like to see, is a checkable list of sections instead of having to edit the plugin code.

Bloke · 2008-01-14 21:31:34

First of all thanks to Sencer and Geert among others for the code, and LeeUmm for reposting.

Fundamentally I have to say I just don’t get it. And by “it” I mean the whole sitemap thing. I must be thick or something. Is it a “statament of intent” to Google/MSN/Yahoo or a statement of fact about your content? Or somewhere fuzzy in between? Does it learn?

Why do all the “generate your sitemap” services (and this plugin to a degree) take fixed values and apply them to every section/article on the site? And set the priority of every page the same? How does that help the bots according to the spec? I’m confused (mind you, doesn’t take much ;-)

A few observations:

In the absence of comments being taken as an update trigger, surely in a blogging site once an article is posted its change frequency should be “never” (or thereabouts, except for perhaps a few edits)?
Granted, the section that the article(s) are posted in will be more frequently updated depending on how often articles are submitted
Thus each section should have a different frequency — roughly. E.g. an “about” section probably won’t change as often as an “article” section
For “corporate” sites, maybe they will be updated more frequently as articles are periodically updated/reviewed by managers who are paid too much and know too little
Setting all the priorities the same does no good. The crawler needs to know the relative importance as deemed by the author, otherwise you might as well just let googlebot do its stuff without the sitemap; it has nothing to go on (I see this plugin omits priority ;-)
As pointed out in the forum thread, hidden/excluded (non-site-search) sections should be omitted as standard (overridable of course)
As Els and others have said, configuration of additional sections to exclude should be an option without having to mod the code
All the data is in TXP to have it intelligently determine how often sections change and offer sensible defaults for each section. Similarly for importance; the more frequent a section is posted to, the more important it is deemed unless you say otherwise. It’s just maths (this is for the “when I click Go” type of sitemap generation; doing it this way for the “automatically when I submit an article” variety might slow the publishing down too much unless another database table is used to cache results)
From a usability perspective the plugin shouldn’t rely on you making files manually, it should do it for you if the files don’t already exist. I know this was a rough-n-ready attempt at first, but it seems to have grown into something that now requires some polish to take advantage of the new stuff in the core
If I’ve understood the spec correctly the sitemap.xml file should be put in the site root and indexed from robots.txt. Again, the plugin should publish the raw .xml version automatically and offer the .gz version for you to ping google with at your own leisure. I have no idea what a ROR sitemap is or who uses it: more research required

And that’s just for starters…

My background in computing is taking data and turning it into usable information. If nobody objected I was half tempted to take this plugin on as a project but I think I need to get it straight in my head exactly what the point of the bloody thing is first! I’ll read up some more, but in the meantime if anyone else can put their point of view forward to set me straight, it all helps.

As far as I can tell, Googlebot does an admirable job on its own without being given a half-arsed list of URLs with wrong frequency information (and that’s not a criticism of the plugin, it’s waaaay better than 90% of the web-based sitemap generators out there!)

Seriously, I know I’m playing Devil’s advocate here but if we can generate some discussion over what everyone who uses it thinks the thing should do and how it benefits search/mankind then perhaps we can work out a very usable and useful plugin between us; I have no problem adopting this plugin if there’s a tangible need for it. Then again, maybe the answer will be that there’s not much point any more if we really sit down and think about what it does for us. At this stage I just don’t know.

So, shall we restart Phase 1 of the Computer Science 101 class: The Feasibility Study… who wants to kick things off?

EDITS: many typos and incongruence fixing. Was too late at night to write :-(

Last edited by Bloke (2008-01-15 10:06:17)

the_ghost · 2008-01-14 23:28:07

Bloke – where you bought so much of inspiration to post this? :)

As for me I’d like ar to see some log-file, or make plugin to messge me after sitemap is recreated after i created an article or editted it. At the current point i have commented out (issue is discussed here) the part of plugin:

if (function_exists("register_callback")) {
//		Uncomment the following 2 Lines if you want the sitemap to
//		be automatically recreated, whenever you edit or post an article.
//		register_callback("asy_make_sitemap_wrapper", "article", "edit");
		register_callback("asy_make_sitemap_wrapper", "article", "create");
}

But as far as i see it doesn’t recreates sitemap currently :( Only manual method works well.

Last edited by the_ghost (2008-01-14 23:47:51)

Textpattern CMS

Textpattern CMS support forum

#85 2007-12-26 22:25:56

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#86 2007-12-26 23:45:50

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#87 2007-12-31 12:08:57

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#88 2007-12-31 12:49:58

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#89 2007-12-31 20:37:06

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#90 2008-01-05 19:52:49

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#91 2008-01-14 19:41:51

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#92 2008-01-14 19:49:36

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#93 2008-01-14 19:59:26

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#94 2008-01-14 20:15:11

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#95 2008-01-14 21:31:34

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

#96 2008-01-14 23:28:07

Re: asy_sitemap: Google-Sitemap (as-is/for developers)

Board footer