Importador del WordPress

Descripció

The WordPress Importer will import the following content from a WordPress export file:

  • Posts, pages and other custom post types
  • Comentaris
  • Custom fields and post meta
  • Categories, tags and terms from custom taxonomies
  • Authors

For further information and instructions please see the Codex page on Importing Content

Filtres

The importer has a couple of filters to allow you to completely enable/block certain features:

  • 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

Instal·lació

The quickest method for installing the importer is:

  1. Visit Tools -> Import in the WordPress dashboard
  2. Click on the WordPress link in the list of importers
  3. Click “Install Now”
  4. Finally click “Activate Plugin & Run Importer”

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

  1. Upload the wordpress-importer folder to the /wp-content/plugins/ directory
  2. Activa l’extensió mitjançant el menú ‘Extensions’ del WordPress
  3. Go to the Tools -> Import screen, click on WordPress

PMF

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.

WordPress Codex: Importing Content

Ressenyes

Juliol 7, 2019
Anything written in the Classic Editor will have its paragraph breaks broken. Does not import statistics and will lose the majority of theme settings. Glad it exists but it's clear this is not something Automattic prioritizes.
Maig 14, 2019
Some time ago I had to moved hosts. This old woman only discovered the extent of my (old) hosts capabilities when my (old) site went down, and they couldn't, nay: they didn't want to sort it out, but I eventually proved that it was their fault that my site crashed the way it did. Proving that didn't help in finding that I'd lost the lot. Fortunately my old WP installation did have the standard export function under Tools -> Export. One ZIP file later in hand and stored safely on my PC, .. I then installed in on my new hosts server using this simple Importer Plugin. - And this quite brilliant little Plugin did it with out any hassle either. (Unlike the standard Import that didn't work). I can't tell you the joy I felt in seeing all my old pages and blogs reappear. True I did have to rejig some, but it was easy. To all those who say its rubbish: then I must vehemently disagree. Using the standard Export function in WP, and this tactful Plugin, then you have a FREE backup tool. No, .. WP doesn't do automatic backs ups, but what this Plugin does: is actually restore your entire site competently, and with one click. It's free, don't bitch: and the title of this review says it all. "For what it's worth," and it's worth a lot when you've lost it. I haven't, so back your site up for free now: then sit back in he knowledge that if it does crash and burn, (as mine did with that nasty 5.2 update), then at least you can get back to where you were before the fires of hell rained down on you. Thanks for reading, Jessica.
Llegiu totes les 281 ressenya

Col·laboradors i desenvolupadors

"Importador del WordPress" és programari de codi obert. La següent gent ha contribuït en aquesta extensió.

Contribuïdors

“Importador del WordPress” s'ha traduït a 52 localitzacions. Gràcies als traductos per les seves aportacions.

Tradueix “Importador del WordPress” a la teva llengua.

Interessats en el desenvolupament?

Navegueu pel codi, baixeu-vos el repositori SVN, o subscriviu-vos al registre de desenvolupament per fisl de subscripció RSS.

Registre de canvis

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

  • Versió inicial