…meie igapäevast IT’d anna meile igapäev…


WordPress ListMaker v2

Filed under: WordPress — Sander @ 14:34:22

WordPress ListMaker v2 is a small utility to make an index – or sitemap – for your WordPress-based blog. It utilizes MetaWeblog API metaWeblog.getRecentPosts XML-RPC call to get a list of your blogposts from the server. It is theoretically possible to use WordPress ListMaker on any blog engine that supports MetaWeblog API, but this has not been tested.

Recently I created WordPress ListMaker – but the first version required way too much things to be done manually. So I created v2, which is much less error-prone and doesn’t require that much manual interference. You can see my blog index as an example of the WordPress ListMaker output. Note that the index will follow/use the theme of your blog. Download WordPress ListMaker v2 from my home page.

Using WordPress ListMaker

  • WordPress ListMaker has no installer, just extract all files to any folder and run WordPressListMaker2.exe.
  • Fill in the full address of your blog and username/password.
  • Click “Get posts” to start downloading them, that may take from few seconds to few minutes, depending on the amount of posts, speed of your connection and speed of the blog server. You can see the progress – or error messages – in the log tab.
  • Tweak the HTML on Code tab if you want to. Switching from Code tab to Preview will update the preview.
  • Click Code to clipboard
  • Create a new post or page on your blog – or you can use an existing post/page.
  • Go to tab Code on the Write Post page and paste the the contents of your clipboard there.
  • Voilà! All done, go to Visual section to edit things further or just publish the page.

Some useful links

The future?

As it is possible to post and edit a page through WordPress XML-RPC interface, I plan to add that at some point in the future. Don’t ask me when – it will happen, when I feel like tackling the non-existing documentation of WordPress again… With luck, it may happen in a few months, but don’t hold your breath.

If you have any suggestions – or want to report an error – then leave me a message here or send an e-mail.

15 kommentaari »

  1. Ma ei mõelnud sellist sitemappi, nagu traditsiooniliselt Google välja pakutud sitemap’id seda on – lihtsalt inimesed on WordPressi foorumis lisanud postitusele tag’i “sitemap”. Sellest ka siin selle mainimine – et ka nemad taipaksid. Ise uut sitemap generatorit ei vaja, minu enda kodulehel on see ilusti olemas. Küll aga vajasin WordPress.com’i blogile indeksit, selleks ka see pisirakendus.

    Kommentaar kirjutas dukelupus — 2007-08-15 @ 19:08:58 | Vasta

  2. I’m trying to get it to run and I couldn’t get version 2 to run on my WordPress.com blog. So I tried exporting the XML file and running the earlier version. The errors I’m getting which cause it to fail on the over 2000 posts are so far related to foreign character entities (didn’t recognize umlaut in one case) nor the double right and left arrows so commonly used in blog titles and post titles in the TITLE HTML tag on WordPress blogs.

    This might have been what stopped version 2 from working with the WordPress.com blog. So far, it keeps finding these character entities so I’m fixing them as I go in the XML file and then trying again. Hopefully this will work soon.

    Kommentaar kirjutas Lorelle VanFossen — 2007-08-16 @ 08:55:50 | Vasta

  3. Hmm, can you give me the exact error message, please? You can copy it from the “Log” tab – just in case, give me the preceding message as well, so I’ll know at what point the error occurs.

    WordPress XML-RPC *should* be encoding all the entities, but if it doesn’t then I have to change the code to do that.

    Kommentaar kirjutas dukelupus — 2007-08-16 @ 09:46:49 | Vasta

  4. Okay, here is my report, from over 24 hours of almost non-stop poking and prodding and pulling out hair.

    I had to install the latest version of Microsoft .NET Framework 3.5 Beta 2, so for others looking for this, that’s the link.

    I tried running Version 2 and it won’t work with WordPress.com – but I say that with conditions. I had to go to Version 1.2 to get it to work from the downloaded XML export file, in which I ran into many character entity errors, which is why it might not have worked with version 2.

    Many foreign character entities and symbol entities using alphabet soup instead of numbers are not recognized by the program, thus it halts and reports an error on that line.

    99% of all these errors were in comments, so getting the program to skip everything within the comments XML tag would be a brilliant move. Otherwise, I can send you a list of the character codes that it did not recognize and you can put them into some kind of filter, if that’s possible. It’s a very long list like &bull;, &ouml;, &auml;, &uuml;, &atilde;, &middot;, and &egrave; – not all common but some are very common for languages. I was stunned when the codes for the double <> weren’t recognized as those are in so many trackbacks and such. It also didn’t recognize >>> and <<< as those are used commonly in comments to “blockquote” from the post or another comment.

    The parser worked very fast. It’s amazing. It took longer to save the file than run the parser on the same file. Amazing.

    I recommend to EVERYONE that they clean out comment spam before exporting the XML file, which I also recommend you put into your instructions for both versions. That would have saved me much grief as many comment spammers use badly formed HMTL tags, which also caused no end of errors such as leaving out quotes in anchor tags or starting with one tag and closing it with another that doesn’t match, thus leaving a broken tagged section.

    Another strange error was discovered after the file was finally parsed. All the multi-word categories/tags came out with a space in the link such as /tag/WordPress Tips instead of /tag/wordpress-tips which meant a lot of search and replace in the parsed output to fix that.

    The end result is just a list, a list that can be sorted by only the first category, which is alphabetical rather than helpful. For instance, if “blogging tips” is the first category selected and “wordpress tips” is the second, the wordpress tips posts aren’t in their own list, just included with all blogging tips. I’d love to see them in their own list.

    Site maps work best when they are in outline form, with information grouped in categories and like topics. I’d love to see the output grouped totally by specific category, not just first category, since many posts belong in more than one category on a blog. A little redundancy can be helpful when plowing through a few hundred posts.

    Sorting posts by date or title is really not helpful in a site map/table of contents. Who really cares when a post is published? Only the blogger, not the readers. Readers are looking for categorized content and keywords, not a big list sorted by date or alphabetically. Few title their posts with the keyword FIRST in line anyway.

    I also found that Pages are put into the mix with the posts, and I had a tough time pulling those out from all the posts.

    Here are some statistics, after I finally cleaned up all the errors that plagued the process for me. The file that went into the parsing program represented 506,797 lines of code (actually more as I finally dug in and deleted a lot of comment spam sections). The end result was an HTML list representing 1,290 links. Very good! Wish it just hadn’t taken so long to get to the end of it.

    I haven’t published the site map as I have to go through and sort out all the posts into their appropriate categories, and that’s 1,290 posts to go through. I’ll probably break them down by series and related content better than just through the category tags so it’s more helpful to my readers.

    Still, this is impressive and wonderful, especially for smaller blogs with less comments, comment spam, and international language issues. I’ve been waiting for something like this for two years. I hope my feedback will help it improve for everyone. Thank you so very, very much!

    Kommentaar kirjutas Lorelle VanFossen — 2007-08-17 @ 06:41:38 | Vasta

  5. Hmm, pita… why does it ask for .NET 3.5? It should ask for .NET 2.0 – as that is what it is set to target in Visual Studio 2008. I recompiled it with Visual Studio 2005 now, available temporarily from here. That version will also replace a space in the tag link with “-”

    What error did you get with v2 and WordPress.com? If I’d know the exact error, I could hopefully fix whatever is wrong with it. It is working fine with all four blogs that I can access in wordpress.com.

    As for character entities – that was one of the issues with v1 that made me look for other ways to get the list. WordPress export XML is rather crappy, containing all kinds of errors that make .NET XML parser choke.

    Last, but not least – thank you for your feedback, Lorelle, it is very much appreciated. Hopefully we can get v2 to work for you.

    Kommentaar kirjutas dukelupus — 2007-08-17 @ 07:53:26 | Vasta

  6. It didn’t “ask”. That’s the latest version I found on the web. It took a while to find that. If there was a link to the specific version of .NET in the readme files, I didn’t find it.

    The error with WordPress.com and version 2 was service unavailable, failure to respond, site not responding, and similar. It didn’t give a specific error regarding a line of code, just didn’t get that far.

    I hope this helps. It’s brilliant, and after a lot of hours of fixing the downloaded XML file, I did get it to run and now I’m sorting it all into some kind of sense, since the output doesn’t make any sense at all to be useful for my readers.

    Thanks and this is so exciting!

    Kommentaar kirjutas Lorelle VanFossen — 2007-08-18 @ 17:02:43 | Vasta

  7. Once again, thank you for your feedback.

    I don’t know why you couldn’t connect to WordPress.com. If the application is allowed through the firewall and WordPress itself is working, then it should work just fine. Can you post to your blog with external editors, such as Windows Live Writer? They use XML-RPC as well for communicating with your blog. If they don’t work for you, then the issue isn’t with the listmaker – if they do, then I have no idea how I could help you, sorry.

    Kommentaar kirjutas dukelupus — 2007-08-18 @ 18:03:14 | Vasta

  8. I had an idea – or, tbh, Lawdy suggested it. You have a huge amount of posts, Lorelle – and that may be the reason for v2 not working for you. It may be, that XML-RPC request simply times out when downloading info about all of them. I cannot check this myself, as I only have approx. 80 posts in my blog.

    However, in a day or few I’ll make listmaker v2.1, that will have the ability to limit the amount of posts downloaded, getting only the latest posts – which will at least give you the ability to add new posts in batches of few hundred or so. It will have some other minor goodies as well.

    Kommentaar kirjutas dukelupus — 2007-08-20 @ 11:04:42 | Vasta

  9. Thanks. I’ll check it out then. – ERK! Wait. Only the most recent? Can’t it be date oriented, like all posts from October 2005 – December 2005? Something like that? It’s the old ones I’m trying to sort out, not just the latest ones. I want a site map, not a “most recent” map. :D

    Kommentaar kirjutas Lorelle VanFossen — 2007-08-30 @ 00:46:48 | Vasta

  10. Thanks your program works as a charm. I will make sure to mention it in my future post about wordpress.com tools . Once again thank you for creating that wonderful program.

    Kommentaar kirjutas skykid — 2008-05-03 @ 19:14:14 | Vasta

  11. […] best option I’ve come across is a smart number called Listmaker by Dukelupus. It’s sleek, fast, and simply works. Still, even this solution requires some […]

    Pingback-viide kirjutas Wordpress.com Sitemap - Instructions « ElleDoesIt — 2008-09-29 @ 13:43:23 | Vasta

  12. Thanks… I’m using this on my blog… http://onestopeats.wordpress.com/index/
    But, I’m yet to find something that updates itself.

    Kommentaar kirjutas Meenakshi Matai — 2009-04-12 @ 08:06:57 | Vasta

  13. Thanks for this good program!

    Kommentaar kirjutas Tin180.com — 2010-03-24 @ 11:45:41 | Vasta

  14. Thanks, it’s really useful. However, I use Linux, so I wrote a Python script that produces a similar output; it can be downloaded from here: https://ubuntuincident.wordpress.com/2011/02/23/archives-list-generator/ .

    Kommentaar kirjutas Jabba Laci — 2011-02-24 @ 01:46:21 | Vasta

RSS feed for comments on this post. TrackBack URI

Lisa kommentaar

Täida nõutavad väljad või kliki ikoonile, et sisse logida:

WordPress.com Logo

Sa kommenteerid kasutades oma WordPress.com kontot. Logi välja /  Muuda )

Google photo

Sa kommenteerid kasutades oma Google kontot. Logi välja /  Muuda )

Twitter picture

Sa kommenteerid kasutades oma Twitter kontot. Logi välja /  Muuda )

Facebook photo

Sa kommenteerid kasutades oma Facebook kontot. Logi välja /  Muuda )

Connecting to %s

Blog at WordPress.com.