WordPress Importer

Beschreibung

Der WordPress Importer kann folgende Inhalte aus einer WordPress-Export-Datei importieren:

  • Beiträge, Seiten und andere individuelle Beitragstypen
  • Kommentare und zugehörige Metadaten
  • Benutzerdefinierte Felder und Beitrags-Meta
  • Categories, tags and terms from custom taxonomies and term meta
  • Autoren

For further information and instructions please see the documention on Importing Content.

Filter

Der Importer bietet einige Filter, die dir erlauben bestimmte Funktionalitäten komplett zu aktivieren/blockieren:

  • import_allow_create_users: return false if you only want to allow mapping to existing users
  • import_allow_fetch_attachments: return false if you do not wish to allow importing and downloading of attachments
  • import_attachment_size_limit: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited)

There are also a few actions available to hook into:

  • import_start: occurs after the export file has been uploaded and author import settings have been chosen
  • import_end: called after the last output from the importer

Installation

Die schnellste Methode, um den Importer zu installieren ist:

  1. Gehe zu Werkzeuge > Daten importieren im WordPress-Dashboard
  2. Klicke auf den WordPress-Link in der Lister der Importer
  3. Klicke „Jetzt installieren“
  4. Zum Schluss klicke „Importer ausführen“

Falls du es vorziehst Dinge manuell einzurichten, dann folge diesen Anweisungen:

  1. Lade den wordpress-importer-Ordner in das /wp-content/plugins/-Verzeichnis
  2. Aktiviere das Plugin mittels dem ‚Plugins‘-Menü in WordPress
  3. Gehe zu Werkzeuge > Daten importieren, klicke auf WordPress

FAQ

Hilfe! Ich bekomme Fehlermeldungen wegen zu geringem Speicher oder einfach nur eine leere Seite.

Wenn deine Exportdatei sehr gross ist, dann kann es passieren, dass das Importskript am PHP-Speicherlimit deines Hosters scheitert.

A message like „Fatal error: Allowed memory size of 8388608 bytes exhausted“ indicates that the script can’t successfully import your XML file under the current PHP memory limit. If you have access to the php.ini file, you can manually increase the limit; if you do not (your WordPress installation is hosted on a shared server, for instance), you might have to break your exported XML file into several smaller pieces and run the import script one at a time.

For those with shared hosting, the best alternative may be to consult hosting support to determine the safest approach for running the import. A host may be willing to temporarily lift the memory limit and/or run the process directly from their end.

Support Article: Importing Content

Rezensionen

8. September 2020
Плагин не смог перенести даже картинки из стандартных записей в медиатеку нового сайта. Так они и тянутся со старого.
7. September 2020
Browser loading says it all. Not fit for purpose for any serious sites, or sites with more than a few posts or pages. This is a feature that should have been updated long time ago, and barely qualifies as a marketing feature for a small personal blogger. Please update both the exporter and importer to ensure that it is fit for purpose
12. August 2020
Relies on the browser loading while processing. This needs to be rewritten. We are on 2020. Sometimes increasing timeout is not possible! It should NOT load on the browser level but have a loading bar that shows the process on the dashboard itself.
17. Juni 2020
I'm giving this two stars not one, because previous attempts left half the images behind, but I have now at least managed to get all the posts and all the images into the new WordPress site... from the previous WordPress.com site. Horrible though. Had to split a relatively small blog (55 posts) into 11 blocks, get my host to raise the timeout massively, change PHP settings, deactivate everything in sight... and I still had to push through 503 errors, STILL getting timeouts after (e.g.) 10 minutes importing a block of 5 posts, re-running several of the imports... But the worst thing is that it pulled down two copies of each image, creating a second unattached copy of the thumbnail and displaying that rather than the 'real' image, which is then viewable by clicking on the thumbnail. Some thumbnails also then displayed bigger than they are, so fuzzy too. Going to have to go through every post manually, replacing the 'ghost' image with the real one, and then deleting it. Just hoping ALL the images really are there. If it turns out the blog author didn't always link to the media file, I may find some are missing and have to back and look for them. Horrible horrible horrible... and that's going from a WordPress blog to a WordPress blog... what can be so hard?!
25. Mai 2020
Dear Team Plugin is working fine, great work, I would like to suggestion if allow more data file size it will great help for people. This time plugin have (Maximum size: 4 MB) that is not enough. Please increase file size to make more useful Thank you
Lies alle 295 Rezensionen

Mitwirkende & Entwickler

„WordPress Importer“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„WordPress Importer“ wurde in 55 Sprachen übersetzt. Danke an die Übersetzerinnen und Übersetzer für ihre Mitwirkung.

Übersetze „WordPress Importer“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

0.7

  • Update minimum WordPress requirement to 3.7 and ensure compatibility with PHP 7.4.
  • Fix bug that caused not importing term meta.
  • Fix bug that caused slashes to be stripped from imported meta data.
  • Fix bug that prevented import of serialized meta data.
  • Fix file size check after download of remote files with HTTP compression enabled.
  • Improve accessibility of form fields by adding missing labels.
  • Improve imports for remote file URLs without name and/or extension.
  • Add support for wp:base_blog_url field to allow importing multiple files with WP-CLI.
  • Add support for term meta parsing when using the regular expressions or XML parser.
  • Developers: All PHP classes have been moved into their own files.
  • Developers: Allow to change IMPORT_DEBUG via wp-config.php and change default value to the value of WP_DEBUG.

0.6.4

  • Improve PHP7 compatibility.
  • Fix bug that caused slashes to be stripped from imported comments.
  • Fix for various deprecation notices including wp_get_http() and screen_icon().
  • Fix for importing export files with multiline term meta data.

0.6.3

  • Add support for import term metadata.
  • Fix bug that caused slashes to be stripped from imported content.
  • Fix bug that caused characters to be stripped inside of CDATA in some cases.
  • Fix PHP notices.

0.6.2

0.6

  • Support for WXR 1.2 and multiple CDATA sections
  • Post aren’t duplicates if their post_type’s are different

0.5.2

  • Double check that the uploaded export file exists before processing it. This prevents incorrect error messages when
    an export file is uploaded to a server with bad permissions and WordPress 3.3 or 3.3.1 is being used.

0.5

  • Import comment meta (requires export from WordPress 3.2)
  • Minor bugfixes and enhancements

0.4

  • Map comment user_id where possible
  • Import attachments from wp:attachment_url
  • Upload attachments to correct directory
  • Remap resized image URLs correctly

0.3

  • Use an XML Parser if possible
  • Proper import support for nav menus
  • … and much more, see Trac ticket #15197

0.1

  • Erstveröffentlichung