e107 import plugin for WordPress.
This plugin is not in activate development.
As I succeeded in moving to WordPress all my old e107 sites, I have no longer interest of maintaining this plugin. But I'll still integrate code other developers are willing to contribute.
The only way you can tell is by having the "Finished !" / "Have fun !" message at the end of the import report. If not, it means the import process didn't had enough time to finish or encountered an error.
While importing content from e107, you may encounter one of the following error:
These means that the script has failed one way or another.
Generally, this is due to constraints set by your hosting provider, limiting the execution time of PHP scripts. This issue affect all scripts consuming lots of CPU and memory resources, like all import scripts. The timeout can come from MySQL, Apache or PHP.
The issue and solutions are detailed in WordPress FAQ, please read this article before complaining to me.
Importing big forums takes a lot of time. For example, on my 4-cores 1.5GHz laptop, it takes more than an hour to import a forum with 18000+ replies. That's expected as I didn't designed this plugin for performances: it doesn't make sense to spend time working on performance for a plugin you'll only use once in the life of your WordPress site.
Yes, you can. I designed this plugin to let you have the opportunity to import one kind of content at a time. So you should be able to import news first, then re-run the importer process to only import pages, then do it again for forums and so on...
Looks like you have some kind of Unicode transcoding errors. Before running e107 Importer, your e107 site must be fully encoded in UTF-8. If it's not the case, please have a look at the Upgrading database content to UTF-8 article on e107 wiki.
This plugin currently import forums to bbPress. But the brand new 2.x plugin version, not the legacy standalone 1.x version. As for BuddyPress forums, they are planed to be replaced by a future version of the new 2.x bbPress.
So as you can see, there is no need to add specific support of the these forums. You just have to be patient.
This plugin ignore the configuration of the profanity filter from e107. If you want to hide words, it should be done by a dedicated WordPress plug-in. As suggested by Jon Freger, you can use the WebPurify plugin.
This plugin disable all extra HTML rendering hooks added by e107 plugins. Which means Linkwords plugin will be ignored while rendering imported content. So as for profanities (see above), you have to use a third-party WordPress plugin to apply Linkwords-like transformations to your imported content.
That's nice from you to propose a donation but quite frankly, money is not the kind of incentives that will push the development of my plugins. But code, bug reports and testing is the kind of contributions I'm looking for. In fact getting rid of my old e107 instances is the best motivator I have. But by popular demand, here is my donation link anyway...
Bug reports and feature requests must be done via GitHub's ticket system.
That's nice from you to propose to update it. All contributions are welcome ! I'll be happy to apply all your patches in the original code to let anyone benefits your work. Even after I will declare this plugin dead.
Feel free to send me patches and code by mail. Or better yet, use GitHub fork/merge features.
Development of this plugin happen in a dedicated GitHub repository. The latter is the official repository of this plugin. All developments are done there. This repository is the reference repository.
FYI, this plugin is also hosted on WordPress plugins' Subversion, but this repository is just a copy of GitHub's. No original development should be performed in the Subversion repository: changes made there will be ignored and deleted if not mirrored in the GitHub repository.