e107 to WordPress migration : v0.9 plug-in released

Posted on by

9 months after the last one, here is the new version (v0.9) of my e107 to WordPress import plug-in !

Change log:

  • “One-click migration” instead of multiple step process (more user-friendly),
  • Better error management (a must-have for precise bug reports),
  • Replace all links to old content with permalinks (increased SEO),
  • Better database management,
  • Work with latest WordPress v2.3.2 and e107 v0.7.11,
  • Code cleaned up ! ;)

42 thoughts on “e107 to WordPress migration : v0.9 plug-in released”

  1. omg i <3 you!!!!!!!!!!! i just tried your new plugin and i almost cried! you’re new update came literally JUST in time! about an hour ago i downloaded the “old” version, and it wouldn’t work. then i checked back and reloaded your page and found you had just posted this one which worked beatutifully! i’m testing it out on another stie right now, and i am ecstatic. you are brilliant. however, i do have one question… the basis of my site revolves around film reviews… all of which are located in the e107_pcontent section of the database. is there anyway you could find a way to import them as well? i have about 1500 reviews, and to do them by hand would drive me insane.

    omg… if you can do it, i would forever be grateful. you need to put up a paypal donation button or something– you rock!!!!! :)

  2. Haha ! Happy to help ! :)

    I don’t know what e107_pcontent is… Ah ! I see: it comes with the “Content Management” plug-in. Let me have 1 or 2 days to try some experimentations…

  3. omg i totally love you!!!! i want to like have your babies and stuff!!!! LOL okay, maybe not that far– but i will make sure to name my first born after you or something! middle name at least! ;-)

  4. dash: I think it’s better to let your website open for now. The plugin is still in beta. You should use my plugin only in a sandbox. And when you think the plugin is good enough for you, and only at this moment, do the migration to WordPress.

    I also need to see how a big site with so much content look like. Especially to decide what to to with the content (like use news or pages, etc…).

    The best thing you can do to help me work on your issue is to provide me a full copy of your e107 database. I know, it’s very sensitive as it contain lots of personnal informations. But I need it to test and fix my plugin. If this can comfort you, Andrius already gave me its database in 2006 and he didn’t complain about any leak.

  7. Hi,

    I just downloaded an installed your import script to my server, but when I call the import-page in wordpress (2.3.3, by the way), it keeps raising this error:

    Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 14592 bytes) in /home/www/web0/html/wordpress/wp-admin/import/e107.php on line 808

    I already edited my php.ini to an allowed memsize of 16M, with no effect. Do you have an idea?

    Thanks,

    Jo

  8. erm… well… I, hehe… edited the wrong php.ini, and now… so… nevermind ;)

    But, just as a formal question, how much memory does the script allocate, anyway, that it hits the 8M-Wall when running it on a fresh WordPress 2.3.3?

  9. But, just as a formal question, how much memory does the script allocate, anyway, that it hits the 8M-Wall when running it on a fresh WordPress 2.3.3?

    I’m not surprised at all, as I didn’t designed my script with performance in mind. In fact I deliberatly ignore performances issues to let my brain focus on data integrity.

    And as a migration is performed only once in the life of your website, it don’t plan to work on performances.

  10. Getting this error on running the script :

    Fatal error: Call to a member function show_errors() on a non-object in /home/roman365/public_html/community/wp-admin/import/e107.php on line 1308

    Cant seem to find a way around it.

    Its 2.3.2 wp installation and 7.11 e107, tried the solutions from earlier versions and tried putting all the e107 and wp tables in the same table, always the same error.

    Any suggestions? Thanks.

  17. PLEASEEEEEEEEEEEEE UPGRADE ITTTTTTTTTTTTT this is so awsome if it will work.. please do your best and soonest

  18. for me it’s writing:

    Fatal error: Call to a member function show_errors() on a non-object in my website url/e107.php on line 1308

    im using e107 0.7.15 and this thing shows on wp 2.7.1

  20. Sorry for my bad english. This comment is translated with google :-D

    Hello Kev,
    you can tell me where should I add the files in the zip? I tried to copy the folder and files to (/wp_plugins) but do not see anything! A help thanks

    The simple steps to be carried out ..

  21. Well,seems like i’m stuck on E107, this plugin doesn’t work with newer versions.

  24. Kevin!

    Tried it, but wp gave me the next message:

    The plugin has no valid “header”

    Did yoy know that???

    Kinds regards

    Hrr

  25. kevin, please update the plugin for Wodpress 3.0 (post, user and comment) and Buddypress (Forum Post), please, please, please !!!
    greating from France.

  26. Hi Kev,

    I’ve tried to use your plugin but got some issues when importing from e107 to wordpress

    Fatal error: Maximum execution time of 60 seconds exceeded in /sitehome/wp-includes/plugin.php on line 302

    Do you have any idea?

    Thanks in advance!

  27. Pingback: How I Swapped e107 News for WordPress

  29. Just done an update using old versions of WordPress(2.3.2) and e107 (0.7.11). Not pretty, but it worked.

    Finding the old WordPress was easy as have tag archives (http://wordpress.org/download/release-archive/) but e107 only release an upgrade package. You can find e107′s old packages in their SVN (http://e107.svn.sourceforge.net/viewvc/e107/tags/e107_v07_11_release/), though you’ll only really need this if you want to verify your e107 install.

    You will probably get a load of php deprecation errors with the old WordPresses, so you’ll probably have to skip past them, but don’t worry too much.

    Once you’ve got yourself migrated it’s just about upgrading your Worpress install. You may find some of them unusable as a system, but if you work up through the versions then you only need to fire off wp-admin/upgrade.php

  30. Got this to work with WordPress 3.0.1 — even though WordPress now has importers as plugins rather than the old way with its own folder in admin. That was nearly a hiccup, as I didn’t want to roll-back to WP2.9.x or earlier.

    I backed up both databases before importing.

    I then created an “import” folder within the wp-admin folder, dropped in the latest e107 converter files there.

    Then I clicked on the Import link on the WP3.0.1 dashboard, and e107 was an option, then followed the instructions. Other than a few minor warnings (on 4 images), it imported 37 pages and 120 news posts all okay.

    Haven’t been through the imported pages and posts to check them, but the import worked all okay — WP3.0.1 and e107 0.7.11.

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Notify me of followup comments via e-mail. You can also subscribe without commenting.