=== WordPress Importer === Contributors: wordpressdotorg Donate link: https://wordpressfoundation.org/donate/ Tags: importer, wordpress Requires at least: 3.6 Tested up to: 4.9 Stable tag: 0.6.4 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html Import posts, pages, comments, custom fields, categories, tags and more from a WordPress export file. == Description == The WordPress Importer will import the following content from a WordPress export file: * Posts, pages and other custom post types * Comments * 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](https://codex.wordpress.org/Importing_Content#WordPress) == Installation == The quickest method for installing the importer is: 1. Visit Tools -> Import in the WordPress dashboard 1. Click on the WordPress link in the list of importers 1. Click "Install Now" 1. 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 1. Activate the plugin through the 'Plugins' menu in WordPress 1. Go to the Tools -> Import screen, click on WordPress == Changelog == = 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 = * Add `wp_import_existing_post` filter, see [Trac ticket #33721](https://core.trac.wordpress.org/ticket/33721). = 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](https://core.trac.wordpress.org/ticket/15197) = 0.1 = * Initial release == Upgrade Notice == = 0.6 = Support for exports from WordPress 3.4. = 0.5.2 = Fix incorrect error message when the export file could not be uploaded. = 0.5 = Import comment meta and other minor bugfixes and enhancements. = 0.4 = Bug fixes for attachment importing and other small enhancements. = 0.3 = Upgrade for a more robust and reliable experience when importing WordPress export files, and for compatibility with WordPress 3.1. == Frequently Asked Questions == = 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](https://codex.wordpress.org/Importing_Content#Before_Importing) == Filters == 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 {"id":2409,"date":"2023-07-24T15:16:59","date_gmt":"2023-07-24T15:16:59","guid":{"rendered":"https:\/\/reflexthebest.com\/why-canadian-inflation-is-about-to-move-higher\/"},"modified":"2023-07-24T15:17:00","modified_gmt":"2023-07-24T15:17:00","slug":"why-canadian-inflation-is-about-to-move-higher","status":"publish","type":"post","link":"https:\/\/reflexthebest.com\/why-canadian-inflation-is-about-to-move-higher\/","title":{"rendered":"Why Canadian Inflation Is About to Move Higher"},"content":{"rendered":"


\n<\/p>\n

\n

<\/a>Last week Statistics Canada confirmed<\/a> that our Consumer Price Index (CPI) dropped to 2.8% in June, its lowest level in more than two years.<\/p>\n

Anyone keeping an eye on Canadian mortgage rates may have been surprised when the Government of Canada (GoC) bond yields barely reacted.<\/p>\n

That\u2019s likely because there are some compelling data to support the belief that inflation is headed higher in the months ahead.<\/p>\n

To understand why inflation has almost certainly bottomed over the near term, we need to take a more detailed look at the significant disinflationary impact that base effects have had on our recent CPI data.<\/p>\n

Let\u2019s start with a quick review of Stats Can\u2019s definition of base effects:<\/p>\n

A base-year effect refers to the impact that price movements from\u00a012\u00a0months earlier have on the current month\u2019s headline consumer inflation. When a large\u00a01-month upward price change in the base month stops influencing or falls out of the\u00a012-month price movement, this has a downward effect on headline\u00a0CPI\u00a0in the current month.<\/em><\/p>\n

Until now, most of the drop in our CPI from its peak of 8.1% down to its new low of 2.8% last month has been caused by higher price-change months rolling out of the back end of the CPI data set. This base-effect tailwind has made our current inflation look milder than it really is. But that is about to change.<\/p>\n

Here is a table that summarizes the monthly CPI data (rounded) that were used to calculate our headline CPI results thus far in 2023.The first line in the table above shows that our CPI rose by 0.9% in January 2022 on a month-over-month basis (see number highlighted in red), and our CPI increased by 0.5% month-over-month in January 2023 (see number highlighted in green).\"Canada<\/a><\/p>\n

When Stats Can added the January 2023 month-over-month result to our CPI data set (+0.5%), it also removed the January 2022 month-over-month result (+0.9%). The net result was that our headline CPI dropped to 5.9% in January 2023. While that was a decrease from the month prior, it still left our CPI at a multiple of the BoC\u2019s 2% target.<\/p>\n

Let\u2019s now compare the six monthly readings that have been dropped from our headline CPI data set thus far in 2023 (highlighted in red) to the new monthly readings that were added in their place (highlighted in green).<\/p>\n

The six monthly readings that were dropped averaged +1.0%. The six new monthly readings that were added averaged +0.43%. That means base effects have reduced our CPI by an average of 0.57% over the past six months.<\/p>\n

Next, let\u2019s look at the numbers that will fall out of our headline CPI data set over the next six months (see numbers highlighted in yellow). They average out to +0.02%. For the base effect to have the same dampening impact on our CPI over next six months that it had over the previous six months, our monthly CPI readings will need to average -0.55%. (Spoiler alert: That\u2019s not happening.)<\/p>\n

This is a big reason why BoC Governor Macklem recently noted that \u201cthe downward momentum of inflation is waning\u201d and why he warned that \u201cthe progress toward price stability could stall\u201d.<\/p>\n

Now let\u2019s try to estimate a range that our headline CPI may be headed toward over the remainder of the year.<\/p>\n

The graph below shows what will happen to our headline CPI if we average monthly readings of 0.0%, +0.1%, +0.2%, +0.3% and +0.4% for the next six months.\"Canada<\/a>In four out of the five scenarios, inflation finishes the year above its current level of 2.8% and, in three of the five scenarios, significantly so.<\/p>\n

The next question to ask is, are these assumptions about CPI readings over the next six months reasonable?<\/p>\n

Consider the following:<\/p>\n