WordPress Importer

Deskripsi

WordPress Importer akan mengimpor konten berikut dari sebuah export file WordPress:

  • Pos, laman, dan tipe pos kustom lainnya
  • Comments and comment meta
  • Bidang kustom dan meta pos
  • Categories, tags and terms from custom taxonomies and term meta
  • Pengembang

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

Filter-filter

Importer memiliki sejumlah filter yang memmapukan Anda mengaktifkan/memblokir fitur tertentu:

  • import_allow_create_users: menghasilkan false jika Anda hanya mengizinkan pemetaan ke pengguna yang telah ada
  • import_allow_fetch_attachments: menghasilkan false jika Anda tidak ingin mengizinkan impor dan pengunduhan lampiran
  • import_attachment_size_limit: menghasilkan integer value dari ukuran file maksimum dalam bytes yang bisa disimpan (nilai default = 0, yakni tak terbatas)

Juga tersedia beberapa tindakan yang bisa disertakan:

  • import_start: berjalan sesudah export file telah diunggah dan pengaturan impor penulis telah dipilih
  • import_end: dijalankan sesudah output terakhir dari importer

Pemasangan

Metode paling cepat untuk menginstal importer adalah:

  1. Buka Perkakas -> Impor pada dasbor WordPress
  2. Klik menu/tautan WordPress dalam daftar importer
  3. Klik “Instal Sekarang”
  4. Lalu klik “Aktifkan Plugin & Jalankan Importer”

Jika Anda lebih suka menjalankan proses manual, ikuti instruksi berikut ini:

  1. Unggah folder wordpress-importer ke dalam direktori /wp-content/plugins/
  2. Aktifkan plugin via menu ‘Plugin’ di Dasbor WordPress
  3. Buka menu Perkakas -> Impor, klik menu WordPress

PSD (FAQ)

Tolong! Saya melihat galat “out of memory” atau laman blank.

Jika file XML Anda sangat besar, script impor mungkin akan melampaui limit memori PHP server.

Pesan seperti”Fatal error: Allowed memory size of 8388608 bytes exhausted” berarti bahwa script tidak berhasil mengimpor file XML dengan pengaturan limit memori PHP server. Jika Anda bisa mengakses file php.ini, Anda bisa mengubah limit secara manual; jika tidak (misalnya jika instalasi WordPress Anda berada dalam shared hosting), Anda mungkin harus memecah file XML tersebut menjadi beberapa bagian berukuran kecil dan mengimpornya satu demi satu.

Bagi pengguna shared hosting, sebaiknya berkonsultasi dengan provider hosting untuk menentukan pendekatan paling aman dalam menjalankan impor. Provider mungkin bersedia menaikkan limit memori untuk sementara waktu dan/atau menjalankan proses impor untuk Anda.

Support Article: Importing Content

Tinjauan

30 Maret 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 Februari 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.
21 November 2019
Mostly works for unmodified exports of simple things, but easily breaks when the XML is formatted slightly differently (but still valid), or when the content being exported is somewhat non-standard.
Baca semua 287 tinjauan

Kontributor & Pengembang

“WordPress Importer” adalah perangkat lunak sumber terbuka. Berikut ini mereka yang sudah berkontribusi pada plugin ini.

Para Kontributor

“WordPress Importer” telah diterjemahkan kedalam 54 lokale. Terima kasih kepada para penerjemah untuk kontribusi-nya.

Terjemahkan “WordPress Importer” dalam bahasa Anda.

Tertarik mengembangkan?

Lihat kode, periksa repositori SVN , atau mendaftar ke log pengembangan melalui RSS.

Log Perubahan

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

  • Dukungan untuk WXR 1.2 dan multiple CDATA sections
  • Pos bukanlah duplikat jika post_type-nya berbeda

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

  • Impor meta komentar (hanya untuk export file dari versi WordPress 3.2 ke atas)
  • Perbaikan bug minor dan beberapa pengembangan

0.4

  • Petakan user_id komentar jka mungkin
  • Impor lampiran dari wp:attachment_url
  • Unggah lampiran ke direktori yang benar
  • Petakan ulang URL gambar dengan benar

0.3

  • Gunakan XML Parser jika mungkin
  • Dukungan impor untuk menu navigasi
  • … and much more, see Trac ticket #15197

0.1

  • Rilis pertama