Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[4.0.2]: Order of lightswitch field labels should be reversed in field configuration to be consistent with order displayed in entry edit form #11259

Closed
richhayler opened this issue May 18, 2022 · 2 comments

Comments

@richhayler
Copy link

richhayler commented May 18, 2022

What happened?

Description

The labels for the opposing lightswitch states in the field configuration page are opposite to how the field is presented in an entry form. The order of the labels should be reversed in the field configuration page to be consistent.

In the example below the field options put the "on" state before the "off" state but when the toggle is presented within an entry edit page the "off" state is presented before the "on" state.

CleanShot 2022-05-18 at 20 36 14@2x

CleanShot 2022-05-18 at 20 34 21@2x

Craft CMS version

4.0.2

@richhayler richhayler changed the title [4.x]: Order of lightswitch field labels should be reversed in field configuration for consistency [4.x]: Order of lightswitch field labels should be reversed in field configuration to be consistent with order displayed in entry edit form May 18, 2022
@richhayler richhayler changed the title [4.x]: Order of lightswitch field labels should be reversed in field configuration to be consistent with order displayed in entry edit form [4.0.2]: Order of lightswitch field labels should be reversed in field configuration to be consistent with order displayed in entry edit form May 18, 2022
@brandonkelly
Copy link
Member

Changed for the next v3 and v4 releases.

@brandonkelly
Copy link
Member

3.7.43 and 4.0.3 are out now with that change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants