I get the message: “[fg-spip-to-wp] Couldn’t connect to the SPIP database. Please check your parameters. And be sure the WordPress server can access the SPIP database. SQLSTATE[28000] [1045] Access denied for user ‘xxx’@’localhost’ (using password: YES)”
Answer:
- First verify your login and password to your SPIP database.
- If SPIP and WordPress are not installed on the same host, you can do this:
- export the SPIP database to a SQL file (with phpMyAdmin for example)
- import this SQL file on the same database as WordPress
- run the migration by using WordPress database credentials (host, user, password, database) instead of the SPIP ones in the plugin settings.
The migration stops and I get the message: “Fatal error: Allowed memory size of XXXXXX bytes exhausted” or I get the message: “Internal server error”
Answer:
- First, deactivate all the WordPress plugins except the ones used for the migration
- You can run the migration again. It will continue where it stopped.
- You can add:
define('WP_MEMORY_LIMIT', '512M');
in your wp-config.php file to increase the memory allowed by WordPress - You can also increase the memory limit in php.ini if you have write access to this file (ie: memory_limit = 1G).
I get a blank screen and the import seems to be stopped
The media are not imported
Answer:
- Check the URL field that you filled in the plugin settings. It must be your SPIP home page URL and must start with http://
The media are not imported and I get the error message: “Warning: copy() [function.copy]: URL file-access is disabled in the server configuration”
Answer:
- The PHP directive “Allow URL fopen” must be turned on in php.ini to copy the medias. If your remote host doesn’t allow this directive, you will have to do the migration on localhost.
I get the message: “Fatal error: Class ‘PDO’ not found”
Answer:
- PDO and PDO_MySQL libraries are needed. You must enable them in php.ini on the WordPress host.
Or on Ubuntu:
sudo php5enmod pdo
sudo service apache2 reload
I get this error: PHP Fatal error: Undefined class constant ‘MYSQL_ATTR_INIT_COMMAND’
Answer:
- You have to enable PDO_MySQL in php.ini on the WordPress host. That means uncomment the line extension=pdo_mysql.so in php.ini
Does the migration process modify the SPIP site it migrates from?
Answer:
- No, it only reads the SPIP database.
I get this error: Erreur !: SQLSTATE[HY000] [1193] Unknown system variable ‘NAMES’
Answer:
- It comes from MySQL 4.0. It will work if you move your database to MySQL 5.0 before running the migration.
I get this error “Parse error: syntax error, unexpected T_PAAMAYIM_NEKUDOTAYIM”
Answer:
- You must use at least PHP 5.3 on your WordPress site.
I get this error: SQLSTATE[HY000] [2054] The server requested authentication method unknown to the client
Answer:
- It is a compatibility issue with your version of MySQL.
You can read this post to fix it: http://forumsarchive.laravel.io/viewtopic.php?id=8667
None image get transferred into the WordPress uploads folder. I’m using Xampp on Windows.
Answer:
- Xampp puts the htdocs in the applications folder which is write protected. You need to move the htdocs to a writeable folder.
Do I need to keep the plugin activated after the migration?
Is there a log file to show the information from the import?
Answer:
- Yes. First you must put these lines in wp-config.php:
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
And the messages will be logged to wp-content/debug.log.
The plugin imports data with wrong encoded characters
Answer:
- This is usually due to a wrong encoding in the original database. You must re-encode your SPIP database before running the import. The procedure is described on: http://contrib.spip.net/Convertir-un-site-SPIP-3-en-utf-8-avec-le-plugin (in French).
Don’t hesitate to let a comment on the forum or to report bugs if you found some.
评价
目前还没有评价