apostrophe-redirects - npm Package Compare versions

Comparing version 2.3.0 to 2.3.1

CHANGELOG.md

index.js

		@@ -148,3 +148,3 @@ var _ = require('lodash');
		let pathOnly = self.apos.utils.regExpQuote(slug.split('?')[0]);
		let redirectRegEx = new RegExp(`redirect-${pathOnly}.*`);
		let redirectRegEx = new RegExp(`^redirect-${pathOnly}(\?.*)?$`);

		@@ -194,5 +194,5 @@ let redirectResult = self.find(req, { slug: redirectRegEx }, {
		});


		};
		}
		};

package.json

		{
		"name": "apostrophe-redirects",
		"version": "2.3.0",
		"version": "2.3.1",
		"description": "Allows admins to create redirects within an Apostrophe site",
		@@ -5,0 +5,0 @@ "main": "index.js",

README.md

		@@ -68,19 +68,1 @@ This module allows admins to add redirects from one URL to another within an [Apostrophe site](http://apostrophecms.org/).
		Now when you create a new redirect, you have the option to browse for both pages and your pieces in the Apostrophe admin UI.

		## Changelog

		2.3.0: "Ignore query string" option for times when you'd like to match the URL regardless of the `?` and everything that follows it. Thanks to Shaun Hurley for the contribution.

		2.2.0: Implemented polymorphic joins for internal pages which also makes it possible to configure your own pieces for polymorphic joins.

		2.1.0: Disables `apostrophe-site-map` for redirects to prevent more superfluous UI tabs.

		2.0.0: Implemented `statusCode` option and user-editable `statusCode` field allowing the user to choose a permanent or temporary redirect. For bc the default is still `302`. If the `statusCode` option is set to `301` instead, permanent redirects will be the default for new redirects. Existing redirects may be manually switched to `301` if desired.

		0.6.6: Disables `apostrophe-seo` and `apostrophe-open-graph` for redirects to prevent superfluous UI tabs.

		0.6.5: Use express middleware instead of relying on `apos.pages.serve`. This lets redirects happen for files, etc.

		0.6.1: the `redirectSlug` should be `type: 'string'` because the old site may have allowed nonsense in slugs that we do not allow. Also compare to `req.url` so query string matches are allowed.

		0.6.0: initial release.

Improved metrics