I'm trying to import my wordpress blog content into Squarespace. There's around 200 posts and all of them contain multiple attached images. For whatever reason the "regular" wordpress import tool didn't work for me so I opted to use the "advanced" tool by uploading my exported XML file from my wordpress installation. The file uploads, and then goes into a "processing" state for several hours until it ultimately stalls. The status bar fills up indicating the import is complete, but the status says "Scheduled" and stays this way forever.
I've reached out to squarespace support 5 times for this issue and every time they give me the same run around response "Our engineering team is looking into this blah blah blah keep in mind there are many moving parts and this issue may take time". I'm pretty certain this isn't a widespread issue so I'm posting here. Can anyone get Wordpress import to work? I've got a very clean wordpress XML export file. Every time I try to import it, it hangs at "scheduled" for several hours until it ultimately results in a "failure".
Download Wordpress Importer
Download 🔥 https://bytlly.com/2y2Mzd 🔥
I finally got the Google importer and API set up, but when I try to run the importer I keep getting an error? How do I resolve this issue so I can import the data? (I waited awhile after setting up the API and even redid the steps for the API).
image1138198 58.5 KB
To give some context, you would want to zip the whole site folder, including the app and logs folders. Using the following screenshots as an example, you would zip up the wordpress-import folder, and then use the wordpress-import.zip file to import into Local by dragging and dropping the archive over Local.
Thanks, but how would the Teleporter Plugin solve this issue? I have imported posts from one wordpress site to another but the Featured images are all missing. How could the Teleporter Plugin help with this?
One problem with the Importer stands out immediately: resource usage. Importing any large file takes time (which is somewhat understandable) and a lot of memory. Some of my initial benchmarks indicate roughly the memory used usually has a lower limit of 3x the size of the file being imported. In addition, the importer is split into disparate stages: parse, import, and post-process. Importing in stages is not usually a problem, but it requires a lot of memory, as the entire file needs to be loaded into memory, potentially multiple times. The huge use of memory requires workarounds; the most common of these is splitting a WXR file into multiple files.
Switching to a hybrid pull/push parser changes the structure of the importer to two stages: combined parse/import, and post-process. As we move through the file, we import each item as we get to it, then forget about it and move on. This means we only ever need the current item (post, term, etc) in memory at one time, so memory usage is massively reduced. In my testing, this took the import of a 41MB WXR file from 132MB to 19MB, with a slight speed boost too.
The importer was never built with anything except the adminadmin (and super admin) UIUI User interface in mind. This causes problems with things like CLI importing, where wp-cliWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is -cli.org/ needs to reinvent parts of the importer in order to use it nicely. The new importer is instead built with the CLI as a first-class citizen, allowing a much nicer import process.
One of the components of this is building logging support into the importer from the start. Typically, users will want lots of information about the import, but for those who frequently run the importer, it can be a pain to sort out the interesting messages from the regular logging. This is fixed by having a configurable logging level, which also allows detailed debugging if desired.
Hi, I'm Ryan McCue. You may remember me from such projects as the REST API.\n\nI'm here today to talk about something a bit different: the WordPress Importer. The WordPress Importer is key to a tonne of different workflows, and is one of the most used plugins on the repo.\n\nUnfortunately, the Importer is also a bit unloved. After getting immensely frustrated at the Importer, I figured it was probably time we throw some attention at it. I've been working on fixing this with a new and improved Importer!\n\nIf you're interested in checking out this new version of the Importer, grab it from GitHub. It's still some way from release, but the vast majority of functionality is already in place. The plan is to eventually replace the existing Importer with this new version.\n\nThe key to these Importer improvements is rewriting the core processing, taking experience with the current Importer and building to fix those specific problems. This means fixing and improving a whole raft of problems:\n\n\nWay less memory usage: Testing shows memory usage to import a 41MB WXR file is down from 132MB to 19MB (less than half the actual file size!). This means no more splitting files just to get them to import!\nFaster parser: By using a streaming XML parser, we process data as we go, which is much more scalable than the current approach. Content can begin being imported as soon as the file is read, rather than waiting for pre-processing.\nResumable parsing: By storing more in the database instead of variables, we can quit and resume imports on-the-go.\nPartial imports: Rethinking the deduplication approach allows better partial imports, such as when you're updating a production site from staging.\nBetter CLI: Treating the CLI as a first-class citizen means a better experience for those doing imports on a daily basis, and better code quality and reusability.\n\n\nCurious as to how all of this is done? Read on!\n\n\n\nParsing\n\nOne problem with the Importer stands out immediately: resource usage. Importing any large file takes time (which is somewhat understandable) and a lot of memory. Some of my initial benchmarks indicate roughly the memory used usually has a lower limit of 3x the size of the file being imported. In addition, the importer is split into disparate stages: parse, import, and post-process. Importing in stages is not usually a problem, but it requires a lot of memory, as the entire file needs to be loaded into memory, potentially multiple times. The huge use of memory requires workarounds; the most common of these is splitting a WXR file into multiple files.\n\nThe problems with the Importer mirror other well-known problems with parsing XML. While the easiest way to parse an XML file is to simply load it into memory, transform it into some data that's easier to work with, then do your tasks on it. This is the way that most people parse XML, and it works fine for small files, but it's not a scalable solution.\n\nThankfully, this is a solved problem. The key is moving from a push parser - which takes a file and returns some data - to a pull (streaming) parser - which takes a file, and gives you a cursor to move through the file. Pull parsers are typically a bit harder to work with, but thankfully PHP allows us to use a hybrid approach (XMLReader and DOMDocument share an internal representation).\n\nWhy use a push parser to start with? Push parsers have two key benefits: they're typically much easier to use, and you get all of the data at the start. Having the full picture of the data makes it easier to work with, and typically it means you can do cross-referencing quite easily (e.g. posts with terms). This usually means you eliminate a post-processing stage, however the Importer needs to do post-processing anyway (thanks to media URLs and IDs changing), so we don't gain anything there. In addition, since we're also producing the XML from the WXR export, we can optimise the export format for single-pass parsing, which will help reduce post-processing. The ease of use of the parser is only a concern for the plugin maintainers, and the hybrid approach allows us to use the pull parser in a much easier way.\n\nSwitching to a hybrid pull\/push parser changes the structure of the importer to two stages: combined parse\/import, and post-process. As we move through the file, we import each item as we get to it, then forget about it and move on. This means we only ever need the current item (post, term, etc) in memory at one time, so memory usage is massively reduced. In my testing, this took the import of a 41MB WXR file from 132MB to 19MB, with a slight speed boost too.\n\nProcessing\n\nOnce we've got our data out of XML and into an internal representation, we need to do some processing. Right now, the processing is suboptimal, as it wasn't designed or built for large imports and sites.\n\nChecking if posts have been imported already is very slow. Each post being imported calls post_exists, which does a direct database query for SELECT ID FROM wp_posts WHERE post_date = %s AND post_title = %s and post_content = %s. None of these fields are indexed, which makes this query slow on sites with lots of posts (for example, a site that you've just imported into). It also completely ignores the GUID field, which is designed for being a deduplication field in the first place. A much more performant solution is to load a map of GUID => ID ahead of time, and use the GUID to deduplicate from here. This increases memory usage, but insignifcantly, as it's only one integer and one small string per post. (This has potential problems if posts are being created while importing; we can lock the site in maintenance mode, or the user can turn this \"prefill\" option off if desired.)\n\nThe importer also currently holds a lot of state in memory. Any posts that need the parent changed, users updated, or URL search-and-replace are stored in memory with maps of the data. This increases memory usage, and also means that the import isn't resumable. Instead, we can store much of this data in the post metadata, which allows resuming importing as well as much easier debugging if a post's data isn't quite what you expect. This also moves the memory usage off to the database, which is much more efficient at deciding what's important.\n\nMedia\n\nRight now, media importing has a few problems. It's currently not idempotent (repeatable with the same result), so you can't re-run or resume an import; the core attachment fetching is slow; and it's built into the main importing process.\n\nOn import, the GUID of the attachment is changed to the new attachment URL. In the past, the GUID has been used by both WordPress core and plugins for the attachment URL, but this is now regarded as bad practice, and is avoided wherever possible. The Importer however doesn't reflect these changes in attitude, as it still changes the GUID to avoid references to the old URL. This makes repeating an import (such as resuming an import, or doing a partial update) impossible, as there's now no ID to cross-reference between the two. Removing the GUID change means we can easily check if an attachment has been imported already. The downside is that plugins still using the GUID may break; this needs to be fixed in the plugins in question, as the GUID is already an unreliable reference to the image.\n\nAs each attachment is imported into WordPress, we also sideload the image at the same time, which blocks the importing process. This means that you're waiting on an image to download when you could be running the rest of the import. Instead, we can change this up to create the media posts as we go, but leave the downloading to post-processing. During post-processing, we can then use a HTTP tool or library that supports parallel downloads to fetch the images simultaneously and process them as they come in. This massively improves time taken for media importing. Decoupling the downloading means we can also handle downloads using a different tool, or even use the existing local files if we already have a copy of the uploads directory (!!!).\n\nCLI\n\nThe importer was never built with anything except the admin UI in mind. This causes problems with things like CLI importing, where wp-cli needs to reinvent parts of the importer in order to use it nicely. The new importer is instead built with the CLI as a first-class citizen, allowing a much nicer import process.\n\nOne of the components of this is building logging support into the importer from the start. Typically, users will want lots of information about the import, but for those who frequently run the importer, it can be a pain to sort out the interesting messages from the regular logging. This is fixed by having a configurable logging level, which also allows detailed debugging if desired.\n\nLet's Go!\n\nThe rewritten Importer already fixes all of these issues, along with other long-standing bugs.\n\nThe plan for the Importer is to restore some of the features which didn't make the cut along the road to this rewrite. Importantly, it currently doesn't contain any admin UI, with only the CLI interface available. After the final pieces of compatibility are sorted out, the plan is to replace the existing Importer plugin with the rewrite, and ship a version 1 of the Importer. (Did you know the current stable version is only 0.6?)\n\nI'd love to have your help improving this! If there's anything you've ever wanted from the Importer, now's the time to say so. Testing your export files with the new Importer to detect any discrepencies would be super helpful too, as due to the nature of the rewrite, it's definitely possible that something's been missed along the way.\n\nHopefully you care about the Importer as much as I do. Let's make it great together.\n\n#importers","contentFiltered":"Hi, I\u2019m Ryan McCue. You may remember me from such projects as the REST APIREST API The REST API is an acronym for the RESTful Application Program Interface (API) that uses HTTP requests to GET, PUT, POST and DELETE data. It is how the front end of an application (think \u201cphone app\u201d or \u201cwebsite\u201d) can communicate with the data store (think \u201cdatabase\u201d or \u201cfile system\u201d) https:\/\/developer.wordpress.org\/rest-api\/..\nI\u2019m here today to talk about something a bit different: the WordPress Importer. The WordPress Importer is key to a tonne of different workflows, and is one of the most used plugins on the repo.\nUnfortunately, the Importer is also a bit unloved. After getting immensely frustrated at the Importer, I figured it was probably time we throw some attention at it. I\u2019ve been working on fixing this with a new and improved Importer!\nIf you\u2019re interested in checking out this new version of the Importer, grab it from GitHub. It\u2019s still some way from release, but the vast majority of functionality is already in place. The plan is to eventually replace the existing Importer with this new version.\nThe key to these Importer improvements is rewriting the coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. processing, taking experience with the current Importer and building to fix those specific problems. This means fixing and improving a whole raft of problems:\n\nWay less memory usage: Testing shows memory usage to import a 41MB WXR file is down from 132MB to 19MB (less than half the actual file size!). This means no more splitting files just to get them to import!\nFaster parser: By using a streaming XML parser, we process data as we go, which is much more scalable than the current approach. Content can begin being imported as soon as the file is read, rather than waiting for pre-processing.\nResumable parsing: By storing more in the database instead of variables, we can quit and resume imports on-the-go.\nPartial imports: Rethinking the deduplication approach allows better partial imports, such as when you\u2019re updating a production siteProduction Site A production site is a live site online meant to be viewed by your visitors, as opposed to a site that is staged for development or testing. from staging.\nBetter CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.: Treating the CLI as a first-class citizen means a better experience for those doing imports on a daily basis, and better code quality and reusability.\n\nCurious as to how all of this is done? Read on!\n\nParsing\nOne problem with the Importer stands out immediately: resource usage. Importing any large file takes time (which is somewhat understandable) and a lot of memory. Some of my initial benchmarks indicate roughly the memory used usually has a lower limit of 3x the size of the file being imported. In addition, the importer is split into disparate stages: parse, import, and post-process. Importing in stages is not usually a problem, but it requires a lot of memory, as the entire file needs to be loaded into memory, potentially multiple times. The huge use of memory requires workarounds; the most common of these is splitting a WXR file into multiple files.\nThe problems with the Importer mirror other well-known problems with parsing XML. While the easiest way to parse an XML file is to simply load it into memory, transform it into some data that\u2019s easier to work with, then do your tasks on it. This is the way that most people parse XML, and it works fine for small files, but it\u2019s not a scalable solution.\nThankfully, this is a solved problem. The key is moving from a push parser \u2013 which takes a file and returns some data \u2013 to a pull (streaming) parser \u2013 which takes a file, and gives you a cursor to move through the file. Pull parsers are typically a bit harder to work with, but thankfully PHPPHP The web scripting language in which WordPress is primarily architected. WordPress requires PHP 5.6.20 or higher allows us to use a hybrid approach (XMLReader and DOMDocument share an internal representation).\nWhy use a push parser to start with? Push parsers have two key benefits: they\u2019re typically much easier to use, and you get all of the data at the start. Having the full picture of the data makes it easier to work with, and typically it means you can do cross-referencing quite easily (e.g. posts with terms). This usually means you eliminate a post-processing stage, however the Importer needs to do post-processing anyway (thanks to media URLs and IDs changing), so we don\u2019t gain anything there. In addition, since we\u2019re also producing the XML from the WXR export, we can optimise the export format for single-pass parsing, which will help reduce post-processing. The ease of use of the parser is only a concern for the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party maintainers, and the hybrid approach allows us to use the pull parser in a much easier way.\nSwitching to a hybrid pull\/push parser changes the structure of the importer to two stages: combined parse\/import, and post-process. As we move through the file, we import each item as we get to it, then forget about it and move on. This means we only ever need the current item (post, term, etc) in memory at one time, so memory usage is massively reduced. In my testing, this took the import of a 41MB WXR file from 132MB to 19MB, with a slight speed boost too.\nProcessing\nOnce we\u2019ve got our data out of XML and into an internal representation, we need to do some processing. Right now, the processing is suboptimal, as it wasn\u2019t designed or built for large imports and sites.\nChecking if posts have been imported already is very slow. Each post being imported calls post_exists, which does a direct database query for SELECT ID FROM wp_posts WHERE post_date = %s AND post_title = %s and post_content = %s. None of these fields are indexed, which makes this query slow on sites with lots of posts (for example, a site that you\u2019ve just imported into). It also completely ignores the GUID field, which is designed for being a deduplication field in the first place. A much more performant solution is to load a map of GUID => ID ahead of time, and use the GUID to deduplicate from here. This increases memory usage, but insignifcantly, as it\u2019s only one integer and one small string per post. (This has potential problems if posts are being created while importing; we can lock the site in maintenance mode, or the user can turn this \u201cprefill\u201d option off if desired.)\nThe importer also currently holds a lot of state in memory. Any posts that need the parent changed, users updated, or URLURL A specific web address of a website or web page on the Internet, such as a website\u2019s URL http:\/\/www.wordpress.org search-and-replace are stored in memory with maps of the data. This increases memory usage, and also means that the import isn\u2019t resumable. Instead, we can store much of this data in the post metadata, which allows resuming importing as well as much easier debugging if a post\u2019s data isn\u2019t quite what you expect. This also moves the memory usage off to the database, which is much more efficient at deciding what\u2019s important.\nMedia\nRight now, media importing has a few problems. It\u2019s currently not idempotent (repeatable with the same result), so you can\u2019t re-run or resume an import; the core attachment fetching is slow; and it\u2019s built into the main importing process.\nOn import, the GUID of the attachment is changed to the new attachment URL. In the past, the GUID has been used by both WordPress core and plugins for the attachment URL, but this is now regarded as bad practice, and is avoided wherever possible. The Importer however doesn\u2019t reflect these changes in attitude, as it still changes the GUID to avoid references to the old URL. This makes repeating an import (such as resuming an import, or doing a partial update) impossible, as there\u2019s now no ID to cross-reference between the two. Removing the GUID change means we can easily check if an attachment has been imported already. The downside is that plugins still using the GUID may break; this needs to be fixed in the plugins in question, as the GUID is already an unreliable reference to the image.\nAs each attachment is imported into WordPress, we also sideload the image at the same time, which blocks the importing process. This means that you\u2019re waiting on an image to download when you could be running the rest of the import. Instead, we can change this up to create the media posts as we go, but leave the downloading to post-processing. During post-processing, we can then use a HTTPHTTP HTTP is an acronym for Hyper Text Transfer Protocol. HTTP is the underlying protocol used by the World Wide Web and this protocol defines how messages are formatted and transmitted, and what actions Web servers and browsers should take in response to various commands. tool or library that supports parallel downloads to fetch the images simultaneously and process them as they come in. This massively improves time taken for media importing. Decoupling the downloading means we can also handle downloads using a different tool, or even use the existing local files if we already have a copy of the uploads directory (!!!).\nCLI\nThe importer was never built with anything except the adminadmin (and super admin) UIUI User interface in mind. This causes problems with things like CLI importing, where wp-cliWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http:\/\/wp-cli.org\/ https:\/\/make.wordpress.org\/cli\/ needs to reinvent parts of the importer in order to use it nicely. The new importer is instead built with the CLI as a first-class citizen, allowing a much nicer import process.\nOne of the components of this is building logging support into the importer from the start. Typically, users will want lots of information about the import, but for those who frequently run the importer, it can be a pain to sort out the interesting messages from the regular logging. This is fixed by having a configurable logging level, which also allows detailed debugging if desired.\nLet\u2019s Go!\nThe rewritten Importer already fixes all of these issues, along with other long-standing bugs.\nThe plan for the Importer is to restore some of the features which didn\u2019t make the cut along the road to this rewrite. Importantly, it currently doesn\u2019t contain any admin UI, with only the CLI interface available. After the final pieces of compatibility are sorted out, the plan is to replace the existing Importer plugin with the rewrite, and ship a version 1 of the Importer. (Did you know the current stable version is only 0.6?)\nI\u2019d love to have your help improving this! If there\u2019s anything you\u2019ve ever wanted from the Importer, now\u2019s the time to say so. Testing your export files with the new Importer to detect any discrepencies would be super helpful too, as due to the nature of the rewrite, it\u2019s definitely possible that something\u2019s been missed along the way.\nHopefully you care about the Importer as much as I do. Let\u2019s make it great together.\n#importersShare this:TwitterFacebook","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/","unixtime":1447810051,"unixtimeModified":1447810651,"entryHeaderMeta":"","linkPages":"","footerEntryMeta":"","tagsRaw":"importers","tagsArray":[{"label":"importers","count":6,"link":"https:\/\/make.wordpress.org\/core\/tag\/importers\/"}],"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F&locale=en_US","hasPrevPost":true,"prevPostTitle":"WP REST API: Versions 1.2.4 (Compatibility Release) and 2.0 Beta 6","prevPostURL":"https:\/\/make.wordpress.org\/core\/2015\/11\/12\/wp-rest-api-versions-1-2-4-compatibility-release-and-2-0-beta-6\/","hasNextPost":true,"nextPostTitle":"WP REST API: Version 2.0 Beta 7","nextPostURL":"https:\/\/make.wordpress.org\/core\/2015\/11\/19\/wp-rest-api-2-0-beta-7\/","commentsOpen":false,"is_xpost":false,"editURL":null,"postActions":"Post ActionsScrollShortlink","comments":[{"type":"comment","id":"28413","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-pavot even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"I can't express how happy I am about this progress!\nThank you very much.","contentFiltered":"I can\u2019t express how happy I am about this progress!\nThank you very much.\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28413","unixtime":1447810566,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28413&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447810566,"hasChildren":false,"userLogin":"pavot","userNicename":"pavot"},{"type":"comment","id":"28414","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28413","contentRaw":"Thanks for caring :)","contentFiltered":"Thanks for caring \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28414","unixtime":1447810743,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28414&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447810743,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28415","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-jb510 even thread-even depth-1","parentID":"0","contentRaw":"Ditto. This is awesome. Having spent a lot of hours last weekend trying to debug a massive wp.com WXR\/XML export (split in over 20 parts and failing on files 14-16)... this is so timely. Looking forward to testing it.\n\nCurious if the pull parser works with a folder full of xml files the way the WP importer did? Since as I said above, what .com dumped was a couple dozen xml files and I don't have a convenient way to glue them back together.\n\nHuge thank you for attending to a long neglected corner of WordPress!","contentFiltered":"Ditto. This is awesome. Having spent a lot of hours last weekend trying to debug a massive wp.com WXR\/XML export (split in over 20 parts and failing on files 14-16)\u2026 this is so timely. Looking forward to testing it.\nCurious if the pull parser works with a folder full of xml files the way the WP importer did? Since as I said above, what .com dumped was a couple dozen xml files and I don\u2019t have a convenient way to glue them back together.\nHuge thank you for attending to a long neglected corner of WordPress!\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28415","unixtime":1447811657,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28415&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447811657,"hasChildren":false,"userLogin":"jb510","userNicename":"jb510"},{"type":"comment","id":"28416","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28415","contentRaw":"Curious if the pull parser works with a folder full of xml files the way the WP importer did?\n\nYou should be able to work with split files by just importing them one after another. (You should also be able to import them in any order, theoretically.) This is something I haven't put a lot of testing into yet though, so give it a shot and let me know!\n\nIn the future, hopefully we'll never need to split files again. :)","contentFiltered":"Curious if the pull parser works with a folder full of xml files the way the WP importer did?\nYou should be able to work with split files by just importing them one after another. (You should also be able to import them in any order, theoretically.) This is something I haven\u2019t put a lot of testing into yet though, so give it a shot and let me know!\nIn the future, hopefully we\u2019ll never need to split files again. \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28416","unixtime":1447811776,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28416&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447811776,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28417","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-sakinshrestha even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"Wow this is awesome... Thanks a lot :)","contentFiltered":"Wow this is awesome\u2026 Thanks a lot \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28417","unixtime":1447812762,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28417&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447812762,"hasChildren":false,"userLogin":"sakinshrestha","userNicename":"sakinshrestha"},{"type":"comment","id":"28418","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-nicholas_io odd alt thread-even depth-1","parentID":"0","contentRaw":"This is Awesome! The WordPress importer as it currently stands is far from being good. I'll be happy testing it out","contentFiltered":"This is Awesome! The WordPress importer as it currently stands is far from being good. I\u2019ll be happy testing it out\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28418","unixtime":1447812822,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28418&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447812822,"hasChildren":false,"userLogin":"nicholas_io","userNicename":"nicholas_io"},{"type":"comment","id":"28419","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor even depth-2","parentID":"28417","contentRaw":"Thanks for the kind words :)","contentFiltered":"Thanks for the kind words \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28419","unixtime":1447812864,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28419&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447812864,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28420","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28418","contentRaw":"Let me know how it goes in testing! If there's any bugs, let's get them squashed :)","contentFiltered":"Let me know how it goes in testing! If there\u2019s any bugs, let\u2019s get them squashed \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28420","unixtime":1447812890,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28420&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447812890,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28421","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-conjur3r even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"Great stuff Ryan. Really nice performance improvements. I've often ran into memory limits during import.\n\nAs an aside, has there been discussion around offline import, most specifically around media items? Such a possibility would allow for sites to be exported wholly together with all of their content items and either kept for archive or imported more easily. Such a site could have been mocked up on an unreachable development server.","contentFiltered":"Great stuff Ryan. Really nice performance improvements. I\u2019ve often ran into memory limits during import.\nAs an aside, has there been discussion around offline import, most specifically around media items? Such a possibility would allow for sites to be exported wholly together with all of their content items and either kept for archive or imported more easily. Such a site could have been mocked up on an unreachable development server.\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28421","unixtime":1447813253,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28421&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447813253,"hasChildren":false,"userLogin":"conjur3r","userNicename":"conjur3r"},{"type":"comment","id":"28422","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28421","contentRaw":"Thanks Mike!\n\nWe have an issue filed for that one. Deferring the actual images getting imported will get a few gains: offline imports, parallel downloads, or static content imports (i.e. image files in a zip).\n\nYou can pass 'fetch_attachments' => false (also the default internally, but not in the CLI) into the importer class in __construct for this already. :)","contentFiltered":"Thanks Mike!\nWe have an issue filed for that one. Deferring the actual images getting imported will get a few gains: offline imports, parallel downloads, or static content imports (i.e. image files in a zip).\nYou can pass 'fetch_attachments' => false (also the default internally, but not in the CLICLI Command Line Interface. Terminal (Bash) in Mac, Command Prompt in Windows, or WP-CLI for WordPress.) into the importer class in __construct for this already. \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28422","unixtime":1447813487,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28422&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447813487,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28423","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-markel even thread-even depth-1","parentID":"0","contentRaw":"Hey, Ryan.\n\nThis is other Ryan. :) We've been dealing with super-large imports on WordPress.com VIP for some time now and I've been dealing with them for a year-plus. I'd love to chat with you at some point about the kinds of things we have run into in these large imports and in other things that are edgier-case like site merges and other things that the import currently can struggle with.\n\nSome of what we are doing on WordPress.com is almost certainly not practical for movement to core, but we can probably provide some valuable insight on larger imports and problems that are encountered there.","contentFiltered":"Hey, Ryan.\nThis is other Ryan. \ud83d\ude42 We\u2019ve been dealing with super-large imports on WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https:\/\/wordpress.com\/ VIP for some time now and I\u2019ve been dealing with them for a year-plus. I\u2019d love to chat with you at some point about the kinds of things we have run into in these large imports and in other things that are edgier-case like site merges and other things that the import currently can struggle with.\nSome of what we are doing on WordPress.com is almost certainly not practical for movement to coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress., but we can probably provide some valuable insight on larger imports and problems that are encountered there.\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28423","unixtime":1447813526,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28423&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447813526,"hasChildren":false,"userLogin":"markel","userNicename":"markel"},{"type":"comment","id":"28424","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-ipstenu odd alt thread-odd thread-alt depth-1","parentID":"0","contentRaw":"This will be a game changer for the many people who want to export from wordpress.com and import to self-hosted where they either can't afford or aren't able to use the migration package.\n\nYou, sir, deserve all the pizza bites.","contentFiltered":"This will be a game changer for the many people who want to export from wordpress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https:\/\/wordpress.com\/ and import to self-hosted where they either can\u2019t afford or aren\u2019t able to use the migrationMigration Moving the code, database and media files for a website site from one server to another. Most typically done when changing hosting companies. package.\nYou, sir, deserve all the pizza bites.\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28424","unixtime":1447814589,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28424&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447814589,"hasChildren":false,"userLogin":"Ipstenu","userNicename":"ipstenu"},{"type":"comment","id":"28425","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor even depth-2","parentID":"28423","contentRaw":"Hey other Ryan! Let's chat; one of the big use cases that lead to me rewriting this was huge VIP-level imports, so it's definitely something I'm conscious of. I'd love to have your and VIP's feedback :)","contentFiltered":"Hey other Ryan! Let\u2019s chat; one of the big use cases that lead to me rewriting this was huge VIP-level imports, so it\u2019s definitely something I\u2019m conscious of. I\u2019d love to have your and VIP\u2019s feedback \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28425","unixtime":1447814942,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28425&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447814942,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28426","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28424","contentRaw":"Thanks Mika, I'll need to organise some of those. ;)","contentFiltered":"Thanks Mika, I\u2019ll need to organise some of those. \ud83d\ude09\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28426","unixtime":1447815857,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28426&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447815857,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28427","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-mattheweppelsheimer even thread-even depth-1","parentID":"0","contentRaw":"This is so, so, great Ryan! \n\nLooking forward to testing this and seeing if our pet bugs in the 0.6 importer to fix \"someday\" still exist. I'll bet not\u2026","contentFiltered":"This is so, so, great Ryan! \nLooking forward to testing this and seeing if our pet bugs in the 0.6 importer to fix \u201csomeday\u201d still exist. I\u2019ll bet not\u2026\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28427","unixtime":1447816511,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28427&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447816511,"hasChildren":false,"userLogin":"mattheweppelsheimer","userNicename":"mattheweppelsheimer"},{"type":"comment","id":"28428","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28427","contentRaw":"Thanks for the kind words, and here's hoping there's no bugs. :)","contentFiltered":"Thanks for the kind words, and here\u2019s hoping there\u2019s no bugs. \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28428","unixtime":1447816546,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28428&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447816546,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28429","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-jakept even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"My biggest frustration is the inability to import Posts only and import images at the same time. Images only come across if the entire site is exported. This is very annoying when trying to transfer a client's blog between sites without bringing across menus and random plugin post types. I can understand the challenge since they're only img tags and not necessarily attached to the post, but it's definitely my biggest hangup with the importer.","contentFiltered":"My biggest frustration is the inability to import Posts only and import images at the same time. Images only come across if the entire site is exported. This is very annoying when trying to transfer a client\u2019s blogblog (versus network, site) between sites without bringing across menus and random pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https:\/\/wordpress.org\/plugins\/ or can be cost-based plugin from a third-party post types. I can understand the challenge since they\u2019re only img tags and not necessarily attached to the post, but it\u2019s definitely my biggest hangup with the importer.\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28429","unixtime":1447817904,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28429&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447817904,"hasChildren":false,"userLogin":"JakePT","userNicename":"jakept"},{"type":"comment","id":"28430","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28429","contentRaw":"I believe this is actually an issue with the way data is exported from WordPress, possibly #17379?","contentFiltered":"I believe this is actually an issue with the way data is exported from WordPress, possibly #17379?\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28430","unixtime":1447818078,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28430&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447818078,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28431","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-bishless even thread-even depth-1","parentID":"0","contentRaw":"This is great news! Thanks for your work, Ryan!","contentFiltered":"This is great news! Thanks for your work, Ryan!\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28431","unixtime":1447822771,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28431&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447822771,"hasChildren":false,"userLogin":"bishless","userNicename":"bishless"},{"type":"comment","id":"28432","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28431","contentRaw":"Thanks! :)","contentFiltered":"Thanks! \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28432","unixtime":1447822808,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28432&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447822808,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28434","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-jeffmcneill even thread-odd thread-alt depth-1","parentID":"0","contentRaw":"I've run into a ton of problems with importing, usually a memory or parsing issue. I've had to eject a lot of content from several site migrations because of this. That you are working on this critical tool for Wordpress means you should be applauded, and lauded. Thank you!","contentFiltered":"I\u2019ve run into a ton of problems with importing, usually a memory or parsing issue. I\u2019ve had to eject a lot of content from several site migrations because of this. That you are working on this critical tool for WordPress means you should be applauded, and lauded. Thank you!\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28434","unixtime":1447825383,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28434&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447825383,"hasChildren":false,"userLogin":"jeffmcneill","userNicename":"jeffmcneill"},{"type":"comment","id":"28435","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28434","contentRaw":"Fingers crossed, splitting files and memory issues will be a thing of the past! Thanks :)","contentFiltered":"Fingers crossed, splitting files and memory issues will be a thing of the past! Thanks \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28435","unixtime":1447826967,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28435&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447826967,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28436","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-debaat even thread-even depth-1","parentID":"0","contentRaw":"Reading the responses, you've definitely hit a soft spot!\nThanks already for picking this challenge.\n\nI myself did have some issues with the importer lately as I was migrating some content from dev to prod.\nAnd this actually had to do with the GUID, so please take real good care to using this.\nI mean, a post developed on site x.dev typically has x.dev in the guid. When I try to import it into x.com, I would like to have an option whether or not to 'translate' the GUID from x.dev to x.com.\n\nThe same goes for the GUID of an image. In some cases, the image may have been uploaded already in the x.com site before. So how do you discriminate between the two images?\nHope you'll get it working nicely.\n\nReading your article, I thought you mentioned something about changing the exporter as well. I'm not sure however, so are there any plans to work on the exporter as well?","contentFiltered":"Reading the responses, you\u2019ve definitely hit a soft spot!\nThanks already for picking this challenge.\nI myself did have some issues with the importer lately as I was migrating some content from dev to prod.\nAnd this actually had to do with the GUID, so please take real good care to using this.\nI mean, a post developed on site x.dev typically has x.dev in the guid. When I try to import it into x.com, I would like to have an option whether or not to \u2018translate\u2019 the GUID from x.dev to x.com.\nThe same goes for the GUID of an image. In some cases, the image may have been uploaded already in the x.com site before. So how do you discriminate between the two images?\nHope you\u2019ll get it working nicely.\nReading your article, I thought you mentioned something about changing the exporter as well. I\u2019m not sure however, so are there any plans to work on the exporter as well?\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28436","unixtime":1447827960,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28436&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447827960,"hasChildren":false,"userLogin":"DeBAAT","userNicename":"debaat"},{"type":"comment","id":"28437","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-mrahmadawais odd alt thread-odd thread-alt depth-1","parentID":"0","contentRaw":"I've had my fair share of WTF Moments\u2122 with WordPress importer. So, believe me when I say this, I am glad someone is finally working on improving that. It's a great news. Going to test it this weekend.","contentFiltered":"I\u2019ve had my fair share of WTF Moments\u2122 with WordPress importer. So, believe me when I say this, I am glad someone is finally working on improving that. It\u2019s a great news. Going to test it this weekend.\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28437","unixtime":1447828699,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28437&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447828699,"hasChildren":false,"userLogin":"mrahmadawais","userNicename":"mrahmadawais"},{"type":"comment","id":"28438","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor even depth-2","parentID":"28436","contentRaw":"The main thing with the GUID is that it shouldn't ever change. The new importer actually uses it more, so if you change the GUIDs, later imports will reimport the same data again. That said, @westonruter's pull request would let you write complex logic to map this back and forth, and I do know it's a common use case. Happy to discuss further on a GH issue :)\n\nSpecifically on images, there's a flag in the options in the new importer called update_attachment_guids - the old importer always changes the GUID to the new filename, but this rewrite avoids that by default, as it makes deduplication on future imports impossible. (The reason the old importer did this is because originally the GUID contained the filename, so that's occasionally used by older code to find the image URL.)\n\nThere's no real plans to change the exporter right now, but if it turns out we can improve import efficiency by changing data in exports (i.e. avoid post-processing by being careful about the element order), we'll likely do that.\n\nThanks for the feedback!","contentFiltered":"The main thing with the GUID is that it shouldn\u2019t ever change. The new importer actually uses it more, so if you change the GUIDs, later imports will reimport the same data again. That said, @westonruter\u2018s pull request would let you write complex logic to map this back and forth, and I do know it\u2019s a common use case. Happy to discuss further on a GH issue \ud83d\ude42\nSpecifically on images, there\u2019s a flag in the options in the new importer called update_attachment_guids \u2013 the old importer always changes the GUID to the new filename, but this rewrite avoids that by default, as it makes deduplication on future imports impossible. (The reason the old importer did this is because originally the GUID contained the filename, so that\u2019s occasionally used by older code to find the image URLURL A specific web address of a website or web page on the Internet, such as a website\u2019s URL www.wordpress.org.)\nThere\u2019s no real plans to change the exporter right now, but if it turns out we can improve import efficiency by changing data in exports (i.e. avoid post-processing by being careful about the element order), we\u2019ll likely do that.\nThanks for the feedback!\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28438","unixtime":1447829239,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28438&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":["westonruter"],"mentionContext":"","commentCreated":1447829239,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28439","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28437","contentRaw":"Thanks for the feedback :)","contentFiltered":"Thanks for the feedback \ud83d\ude42\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28439","unixtime":1447829253,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28439&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":2,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447829253,"hasChildren":false,"userLogin":"rmccue","userNicename":"rmccue"},{"type":"comment","id":"28440","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-samhotchkiss even thread-even depth-1","parentID":"0","contentRaw":"You're amazing, Ryan, well done.","contentFiltered":"You\u2019re amazing, Ryan, well done.\n","permalink":"https:\/\/make.wordpress.org\/core\/2015\/11\/18\/wordpress-importer-redux\/#comment-28440","unixtime":1447829513,"loginRedirectURL":"https:\/\/login.wordpress.org\/?redirect_to=https%3A%2F%2Fmake.wordpress.org%2Fcore%2F2015%2F11%2F18%2Fwordpress-importer-redux%2F%23comment-28440&locale=en_US","approved":true,"isTrashed":false,"prevDeleted":"","editURL":null,"depth":1,"commentDropdownActions":"","commentFooterActions":"","commentTrashedActions":"Untrash","mentions":[],"mentionContext":"","commentCreated":1447829513,"hasChildren":false,"userLogin":"samhotchkiss","userNicename":"samhotchkiss"},{"type":"comment","id":"28441","postID":"15550","postTitleRaw":"WordPress Importer Redux","cssClasses":"comment byuser comment-author-rmccue bypostauthor odd alt depth-2","parentID":"28440","contentRaw":"Thanks ff782bc1db
download bubble shooter mod apk android 1 com
quick heal pc cleaner free download
minecraft pocket edition free download for pc offline