Well, this is a real issue since if all the drafts got published they would get broadcast to the rss readers. So my workaround will be to “schedule” the blogger draft posts for some distant future date in blogspot before importing to WP. This plugin preserves that scheduled status but not the draft status. Then after the import, I will edit each scheduled post in WP and changed them back to draft.
Ron,
to answer your question, yes the syntax on 720 is correct, the vertical bar is a logical OR.
The problem is that the function isDraft was always returning a false. This in turn was due to an incorrect schema used for parsing that bit of the XML passed by blogger.
So in summary, the fix is…
Open the file “blogger-importer-blogitem.php” and change the line
from
define('SIMPLEPIE_NAMESPACE_ATOMPUB', 'http://www.w3.org/2007/app');
to
define('SIMPLEPIE_NAMESPACE_ATOMPUB', 'http://purl.org/atom/app#');
N.B. the # is important so make sure you copy the whole string.
I’ve created a ticket for this http://core.trac.wordpress.org/ticket/21023
Fixed in trunk for version 0.6. Development version of the code can be found here:
http://wordpress.org/extend/plugins/blogger-importer/developers/
Great, that took care of it: my test shows that Published, Scheduled AND Draft status all come across intact … thanks!
But about that single vertical bar…this reference show it as a bitwise inclusive OR operator where the result is an integer with bits set if either of the two operands have the corresponding bit set.
http://php.net/manual/en/language.operators.bitwise.php
The desired result (true or false) may actually work in this case, however, I think that line 720 should have the double vertical bar to match the logical “OR” intended. I’m not a PHP guru by a long shot since I cut my programmer teeth on Pascal/Delphi which is a strongly typed language, so the looseness of C , javascript, and PHP kinda creeps me out. 8-/
Yes, you are correct, that should be a double || not a single. It will work with bitwise OR but it should be changed so it’s more logical to read.
I cannot find this line of code in the current version of the plug in. Other notes say this problem has been fixed, but it is publishing my drafts after I import as of 2/17/2013. Suggestions?
