My favorites | Sign in
Project Logo
                
Details: Show all Hide all

Older

  • Jan 12, 2009
    issue 3 (wxr2blogger, line 121, line 104, line 94, line 65) Owner changed by rjwa...@durables.org   -  
    Owner: rjwa...@durables.org
    Owner: rjwa...@durables.org
  • Jan 12, 2009
    wxr2blogger-1.0.2.tar.gz (Release 1.0.2) file uploaded by rjwa...@durables.org   -  
    Labels: Featured
    Labels: Featured
  • Jan 12, 2009
    r8 (Tag for 1.0.2 release. ) committed by rjwa...@durables.org   -   Tag for 1.0.2 release.
    Tag for 1.0.2 release.
  • Nov 18, 2008
    issue 4 (line 198 <thr:in-reply-to href='http://www.blogger.com/feeds...) Status changed by rjwa...@durables.org   -  
    Status: Fixed
    Status: Fixed
  • Nov 18, 2008
    issue 5 (Blogger doesn't allow imports from wxr2blogger any more) Status changed by rjwa...@durables.org   -   Should be fixed now.
    Status: Fixed
    Should be fixed now.
    Status: Fixed
  • Nov 18, 2008
    r7 (Fake out that this file was generated by Blogger... ) committed by rjwa...@durables.org   -   Fake out that this file was generated by Blogger...
    Fake out that this file was generated by Blogger...
  • Nov 17, 2008
    issue 5 (Blogger doesn't allow imports from wxr2blogger any more) commented on by rjwa...@durables.org   -   Cool - thanks for the tip. I've no bandwidth to apply to working on this right now - I might get a chance to try that fix, but joining forces isn't going to happen at the moment. Maybe when the craziness at work and home die down, I'll reconsider... :-)
    Cool - thanks for the tip. I've no bandwidth to apply to working on this right now - I might get a chance to try that fix, but joining forces isn't going to happen at the moment. Maybe when the craziness at work and home die down, I'll reconsider... :-)
  • Nov 17, 2008
    issue 5 (Blogger doesn't allow imports from wxr2blogger any more) commented on by jlueck   -   I believe faking out the Generator element of the top-level feed element will do the trick. Just create a <generator>Blogger</generator> (under the correct namespace, of course) and this should allow your translated blogger export files to work. This is what I'm doing in my project (very similar to yours): http://code.google.com/p/gconverters-appengine/ If you'd like help, please let me know. Or, perhaps we can join forces on this wordpress to Blogger portability problem.
    I believe faking out the Generator element of the top-level feed element will do the trick. Just create a <generator>Blogger</generator> (under the correct namespace, of course) and this should allow your translated blogger export files to work. This is what I'm doing in my project (very similar to yours): http://code.google.com/p/gconverters-appengine/ If you'd like help, please let me know. Or, perhaps we can join forces on this wordpress to Blogger portability problem.
  • Oct 05, 2008
    issue 5 (Blogger doesn't allow imports from wxr2blogger any more) reported by rjwa...@durables.org   -   Blogger seems to have disabled wxr2blogger import functionality. Need to fake out the import functionality more.
    Blogger seems to have disabled wxr2blogger import functionality. Need to fake out the import functionality more.
  • Oct 05, 2008
    issue 3 (wxr2blogger, line 121, line 104, line 94, line 65) changed by rjwa...@durables.org   -   Glad there's a word-around, but I shouldn't be crashing anyway. I'll try make this a bit more robust.
    Status: Accepted
    Labels: OpSys-All
    Glad there's a word-around, but I shouldn't be crashing anyway. I'll try make this a bit more robust.
    Status: Accepted
    Labels: OpSys-All
  • Oct 05, 2008
    issue 4 (line 198 <thr:in-reply-to href='http://www.blogger.com/feeds...) changed by rjwa...@durables.org   -   I think this is harmless, but if you want to check the current trunk, I've removed the blogID.
    Status: Started
    Labels: OpSys-All
    I think this is harmless, but if you want to check the current trunk, I've removed the blogID.
    Status: Started
    Labels: OpSys-All
  • Oct 05, 2008
    r6 (Remove an old BlogID and replace it with something a bit mor...) committed by rjwa...@durables.org   -   Remove an old BlogID and replace it with something a bit more generic.
    Remove an old BlogID and replace it with something a bit more generic.
  • Oct 05, 2008
    issue 1 (ExpatError instead of atom-xml files) commented on by rjwa...@durables.org   -   Looks like someone at WordPress has updated the ticket with a patch. No idea when this will be included in a release, though.
    Looks like someone at WordPress has updated the ticket with a patch. No idea when this will be included in a release, though.
  • Sep 22, 2008
    issue 4 (line 198 <thr:in-reply-to href='http://www.blogger.com/feeds...) reported by xiangningliu   -   I think the numbers "2746484575476953423" should be the blogID.
    I think the numbers "2746484575476953423" should be the blogID.
  • Sep 15, 2008
    issue 3 (wxr2blogger, line 121, line 104, line 94, line 65) commented on by sam.haraldson   -   Upgrading to the latest version of Wordpress, manually removing all the suspect spam comments from the XML and adding the xmlns:excerpt="http://www.example.com/the/excerpt/namespace" code to the top allowed me to successfully execute wxr2blogger.
    Upgrading to the latest version of Wordpress, manually removing all the suspect spam comments from the XML and adding the xmlns:excerpt="http://www.example.com/the/excerpt/namespace" code to the top allowed me to successfully execute wxr2blogger.
  • Sep 15, 2008
    issue 3 (wxr2blogger, line 121, line 104, line 94, line 65) reported by sam.haraldson   -   What steps will reproduce the problem? Executing the script: python wxr2blogger wordpress.xml bloggerID 0000000000000000 Produces the following results: Traceback (most recent call last): File "wxr2blogger", line 121, in <module> ch = parse_channel(i) File "wxr2blogger", line 104, in parse_channel it = parse_item(i) File "wxr2blogger", line 94, in parse_item it['comments'].append(parse_comment(i)) File "wxr2blogger", line 65, in parse_comment com['content'] = i.childNodes[0].data AttributeError: Element instance has no attribute 'data' What is the expected output? What do you see instead? ? What version of the product are you using? On what operating system? 1.0.1 Please provide any additional information below. These results came after I manually removed all the "escape characters" that Wordpress exported with some spam comments. These produced other errors documented elsewhere in another issues thread.
    What steps will reproduce the problem? Executing the script: python wxr2blogger wordpress.xml bloggerID 0000000000000000 Produces the following results: Traceback (most recent call last): File "wxr2blogger", line 121, in <module> ch = parse_channel(i) File "wxr2blogger", line 104, in parse_channel it = parse_item(i) File "wxr2blogger", line 94, in parse_item it['comments'].append(parse_comment(i)) File "wxr2blogger", line 65, in parse_comment com['content'] = i.childNodes[0].data AttributeError: Element instance has no attribute 'data' What is the expected output? What do you see instead? ? What version of the product are you using? On what operating system? 1.0.1 Please provide any additional information below. These results came after I manually removed all the "escape characters" that Wordpress exported with some spam comments. These produced other errors documented elsewhere in another issues thread.
  • Sep 06, 2008
    issue 2 (undefined entity: line 1420) Cc changed by rjwa...@durables.org   -  
    Cc: rjwa...@durables.org
    Cc: rjwa...@durables.org
  • Sep 06, 2008
    issue 2 (undefined entity: line 1420) Owner changed by rjwa...@durables.org   -  
    Owner: rjwa...@durables.org
    Owner: rjwa...@durables.org
  • Sep 06, 2008
    issue 2 (undefined entity: line 1420) changed by rjwa...@durables.org   -   Looks like yet another WordPress output bug. The bogus data this time is undeclared entities.
    Status: Accepted
    Cc: rjwa...@durables.org
    Looks like yet another WordPress output bug. The bogus data this time is undeclared entities.
    Status: Accepted
    Cc: rjwa...@durables.org
  • Sep 05, 2008
    issue 2 (undefined entity: line 1420) reported by sam.haraldson   -   What steps will reproduce the problem? 1. execute the wxr2blogger script 2. 3. What is the expected output? What do you see instead? The desired output would be the creation of a new file. Instead, the following is produced: > File "wxr2blogger", line 114, in <module> > p = parseString(u.encode("utf-8")) > File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/minidom.py", line 1923, in parseString > File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 940, in parseString > File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 223, in parseString > xml.parsers.expat.ExpatError: undefined entity: line 1420, column 38 What version of the product are you using? On what operating system? wxr2blogger 1.0.1, Terminal, Mac OS X 10.5.4 Please provide any additional information below. The README suggests the following work around which returns the same results as the above error: > Add the following in before the last ">": > xmlns:excerpt="http://www.example.com/the/excerpt/namespace" The error is occurring on line 1420 of the file I am trying to process. Here is the content of the file in relation to line 1420 of said file: 1413 <wp:comment_id>114</wp:comment_id> 1414 <wp:comment_author><![CDATA[Gallatin Crest Trail - Gallatin Range]]></wp:comment_author> 1415 <wp:comment_author_email></wp:comment_author_email> 1416 <wp:comment_author_url>http://skiresorts.thesourcesnowboards.com/2008/08/25/gallatin-crest-trail-gallatin-range/</wp:comment_author_url> 1417 <wp:comment_author_IP>74.54.143.50</wp:comment_author_IP> 1418 <wp:comment_date>2008-08-25 16:01:10</wp:comment_date> 1419 <wp:comment_date_gmt>2008-08-25 22:01:10</wp:comment_date_gmt> 1420 <wp:comment_content>[...] La face cach&Atilde;&copy;e d&#8217;un bavarois wrote an interesting post today onHere&#8217;s a quick excerpt [...]</wp:comment_content> 1421 <wp:comment_approved>spam</wp:comment_approved> 1422 <wp:comment_type>pingback</wp:comment_type> 1423 <wp:comment_parent>0</wp:comment_parent> 1424 </wp:comment>
    What steps will reproduce the problem? 1. execute the wxr2blogger script 2. 3. What is the expected output? What do you see instead? The desired output would be the creation of a new file. Instead, the following is produced: > File "wxr2blogger", line 114, in <module> > p = parseString(u.encode("utf-8")) > File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/minidom.py", line 1923, in parseString > File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 940, in parseString > File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 223, in parseString > xml.parsers.expat.ExpatError: undefined entity: line 1420, column 38 What version of the product are you using? On what operating system? wxr2blogger 1.0.1, Terminal, Mac OS X 10.5.4 Please provide any additional information below. The README suggests the following work around which returns the same results as the above error: > Add the following in before the last ">": > xmlns:excerpt="http://www.example.com/the/excerpt/namespace" The error is occurring on line 1420 of the file I am trying to process. Here is the content of the file in relation to line 1420 of said file: 1413 <wp:comment_id>114</wp:comment_id> 1414 <wp:comment_author><![CDATA[Gallatin Crest Trail - Gallatin Range]]></wp:comment_author> 1415 <wp:comment_author_email></wp:comment_author_email> 1416 <wp:comment_author_url>http://skiresorts.thesourcesnowboards.com/2008/08/25/gallatin-crest-trail-gallatin-range/</wp:comment_author_url> 1417 <wp:comment_author_IP>74.54.143.50</wp:comment_author_IP> 1418 <wp:comment_date>2008-08-25 16:01:10</wp:comment_date> 1419 <wp:comment_date_gmt>2008-08-25 22:01:10</wp:comment_date_gmt> 1420 <wp:comment_content>[...] La face cach&Atilde;&copy;e d&#8217;un bavarois wrote an interesting post today onHere&#8217;s a quick excerpt [...]</wp:comment_content> 1421 <wp:comment_approved>spam</wp:comment_approved> 1422 <wp:comment_type>pingback</wp:comment_type> 1423 <wp:comment_parent>0</wp:comment_parent> 1424 </wp:comment>
  • Aug 28, 2008
    r5 (Tag for 1.0.1 release. ) committed by rjwa...@durables.org   -   Tag for 1.0.1 release.
    Tag for 1.0.1 release.
  • Aug 28, 2008
    r4 (Update the README for some known issues and workarounds. Al...) committed by rjwa...@durables.org   -   Update the README for some known issues and workarounds. Also, make the number of posts per Atom file a tunable variable.
    Update the README for some known issues and workarounds. Also, make the number of posts per Atom file a tunable variable.
  • Aug 28, 2008
    issue 1 (ExpatError instead of atom-xml files) Labels changed by rjwa...@durables.org   -  
    Labels: Type-Other Type-Defect
    Labels: Type-Other Type-Defect
  • Aug 28, 2008
    issue 1 (ExpatError instead of atom-xml files) Status changed by rjwa...@durables.org   -   I've filed a ticket with WordPress here: http://trac.wordpress.org/ticket/7624 I will leave this issue open until I hear more about this from WordPress.
    Status: Accepted
    I've filed a ticket with WordPress here: http://trac.wordpress.org/ticket/7624 I will leave this issue open until I hear more about this from WordPress.
    Status: Accepted
  • Aug 28, 2008
    issue 1 (ExpatError instead of atom-xml files) commented on by rjwa...@durables.org   -   Yup - someone else reported that, too. It's actually a malformed XML file output by WordPress. As a workaround, look at the top of the file and you should see something like this (about 19 lines down): <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:wp="http://wordpress.org/export/1.0/" > Add the following in before the last ">": xmlns:excerpt="http://www.example.com/the/excerpt/namespace" so that the it looks like this: <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:wp="http://wordpress.org/export/1.0/" xmlns:excerpt="http://www.example.com/the/excerpt/namespace" > and try again. I'll update the README. There's not much else I can do until WordPress fixes this.
    Yup - someone else reported that, too. It's actually a malformed XML file output by WordPress. As a workaround, look at the top of the file and you should see something like this (about 19 lines down): <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:wp="http://wordpress.org/export/1.0/" > Add the following in before the last ">": xmlns:excerpt="http://www.example.com/the/excerpt/namespace" so that the it looks like this: <rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:wp="http://wordpress.org/export/1.0/" xmlns:excerpt="http://www.example.com/the/excerpt/namespace" > and try again. I'll update the README. There's not much else I can do until WordPress fixes this.
  • Aug 28, 2008
    issue 1 (ExpatError instead of atom-xml files) commented on by m.kalina   -   Voila, the whole item (the line with the ** is line no 1421): <item> <title>Festgestellt</title> <link>http://3th.be/?page_id=903</link> <pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate> <dc:creator><![CDATA[Michael]]></dc:creator> <category><![CDATA[Text]]></category> <category domain="category" nicename="text"><![CDATA[Text]]></category> <guid isPermaLink="false">http://3th.be/?page_id=903</guid> <description></description> <content:encoded><![CDATA[1. Coca-Cola schmeckt nur aus dem Eiskasten wirklich gut. (Eiswürfel nehmen dem Getränk die Süße, dadurch wird es noch besser.)]]></content:encoded> ** <excerpt:encoded><![CDATA[]]></excerpt:encoded> <wp:post_id>903</wp:post_id> <wp:post_date>0000-00-00 00:00:00</wp:post_date> <wp:post_date_gmt>0000-00-00 00:00:00</wp:post_date_gmt> <wp:comment_status>open</wp:comment_status> <wp:ping_status>open</wp:ping_status> <wp:post_name></wp:post_name> <wp:status>draft</wp:status> <wp:post_parent>0</wp:post_parent> <wp:menu_order>0</wp:menu_order> <wp:post_type>page</wp:post_type> <wp:post_password></wp:post_password> <wp:postmeta> <wp:meta_key>_edit_lock</wp:meta_key> <wp:meta_value>1219058119</wp:meta_value> </wp:postmeta> <wp:postmeta> <wp:meta_key>_edit_last</wp:meta_key> <wp:meta_value>2</wp:meta_value> </wp:postmeta> <wp:postmeta> <wp:meta_key>_wp_page_template</wp:meta_key> <wp:meta_value>default</wp:meta_value> </wp:postmeta> </item>
    Voila, the whole item (the line with the ** is line no 1421): <item> <title>Festgestellt</title> <link>http://3th.be/?page_id=903</link> <pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate> <dc:creator><![CDATA[Michael]]></dc:creator> <category><![CDATA[Text]]></category> <category domain="category" nicename="text"><![CDATA[Text]]></category> <guid isPermaLink="false">http://3th.be/?page_id=903</guid> <description></description> <content:encoded><![CDATA[1. Coca-Cola schmeckt nur aus dem Eiskasten wirklich gut. (Eiswürfel nehmen dem Getränk die Süße, dadurch wird es noch besser.)]]></content:encoded> ** <excerpt:encoded><![CDATA[]]></excerpt:encoded> <wp:post_id>903</wp:post_id> <wp:post_date>0000-00-00 00:00:00</wp:post_date> <wp:post_date_gmt>0000-00-00 00:00:00</wp:post_date_gmt> <wp:comment_status>open</wp:comment_status> <wp:ping_status>open</wp:ping_status> <wp:post_name></wp:post_name> <wp:status>draft</wp:status> <wp:post_parent>0</wp:post_parent> <wp:menu_order>0</wp:menu_order> <wp:post_type>page</wp:post_type> <wp:post_password></wp:post_password> <wp:postmeta> <wp:meta_key>_edit_lock</wp:meta_key> <wp:meta_value>1219058119</wp:meta_value> </wp:postmeta> <wp:postmeta> <wp:meta_key>_edit_last</wp:meta_key> <wp:meta_value>2</wp:meta_value> </wp:postmeta> <wp:postmeta> <wp:meta_key>_wp_page_template</wp:meta_key> <wp:meta_value>default</wp:meta_value> </wp:postmeta> </item>
  • Aug 27, 2008
    issue 1 (ExpatError instead of atom-xml files) Owner changed by rjwa...@durables.org   -   This looks like it's choking on your WXR file. Can you send me the contents of line 1421 of the file, plus a few lines in and around that? Maybe we can figure out what's going on.
    Owner: rjwa...@durables.org
    This looks like it's choking on your WXR file. Can you send me the contents of line 1421 of the file, plus a few lines in and around that? Maybe we can figure out what's going on.
    Owner: rjwa...@durables.org
  • Aug 26, 2008
    issue 1 (ExpatError instead of atom-xml files) reported by m.kalina   -   What steps will reproduce the problem? 1. Normal usage as intended. What is the expected output? What do you see instead? I get an error message (I suppose) instead of Atom-formatted files. What version of the product are you using? On what operating system? Newest version on Mac OS X. Please provide any additional information below. This is the output: Traceback (most recent call last): File "/Users/Michael/Downloads/wxr2blogger-1.0/wxr2blogger", line 107, in <module> p = parseString(u.encode("utf-8")) File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/minidom.py", line 1923, in parseString File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 940, in parseString File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 223, in parseString xml.parsers.expat.ExpatError: unbound prefix: line 1421, column 0
    What steps will reproduce the problem? 1. Normal usage as intended. What is the expected output? What do you see instead? I get an error message (I suppose) instead of Atom-formatted files. What version of the product are you using? On what operating system? Newest version on Mac OS X. Please provide any additional information below. This is the output: Traceback (most recent call last): File "/Users/Michael/Downloads/wxr2blogger-1.0/wxr2blogger", line 107, in <module> p = parseString(u.encode("utf-8")) File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/minidom.py", line 1923, in parseString File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 940, in parseString File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/xml/dom/expatbuilder.py", line 223, in parseString xml.parsers.expat.ExpatError: unbound prefix: line 1421, column 0
  • Aug 26, 2008
    r3 (First release. ) committed by rjwa...@durables.org   -   First release.
    First release.
  • Aug 26, 2008
    r2 (Initial check-in. ) committed by rjwa...@durables.org   -   Initial check-in.
    Initial check-in.
  • Aug 26, 2008
    Project wxr2blogger created by rjwa...@durables.org   -   Convert WordPress WXR files into Blogger Atom files
    Convert WordPress WXR files into Blogger Atom files
 
Hosted by Google Code