Changeset 1069133
- Timestamp:
- 01/16/2015 07:13:42 AM (11 years ago)
- File:
-
- 1 edited
-
readymade-wordpress-importer-061/trunk/readme.txt (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
readymade-wordpress-importer-061/trunk/readme.txt
r769824 r1069133 4 4 Tags: importer, wordpress, typepad, movabletype, attachments, import, uploads, transfer 5 5 Requires at least: 3.0 6 Tested up to: 3. 66 Tested up to: 3.0 7 7 Stable tag: 0.6.10 8 8 … … 11 11 == Description == 12 12 13 The ReadyMade WordPress Importer is a branch of the default WordPress importer. Our version modifies the default in three ways: 13 NOTE: This plugin has been superseded by the [TP2WP Importer](https://wordpress.org/plugins/tp2wp-importer/) and should now be considered deprecated. 14 14 15 1. If there is an attachment in the WXR and the importer is not able to determine the file type from the file name (ie missing extension), the patched version will make a light (body-less) request to the web server where the file is hosted for information we can use about the file. The things we're interested in are file type, size, and filename. 16 1. If the importer is processing an attachment under the above situation, and it is able to determine the file type, then it will rewrite the local version of the file to have the appropriate file extension. 17 1. When moving from one host to another, or from WordPress.com to a self-hosted site, you may setup hosting for your domain, let's call it "yourdomain.com" for example, before publicly directing the DNS to the new server. This is the correct thing to do if importing using WXR files. However, some hosts will then process references to "yourdomain.com" as internal references, rather than links to outside resources. This means that the importation process is essentially short circuited, with the public version of "yourdomain.com" being invisible to your new server. The ReadyMade WordPress Importer solves this problem by using TW2WP.com servers to identify the public IP of the source server and then uses that IP, rather than the domain, to import files. 18 19 ReadyMadeWeb developed this plugin in the process of creating a service to convert TypePad and MovableType MTIF data file to WordPress WXR formatted files. During this process we've encountered some unique problems with TypePad data. Namely, many TypePad files, particularly images, are saved without file extensions. This prevents the default WordPress importer from importing those files into the wp-content/uploads folder. By adding MIME type detection as a fallback, we prevent many files from being excluded from the import process. With most converted TypePad data, imports would contain no images whatsoever wihout this plugin as nearly all images on TypePad sites are stored without file extensions. 20 21 To convert your TypePad or MovableType MTIF data file to WordPress WXR data file and therefore preserve your attachments, permalinks, and more visit: 22 23 [TP2WP.com](http://tp2wp.com) 15 For more information visit [TP2WP.com](http://tp2wp.com) 24 16 25 17 == Installation == 18 19 NOTE: This plugin has been superseded by the [TP2WP Importer](https://wordpress.org/plugins/tp2wp-importer/) and should now be considered deprecated. 20 21 For more information visit [TP2WP.com](http://tp2wp.com) 26 22 27 23 The quickest method for installing the importer is: … … 32 28 33 29 == Changelog == 30 31 NOTE: This plugin has been superseded by the [TP2WP Importer](https://wordpress.org/plugins/tp2wp-importer/) and should now be considered deprecated. 32 33 For more information visit [TP2WP.com](http://tp2wp.com) 34 34 35 35 = 0.6.10 = … … 65 65 == Frequently Asked Questions == 66 66 67 = Help! I'm getting out of memory errors or a blank screen. = 68 If your exported file is very large, the import script may run into your host's configured memory limit for PHP. 67 NOTE: This plugin has been superseded by the [TP2WP Importer](https://wordpress.org/plugins/tp2wp-importer/) and should now be considered deprecated. 69 68 70 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. 71 72 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. 73 74 More Info: [WordPress Codex: Importing Content](http://codex.wordpress.org/Importing_Content#Before_Importing) 75 76 More Info: [tp2wp.com/faq](http://tp2wp.com/faq) 77 78 == Filters == 79 80 Like the WordPress importer, ReadyMade WordPress Importer has filters that allow you to completely enable/block certain features: 81 82 * `import_allow_create_users`: return false if you only want to allow mapping to existing users 83 * `import_allow_fetch_attachments`: return false if you do not wish to allow importing and downloading of attachments 84 * `import_attachment_size_limit`: return an integer value for the maximum file size in bytes to save (default is 0, which is unlimited) 85 86 There are also a few actions available to hook into: 87 88 * `import_start`: occurs after the export file has been uploaded and author import settings have been chosen 89 * `import_end`: called after the last output from the importer 69 For more information visit [TP2WP.com](http://tp2wp.com)
Note: See TracChangeset
for help on using the changeset viewer.