– Importer: Serendipity

S.t.a.b.l.e tag:

Importer for Serendipity Weblog Software, supporting PostgreSQL and MySQL via PDO. (profile at
WordPress version required:3.0.0
WordPress version tested:3.1.0
Plugin version:0.0
Added to WordPress repository:07-05-2016
Last updated:20-01-2012
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Rating, %:0
Rated by:0
Plugin URI:
Total downloads:929
plugin download
Click to start download

NO VERSION RELEASED!! Don’t know why WP Plugin Directory shows a version even if i haven’t released a TAG or BRANCH to SVN!!

[DE] Das ist ein umfangreicher Importer um alle Daten aus einem Serendipity Weblog nach WordPress zu übertragen. Da meist nicht alle Informationen übernommen werden wenn man aus einem RSS Feed importiert, greift mein Script direkt (nur lesend) auf die Daten der MySQL oder PostgreSQL Datenbank zu. Es ist auch möglich den Import mehrmals laufen zu lassen. Es werden wahlweise nur neue Beiträge übernommen seit dem letzten Start oder wenn gewünscht, bestehende ersetzt.

Das Serendipity Plugin “Tagging of entries” (serendipity_event_freetag) wird unterstützt und die Tags werden mit importiert.


This is the long description. No limit, and you can use Markdown (as well as in the following sections).

For backwards compatibility, if this section is missing, the full length of the short description will be used, and Markdown parsed.

A few notes about the sections above:

  • “Contributors” is a comma separated list of usernames
  • “Tags” is a comma separated list of tags that apply to the plugin
  • “Requires at least” is the lowest version that the plugin will work on
  • “Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on higher versions… this is just the highest one you’ve verified.
  • Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for stable.

    Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that’ll be used for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt
    is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.

    If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where you put the stable version, in order to eliminate any doubt.