Skip to content

Commit f3844ee

Browse files
authored
fix(next): email verification not working due to incorrect token url parsing (#11439)
### What? This PR reverts a presumably accidental change made in [b80010b](b80010b), 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`
1 parent c21dac1 commit f3844ee

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

packages/next/src/views/Verify/index.tsx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ export { generateVerifyMetadata } from './meta.js'
1414
export async function Verify({ initPageResult, params, searchParams }: AdminViewServerProps) {
1515
// /:collectionSlug/verify/:token
1616

17-
const [collectionSlug, token] = params.segments
17+
const [collectionSlug, verify, token] = params.segments
1818
const { locale, permissions, req } = initPageResult
1919

2020
const {

0 commit comments

Comments
 (0)