Philipp Meyer f3844ee533 fix(next): email verification not working due to incorrect token url parsing (#11439) ...

### What?
This PR reverts a presumably accidental change made in
[b80010b1a1](b80010b1a1),
that broke the email verification feature in v3.24.0 and onwards.
### Why?
Through the missing verify in `const [collectionSlug, verify, token] =
params.segments`, the token value was always the string `verify`

2025-02-28 00:05:05 +00:00

..

elements

fix(next): disables active nav item (#11434)

2025-02-27 15:21:28 -05:00

exports

chore: temporarily revert 10597 (#10718)

2025-01-22 16:36:54 -05:00

layouts/Root

perf(next): reduce getNavPrefs calls from 3 to 1 per page load (#11318)

2025-02-21 05:17:39 +00:00

routes

fix(next): pre-flight OPTIONS request errors from the graphql endpoint (#11103)

2025-02-11 13:22:16 -05:00

scss

feat(ui)!: scope all payload css to payload-default layer (#8545)

2024-10-04 13:02:56 -06:00

templates

feat(ui): exposes context of the view being rendered on the server (#10620)

2025-01-16 15:44:09 -05:00

utilities

perf: ensure fetching and updating preferences doesn't cause transaction errors and is done correctly (#11311)

2025-02-21 01:53:56 +00:00

views

fix(next): email verification not working due to incorrect token url parsing (#11439)

2025-02-28 00:05:05 +00:00

config.ts

feat!: prebundle payload, ui, richtext-lexical (#6579)

2024-06-17 14:25:36 -04:00

esbuildEntry.ts

feat!: upgrade minimum react, react-dom, @types/react and @types/react-dom versions to match exactly what Next.js is using, various dependency cleanup (#7106)

2024-07-11 18:33:45 +00:00

index.js

stuff

2024-03-19 11:33:32 -04:00

withPayload.js

fix(next): use correct hmr url if assetPrefix is set in next config (#10859)

2025-02-22 00:27:07 +00:00