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

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 ! ;)

13 Responses to “e107 to Wordpress migration : v0.9 plug-in released”


  1. 1 dash

    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. 2 kev

    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. 3 dash

    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. 4 kev

    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.

  5. 5 dash

    okay, kev– i’m going to email you about this now. thanks so much!

  6. 6 kev

    Dash: thanks, I’ve received it.

  7. 7 Jo

    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. 8 Jo

    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. 9 kev

    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. 10 Duncan

    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.

  11. 11 andreW

    and how about wp 2.3.5 ?

  12. 12 funis

    what about wordpress 2.5? does it work?

  13. 13 Helge

    What about WP 2.6?

Leave a Reply

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