craftcms / craftcms/cms

[5.x]: Left behind redactor references

Open
#17,891 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PHP
Stars
3.6k
Forks
705
Avg merge
1d 5h
Merged PRs (30d)
134

Description

What happened?
Description

We've fully migrated a craft 4 to 5 site. Redactor fields have all been converted to CKEditor. There are no redactor fields anywhere in the site. Searching the yaml files I still see references to craft/redactor/field

No problems exist that I can see. There are no errors, and all of the fields seem to work correctly so this issue has no symptoms other than the weird Yaml references. Why are they still there? Redactor has been uninstalled.

Steps to reproduce
  1. Migrate to craft 5 from 4.
  2. Migrate Redactor to CK
  3. Remove all redactor fields
  4. Uninstall Redactor
  5. Search Yaml files for "craft\redactor\Field"
Expected behavior

No references to redactor in Yaml config

Actual behavior

Lots of references in Yaml config.

Craft CMS version

5.8.16

PHP version

No response

Operating system and version

Servd

Database type and version

No response

Image driver and version

No response

Installed plugins and versions
Image

Contributor guide

Open the contributing guide

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.

Research direction

Start by reproducing the Craft 4-to-5 migration described in the issue, including Redactor-to-CKEditor migration and Redactor removal. Search the resulting YAML configuration for "craft\redactor\Field" and compare the references with the installed fields; done means determining why they remain and confirming whether the configuration is cleaned up without errors.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.