by Frédéric GILLES
4.9 (32 reviews)
FG SPIP to WordPress
A plugin to migrate categories, articles, news, and images from SPIP to WordPress
Tested up to WP 6.8 (Current: 6.9)
v3.35.1
Current Version v3.35.1
Updated 9 months ago
Last Update on 28 Mar, 2025
Synced 11 hours ago
Last Synced on
Rank
#15,966
+3 this week
Active Installs
100+
-18%
KW Avg Position
1
—
No change
Downloads
28.1K
+1 today
Support Resolved
0%
—
No change
Rating
98%
Review 4.9 out of 5
4.9
(32 reviews)
Next Milestone 200
100+
200+
2,613
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 72 more installs to reach 200+
Rank Changes
Current
#15,966
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
4.9
32 reviews
Overall
98%
5
30
(94%)
4
1
(3%)
3
1
(3%)
2
0
(0%)
1
0
(0%)
Tracked Keywords
Showing 1 of 1| Keyword | Position | Change | Type | Updated |
|---|---|---|---|---|
| spip | 1 | — | Tag | 12 hours ago |
Unlock Keyword Analytics
Track keyword rankings, search positions, and discover new ranking opportunities with a Pro subscription.
- Full keyword position tracking
- Historical ranking data
- Competitor keyword analysis
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 3.35.1
- Last Updated
- Mar 28, 2025
- Requires WP
- 4.5+
- Tested Up To
- 6.8
- PHP Version
- 5.6 or higher
- Author
- Frédéric GILLES
Support & Rating
- Rating
- ★ ★ ★ ★ ★ 4.9
- Reviews
- 32
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
WP Adminify – White Label WordPress, Admin Menu Editor, Login Customizer
7K+ installs
#2,738
Master Addons For Elementor - White Label, Free Widgets, Hover Effects, Conditions, & Animations
40K+ installs
#930
Query Monitor - The developer tools panel for WordPress
200K+ installs
#255
Header and Footer Scripts
200K+ installs
#258
Performance Lab
200K+ installs
#267
Frequently Asked Questions
Common questions about FG SPIP to WordPress
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"
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
Same as above
The media are not imported
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"
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"
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'
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
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"
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
Same as above
The media are not imported
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"
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"
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'
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
No, it only reads the SPIP database.
I get this error: Erreur !: SQLSTATE[HY000] [1193] Unknown system variable 'NAMES'
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"
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
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.
Xampp puts the htdocs in the applications folder which is write protected. You need to move the htdocs to a writeable folder.
I get this error: Erreur !: SQLSTATE[HY000] [1193] Unknown system variable 'NAMES'
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"
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
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.
Xampp puts the htdocs in the applications folder which is write protected. You need to move the htdocs to a writeable folder.
No
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
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).
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
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).