16 thoughts on “WordPress to e107 v0.6: Better Content Rendering and Extended News support”

1. I fail to import anything at all… i have copied my e107 database into the wordpressdatabase.

   Now when i run your import script all i see is errors like:

   WordPress database error: [Table '14_psygarden_e.wp_options' doesn't exist]
   

   I never nowhere specify the _e database, but instead i wanted it to read/write to the 14_psygarden_wordpress database.

   Somehow it seems to reed the db name from the actual database and from then on continue to read and write to it. I doubt that it’s supposed to do this.

   in the end, i can’t import a single thing.

   Let me know if i’m doing somemthing wrong!

2. I was able to get rid of all the errors by placing a copy of my wordpress tables in the e107 database, so it could insert its data there. i’ll have to move the resulting tables from the e107 to the wordpress database afterwords

   So this problem only occurs when your wordpress and e107 database are not the same.

3. my next error occured when trying to import comments:

   Importing e107 comments as WordPress comments...
   
   Warning: Unknown(../wp-admin/import/e107-includes/date_class.php): failed to open stream: No such file or directory in /var/www/virtual/psygarden.be/htdocs/wordpress/wp-admin/import/e107-includes/bbcode_handler.php(190) : eval()'d code on line 1
   
   Warning: (null)(): Failed opening '../wp-admin/import/e107-includes/date_class.php' for inclusion (include_path='.:/usr/share/php:/usr/share/pear') in /var/www/virtual/psygarden.be/htdocs/wordpress/wp-admin/import/e107-includes/bbcode_handler.php(190) : eval()'d code on line 1
   
   Fatal error: Undefined class name 'convert' in /var/www/virtual/psygarden.be/htdocs/wordpress/wp-admin/import/e107-includes/bbcode_handler.php(190) : eval()'d code on line 2
   

4. Hi Rik, thanks for your bug report.

   For your first problem: you are right. I didn’t work on the importer for 2 month but if I remember the code, if think I’ve never taken care of that case. I will check this the next time I’ll work on the importer.

   For your 2nd problem: as you can see in the error message, e107-includes folder is missing. This folder contain importer third-party code. You will find this folder in the original wordpress-e107-importer-0.6.tar.gz archive.

5. This worked ALMOST flawlessly for me. I had to reset EVERY password on the system but thats not a big deal for a small site like mine (7 registered users, hah)…I received no errors while importing. The imported e107 passwords for my users just don’t work. This script saved me HOURS of manual imports…something I had to do when I switched to e107.

6. Thanks Travis for your report. It’s probably written anywhere in the plugin but yes, all passwords are automaticcaly resetted when user are imported. This is normal because password are encrypted in the e107 database and I can’t uncrypt them !

   However, there is probably a way to transform the encrypted version from e107 to wordpress if both use a simple MD5 hashing algorithm. But I’m not sure of this and I need to investigate further.

7. Oh, BTW Travis, in my plugin it is written that “All users’ password will be resetted”. Look at line 604 of the e107.php file from the 0.6 version of my script.

8. Rik: I’ve just tried to import an e107 website to a wordpress blog. Each was relying on a separate database and everything was working as expected ! I still don’t understand what was the origin of your problem…

9. no way to import my e107 posts.
   the tables are in the same db but
   these are the errors: (the directory includes is there!)

   Importing e107 news as WordPress posts...
   
   Warning: tohtml(): Unable to access ../wp-admin/import/e107-includes/profanity_filter.php in c:\hosting\teatroinverso.it\wwwroot\public\wp\wp-admin\import\e107-includes\e_parse_class.php on line 413
   
   Warning: tohtml(../wp-admin/import/e107-includes/profanity_filter.php): failed to open stream: No such file or directory in c:\hosting\teatroinverso.it\wwwroot\public\wp\wp-admin\import\e107-includes\e_parse_class.php on line 413
   
   Fatal error: tohtml(): Failed opening required '../wp-admin/import/e107-includes/profanity_filter.php' (include_path='.;c:\php4\pear') in c:\hosting\teatroinverso.it\wwwroot\public\wp\wp-admin\import\e107-includes\e_parse_class.php on line 413
   

10. Pingback: e107 to WordPress v0.7: support Categories and Private Pages at Coolkevmen

11. Hi ale.

    You have the following error:

    Unable to access ../wp-admin/import/e107-includes/profanity_filter.php
    

    because you’ve turned on the profanity filter on your e107 website. Unfortunately I didn’t use the profanity filter feature so I never encounter your problem.

    You can fix this by turning off the profanity filter in your e107 preferences.

12. You can fix this by turning off the profanity filter in your e107 preferences.

    FYI, this is now done automatically since version 0.8 of my script.

    I’ve choose to turn off profanity filter, because if profanities must be hidden in content, it should be done by a dedicated WordPress plug-in, not by a direct alteration of original content.

13. You might want to try the WebPurify WP Plugin…. (if you want to use a one, that is)

14. great great post

15. Please please please update this script to the latest e107 (0.7.24) version… This is so needed by so many especially when e107 is being attacked like crazy lately and people wants to convert websites to WP.
    This is great work that should be expanded on, perhaps ad it as a permanent plugin on WP. You will make a lot of people happy by doing so. I am even willing to donate for something like this.

16. @duce: See my other comment here.