- 07/02/11 15:54:09 (3 years ago)
- 1 edited
r403760 r403761 50 50 = What is the status of this plugin ? = 51 51 52 This plugin is not far from being feature-complete. I think I’m reaching the end of the active development of this plugin. I don’t see the need to add new features. 53 54 I also feel this way because I succeeded in moving to WordPress most of the content of my old e107 sites. I now only need to import some stuff to definitively get rid of e107 from my life. After finishing these imports, I'll declare the plugin no longer active. This mean I will no longer update it, but will still integrate code other developers are willing to contribute. 55 56 Before that happen, I will of course release one or two revisions of this plugin. But expect bug fixes and tiny enhancements, not big new features. 57 58 = Why the import process fail, or do not end well ? = 52 This plugin is **not in activate development**. 53 54 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. 55 56 = How can I know the import process finished well ? = 57 58 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. 59 60 = Why the import process failed, or did not end well ? = 59 61 60 62 While importing content from e107, you may encounter one of the following error: … … 63 65 * *MySQL has gone away* 64 66 * *PHP Fatal error: Maximum execution time exceeded* 67 65 68 66 69 These means that the script has failed one way or another. 67 70 68 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. 71 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. 69 72 70 73 The issue and [solutions are detailed in WordPress FAQ](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), please read this article before complaining to me. 74 75 76 77 71 78 72 79 = Can I import content step by step ? =
Note: See TracChangeset for help on using the changeset viewer.