Importatore WordPress

Descrizione

L’importatore WordPress importerà i seguenti contenuti da un file di esportazione di WordPress:

  • Articoli, pagine ed altri tipi di custom post type
  • Comments and comment meta
  • Campi personalizzati e metadati degli articoli
  • Categories, tags and terms from custom taxonomies and term meta
  • Autori

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

Filtri

L’importatore ha una coppia di filtri per consentirti di abilitare/bloccare completamente alcune funzionalità:

  • import_allow_create_users: restituisce false se si desidera permettere solamente di mappare gli utenti su quelli esistenti
  • import_allow_fetch_attachments: restituisce false se non si desidera consentire l’importazione e lo scaricamento degli allegati
  • import_attachment_size_limit: restituisci un valore intero per la dimensione massima di salvataggio del file in byte return (il valore standard è 0, nessun limite)

Vi sono anche alcune azioni a cui agganciarsi in:

  • import_start: si verifica dopo che il file di esportazione è stato caricato e sono stati scelte le impostazioni di importazione autore
  • import_end: chiamato dopo l’ultimo output dell’importatore

Installazione

Il metodo più rapido per installare l’importatore è:

  1. Visitare Strumenti -> Importa nella bacheca di WordPress
  2. Fare clic sul link WordPress nell’elenco degli importatori
  3. Fare clic su “Installa adesso”
  4. Alla fine fare clic su “Attivare il plugin ed eseguire l’importatore”

Se preferite eseguire le operazioni manualmente seguite le seguenti istruzioni:

  1. Caricate la cartella wordpress-importer nella directory /wp-content/plugins/
  2. Attiva il plugin attraverso il menu ‘Plugin’ di WordPress
  3. Andare sula schermata Strumenti -> Importa e fare clic su WordPress

FAQ

Aiuto! Mi esce un errore di memoria esaurita (out of memory) o una schermata nera.

Se il vostro file di esportazione è molto grande, lo script di importazione potrebbe incorrere nel liite di memoria PHP impostato dal vostro hosting.

Un messaggio del tipo “Fatal error: Allowed memory size of 8388608 bytes exhausted” indica che lo script non può importare il file XML correttamente con il limite di memoria di PHP attuale. Se si ha accesso al file php.ini potete incrementare questo valore manualmente; se non potete farlo (la vostra installazione di WordPress è ad esempio ospitata su un server condiviso), dovrete suddividere il file XML di esportazione in parti più piccole ed eseguire lo script d importazione per ciascuno di essi.

Per chi è su uno shared hosting, la migliore alternativa può essere quella di consultare il supporto del vostro hosting per determinare l’approccio più sicuro per eseguire l’importatore. Un hosting potrebbe volere aumentare temporaneamente il limite di memoria e/o eseguire il processo direttamente dalla loro parte.

Support Article: Importing Content

Recensioni

17 Giugno 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 Maggio 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 Marzo 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 Febbraio 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.
Leggi tutte le recensioni di 290

Contributi e sviluppo

“Importatore WordPress” è un software open source. Le persone che hanno contribuito allo sviluppo di questo plugin sono indicate di seguito.

Collaboratori

“Importatore WordPress” è stato tradotto in 55 lingue. Grazie ai traduttori per i loro contributi.

Traduci “Importatore WordPress” nella tua lingua.

Ti interessa lo sviluppo?

Esplora il Codice segui il Repository SVN iscriviti al Log delle Modifiche. Puoi farlo tramite RSS con un lettore di feed.

Changelog (registro delle modifiche)

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