ProBlogger: Transfer Your Blog From WordPress.com to WordPress.org Part 2

Transfer Your Blog From WordPress.com to WordPress.org Part 2

Posted: 04 Aug 2012 07:01 AM PDT

This guest post is by Ayelet Weisz of All Colores.

Yesterday, I started the convoluted process of swapping my blog from WordPress.com to WordPress.org. As you may remember, I’d finally got to the point where I was ready to import the files of my blog. Everything seemed to be okay, until….

Big Deal #4: The import keeps getting stuck

You see that white screen? That’s how it stayed.

At first, I was happy. The little circle on my browser was turning. I assumed it would take a lot of time. Even though my blog was obviously smaller (2.9 megabytes) than the maximum allowed file (64 megabytes), I figured it would take time to import eight months worth of blogging with almost 2000 photographs.

So I let it be.

When I returned to my computer, I found out that the import process had got stuck. Remember, my blog crashed for almost 48 hours. I was sure that was the reason of my current technical challenge. After my blog returned to life and I was able to work again, I repeated the process explained above. While my blog hasn’t crashed since (and it was in late February), after a short moment of importing, nothing was circling anymore: the white screen of the import remained white.

Big Deal #5: Challenges with the blog file

I decided to open the file I had exported from WordPress.com. This is what it looked like:

I learned that there were two errors in the file:

Error on line 149 at column 32: Namespace prefix atom on link is not defined.
Error on line 150 at column 29: Namespace prefix atom on link is not defined.

I Googled it and found various discussions on the matter. I looked for ways to fix the file, yet found no help in simple language. I tried exporting the file from WordPress.com and importing to WordPress.org various times, and kept hitting the same error, only in different lines and columns each time.

As I kept searching the web, more and more answers seemed to lead to one solution, but one that sounded too simple—and to be honest, too frustrating—to be true.

The advice said, refresh the page.

I exported the file once more. Imported it once more. And then refreshed it an unbelievable number of times.

Each time, more and more files appeared to be added. Sometimes only a few files were added when I hit Refresh; sometimes there were many at a time.

Either way, the list of files kept growing.

At the end of every file line, it said “already exists”. For example, “Media ‘DSCF1372′ already exists”. Also, I didn’t see all my posts and pages on the list. I was concerned that some aspects of the blog were being imported multiple times and some not at all.

Then I got some good news.

“All Done. Have Fun!” WordPress.Org wrote to me.

Could it all really be done? Could I now actually stop dealing with technicalities and return to writing?

I logged in to my new URL: www.AllColores.com—no “WordPress” between my blog’s name and the dot-com—and I saw my blog! It was an exciting moment.

Until I noticed something was not okay.

Big Deal #6: My photos weren’t included

All was well with the posts and the comments on my blog, but no photos appeared in the posts. Let me remind you, we are talking about almost 2000 photos, which I made sure to include in the export and import processes.

After some digging in my dashboard, it turned out I’d actually done things well. The photos were indeed imported to the new blog … most of them just weren’t “attached” to any blog post.

The solution? Take a deep breath!

On the left-hand sidebar of your dashboard you will find the word “media”. Click on it. You will reach your media library, where all your photos are listed. I had 1856 media files, all of which were photos, and 1847 of them were unattached. That means that only nine photos were attached.

As you will see in the above photo, in each line beside the media file, you will find a column named “author”. Next to it, there will be a column called “attached to”. If the photo is unattached, an Attach button will be available. Click on that button to attach the picture to the post.

An image will pop up, asking you to search for a post or a page. You can type the beginning of a post title, or choose from a list offered by WordPress by clicking on the right post, then click on Select.

If you, too, have many media files and don’t feel like spending hours “attaching” them to countless posts, you can Google for plugins that might do it for you. From the various message board discussions I read, these actually had helped several people. I tried a couple of options, but they did nothing for me. It was back to manual work.

How do you remember which media file belongs in which post?

That’s where not deleting your WordPress.com blog comes in handy. Keep one window open on your WordPress.org dashboard, and log back in to your WordPress.com dashboard on another. Go to your media library. In your WordPres.com dashboard, files are attached to posts. Follow what it says there as you attach photos on your WordPress.org dashboard.

And, as it turns out, there’s a way to hurry up the process after all.

On any given page, mark all the photos related to a single post and only then click Attach on one of the photos. You will select a post the same way, yet when you click Select, up to twenty photos will be attached at the same time.

Once I was done attaching, I verified that all photos were transferred and attached well.

The end result

Here is a part of my post “More Photos from Bariloche”, which I published while in Argentina in September 2011 to let everyone back home know I’d been doing well and enjoying the snow.

Here is part of that post as it appeared on my new WordPress.org blog in late February 2012:

At last, I could breathe a sigh of true relief. I would have preferred to start with WordPress.org, yet accomplishing this triumph gave me a new boost of energy as I returned to do what I love most: writing.

Have you encountered any other technical challenges while transferring your blog from WordPress.com to WordPress.org? Share your tips and tricks with us in the comments.

Ayelet Weisz is an enthusiastic writer and translator from Israel. She celebrates the everyday and extraordinaire joys of life through travel on her travel blog, All Colores. Follow her adventures onTwitter and sign up to her RSS Feed.

Originally at: Blog Tips at ProBlogger

Transfer Your Blog From WordPress.com to WordPress.org Part 2

ProBlogger: Transfer Your Blog From WordPress.com to WordPress.org Part 1

Transfer Your Blog From WordPress.com to WordPress.org Part 1

Posted: 03 Aug 2012 07:00 AM PDT

This guest post is by Ayelet Weisz of All Colores.

It was finally happening: I was about to embark on the trip of my dreams—and I wanted to write all about it.

I decided that a travel blog, shared initially with family and friends, would be a great experiment to see if I felt comfortable with the format of blogging that I’d wanted to try for quite some time. I did some research and found out that WordPress was a highly recommended platform. I read about the differences between WordPress.com and WordPress.org, yet I wasn’t up for all the technical mumbo-jumbo that I thought comes with launching a site on WordPress.org, even if it allowed me to monetize the blog.

I opted for WordPress.com, thinking I could always transfer later if I decided that was the path for me.

Transferring from WordPress.com to WordPress.org looks easy at first

I read blog posts about it, I read explanations about it on the WordPress website, I watched videos on YouTube. And they all said roughly the same thing: all you have to do is follow these very simple steps, and then your blog is exported from WordPress.com and imported to WordPress.org.

What’s the big deal?

The basic process is supposed to go something like this:

Log in to your WordPress.com dashboard.
Choose “Tools” on your left-hand sidebar.
Under “Tools”, choose “Export”.

There, choose the material you’d like to export. You can choose to export only your posts, for example, and create brand-new pages at your blog’s new home. Or you could choose to transfer the pages, yet start fresh on the posts front. You can also choose to export all the content at once—posts, pages, media files and comments.

Since I wanted to transfer everything in my blog to its new location, I chose All Content and clicked on Download Export File.

The file was downloaded pretty quickly. The file—an XML file type—appeared at the bottom of my screen.

My blog’s name is All Colores and the URL I had at WordPress.com was http://allcolores.wordpress.com . That’s why you see it in the image. When the download ended, I clicked on that box to open the file, which contained lots and lots of lines of code. Who knows how to read that?

Later, since I wanted to import this file to my WordPress.org blog, I needed to know where this file was saved. You’ll see soon that I needed to select it from my computer and upload it. But I didn’t know where that code was saved! It looked as weird to me as writing from right to left will probably look to you. What’s a blogger to do?

The solution is simple—at least in this case—so savor it: click on that arrow you see and choose to view the file in a folder. A folder will open up with a list of files, and the file you need will be marked—like magic! This is what you will see at the bottom of your screen:

(Note: You might not see Hebrew on your computer—unless you have an Israeli computer like I do…)

You can make a note for yourself or memorize the location where this file is saved. I decided to copy it to my desktop, where I don't have many wandering files and it would be easy for me to pick up during the import process.

Important: Do not delete your site from WordPress.com, at least not yet. You might need it later in the import process.

Big Deal #1: Get a domain and server, and install WordPress.org

You’ve exported the file and you know where it’s saved—congratulations! Now … where do you move it to?

Getting a domain is the easy part. That’s the www.YourSite.com URL. Just Google around for best domain sellers and you’ll find plenty of recommendations. I got mine at NameCheap, as I got a personal recommendation for that store, and it included some free protection with its regular sales price.

Next, Google for recommendations on a web host where you can host your site. If you plan on writing lots of posts and including many media files, it is best to find a host with unlimited space. It won’t necessarily cost you more. Another aspect to consider is that some hosts will allow you to use a large or unlimited number of domains. This is important if you dream of launching a network of blogs. Hosts will sometimes offer a one-click installation of WordPress, which will make your life a bit easier, yet I suggested finding YouTube videos that will guide you until that one click. For me, Hostgator has been the perfect fit these past few months, and I am also satisfied with its customer service.

Big Deal #2: The blog crashes after you’ve finished installing

Note that it’s best to do this process a few days before you actually plan to start working on your blog. While your site will usually go live right away, sometimes it can take up to 72 hours for all the systems of cyberspace to cooperate and recognize your blog. If your blog does crash in the meantime, you will not even have access to write posts.

For me, it took almost 48 hours. Those 48 hours plus all the technical challenges that followed added up to days. Remember, I had no idea what I was doing and therefore researched almost every move as I went along. Those days were days I cleared to write content for my blog before a busy month started, and instead, I found myself dealing with technical mumbo-jumbo. So register and install in advance!

This whole ordeal of domain, server, and installation processes scared me immensely back in July, when I launched my blog. Little did I know that you can find great how-to videos on YouTube. Just doing it would have you done with these challenges in almost no time—rather than taking days off your writing time. If you’re reading this and haven’t launched your blog yet, stop right now. Go get yourself a domain and a host. Trust me, the worst in this post is yet to come.

Once that’s installed, you’re ready to begin importing your blog

You can now access your dashboard from http://yourdomain.com/wp-admin. So access it and log in. Once you do, it’s time to start the importing process!

Follow these steps:

Click on Tools on the left sidebar.
Choose Import.
Your screen will look like the image bellow. Click on “WordPress” at the bottom of this list.

This is what I saw when I clicked on “WordPress”:

My Dashboard was darkened and I was required to install a plugin that would enable the importing of my blog to WordPress.org.

As with any plugin on WordPress.org, after you download it—which usually takes a second—you must activate it before it will work. The screen for activating the plugin will appear right after the download is complete. But if you accidentally closed your browser or clicked on something else, worry not: you can always access your downloaded plugins on the left-hand sidebar of the Dashboard. Each plugin that you activate can later be de-activate and even deleted here.

I decided to follow the advice of WordPress and the YouTube videos I watched: I downloaded the plugin and clicked on Activate Plugin & Run Importer. Within a second, the plugin was activated. That’s right—no installation nightmares! How good is that?

Finally, you get to upload your file (good thing you know where it’s saved). Import it and then start working, right?

Wrong. This is where all the trouble begins!

First, I was concerned my blog might be too large, as it contained almost 2000 photos. WordPress asked me to upload a file with the maximum size of 64MB (64 megabytes). I looked at my saved blog file to see how big it was. The number I got was 2989. That’s way bigger than 64! But wait—this figure had different letters next to it: KB. That would be kilobytes.

What does this mean? I asked Google. It turned out 2989 kilobytes equaled 2.9 megabytes. If you scroll back up, you’ll see this information was given to me when it was time to save the file. Paying attention to details is important. What’s 2.9 megabytes compared to 64 megabytes? I was about to find out.

I uploaded my file…

Big Deal #3: My blog’s file version was outdated

This is the message I received when I tried uploading my file: “This WXR file (version 1.2) may not be supported by this version of the importer. Please consider updating”.

Well, I did consider it. However, first, I couldn’t figure out what a WXR file was. I thought it might be the file I just uploaded—that seemed to make sense, yet that file was an XML file. Could a file be both XML and WXR?

Second, I couldn’t figure out how to update the file. I searched on my WordPress.com dashboard and on Google and couldn’t find the answer.

WordPress tip: For any challenge you might be experiencing, type it into Google and you’ll find plenty of message board discussions that were started by people with similar challenges. Many of these discussions take place on WordPress forums, which will start showing up many times once you Google your challenge.

I found message board discussions regarding my file version challenge. I just didn’t find solutions. When I did find message board answers that seemed to be offering a solution, the language they used was too technical for me to understand and know how to implement. I didn’t have the background or experience necessary to do it.

Whether it was the “right” thing to do or not, this is what worked for me. I don’t know if this will work for you too. What made most sense to me was that the above-mentioned comment referred to the file I just uploaded. I mean, it wasn’t there before, it appeared the moment the file finished uploading and it mentioned a file! Unable to discover how to update its version, I decided to go along and use it anyway the way it was. After all, if the file “may not be supported”, it may be supported. WordPress did not obligate me to update—it simply recommended it.

For me, this worked. I had a bunch of technical challenges that you’ll read about tomorrow, and they may or may not have resulted from this decision. Nonetheless, the fact is my blog is up and running on its new domain as you read this. Therefore, this is the place to smile: there is hope!

Before you click Submit…

It’s important to notice two elements on this page before continuing to the next screen.

First, you can assign user roles and positions to posts during this import. If you do this, you might need to handle more settings manually later on. Since I am the only author of my blog, I decided to leave this space blank and avoid dealing with settings. If you have more than one writer, you will likely want to explore it further.

Second, you need to choose whether to download attachments. If you leave the box “download and import file attachments” (right above the Submit button) empty, your photos and videos will not be imported to your WordPress.org file. Do yourself a favor, check that box.

Then click Submit.

At last, you can breathe

WordPress is importing your blog file! Yay! Celebration time, right?

Wrong!

That’s right: there were problems with this step too. Don’t worry—I’ll show you what the problem was, and explain how I solved it tomorrow in the second part of this series. In the meantime, if you have any WordPress.com to WordPress.org war stories to share, we’d love to hear them in the comments!

Originally at: Blog Tips at ProBlogger

Transfer Your Blog From WordPress.com to WordPress.org Part 1

Pages

USAHA BERSAMA

Ads 468x60px