Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Entry IDs not resolving into URLs in navigation template

Open
  • Is something wrong?
#15,628 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
laravel, php
Domain
backend, content

Research direction

Start by reading the navigation template example and checking how the url variable handles entry links in navigation blueprints. Reproduce with a navigation item whose link field points to an entry, then trace where the raw entry:: ID is rendered. Done means the front end outputs a navigable URL for that entry; the issue does not name a test or source file.

Written by the indexing model from the issue text.

Description

navigations
Bug description

We have a client that is experiencing an issue where when they link to an entry in a navigation blueprint with a link field, the entry ID doesn't resolve into a URL on the front end. It just shows the raw entry id which isn't navigable.

Looking through the release notes, #15004 is somewhat relevant.

Template:
{{ nav:footer_navigation }} {{ if link_menu == "about" }}<a class="primary d-block fw-600" href="{{ url }}">{{ title }}</a>{{ /if }} {{ /nav:footer_navigation }}

Output:

href="entry::4af6f16d-80e3-42af-ba38-b7818df99593">Contact

How to reproduce

Link to an entry in a navigation blueprint with a link field, the entry ID doesn't resolve into a URL on the front end.

Logs
The only thing in the log:

[2026-10-11 13:12:50] local.DEBUG: Error contacting Outpost: cURL error 28: Operation timed out after 5001 milliseconds with 0 bytes received (see https://curl.se/libcurl/c/libcurl-errors.html) for https://outpost.statamic.com/v3/query
Environment
Environment
Laravel Version: 13.0.0
PHP Version: 8.5.10
Composer Version: 2.10.3
Environment: production
Debug Mode: OFF
Maintenance Mode: OFF
Timezone: America/Chicago
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: pusher
Cache: file
Database: mysql
Logs: stack / single
Mail: postmark
Queue: sync
Session: file

Storage
public/storage: LINKED

Statamic
Addons: 9
License Key: Set
Sites: 4 (site1, site2, site3, site4)
Stache Watcher: Disabled
Static Caching: Disabled
Version: 6.34.0 PRO

Statamic Addons
4rn0/statamic-image-optimizer: 1.3.0
aryehraber/statamic-color-extractor: 2.1.0
isapp/statamic-honeypot: 6.0.0
jacksleight/statamic-bard-texstyle: 4.2.1
mitydigital/feedamic: 3.0.13
mitydigital/sitemapamic: 3.5.1
rias/statamic-redirect: 4.2.1
statamic/seo-pro: 7.14.1
stillat/antlers-layouts: 2.1.1
Installation

Fresh statamic/statamic site via CLI

Additional details

No response

Dominant language
PHP
Stars
4.9k
Forks
647
Avg merge
1d 20h
Merged PRs (30d)
113

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from statamic/cms

All issues in statamic/cms

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.