craftcms / craftcms/cms

No longer required fields, are still required

Open
#3,589 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Description

After making some fields as not required anymore, that fields when empty are considered invalid. This is happening at least for categories

Steps to reproduce
  1. Add required fields
  2. Create a category
  3. Remove the requirement rule on that fields
  4. Make the fields empty
  5. Save
Additional info

PHP version 7.1.23
MySQL 5.7.24
GD 7.1.23
Craft Pro 3.0.35

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 category workflow described in the issue: make fields required, create a category, remove the requirement, clear the fields, and save. The fix is complete when fields whose requirement was removed can remain empty without being rejected during category saving.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.