bloggerbackup Forum Rss Feed

New Post: Back up doesn't start...

joao_pimentel — Sat, 15 Dec 2012 23:12:54 GMT

and don't forget to move on with image backups...

Really nice app you guys have created

New Post: Back up doesn't start...

gduncan411 — Sat, 15 Dec 2012 23:09:56 GMT

Glad you figured it out. I love problems that solve themselves... :)

New Post: Back up doesn't start...

joao_pimentel — Sat, 15 Dec 2012 21:14:23 GMT

Bad configuration on BACKUP FILE NAMING

It's working now :)

Thanks guys, very good application

PS: Include images upload on the next versions...

New Post: Back up doesn't start...

joao_pimentel — Sat, 15 Dec 2012 21:03:55 GMT

I put everything ok, the user ID and credentials, but the buckup doesn't start

It says:
"Saving pots "post name"" but nothing happens!!

Can you kindly help me?

Thank you

João

LOG:
____________________________-

2012-12-15 20:51:01,297 [1] ERROR BloggerBackup.MainForm - Error in AddItems,selectedOptions.PostNameOptions
System.NullReferenceException: A referência de objecto não foi definida como uma instância de um objecto.
   em BloggerBackup.PathBuilderForm.ShowDialog(IWin32Window owner, AllSaveNameOptions baseSaveOptions, SelectedSaveNameOptions selectedOptions, String blogTitle, String backupPath, ILog log)
2012-12-15 20:51:01,299 [1] INFO BloggerBackup.MainForm - Start ShowExample
2012-12-15 20:51:01,349 [1] INFO BloggerBackup.MainForm - End ShowExample
2012-12-15 20:51:03,459 [1] INFO BloggerBackup.MainForm - End ShowDialog
2012-12-15 20:51:03,459 [1] INFO BloggerBackup.MainForm - CustomPathBuilderButton_Click End
2012-12-15 20:51:08,390 [1] INFO BloggerBackup.MainForm - Starting background processing...
2012-12-15 20:51:08,391 [1] INFO BloggerBackup.MainForm - Determining batch size
2012-12-15 20:51:08,391 [1] INFO BloggerBackup.MainForm - Issuing first query...
2012-12-15 20:51:08,976 [1] INFO BloggerBackup.MainForm - Creating backup folder...
2012-12-15 20:51:08,977 [1] INFO BloggerBackup.MainForm - Setting up output file...
2012-12-15 20:51:08,978 [1] INFO BloggerBackup.MainForm - The newest post for this blog is 13-12-2012 15:58:28
2012-12-15 20:51:08,979 [1] INFO BloggerBackup.MainForm - Processing batch of 25 posts
2012-12-15 20:51:08,980 [1] INFO BloggerBackup.MainForm - Saving post Rua pedonal, mais capital!
2012-12-15 20:51:47,691 [1] INFO BloggerBackup.MainForm - Starting background processing...
2012-12-15 20:51:47,693 [1] INFO BloggerBackup.MainForm - Determining batch size
2012-12-15 20:51:47,694 [1] INFO BloggerBackup.MainForm - Issuing first query...
2012-12-15 20:51:48,322 [1] INFO BloggerBackup.MainForm - Creating backup folder...
2012-12-15 20:51:48,323 [1] INFO BloggerBackup.MainForm - Setting up output file...
2012-12-15 20:51:48,324 [1] INFO BloggerBackup.MainForm - The newest post for this blog is 13-12-2012 15:58:28
2012-12-15 20:51:48,325 [1] INFO BloggerBackup.MainForm - Processing batch of 25 posts
2012-12-15 20:51:48,326 [1] INFO BloggerBackup.MainForm - Saving post Rua pedonal, mais capital!
2012-12-15 20:51:55,340 [1] INFO BloggerBackup.MainForm - CustomPathBuilderButton_Click Start
2012-12-15 20:51:55,343 [1] INFO BloggerBackup.MainForm - Before BuildPath.ShowDialog
2012-12-15 20:51:55,343 [1] INFO BloggerBackup.MainForm - Start ShowDialog
2012-12-15 20:51:58,558 [1] ERROR BloggerBackup.MainForm - Error in AddItems,selectedOptions.FolderNameOptions
System.NullReferenceException: A referência de objecto não foi definida como uma instância de um objecto.
   em BloggerBackup.PathBuilderForm.ShowDialog(IWin32Window owner, AllSaveNameOptions baseSaveOptions, SelectedSaveNameOptions selectedOptions, String blogTitle, String backupPath, ILog log)
2012-12-15 20:51:59,086 [1] ERROR BloggerBackup.MainForm - Error in AddItems,selectedOptions.PostNameOptions
System.NullReferenceException: A referência de objecto não foi definida como uma instância de um objecto.
   em BloggerBackup.PathBuilderForm.ShowDialog(IWin32Window owner, AllSaveNameOptions baseSaveOptions, SelectedSaveNameOptions selectedOptions, String blogTitle, String backupPath, ILog log)
2012-12-15 20:51:59,086 [1] INFO BloggerBackup.MainForm - Start ShowExample
2012-12-15 20:51:59,088 [1] INFO BloggerBackup.MainForm - End ShowExample
2012-12-15 20:52:09,790 [1] INFO BloggerBackup.MainForm - End ShowDialog
2012-12-15 20:52:09,790 [1] INFO BloggerBackup.MainForm - CustomPathBuilderButton_Click End
2012-12-15 20:52:38,273 [1] INFO BloggerBackup.MainForm - Starting background processing...
2012-12-15 20:52:38,274 [1] INFO BloggerBackup.MainForm - Determining batch size
2012-12-15 20:52:38,275 [1] INFO BloggerBackup.MainForm - Issuing first query...
2012-12-15 20:52:38,884 [1] INFO BloggerBackup.MainForm - Creating backup folder...
2012-12-15 20:52:38,886 [1] INFO BloggerBackup.MainForm - Setting up output file...
2012-12-15 20:52:38,887 [1] INFO BloggerBackup.MainForm - The newest post for this blog is 13-12-2012 15:58:28
2012-12-15 20:52:38,888 [1] INFO BloggerBackup.MainForm - Processing batch of 25 posts
2012-12-15 20:52:38,888 [1] INFO BloggerBackup.MainForm - Saving post Rua pedonal, mais capital!

________________________________________________________________________________

*** 1.0.9.23, 4/2/2008
Fixed bug where a post without a title could not be restored

*** 1.0.9.22, 1/19/2008
Updated to clean up the initial behavior, when creating "new settings" on the first load.
    Now it will not prompt you to save the settings if you haven't made any changes.
    For example, you start the new version and then File/Open your existing BBSettings file.
    This version will not ask you to save your previous settings, which are empty, before opening that file.

Updated to better handle errors during the "Getting next chunk,..." process
    Fixed a bug where the retry wasn't happening.

Added more error logging to the Backing Up Posts process

*** 1.0.9.21, 1/18/2008
Fixed bug with a blog entry not having a "Post" field.

Updated to use a better method of getting the blog URL when using the "Get Feed URL" button.

*** 1.0.9.20, 12/31/2007
Some Posts No Longer Have Title Elements (Blogger Issue)
    Fixed an error that would occur when determing a post file name if there was no "title" element in the post's atom XML.
        If no title is found, "NoTitle-" + Published date is used (NoTitle-20061204102200)

        This used to work fine, but something seems to have changed on the Blogger side of the world.

    When I look at the "NoTitle..." posts from my blog, they DON'T have "official" title's anymore.
    But I have old backups of those posts and they DID have title's... At least then they did then...

    When I go to the raw "self" feed for a post (say href="http://www.blogger.com/feeds/5655811/posts/default/106026670028866448") there's no title there anymore either.

    So the GData.Net library is not broken, Blogger is.

    sigh...

Added an override to override Published dates for restored posts (Work Item #13734)
    Updated dates cannot be overridden...

Fixed bug where the Restore form could be "Ok"'d without entering a password.

When selecting files to restore, ".Comment.XML" are filtered out (since comment restore is not yet supported). (Work Item #12969)
Updated to restore labels/categories when restoring posts. (Work Item #13628)

Changed Comment URL calculation to handle Service.Post feeds

Updated the GData.Net (Google Data API for .NET) library to the latest release version (1.1.2.0)

Moved to VS2008 Development environment

Added a manifest (for Vista... not required, but VS2008 made it easy...)

Added additional error checking and logging to the Custom Path Builder process

Updated to use the Service.Post URL (if available) instead of the ServiceFeed (aka Alternate) (Work Item #11853)
    This was done to avoid/resolve FeedBurner redirection issues.

    ServiceFeed (aka Alternate) feed would be something like http://blogname.blogspot.com/feeds/posts/default (previously used)
    Service.Post feed would be something like http://www.blogger.com/feeds/BlogID/posts/default

    The Service.Post feed can be manually seen via the Blog's header ("view source"), Link element with the rel="service.post" attribute.

Added a "Get Feed URL" button to "Manually add a Blogger blog" on the Blog List form

Changed the "Custom Path Builder" button caption to "Backup File Naming" (Work Item #12690)

Change the title of the "Path Builder" form to "Backup File Naming Options" (Work Item #12690)

Made the default size of the "Backup File Naming Options" form smaller. (Work Item #12690)

Now the last used/selected Blog in the Available Blogs list will be remembered and restored. (Work Item #12689)

Updated to support for private, non-feed publishing blogs.
    This will require the user to log into Blogger though...

Added a Right-Click Edit feature to the Blog List form
    Now you can edit existing blog list items

Added "Log into Blogger when backing up this feed" checkbox to the Blog List form, Manual tab
    With this you can indicate that you want to log into Blogger when backing up the selected Blog

*** 1.0.7.16, 8/10/2007
Double left clicking on the Processing Results list will open the selected file
    If you're backing up in the "One file per post" mode, when you double click on a Post title in the "Processed posts" list the given post will be opened in what ever program is configured to open *.XML files (i.e. Internet Explorer, etc)

The way settings are saved was reworked from the ground up (Work Item #12082)
    Settings are now saved via a "normal" process.
    File/Open, File/New, File/Save, File/Save As menu items have been added.

    You can now save your settings in the location that makes sense to you.
        There is no more hidden, magical, registry or isolated storage being used. It's all in the one BBSettings file.

    This also means you can backup your Settings, use them on different machines, etc.

    Also each blog now has it's own group of settings.
        So for one of your blogs you can choose to backup comments, whereas on another you can choose to NOT backup comments.

    The Blogger Password IS NOT saved in the BBSettings file. Nor is it saved in any other location on the computer.
    The WebProxy Password IS saved in the BBSettings file, but is encrypted using Microsoft's Data Protection API.

The method of selecting blogs has been reworked from the ground up (Work Item #12081)
    You can now manually add Blogger blogs to the list.
    You don't have to login at all to backup your blog.

    NOTE: The Blogger Backup utility uses your Public Feed to backup your posts.
    If your feeds are off, then nothing can be backed up
    If your feeds are set to Summary, then only those Summary feeds will be backed up.

    I am looking into providing support for private feed backup support (but that will require you to log in to backup your blog...)

    Also Restoring Posts of course requires you to log in...

*** 1.0.6.15, 7/29/2007
Updated the GData.Net (Google Data API for .NET) library to the latest release version (1.0.9.9)

Added Log4Net logging
    Logging is on by default and for all levels.
    No sensitive information (i.e. password) is meant to be logged.
        BUT since errors/exceptions are logged, and I'm not in control of all of those, I cannot guarantee that those exceptions will not include sensitive information.

    By default the logs will be created in your Application Data folder and be called ApplicationLog.txt.
        The logs are "rolling", meaning each time you start the program, you get a fresh new log file
        Only the most recent 5 historical logs are saved (for a total of 6 log files, the current log and 5 historical logs)

    A Help/View Logs menu item has been added to open the folder where the logs are...

*** 1.0.5.14, 7/21/2007
Added Restore Post Feature (Work Item #11531)
    Now you can selectively restore previously backed up posts
    This is feature, like the rest of the app, is in beta testing (i.e. once it hits the public, I'm sure people are going to find issues/bugs/etc)

    Only "One Post per File" backups are currently supported.

    PLEASE NOTE: Blogger has a 50 Post Per Day limit.
    Meaning you will only be able to post a maximum of 50 posts a day to a blog. Total. This is a Google/Blogger limitation.
    No errors that I can catch will occur, once you hit the 50 limit the posts will just not appear in the blog.

    To try to help you track the number of posts you've restored on a given day, a Restored Posts count is tracked.

    Also where possible I try to warn you when you've hit the 50 post a day limit...

Added the underscore "_" character as a built-in post naming option (Work Item #11840)

Added the Post's page URL as a Post Naming option (Work Item #11841)
    If the post's complete URL is http://coolthingoftheday.blogspot.com/2007/07/This_is_a_Blog_Post.html

    Then the page URL "This_is_a_Blog_Post" is the value used for this new Post Naming option.

*** 1.0.4.10, 7/14/2007
Added new Path Builder feature
    Now you can create the folder structure and post file names that best suit you.

    It will default to [Backup Folder]\Blog Title\PublishedDate(ISO8601 YYYYMMDDTHHMMSS formatted)"-"PostTitle.XML (pretty much the way it was before).

    But now YOU can tweak that path to best fit your style and needs.

    Want to store each year's posts in a different subfolder?
    Want to store each month's posts in a different subfolder?
    Want to reverse that and store it my month/year?

    Done, done, done.

    Want to change the post file name? Say only using the post title?
    Or Year-Month-PostTitle?
    Or only use the ISO8601 date (YYYYMMDDTHHMMSS - 20070707T081012)?
    Want to use custom static text value?

    Done, done, done, done.

    Want to use Updated dates instead of Published dates?

    Done.

    Want to play around and see how the different options will effect the final names?

    Done.

    Again, the new path build is meant to allow you the all the flexibility you may need or want.

    This is the first time I've built something like this, so please bear with me as I may tweak it in future versions...

Removed "Add blog title to folder" feature
    Built into the new Path Builder functionality

*** 1.0.3.8, 7/8/2007
Fixed bug where backing up wouldn't ever stop if a blog had a multiple of 25 posts (25, 100, 350, etc) (Work Item #11588)

Fixed bug where the "Get only the most recent ### posts" feature was also broken. (Work Item #11593)

Now when the "Backup Posts" button is clicked the Backed Up count (the number at the bottom right) in the status bar is cleared.

*** 1.0.2.7, 7/7/2007
Fixed bug where you couldn't "Stop" in the middle of the "Error looking for comments, retrying.." loop (Work Item #11570)
    Now if Stop is pressed, and the app is in the retrying comments loop, it will now exit/stop processing correctly.

Fixed bug where you couldn't "Stop" in the middle of the ""Error getting next chunk, retrying.." loop
    Now if Stop is pressed, and the app is in the retrying get next chunk loop, it will now exit/stop processing correctly.

Updated the "Add blog title to folder" feature to better remove characters that are invalid for a folder name
    Previously I was just using IO.Path.GetInvalidPathChars as my list of "bad" characters.
    The problem is that that list didn't include the many of the common "bad" characters, like :,*,|, ", etc
    Now I'm using both the IO.Path.GetInvalidPathChars AND IO.Path.GetInvalidFileNameChars to ensure a blog title that's compatible with the file system

Added global unhandled exception handler
    Now if an unhandled exception occurs, a big ugly error dialog will appear with the error message.
    A trace message was also added. I need to add more tracing as well as an easy method for the user to turn it on & view it.

*** 1.0.1.6, 5/19/2007
Removed "Blogger 2.0 (Old Blogger)" as an option

Added "Only new posts since" feature
    Using this to get the posts posted between now and the given date

Changed form/control layout

Added an initial "All Posts since last backup" type of feature
    Now the newest/latest Post's date is saved when backing up.
    The next time that blog is selected; the "Only new posts since" fields will be populated with that date/time.

Fixed a bug in the "Safe Name" function, where it wouldn't work after creating a "0001" named file.
    So after saving a same-named post for the third time, the application would appear to freeze up.
    Stupid location of a Dim was the cause (Note to Self, Dim/initialize an incrementing variable OUTSIDE the loop ... sigh...)

Added more reliable Comment saving.
    Added retries and cleaned up the code a little to try to make comment saving more reliable.

*** 1.0.0.5, 3/17/2007
Added "Maximum Enrties Per File" option
    When backing up post to a single file, this option will let you "batch" them into groups.
    Setting "Maximum Enrties Per File" to 250 when using the "Atom Combinded" format means that the a given combinded XML file will only have 250 posts in and and additional files added as needed.
    For example, if you have 397 posts in your blog, and your max is set to 250, you will get two files. The first with 250 posts and the second with the remainder...

Updated to remember and restore main form size and position

Upgraded/replaced the gdata.dll with the latest release of google.gdata.client.dll(1.0.9.4)

Added error handling to better deal with timeout issues when getting the get batch of posts.

*** 1.0.0.4, 3/15/2007
Updated Blogger root URL, Replacing "Blogger 3.0 (Beta)" with "Blogger 3.0" and "Blogger 2.0" with "Blogger 2.0 (Old Blogger)"

*** 1.0.0.3, 11/26/2006
Updated to support saving of comments from Blogger 3/(Beta) blogs
    Blogger 2 does not support the extraction of comments...
    Comments currently always save a seperate Atom 1.0 files no matter the selected "save posts as(format)" option

Added "Save posts as(format)" option
    This is the begining of support for saving the posts in different formats.

    Atom Single (one file per post)
    Atom Combinded(all posts in one file)
    [Pending] BlogML Combinded(all posts in one file)
    [Pending] HTML Single
    [Pending] HTML Combinded
    [Possible] Open XML/WordML (Office 2007) Single [Require .Net 3 be installed]
    [Possible] Open XML/WordML (Office 2007) Combinded [Require .Net 3 be installed]
    [Possible] PDF Single
    [Possible] PDF Combinded
    [Possible] MHTML
    etc, etc.

    * This feature needs some major rework and needs a provider/plugin model.

Fixed bug where Latest 50 & Latest 100 stopped after only getting the latest 25

Added Version Number to main form's title text
    This was done to make it very easy to see what version is being run.

*** 1.0.0.2, 11/23/2006
Added Tools/Options Menu

Add Options Dialog

Added support for web proxies

Implemented web proxy support in GData

Updated to better handle File Path's & Names that exceed MAX_PATH
    File names are now truncated, if need be.

*** 1.0.0.1, 11/22/2006
Fixed Blogger 3.0 issue.
    Now works with both Blogger 2 and Blogger 3

Added Release History text file and related Help menu item

Added "Append Blog Title to Backup Path" option, defaulted as true/on.
    This will add an additional folder level, named based on the given blog's title.

Updated descriptive label text, changing case, etc.

Updated tab order

Swaped positions of "Get only the most recent:" and "Overwrite existing backups?"

*** 1.0.0.0, 11/21/2006
First public alpha release

New Post: Not able to restore from the back up file

gduncan411 — Mon, 20 Feb 2012 16:31:17 GMT

It isn't taking them all and putting them into a single post, but it is parsing it. One way to keep the file from being to big is to use the All Posts, One File method, but then change the number of posts per file.

In any case, I don't think this utility is really going to help you. Blogger has a limit of posts that can be made a day, 50, so the utility can only restore 50 posts a day. It would take about forever to restore 38,000.

Best bet might be to use Bloggers built-in export feature and then import that into the new blog. That will work around the 50 per day limit

New Post: Not able to restore from the back up file

telugustudio — Mon, 20 Feb 2012 13:33:23 GMT

As i told above, i think when i click restore posts, its trying to take all posts file into a single post...so this time i took back up with "Each post in different file"..and i got a xml file for each post. so this time i tried to restore single post(single xml file) , but this time "Error posting to bloger : Execution of Request failed : http://xxxxxxx.blogspot.com/feeds/posts/default"..so this one also failed to restore.

And one more thing , when i tried add settings in starting, first manually add/edit a bog, there i gave my blog details and then click Get feed URL , nothing came..why??????? so i chose second method "login to blogger to choose ur blogs"

Can u please any body help me to restore my blog , in any method????????????????????????????????????????

New Post: Not able to restore from the back up file

telugustudio — Mon, 20 Feb 2012 12:38:22 GMT

I want to copy my posts to another blog.So i took the backup of my blog with this utility , in single file sized 105 MB (because my blog is having around 38,000 posts). now i want to restore with this xml file to another blog..but iam unable to, whenever i click restore posts and select the file, then its going to NOT RESPONDING . But after some time (5 to 10 mins), its came to normal and one more window opened " Select posts to restore.." , there i can see the required xml file and i fill in my blog user id and password , then i click ok...Next the status bar of the Utility is looks like :

1. first " Loading c:/........./........./............./............./back up.xml "

2 .Next , " Creating post back up"

3. Next "Posting to blogger "

4 .Next error occured , "Error Occured to Blogger : The request was aborted: the request was cancelled "

This is my problem, can you please help me with this..And in the Processed Posts Area, There is "back up"And as of my understanding, its look like its trying to create the whole .xml file in a single post , and so its giving me error...it has to post in seperate posts , right?

New Post: backup not catching comments?

gduncan411 — Mon, 09 Jan 2012 19:41:48 GMT

Also quickly, in looking at your client's site, looks like a number of the older posts don't have comments (at least in spot checking them) so there's no easy 1:1 count for the comments. In walking the code, it looks like we're grabbing the comments where that do exist. Am spot checking more now... :)

New Post: backup not catching comments?

gduncan411 — Mon, 09 Jan 2012 19:30:40 GMT

Cathy, I've emailed you, via the CodePlex Contact User feature, so we can move this discussion offline for a bit. You should have already gotten it, if not, please shoot me an email when you get a chance... gduncan411[at]hotmail[dot]com

Thanks

New Post: backup not catching comments?

CathyT — Mon, 09 Jan 2012 18:56:23 GMT

Ah. Thanks for that. THat explains why this utility (Replace Pioneer) isn't working. I'm going to try to import the combined file (from replace pioneer) into WP.com - they accept / import atom files. Perhaps that will work, then I can download that file and import to self-hosted... yeesh. what a pain!

Oh yes -you can see the feeds at http://pinkdandychatter.com (not mine, a clients')

Your friendly geeks,

Cathy Tibbles

CEO / WordPress Consultant

310-928-DSWP

Visit the Blog

On Mon, Jan 9, 2012 at 10:10 AM, gduncan411 <notifications@codeplex.com> wrote:

From: gduncan411

Yeah, there should be (keyword) one comment.xml file for every post with one or more comments, so if every post had one or more comment then there should be 1440'ish comment files.

Is your blog public with a public feed? Can you give me it's URL?

As for merging them, that would be tough. With code, I'm sure it could be done with code, but with a stand-alone utility, none come to mind.

Even Google's Blogger Export keeps the comments separate (it puts them at the end of the Export in their own <entry> entries). So they are not inline with their original comment, but separate entries that are "linked" to their original posts with the <thr:in-reply-to> elements.

To see this, create a simple test blog, put a few posts and comments on it and then use the Blogger export feature (which I've had timeout/issues with too BTW).

On a related note, doesn't WordPress have a Blogger import feature?

Read the full discussion online.

To add a post to this discussion, reply to this email (bloggerbackup@discussions.codeplex.com)

To start a new discussion for this project, email bloggerbackup@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

New Post: backup not catching comments?

gduncan411 — Mon, 09 Jan 2012 18:10:08 GMT

Yeah, there should be (keyword) one comment.xml file for every post with one or more comments, so if every post had one or more comment then there should be 1440'ish comment files.

Is your blog public with a public feed? Can you give me it's URL?

As for merging them, that would be tough. With code, I'm sure it could be done with code, but with a stand-alone utility, none come to mind.

Even Google's Blogger Export keeps the comments separate (it puts them at the end of the Export in their own <entry> entries). So they are not inline with their original comment, but separate entries that are "linked" to their original posts with the <thr:in-reply-to> elements.

To see this, create a simple test blog, put a few posts and comments on it and then use the Blogger export feature (which I've had timeout/issues with too BTW).

On a related note, doesn't WordPress have a Blogger import feature?

New Post: backup not catching comments?

CathyT — Mon, 09 Jan 2012 17:42:11 GMT

gduncan411 wrote:

One question... when saving the posts, what option did you use? "Atom, one file per post" or "Atom, All posts in single file"?

The comment above applies to "Atom, one file per post". If you used the "All posts in a single file" in doing a test run, it looks like there might be a bug where the *.comment.xml files might be stored in another location, in the "current" folder (the folder the app thinks is the current folder). For example, during the test run I mentioned, the comment files were stored in the sample folder as the app/exe.

If you're not seeing any *.comments.xml files, do a quick drive search and see if you can find time (yeah, I know... lame.. sorry about that).

That issue is fixed in a v1.5 (which is in private beta at this point, which I can add you too if you wish?). The comments are still separate, but at least they are with the bigger/main XML file.

I used "all posts in single file" up to 100 per file. That created 15 files of posts. I found the comments- thank you! But there are only 570 comment files, which I dont understand? If there are 1447 posts, and *nearly* all of them have comments, shouldn't there be approx 1,440 comment files?

can you shed some light?

Also - if I can pick your brain for a sec - do you know of a program where I can 'sew' these files together?

New Post: backup not catching comments?

gduncan411 — Mon, 09 Jan 2012 15:13:56 GMT

One question... when saving the posts, what option did you use? "Atom, one file per post" or "Atom, All posts in single file"?

The comment above applies to "Atom, one file per post". If you used the "All posts in a single file" in doing a test run, it looks like there might be a bug where the *.comment.xml files might be stored in another location, in the "current" folder (the folder the app thinks is the current folder). For example, during the test run I mentioned, the comment files were stored in the sample folder as the app/exe.

If you're not seeing any *.comments.xml files, do a quick drive search and see if you can find time (yeah, I know... lame.. sorry about that).

That issue is fixed in a v1.5 (which is in private beta at this point, which I can add you too if you wish?). The comments are still separate, but at least they are with the bigger/main XML file.

New Post: backup not catching comments?

gduncan411 — Mon, 09 Jan 2012 14:58:33 GMT

The Blogger Backup utility stores the comments as separate XML files... So there should be a XML file for the blog post and then one named *.comments.xml.

So if there's a post named 20120105T024600-Greg.xml, any comments would be in 20120105T024600-Greg.comments.xml

Does that make sense? I know this makes restoring them a pain, but at the time it was the only way I could find to easily save the comments.

New Post: backup not catching comments?

CathyT — Mon, 09 Jan 2012 04:48:00 GMT

Hi there,

I know its been awhile since you released this, but it is working wonderfully to move a large site (blogger refuses to do a download - gets a time out error). I downloaded files of 100 posts & comments each. And used a conversion utility to change to RSS and uploaded to WP. Fine. Except! There's no comments in the atom / xml files when I open to look at them. I'm not sure if I'm supposed to be able to view them or not? Either way, they're not importing. and I checked the log - it says it is checking for comments, then saving them, etc, but there aren't any to be found in the actual xml file. Can you point me in the right direction please?

Thank you!

New Post: From BloggerBackup to Wordpress

gduncan411 — Tue, 13 Jul 2010 21:49:43 GMT

Sorry about the 50 post limit... That's imposed by Google/Blogger and there's nothing I can do about that.

The backups are just XML files, so just about anything can be done to them. Same for converting them to the official export format. I've not done either so really can't help much in that regard.

Faced with the same problem, I'd create an official Blogger Export and the compare that with the single Blogger Backup XML file and see what's different. Then you can tweak that file and go from there

The Blogger Backup XML files are generated by the Google GData component (i.e. it's not something I made up) so there shouldn't be much difference at all.

New Post: From BloggerBackup to Wordpress

TheBeat — Tue, 13 Jul 2010 21:00:53 GMT

Hi, I've downloaded BloggerBackup 1.0.9.23 some time ago and I've used it only to save posts.

2 days ago my blog was removed from Blogger team for Spam (???), but when I try to restore my old posts to another blog, I'm able to restore only 50 posts/day.

Is it possible to use BloggerBackup saved files to create posts directly in a Wordpress blog, with the Import function ?

New Post: Please help.. Backup won't start

gduncan411 — Wed, 06 Jan 2010 17:27:59 GMT

Can you email me (gduncan411 at hotmail com);

a) A screenshot of the application

b) The error logs (Available via the Help menu and then View Logs... )

c) Your BBSettings file (usually saved in youy My Documents folder)

d) What OS you're using

e) A screenshot of the error you mention?

Thanks,
Greg

New Post: Please help.. Backup won't start

Donna13 — Wed, 06 Jan 2010 12:24:30 GMT

I don't know if I have done something wrong but I have just downloaded Blogger Backup and when I tried to back up it is doing nothing.. I am also getting error messages when I try to edit post names. Can someone please help me???

New Post: Blogger Backup utility won't Start

gduncan411 — Mon, 04 Jan 2010 14:25:02 GMT

Awesome! [Well awesome that it wasn't the project ;) ... sorry about the virus...]

Thanks the kind words and for following up (my fingers were beginning to cramp... lol)

Thanks again,
Greg

From: [email removed]
To: [email removed]
Date: Sun, 3 Jan 2010 13:28:42 -0800
Subject: Re: Blogger Backup utility won't Start [bloggerbackup:79497]

From: nenesse

Hey mate, you can finally uncross your fingers !
I fixed my problem.
The reason why the tool wouldn't work is because I was infected with a nasty little bugger called trojan.Win32.TDSS, which infected my atapi.sys.
I Used a rootkit remover from Esage Labs @ http://www.esagelab.com/ to remove it and after that, your beautiful tool would launch again.
Thx again so much for taking the time to help me.
And congratz for this great project you're running. I can tell you it's making the life of many bloggers much easier.
Cheers.
nenesse

Read the full discussion online.
To add a post to this discussion, reply to this email (bloggerbackup@discussions.codeplex.com)
To start a new discussion for this project, email bloggerbackup@discussions.codeplex.com
You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.
Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com