WordPress Importer (WordPress 內容匯入程式)

外掛說明

WordPress 內容匯入程式能從 WordPress 資料匯出檔中匯入以下內容:

  • 文章、頁面以及其他自訂內容類型
  • 留言及留言中繼資料
  • 自訂欄位及文章中繼資料
  • 分類、標籤、自訂分類法詞彙及其對應中繼資料
  • 作者

如需進一步了解相關資訊及說明,請參閱〈匯入內容〉線上說明。

篩選器

匯入程式所提供的篩選器能讓你完全啟用/封鎖某些功能:

  • import_allow_create_users:如果只是要對應至現有使用者,會傳回 false。
  • import_allow_fetch_attachments:如果不開放匯入及下載附件,會傳回 false。
  • import_attachment_size_limit:傳回最大檔案檔案大小的整數值,並以位元組 (Bytes) 為單位進行儲存。預設值為 0,代表不限制。

還有以下動作勾點可供使用:

  • import_start:上傳資料匯出檔及選取匯入作者設定後會出現。
  • import_end:內容匯入程式完成匯入便會呼叫。

安裝方式

安裝匯入程式最快的方式如下:

  1. 在 WordPress 控制台左側選單中,點擊 [工具] [匯入程式]。
  2. 點擊內容匯入程式清單中的 WordPress 連結。
  3. 點擊 [立即安裝]。
  4. 最後,點擊 [啟用外掛並執行匯入程式]。

如果偏好進行手動安裝,請依照以下步驟進行操作:

  1. wordpress-importer 資料夾上傳至 /wp-content/plugins/ 目錄。
  2. 在 WordPress 管理後台的 [外掛] 選單中啟用外掛。
  3. 到 [工具] [匯入程式] 頁面中,點擊 WordPress 連結。

常見問題集

我遇到主機記憶體錯誤或空白畫面,亟需協助!

如果要匯入的檔案大小非常大,匯入指令碼執行時可能會遇到主機限制 PHP 記憶體使用量的問題。

出現類似 [Fatal error: Allowed memory size of 8388608 bytes exhausted] 的訊息時,便表示在目前的 PHP 記憶體限制下,指令碼無法成功匯入 XML 檔案。如果你在主機上擁有變更 php.ini 檔案的權限 (詳情請洽詢主機商),你便能手動調高記憶體限制值;一般來說,如果是安裝於共享主機的 WordPress 網站,你便沒有權限變更 php.ini 中的設定值,這時你需要將 XML 檔案匯出成數個較小的檔案,然後才執行匯入指令碼一一匯入。

對於這種無法變更 PHP 環境設定值的共享主機,最好的選擇是洽詢主機技術支援提供協助,以便確定執行匯入最安全的做法。主機商可能會暫時解除主機記憶體限制,或由他們那端直接執行相關程序。

技術支援文章:匯入內容

使用者評論

2024 年 7 月 18 日 1 則留言
We tried this multiple times but not working. It has some conflict with hosting and our hosting company suggests not to use this plugin. It wasted so many hours in the process and now I need to find another alternative.
2023 年 11 月 4 日
I remember the time when this plugin was partially useless, but today I managed to export all of my posts and images easily and import them to my new installation. So, there was no need for a 3rd party plugin.This is useful for cluttered databases: when you transfer all your posts and images to new installation, then your database will have nothing but posts and images. Light and fast.Bye
2023 年 10 月 6 日 1 則留言
Good for the main use cases: restore from backup, and moving posts between blogs. Unfortunately the image import doesn’t seem to work (WordPress 6.3 with plugin 0.8.1), which makes it a pain to clean up image-heavy posts. One thing I’d like to do with this that I can’t is to import another copy of a cross-post and merge the comment threads. As it is, the best I can do is import the duplicate copy and then use another plugin (or dig into the database) to move the comments around.
2023 年 8 月 10 日
Needed to copy the content of the old website to the one which is developed from scratch – and it worked!
2023 年 7 月 21 日 1 則留言
I’ve used this just a few times in the past 18 months. And one time it was an incredible, urgent need as there were no server backups available from a web host (not with them anymore). Another time I made a mistake and deleted some comments. Anyway, this is only the 2nd review for this plugin within the past year or so. And I see a lot of negative scored posts. After reading them, I noticed a number of the 1-star reviews seemed to be user error. I’ve been in IT Management, development, and consulting for 4 decades. I use very little custom coding on my sites because, in my past experience, there are far less issues during updates and upgrades. So, with that said, I have also noticed there are a lot of optional settings to decide when using this tool. And many are preselected that I unselect. I recommend taking your time when using this tool and defining your own settings every time you use it. I use about 20 plugins and there’s no interference with any of them. But, I am careful about which plugins I retain. Also, I use this plugin just create backups or to perform restores from them. Then, I uninstall it until I need it again. For example, I’m here today because I’m getting ready to use it again as I’m about to make some major category changes. It will be very handy to use this tool to perform backups (and any needed restores) instead of using a site restore that will reset recent work on posts or pages. I use this as an additional backup and as an archive for all my sites. It’s always saved me when I needed it and I’ve found it to be reliable and solid. It’s been absolutely perfect for me when performing work on tags and categories so I don’t have to use a site restore.
閱讀全部 310 則使用者評論

參與者及開發者

以下人員參與了開源軟體〈WordPress Importer (WordPress 內容匯入程式)〉的開發相關工作。

參與者

〈WordPress Importer (WordPress 內容匯入程式)〉外掛目前已有 59 個本地化語言版本。 感謝全部譯者為這個外掛做出的貢獻。

將〈WordPress Importer (WordPress 內容匯入程式)〉外掛本地化為台灣繁體中文版

對開發相關資訊感興趣?

任何人均可瀏覽程式碼、查看 SVN 存放庫,或透過 RSS 訂閱開發記錄

變更記錄

0.8.2

  • Update compatibility tested-up-to to WordPress 6.4.2.
  • Update doc URL references.
  • Adjust workflow triggers.

0.8.1

  • Update compatibility tested-up-to to WordPress 6.2.
  • Update paths to build status badges.

0.8

  • Update minimum WordPress requirement to 5.2.
  • Update minimum PHP requirement to 5.6.
  • Update compatibility tested-up-to to WordPress 6.1.
  • PHP 8.0, 8.1, and 8.2 compatibility fixes.
  • Fix a bug causing blank lines in content to be ignored when using the Regex Parser.
  • Fix a bug resulting in a PHP fatal error when IMPORT_DEBUG is enabled and a category creation error occurs.
  • Improved Unit testing & automated testing.

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