If you see the post I linked, could get the idea.
WP, MT and Blogger are using same way for skinning so the technique for Blogger is appliable for WP and MT with a few changes.
Keyvan NayyeriWaegis Anti-Spam Filter - Stay Away from Spams on Your Community Server Sites
No, this won't work for that. You'd have to set up your own WordPress site on your own machine, and then do a WordPress to WordPress export, import the site to your local machine, and THEN replace the file on your local machine and use it to export from there to CS. I know that's a pain in the butt, but you could always yell at WordPress and tell them to support open standards .
I actually did this yesterday and it worked out decently well. I had to create a temp PHP wordpress site, then export its files using Robert McLaw's BlogML Wordpress exporter.
I still had to massage the data a bit though, the schema that Robert used may have been out of date so I had to some massaging to get it to work with the BlogML v2.0 standard (shifting a few elements around).
If wordpress could provide an XSD schema of their extended RSS format then it should be fairly simple to churn out an XSLT using XML mapping software.
hkarthik,
Can you use my contact page at http://www.windows-now.com/blogs/robert/contact.aspx and message me about this offline? I'd like to get a copy of the changes that you made so I can update my export file. I went off the last schema in the Schemas folder, but it may not have been updated.
The reason I went with a native BlogML solution and not an XSD for the WXR file is because their format REALLY sucks, and doesn't pull out anywhere near as much info as it should to do a full export. BlogML doesn't provide enough info either, but it's much closer than WXR.
Long live BlogML .
Hello Robert.
I would think a one-step process to import either Blogger or WordPress into CS should be a priority, if not for Telligent, then leastways for Über-devs such as yourselves, since it would introduce more people to what is undeniably the best blogging software out there.
WordPress has such a tool, for importing blog entries into Wordpress, so I cannot see why it can't be done. (Then again, I am no longer a developer, so what do I know?)
This is the only thing stopping me from going live with CS for my personal blog, and getting clients to use the community features of Community Server.
John Obeto IIManaging Partner LogikworxEditor, SmallBizVista.comBlog: AbsoluteVista
Now, It would be possible to put a web-based BlogML tool into the default CS installation, but you’d still have extra steps if the other blog engines didn’t have BlogML built-in too. As a Blogger customer, you should write to Google and tell them to support BlogML for their export system.
Anyways, John I'll e-mail you about this more in about a week or so. Might be able to get you off a substandard blogging engine sooner than you think .
Much appreciated, Rob.
I cannot wait to get off Blogger fast enough.
It seems to be at LEAST two steps. One: get the BlogML file. I did that.
Two: import it in to CS. Mine timed out. Is it too big? Mine is 4522k. about 4000 posts.
On further inspection, there is this error ast the end of my exported Xml file:
<b>Fatal error</b>: Maximum execution time of 60 seconds exceeded in <b>D:\myhostaccount\wp\wp-admin\export.php</b> on line <b>172</b><br />
any ideas?
I don't know much about WordPress, but it sounds like you may need to increase the timeout in your .htcaccess file so that the script can run longer.
I think I can make this change in the script itself, so once I figure out what schema errors I had for BlogML 2.0, I'll drop that fix in there too.
Karthik,
Can you please tell me what you had to do to "massage" the data? I'd like to be able to get my exporter tool working properly... Thanks!
-Robert
dlature,
I made a simple change to the converter to adjust the execution time to 3 minutes. You can download the updated file here. Lemme know if you have any other problems.
interscape: dlature, I made a simple change to the converter to adjust the execution time to 3 minutes. You can download the updated file here. Lemme know if you have any other problems. -Robert
thanks for your attention to this. However, now I get the following errors when exporting:
<b>Fatal error</b>: Maximum execution time of 60 seconds exceeded in <b>D:\myaccount\wp\wp-includes\formatting.php</b> on line <b>1058</b><br />
<br />
<b>Fatal error</b>: Maximum execution time of 60 seconds exceeded in <b>D:\myaccount\wp\wp-includes\wp-db.php</b> on line <b>82</b><br />
I had a feeling that was gonna happen. Simply changing it in my script was not enough. You have to do one of two things:
HTH