Faster than manual, but not free of pain
What I thought today:
- It’s always good to have helpful developers around, especially when they work on similar issues than you do. One of my current tasks is the migration of the vLib blog from b2evolution to WordPress… and the helpful developer wrote a script to do this job.
- It’s always a challenge to be an early adopter. After using the script we noticed some traps which required a certain amount of manual work in addition.
Just one example: b2evolution demands that html tags are closed and therefore all our image tags included a closing slash, e.g.<img src="http://vlib.mpg.de/img/sfx-citation-linker-tabs.png"/>. The import worked fine, but editing and saving the post under WordPress removed the tag. It looks like WP don’t like the string"/>, adding a blank between slash and bracket solves the problem - There is no reason to keep silent. The helpful developer listened patiently to all my complaints and did some minor revisions to his code. I hope this will reduce the work for those who are coming after me!
October 1st, 2008 at 10:22 pm
BTW: This post was also meant to test WordPress’ pingback mechanism which discovers links to external blog postings and then tries to ping them. As a result, a comment is added to the target blog and can be approved by the corresponding administrator (as any other comment). In this case, the term “script” is linked with Robert’s posting and he meanwhile accepted the comment (the forth entry was added automatically).