Describe your question/issue in detail
Impacted feature
Linked relationship document has broken resolved URL (notice the url
key value):
{
"id": "aIHjYREAAB8ADpKj",
"type": "page",
"tags": [redacted],
"lang": "en-us",
"slug": [redacted],
"first_publication_date": "2025-07-24T07:40:52+0000",
"last_publication_date": "2025-07-24T07:51:20+0000",
"uid": "lorem-ipsum",
"url": ">&<00029aH5SrREAACMACQZl%%parent_path>&<00018aH5SrREAACMACQZl%%/lorem-ipsum",
"link_type": "Document",
"key": "c24cd137-cd4e-48e5-9e07-94339fd9fc0f",
"isBroken": false,
"text": "Learn More"
}
Route definition:
{
type: 'page',
lang: 'en-us',
path: '/:parentpath?/:path?/:uid',
resolvers: {
parentpath: 'path.parent_path',
path: 'path',
},
},
To get this object (link field), we go through two content relationships: Slice -> Group field (relation 1) -> Group field (relation 2) -> Link.
What's odd is that we already have a footer with page links and those links are not broken. This makes me think the issue may be related to the newest Field Picker in Slice Machine.
What steps have you taken to resolve this issue already?
- compared with another project of mine where the solution is pretty much the same (the only difference is in the naming – Paths being Page Categories) and it works over there perfectly fine, although I haven't tested it with such deep nesting
- re-published path documents and page documents for potentially fixing refs in Prismic's database
- added/removed
/:lang?
part in the path
Errors
Just a broken link.
Your Role
Frontend developer.
Hosting provider
All happening locally.
Package.json file
{
"name": [redacted],
"version": "0.1.0",
"private": true,
"scripts": {
"dev": "concurrently \"npm:next:dev\" \"npm:slicemachine\" --names \"next,slicemachine\" --prefix-colors blue,magenta",
"next:dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint",
"lint:fix": "prettier --write . && next lint --fix",
"slicemachine": "start-slicemachine"
},
"dependencies": {
[redacted],
"@gsap/react": "^2.1.0",
"@next/bundle-analyzer": "^15.2.1",
"@next/third-parties": "^15.1.6",
"@prismicio/client": "^7.16.1",
"@prismicio/helpers": "^2.3.9",
"@prismicio/next": "^1.7.1",
"@prismicio/react": "^3.2.1",
[redacted],
"@tailwindcss/aspect-ratio": "^0.2.1",
"@tanstack/eslint-plugin-query": "^5.78.0",
"@tanstack/react-query": "^5.80.6",
"@typeform/embed-react": "^2.21.0",
"email-validator": "^2.0.4",
"embla-carousel-auto-scroll": "^8.6.0",
"embla-carousel-autoplay": "^8.5.1",
"embla-carousel-react": "^8.5.1",
"graphql": "^16.11.0",
"graphql-request": "^7.2.0",
"gsap": "^3.12.5",
"intl-tel-input": "^17.0.13",
"next": "14.1.4",
"next-seo": "^6.5.0",
"react": "^18",
"react-dom": "^18",
"react-hook-form": "^7.57.0",
"react-select": "^3.2.0"
},
"devDependencies": {
"@slicemachine/adapter-next": "^0.3.81",
"@types/node": "^20",
"@types/react": "^18",
"@types/react-dom": "^18",
"autoprefixer": "^10.0.1",
"concurrently": "^9.1.2",
"netlify-cli": "^17.21.1",
"postcss": "^8",
"prettier": "^3.1.0",
"slice-machine-ui": "^2.17.1",
"tailwindcss": "^3.3.0",
"typescript": "^5"
}
}
Steps to reproduce
To get the object with a broken URL (link field), we go through two content relationships: Slice -> Group field (relation 1) -> Group field (relation 2) -> Link.
What's odd is that we already have a footer with page links and those links are not broken. This makes me think the issue may be related to the newest Field Picker in Slice Machine.