bloggerimporter - Project Hosting on Google Code

Earlier this year Nov 25, 2009 BloggerImporter (One-sentence summary of this page.) Wiki page edited by takatsugu.shigeta - Revision r17 Edited wiki page through web user interface. Revision r17 Edited wiki page through web user interface. Nov 25, 2009 Top (One-sentence summary of this page.) Wiki page edited by takatsugu.shigeta - Revision r16 Edited wiki page through web user interface. Revision r16 Edited wiki page through web user interface. May 13, 2009 issue 11 (entry_basename set to 'index' on all entries) reported by crywalt - What steps will reproduce the problem? 1. Import Blogger/Google blog using BloggerImporter. What is the expected output? What do you see instead? In the MySQL table each entry is imported with entry_basename set to 'index'. It should be set to a unique name to allow individual entry files if MT is set to create them. What version of the product are you using? On what operating system? Movable Type Pro version 4.25 with: Community Pack 1.62, Professional Pack 1.3, BloggerImporter 0.3 on Solaris 8 Please provide any additional information below. After importing my Blogger blog, there were no individual HTML files for each entry. MT only created index.html files for each month. Turns out this was because each entry's entry_basename was set to 'index'. I fiddled up some SQL to create a new basename based on the entry_title and rebuilt the blog and got the individual files I was looking for. What steps will reproduce the problem? 1. Import Blogger/Google blog using BloggerImporter. What is the expected output? What do you see instead? In the MySQL table each entry is imported with entry_basename set to 'index'. It should be set to a unique name to allow individual entry files if MT is set to create them. What version of the product are you using? On what operating system? Movable Type Pro version 4.25 with: Community Pack 1.62, Professional Pack 1.3, BloggerImporter 0.3 on Solaris 8 Please provide any additional information below. After importing my Blogger blog, there were no individual HTML files for each entry. MT only created index.html files for each month. Turns out this was because each entry's entry_basename was set to 'index'. I fiddled up some SQL to create a new basename based on the entry_title and rebuilt the blog and got the individual files I was looking for. May 13, 2009 issue 10 (Comments Cannot Be Enabled Through Interface) reported by crywalt - What steps will reproduce the problem? 1. Import Blogger/Google blog using BloggerImporter where Blogger is set with comments disabled. What is the expected output? What do you see instead? In the MySQL table mt_entry, all rows have column entry_allow_comments set to NULL. What version of the product are you using? On what operating system? Movable Type Pro version 4.25 with: Community Pack 1.62, Professional Pack 1.3, BloggerImporter 0.3 on Solaris 8 Please provide any additional information below. After importing my Blogger blog, I couldn't find the comments on the blog. They'd been imported, and were there in the MT interface, but they weren't visible on the blog and there was no form for adding new comments. It turned out, checking the database, all the entries had been imported with entry_allow_comments set to NULL, meaning even existing comments wouldn't appear. I could've gone into each individual entry and set the Accept Comments flag for all of them one at a time. Instead I updated the MySQL directly, changing entry_allow_comments to 1 to allow comments to appear. BloggerImporter should determine each individual entry's comments setting instead of taking the sitewide setting. Maybe. It may not be possible. What steps will reproduce the problem? 1. Import Blogger/Google blog using BloggerImporter where Blogger is set with comments disabled. What is the expected output? What do you see instead? In the MySQL table mt_entry, all rows have column entry_allow_comments set to NULL. What version of the product are you using? On what operating system? Movable Type Pro version 4.25 with: Community Pack 1.62, Professional Pack 1.3, BloggerImporter 0.3 on Solaris 8 Please provide any additional information below. After importing my Blogger blog, I couldn't find the comments on the blog. They'd been imported, and were there in the MT interface, but they weren't visible on the blog and there was no form for adding new comments. It turned out, checking the database, all the entries had been imported with entry_allow_comments set to NULL, meaning even existing comments wouldn't appear. I could've gone into each individual entry and set the Accept Comments flag for all of them one at a time. Instead I updated the MySQL directly, changing entry_allow_comments to 1 to allow comments to appear. BloggerImporter should determine each individual entry's comments setting instead of taking the sitewide setting. Maybe. It may not be possible. May 12, 2009 issue 1 (Importing entries fails) commented on by crywalt - I just spent a couple of minutes tracking down what's causing this error on my system and the trouble seems to be the local server (the one running MT) not having SSL enabled for Perl. BloggerImporter is trying to make an https connection to Google and returning a 501 error because libwww-perl can't make secure connections without the SSL modules installed (Crypt::SSLeay or IO::Socket::SSL). BloggerImporter doesn't return a proper error for 501, so it just returns a generic "An error occurred . Please check your import file." Of course there's no import file because you're importing directly from Blogger. If all this is gobbledygook to you, the main thing is your ISP needs to install the Crypt::SSLeay Perl module. I just spent a couple of minutes tracking down what's causing this error on my system and the trouble seems to be the local server (the one running MT) not having SSL enabled for Perl. BloggerImporter is trying to make an https connection to Google and returning a 501 error because libwww-perl can't make secure connections without the SSL modules installed (Crypt::SSLeay or IO::Socket::SSL). BloggerImporter doesn't return a proper error for 501, so it just returns a generic "An error occurred . Please check your import file." Of course there's no import file because you're importing directly from Blogger. If all this is gobbledygook to you, the main thing is your ISP needs to install the Crypt::SSLeay Perl module. Mar 14, 2009 issue 1 (Importing entries fails) commented on by j_goo...@hoblitt.com - I've encountered the same issue with 0.3 and version 4.24-en. The error is the same if I try to use a blogger exported .xml file or not. I've encountered the same issue with 0.3 and version 4.24-en. The error is the same if I try to use a blogger exported .xml file or not. Jan 17, 2009 issue 1 (Importing entries fails) commented on by gerharzm - I'm experiencing the same problem running MT 4.21. I have one blog on Blogger with 50 posts. Where can we find this "import file" that the error message asks us to check? I'm experiencing the same problem running MT 4.21. I have one blog on Blogger with 50 posts. Where can we find this "import file" that the error message asks us to check? Jan 08, 2009 issue 9 (Urls are not carried over) commented on by webiest - Thanks a lot for fixing this and issue #8 so fast. Thanks a lot for fixing this and issue #8 so fast. Jan 08, 2009 ReleaseNotes0_3 Wiki page edited by takatsugu.shigeta Jan 08, 2009 ReleaseNotes0_3 Wiki page added by takatsugu.shigeta Jan 08, 2009 BloggerImporter-0.3.tar.gz (BloggerImporter-0.3.tar.gz) file uploaded by takatsugu.shigeta Jan 08, 2009 BoggerImporter-0.3.zip (BoggerImporter-0.3.zip) file uploaded by takatsugu.shigeta Jan 08, 2009 r13 ( * ver 0.3 ) committed by takatsugu.shigeta - * ver 0.3 * ver 0.3 Jan 08, 2009 issue 9 (Urls are not carried over) Status changed by takatsugu.shigeta - ok, I implemented this at Revision 12. Status: Done ok, I implemented this at Revision 12. Status: Done Jan 08, 2009 r12 ( * issue 9 * carrying over basename ) committed by takatsugu.shigeta - * issue 9 * carrying over basename * issue 9 * carrying over basename Jan 08, 2009 issue 9 (Urls are not carried over) Status changed by takatsugu.shigeta - Thanks for your idea. I didn't think carrying over basename. I will implement soon. Thanks! Status: Started Thanks for your idea. I didn't think carrying over basename. I will implement soon. Thanks! Status: Started Jan 08, 2009 issue 7 (An error occurred on saving assets) Status changed by takatsugu.shigeta - I fixed this at Revision 11. Status: Done I fixed this at Revision 11. Status: Done Jan 08, 2009 r11 ( * issue 7 * if path is undef, don't add the asset. ) committed by takatsugu.shigeta - * issue 7 * if path is undef, don't add the asset. * issue 7 * if path is undef, don't add the asset. Jan 08, 2009 issue 8 (Multiple authors are not carried over.) Status changed by takatsugu.shigeta - Thanks for your cooperation. I fixed Revision 10. Status: Done Thanks for your cooperation. I fixed Revision 10. Status: Done Jan 08, 2009 r10 ( * issue 8 * create authors if a blog has multiple users. ) committed by takatsugu.shigeta - * issue 8 * create authors if a blog has multiple users. * issue 8 * create authors if a blog has multiple users. Jan 08, 2009 issue 8 (Multiple authors are not carried over.) Status changed by takatsugu.shigeta - Status: Started Status: Started Jan 07, 2009 issue 9 (Urls are not carried over) reported by webiest - What steps will reproduce the problem? 1. Run an import. What is the expected output? What do you see instead? The urls / Basename of the blog post should match the blogger url. They end up being longer than the blogger post. What version of the product are you using? On what operating system? Latest version as of this date. Windows XP running the import. Please provide any additional information below. What steps will reproduce the problem? 1. Run an import. What is the expected output? What do you see instead? The urls / Basename of the blog post should match the blogger url. They end up being longer than the blogger post. What version of the product are you using? On what operating system? Latest version as of this date. Windows XP running the import. Please provide any additional information below. Jan 07, 2009 issue 8 (Multiple authors are not carried over.) reported by webiest - What steps will reproduce the problem? 1. Run an import What is the expected output? What do you see instead? Authors should get carried over and created if they do not yet exist What version of the product are you using? On what operating system? Current versions as of this date. Windows XP running the import. Please provide any additional information below. It only seems to import one author. What steps will reproduce the problem? 1. Run an import What is the expected output? What do you see instead? Authors should get carried over and created if they do not yet exist What version of the product are you using? On what operating system? Current versions as of this date. Windows XP running the import. Please provide any additional information below. It only seems to import one author. Older Dec 23, 2008 issue 7 (An error occurred on saving assets) reported by takatsugu.shigeta - I received following report. I will fix soon. Sorry for your inconvenience. > Saving asset ('')...ok (ID 228) > Error: fileparse(): need a valid pathname at > /path/to/cgi/mt/plugins/BloggerImporter/lib/BloggerImporter/Import.pm line 126 I received following report. I will fix soon. Sorry for your inconvenience. > Saving asset ('')...ok (ID 228) > Error: fileparse(): need a valid pathname at > /path/to/cgi/mt/plugins/BloggerImporter/lib/BloggerImporter/Import.pm line 126 Oct 02, 2008 issue 5 (Import Fails with specific error message under MT4.21) Status changed by takatsugu.shigeta - The cause of this problem was occurred by Blogger API. But now fixed. http://code.google.com/p/gdata-issues/issues/detail?id=798 If you have any chances, please try BloggerImporter0.2? Thanks! Status: Fixed The cause of this problem was occurred by Blogger API. But now fixed. http://code.google.com/p/gdata-issues/issues/detail?id=798 If you have any chances, please try BloggerImporter0.2? Thanks! Status: Fixed Oct 02, 2008 issue 4 (Import Error) Status changed by takatsugu.shigeta - The cause of this problem was occurred by Blogger API. But now fixed. http://code.google.com/p/gdata-issues/issues/detail?id=798 If you have any chances, please try BloggerImporter0.2? Thanks! Status: Fixed The cause of this problem was occurred by Blogger API. But now fixed. http://code.google.com/p/gdata-issues/issues/detail?id=798 If you have any chances, please try BloggerImporter0.2? Thanks! Status: Fixed Oct 02, 2008 issue 6 (Can't import comments) Status changed by takatsugu.shigeta - fixed. http://code.google.com/p/bloggerimporter/source/detail?r=9 Status: Verified fixed. http://code.google.com/p/bloggerimporter/source/detail?r=9 Status: Verified Oct 02, 2008 r9 ( * fixed issue:6 ) committed by takatsugu.shigeta - * fixed issue:6 * fixed issue:6 Oct 02, 2008 issue 6 (Can't import comments) reported by takatsugu.shigeta - GData Blogger API reponses following data in comment feeds. <entry>... <link rel='alternate' type='text/html' href='http://comewalk.blogspot.com/2007/08/test-1.html?showComment=1187254800000#c2599434779075318544' title=''/> </entry> BloggerImporter uses above href as entry's permalink by using following regex. $href =~ s/(#.?$)//g; But probably Blogger API changes to add a parameter of showComment. Then BloggerImporter failed importing comments. BloggerImporter should solve like this. $href =~ s/(\?.?$)//g; GData Blogger API reponses following data in comment feeds. <entry>... <link rel='alternate' type='text/html' href='http://comewalk.blogspot.com/2007/08/test-1.html?showComment=1187254800000#c2599434779075318544' title=''/> </entry> BloggerImporter uses above href as entry's permalink by using following regex. $href =~ s/(#.?$)//g; But probably Blogger API changes to add a parameter of showComment. Then BloggerImporter failed importing comments. BloggerImporter should solve like this. $href =~ s/(\?.?$)//g; Sep 29, 2008 issue 5 (Import Fails with specific error message under MT4.21) reported by adam.tinworth - What steps will reproduce the problem? Standard import. What is the expected output? What do you see instead? This output is produced: Importing entries into blog Importing entries as user 'Adam' Error: :1: parser error : Start tag expected, '<' not found Invalid repeating query parameteterstart-index ^ at /home/adders/public_html/cgi-bin/mt/plugins/BloggerImporter/lib/BloggerImporter/Import.pm line 328 What version of the product are you using? On what operating system? Blogger importer 0.1, Movable Type 4.1 & 4.2 Please provide any additional information below. What steps will reproduce the problem? Standard import. What is the expected output? What do you see instead? This output is produced: Importing entries into blog Importing entries as user 'Adam' Error: :1: parser error : Start tag expected, '<' not found Invalid repeating query parameteterstart-index ^ at /home/adders/public_html/cgi-bin/mt/plugins/BloggerImporter/lib/BloggerImporter/Import.pm line 328 What version of the product are you using? On what operating system? Blogger importer 0.1, Movable Type 4.1 & 4.2 Please provide any additional information below. Sep 25, 2008 issue 4 (Import Error) reported by i...@attractcustomers.com - What steps will reproduce the problem? 1. Import / Importing from Blogger 2. gmail address / password entered 3. Entered Blogger URL 4. Entered Upload path ( /blog) What is the expected output? What do you see instead? It seemed to be working just fine, got through what I think was all posts (about 47 of them) then gave following error message: Error: :1: parser error : Start tag expected, '<' not found Invalid repeating query parameteterstart-index ^ at /home/gccom/public_html/blog/plugins/BloggerImporter/lib/BloggerImporter /Import.pm line 328 What version of the product are you using? On what operating system? 0.2? Unix/Apache Please provide any additional information below. What steps will reproduce the problem? 1. Import / Importing from Blogger 2. gmail address / password entered 3. Entered Blogger URL 4. Entered Upload path ( /blog) What is the expected output? What do you see instead? It seemed to be working just fine, got through what I think was all posts (about 47 of them) then gave following error message: Error: :1: parser error : Start tag expected, '<' not found Invalid repeating query parameteterstart-index ^ at /home/gccom/public_html/blog/plugins/BloggerImporter/lib/BloggerImporter /Import.pm line 328 What version of the product are you using? On what operating system? 0.2? Unix/Apache Please provide any additional information below. Aug 15, 2008 issue 3 (Publishing error after Import) commented on by saumilalpa - Hey i downloaded the plugin and imported posts from blogger but was facing publishing error so i did it 3 times so in the end i have 3 of each. After that, i wanted to delete the duplicate posts but after deleting i could not publish thanks to MT errors. Now that i can, the posts are still not disappearing from the blog. I can still see 3 of each. What do i do?? Hey i downloaded the plugin and imported posts from blogger but was facing publishing error so i did it 3 times so in the end i have 3 of each. After that, i wanted to delete the duplicate posts but after deleting i could not publish thanks to MT errors. Now that i can, the posts are still not disappearing from the blog. I can still see 3 of each. What do i do?? Aug 11, 2008 issue 3 (Publishing error after Import) commented on by saumilalpa - It did import, but i cant publish. Because of the server error i was getting, i ended up importing it thrice. Today, after deleting, when i am trying to publish, same error after "publishing entry archive...." It did import, but i cant publish. Because of the server error i was getting, i ended up importing it thrice. Today, after deleting, when i am trying to publish, same error after "publishing entry archive...." Aug 11, 2008 issue 3 (Publishing error after Import) commented on by takatsugu.shigeta - Have you finished importing your entries? You can see at dashboard or list entries on Movable Type. I guess this error causes publishing, not importing. Your server's spec may be low or your server may be busy. Have you finished importing your entries? You can see at dashboard or list entries on Movable Type. I guess this error causes publishing, not importing. Your server's spec may be low or your server may be busy. Aug 11, 2008 issue 3 (Publishing error after Import) reported by saumilalpa - What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Instead of complete publishing, it shows an error after "Publishing Entry archives..." The error says "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@clublogan.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.8b mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at clublogan.com Port 80" What version of the product are you using? On what operating system? Please provide any additional information below. What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead? Instead of complete publishing, it shows an error after "Publishing Entry archives..." The error says "Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@clublogan.com and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.8b mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at clublogan.com Port 80" What version of the product are you using? On what operating system? Please provide any additional information below.

issue 10 (Comments Cannot Be Enabled Through Interface) reported by crywalt - What steps will reproduce the problem? 1. Import Blogger/Google blog using BloggerImporter where Blogger is set with comments disabled. What is the expected output? What do you see instead? In the MySQL table mt_entry, all rows have column entry_allow_comments set to NULL. What version of the product are you using? On what operating system? Movable Type Pro version 4.25 with: Community Pack 1.62, Professional Pack 1.3, BloggerImporter 0.3 on Solaris 8 Please provide any additional information below. After importing my Blogger blog, I couldn't find the comments on the blog. They'd been imported, and were there in the MT interface, but they weren't visible on the blog and there was no form for adding new comments. It turned out, checking the database, all the entries had been imported with entry_allow_comments set to NULL, meaning even existing comments wouldn't appear. I could've gone into each individual entry and set the Accept Comments flag for all of them one at a time. Instead I updated the MySQL directly, changing entry_allow_comments to 1 to allow comments to appear. BloggerImporter should determine each individual entry's comments setting instead of taking the sitewide setting. Maybe. It may not be possible.

What steps will reproduce the problem? 1. Import Blogger/Google blog using BloggerImporter where Blogger is set with comments disabled. What is the expected output? What do you see instead? In the MySQL table mt_entry, all rows have column entry_allow_comments set to NULL. What version of the product are you using? On what operating system? Movable Type Pro version 4.25 with: Community Pack 1.62, Professional Pack 1.3, BloggerImporter 0.3 on Solaris 8 Please provide any additional information below. After importing my Blogger blog, I couldn't find the comments on the blog. They'd been imported, and were there in the MT interface, but they weren't visible on the blog and there was no form for adding new comments. It turned out, checking the database, all the entries had been imported with entry_allow_comments set to NULL, meaning even existing comments wouldn't appear. I could've gone into each individual entry and set the Accept Comments flag for all of them one at a time. Instead I updated the MySQL directly, changing entry_allow_comments to 1 to allow comments to appear. BloggerImporter should determine each individual entry's comments setting instead of taking the sitewide setting. Maybe. It may not be possible.

Earlier this year

Older