WordPress Annoyances

So far the transition from Blogspirit to WordPress has been a bit better than I feared, though I think the difficulties I’ve experienced validated my hesitation.  WordPress is definitely software “by geeks for geeks,” meaning it comes broken in numerous ways and requires manual programming on the user’s part in order to get it working write.  So far, this blog is still “broken” because of errors on WordPress’s part.

0. Importing has to be done through the web front-end.  There is no FTP or CLI method to batch-upload to the blog.  This is incredibly wasteful, as tdaxp is a large site that requires a long time to enter a file, click, submit, wait, submit, repeat, over and over.
1. It comes broken, and WordPress knows it.  WordPress imports tags as numbers.  The only solution is to delete what you’ve imported, manually change the code in a file, and import again
2. It comes broken, and WordPress doesn’t know it.  WordPress is importing only about half of the comments that exist in wordpress data file.  It doesn’t generate an error or leave any trace of the eaten comments — just, they’re gone.

2 thoughts on “WordPress Annoyances”

  1. Sounds like you need some sort of HTML-based macro recorder. Have you evaluated such tools? I’ve used an older version of this http://www.iopus.com/imacros/ and they have a 30-day free trial.

    For the tag trouble, could you script the pre-import massaging that needs to be done to all or some of your the files?

  2. Moon,

    Thanks for the link!

    Tag was a one-line fix in import/wordpress.php, but still annoying to have to find.

    For comments — I guess I’ll modify my perl script to compare comments to what’s already in the database, and create a new file to import into mysql.

    I’m less frustrated now than I was, but there’s definitely a tradeoff between ease of use / power.

Leave a Reply

Your email address will not be published. Required fields are marked *