No events trigger when using exactMatch redirect about craft-retour HOT 4 CLOSED

Addressed in: 8a2e4ed & 69b4a3e

Craft CMS 3:

You can try it now by setting your semver in your composer.json to look like this:

    "nystudio107/craft-retour": "dev-develop as 3.2.9",

Then do a composer clear-cache && composer update

…..

Craft CMS 4:

You can try it now by setting your semver in your composer.json to look like this:

    "nystudio107/craft-retour": "dev-develop-v4 as 4.1.11",

Then do a composer clear-cache && composer update

from craft-retour.

Addressed in: 72af1f3 & 0f62cc8

Craft CMS 3:

You can try it now by setting your semver in your composer.json to look like this:

    "nystudio107/craft-retour": "dev-develop as 3.2.9",

Then do a composer clear-cache && composer update

…..

Craft CMS 4:

You can try it now by setting your semver in your composer.json to look like this:

    "nystudio107/craft-retour": "dev-develop-v4 as 4.1.11",

Then do a composer clear-cache && composer update

from craft-retour.

Thanks for this, it was the other route I was thinking of but the code seemed like it was perfect not to be used 😄

@khalwat - I can see the before and after events but can't see the resolved event (which is the one I'm actually trying to target).

Thinking that one will need to sit in the findRedirectMatch() method to match how it's used in resolveRedirect()? Also, should that event trigger when a cached redirect is returned too? It has resolved to get a redirect after all.

I'll avoid the PR embarrassment this time 😅

from craft-retour.

Ah my bad, I'll get that in there.

And no, those events shouldn't fire if they are cached.

from craft-retour.