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

[6.x]: Settings utilities links route to non-existent /Index pages

Open
#19,214 4 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
Quiet
Tech stack
php
Domain
backend

Research direction

Reproduce the issue in the Craft CMS control panel by opening Settings and selecting Sections, Entry Types, and Fields, then inspect the browser console. Trace the links that produce the settings/sections/Index, settings/entry-types/Index, and settings/fields/Index routes. Done means each selected settings page opens without a Page not found error.

Written by the indexing model from the issue text.

Description

bug
What happened?
Description

In Craft CMS 6.0.0-alpha.10, clicking some Settings utility items causes a frontend console error and the page does not open correctly.

The console shows errors like:

Uncaught (in promise) Error: Page not found: settings/sections/Index
Uncaught (in promise) Error: Page not found: settings/entry-types/Index
Uncaught (in promise) Error: Page not found: settings/fields/Index

Steps to reproduce
  1. Log in to the Craft CMS control panel.
  2. Go to Settings.
  3. Click Sections, Entry Types, or Fields.
  4. Check the browser console.
Expected behavior

The selected settings page should open without any console errors.

Actual behavior

The page fails to load and the console reports Page not found errors for routes ending in /Index.

Craft CMS version

6.0.0-alpha.10

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions
Image
Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
13h 8m
Merged PRs (30d)
250

Getting set up

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 craftcms/cms

All issues in craftcms/cms

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.