WordPress.org

1. wilkes888
   Member
   Posted 9 months ago #
   

   I'm having trouble transferring a blog from a WordPress.com account to a fresh installation on Hostgator.

   STEP 1. I used TOOLS | EXPORT from my WordPress.com Dashboard which generates the *.wxr file.

   STEP 2.I used the TOOLS | IMPORT from my WordPress.org installation ti import the *.wxr file.

   However, when I tried this the import hangs. There is NO ERROR MESSAGE about memory (like a lot of other posters have stated). It just hangs.

   When I try to install the same file again it may get a little bit further (i.e. a few more posts and imported according to the dialogue box which appears).

   If there something specific that I have to do with a setting in Hostgator. I want to double check before I start messing around with stuff I don't understand.

   [ Please do not bump, that's not permitted here. ]

2. songdogtech
   Moderator-Grizzly Bear Trapper
   Posted 9 months ago #
   

   How many megs is the .wxr file?

   You may need to raise php's memory at Hostgator in php.ini. And see WordPress WXR File Splitter (RSS XML)

3. wilkes888
   Member
   Posted 9 months ago #
   

   Thanks, I'll try that...

   FYI - The *.WXR file was 4.5 Meg. From what I've seen that isn't considered a large file. My host is Hostgator. Their helpdesk state that this isn't a big file for WordPress *.WXR uploads. Also they said that is it was a size issue "it would just error out" rather than hang.

   Although we didn't get any error messages we tried the instructions here.

   http://codex.wordpress.org/FAQ_Working_with_WordPress#How_do_I_Import_a_WordPress_WXR_file_when_it_says_it_is_too_large_to_import.3F

   The support followed the instructions and made the following changes.

   • php.ini (e.g. memory_limit = 64M ;)
   • .htaccess (e.g. php_value memory_limit 64M)
   • wp-config.php (e.g. define('WP_MEMORY_LIMIT', '64MB')
   • php.ini (e.g. max_execution_time = 600 ;)
   • php.ini (e.g. upload_max_filesize = 64M ; and post_max_size = 64M ;)
   • .htaccess (e.g. php_value upload_max_filesize 64M and php_value post_max_size = 64M)

   I tried the upload again and it just imports a few more entries but just hangs again.

   NOTE TO ADMIN: Apologies for bumping, (I was unaware of the 'no-bump-rule') but with no-one answering my question on the forum in 2 weeks and no response from other channels I didn't see much choice. I couldn't find any more help on the web... I've spent hours on the searching for a solution, including the forum archives, but bar manually splitting the XML file, (which I'm nervous of as I'm not versed in XML) nothing has worked.

   I have also tried @Wordpress.org and @WordpressDotCom on twitter... no-one replied.

   Right now I have paid for site hosting for over a month now, I am unable to migrate from WordPress.com. Hostgator support told me that they "do not officially support" WordPress and told me to go to this forum.

   If there any other resources please let me know and I will search there too.

4. wilkes888
   Member
   Posted 9 months ago #
   

   UPDATE:

   Big thanks Songdogtech, using the WXR file splitter I managed to split my current (6-7 Meg) WXR file into 7 individual files and eventually uploaded all the files in the last 4 hours.

   FYI - Of the 7 file parts generated, 5 were uploaded successfully on the first attempt. Parts 2 and 3 had to be uploaded multiple times as they just froze.

   It's not an experience I want to do again and I'm now very nervous of recommending that anyone start on WordPress.com as I've now spent days on the migration process. Also, I purchased (and now deleted) the site direct from WordPress.com but none of the shortlinks from the WordPress.com site permalinks work (they all produce a 404 error.) The site link structure seems to have been replaced by numbers.

5. songdogtech
   Moderator-Grizzly Bear Trapper
   Posted 9 months ago #
   

   Hostgator support told me that they "do not officially support" WordPress...

   Exactly. WordPress is not difficult - at all - for a web host to support. Hostgator is a known problematic host. See Recommended WordPress Web Hosting

   They made too many changes to php.ini and .htaccess. All that was needed is the memory bump in wp-config.php and the timeout bumps in php.ini. The changes in .htaccess are redundant.

   A 4.5 meg XXR file is fair size and may be timing out because of Hostgator's limits beyond the shared hosting plan you have.

   It's not an experience I want to do again and I'm now very nervous of recommending that anyone start on WordPress.com as I've now spent days on the migration process.

   You need to understand the difference between the web host and the software such as WordPress.

   The site link structure seems to have been replaced by numbers....

   Those are called permalinks; reset them in Dashboard>>Settings>>Permalinks to the settings you used at .com. Using Permalinks « WordPress Codex

6. wilkes888
   Member
   Posted 9 months ago #
   

   Thanks again songdogtech, really appreciate your help.

   Those are called permalinks; reset them in Dashboard>>Settings>>Permalinks to the settings you used at .com. Using Permalinks « WordPress Codex

   I have just changed the permalink settings. I was unaware that there were multiple settings. I will test and revert.

   Hostgator is a known problematic host. See Recommended WordPress Web Hosting

   I actually did my research and chose Hostgator because it was a 'recommended host' on the 'Wordpress.com' forum!

   WORDPRESS.COM: Recommended WordPress.org Web Hosting
   

   You need to understand the difference between the web host and the software such as WordPress.

   I can understand if it looks like I'm attacking WordPress as a whole. But as someone new to WordPress, I have no way of telling whether the migration issues were due to WordPress.com... or HostGator. From where I stand each party seems to be blaming the other so you can imagine how frustrating this is! Apart from you, Songdogtech, I've found myself left adrift with very little information.

   Note, I was an IT programmer (albeit about 10 years ago... VB6.0 etc). If I am having trouble I can imagine how difficult it must be for someone who is a tech luddite!

   Technical issues aside, the statement is on 'the process' regardless of who is to blame. Right now I wouldn't recommend that anyone start on WordPress.com and migrate to WordPress.org as I've spent so much time trying to figure out what's on (or going wrong).

   HINT: A migration guide would be useful ;)

7. wilkes888
   Member
   Posted 9 months ago #
   

   Hi Songdogtech, I've tested the permalinks and they definitely work when I change the domain.

   So these two links are equivalent

   OLD BLOG:
   https://wilkes888.wordpress.com/2012/07/30/photo-album-sushisamba-opening-weekend-54-pictures/

   NEW BLOG:
   http://wilkes888.com/2012/07/30/photo-album-sushisamba-opening-weekend-54-pictures/

   However, will the autoredirect from WordPress.com also take into account the change from secure https: to http:?

   I notice that if I try to make a secure connection to the new site I get an error message. I don't need a secure connection for my readers.

Reply

You must log in to post.