WordPress Importør

Beskrivelse

Importprogrammet for WordPress vil importere følgende innhold fra en eksportfil for WordPress:

  • Innlegg, sider og egendefinerte innholdstyper
  • Comments and comment meta
  • Tilpassede felt og metadata for innhold
  • Categories, tags and terms from custom taxonomies and term meta
  • Forfattere

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

Filtre

Importprogrammet har et par filtre som tillater deg fullstendig å tillate/blokkere visse egenskaper:

  • 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)

Det er også noen få handlinger («actions») å hekte seg på:

  • 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

Installasjon

Den raskeste metoden å installere importøren på er:

  1. Besøk Verktøy-> Import på administrasjonspanelet i WordPress
  2. Klikk på lenken for WordPress i listen over importører
  3. Klikk «Installer nå»
  4. Til slutt klikk «Aktiver utvidelsen & Kjør import»

If you would prefer to do things manually then follow these instructions:

  1. Last opp wordpress-importer-mappen til /wp-content/plugins/-mappen
  2. Aktiver utvidelsen på ‘Utvidelser’-siden i WordPress
  3. Go to the Tools -> Import screen, click on WordPress

FAQ

Help! I’m getting out of memory errors or a blank screen.

If your exported file is very large, the import script may run into your host’s configured memory limit for PHP.

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

Vurderinger

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
30. mars, 2020
Importing a couple dozen posts including attachments: ✓ Importing a couple dozen pages including attachments: ✓ Importing ~100 media files including attachments: ✗ HTTP 503. I've tried disabling leech & hotlinking protection on the source domain. I've tried increasing the PHP memory_limit to 512MB, max_execution_time to 0 (unlimited), max_input_time to -1 (same as max_ececution_time), post_max_size to 128MB, upload_max_filesize to 128MB. Note that the media files I was attempting to import were less than 100MB combined. But I kept getting a HTTP 503. The way I eventually got around it was as follows: start the import of media, including attachments. When it fails, do it again, but this time without attachments. You will get a list showing you which media files were actually imported already and which haven't been imported. Now edit the xml file and remove all entries (delimited by <item>…</item>) that have already been imported. Start the media import again, with the edited xml file and include attachments. If it fails again, repeat the import but without attachments. Note files already imported, remove from xml file, rinse and repeat. Tedious? Perhaps. This plugin's fault? I honestly don't know. My cheap hoster's fault? Entirely possible. My skills not being as good as I think they are? Definitely an option. But was it the quickest way to get the job done? Yes, for me it was. Hopefully this information can help someone else. Or perhaps at least it'll help the plugin author to make this plugin more foolproof 😉
7. februar, 2020
Timing out on a perfectly healthy VPS after importing only 25 posts and their media attachments. Have to workaround by migrating to a locally hosted site, then using a working migrator tool to the online site. Could there be an option to split XML into smaller chunks? I realise this is difficult to get to work everywhere, but I always advise people starting out a website and not sure how much effort they will put in to start a wordpress.com site, and its easy to upgrade. Thats a big part of what makes wordpress such a great platform for all kinds of users. When its so difficult to migrate to a self hosted wordpress, then its the opposite just a pain in the butt.
Les alle 291 vurderinger

Bidragsytere og utviklere

“WordPress Importør” er programvare med åpen kildekode. Følgende personer har bidratt til denne utvidelsen.

Bidragsytere

“WordPress Importør” har blitt oversatt til 55 språk. Takk til oversetterne for deres bidrag.

Oversett “WordPress Importør” til ditt språk.

Interessert i utvikling?

Bla gjennom koden, sjekk ut SVN-repositoriet, eller abonner på utviklingsloggen med RSS.

Endringslogg

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

  • Initial release