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

Issue with Sub-Text Field on Navigation Menu After CKEditor Conversion

Open
#283 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
backend

Research direction

No repository files or tests are named. Start by reproducing the dashboard navigation-menu edit flow with Craft 4.11.1, PHP 8.2, MySQL 8.0.35, and the listed plugin version; trace why the CKEditor-converted sub-text field is absent from the editor while present on the front end. Done means existing menu sub-text is visible and editable in the dashboard.

Written by the indexing model from the issue text.

Description

bug
Description

We wanted to raise this issue we've encountered after converting fields from the Reactor plugin to CKEditor. The sub-text field is not displaying on the navigation menu. While it appears correctly in the field settings and is linked to CKEditor as expected, it is not showing up on the navigation menu itself. However, the data is correctly displayed on the front end since it is being fetched from the database.

At the moment, we're unable to modify the existing data on the menu. We are investigating this further and will keep you updated.
sub-text-not-showing
image

Steps to reproduce
  1. Login to the dashboard
  2. Select the navigation menu
  3. Edit the menu
  4. Unable to see the sub-text field
Additional info
  • Craft version: 4.11.1
  • PHP version: 8.2
  • Database driver & version: MySQL 8.0.35
  • Plugins & versions: 3.8.9
Dominant language
PHP
Stars
47
Forks
32
Avg merge
3d 20h
Merged PRs (30d)
3

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/ckeditor

All issues in craftcms/ckeditor

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.