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

[Bug]: Text Input disabled property not working in settingsDisplay: tabs mode #2094

Open
gpsblues opened this issue Mar 11, 2025 · 0 comments

Comments

@gpsblues
Copy link

Operating system

Win11

Publii version

0.46.4 (build 17047)

Post editor

None

Bug description

The disabled:true property for a Text Input field within the plugin.json file does not function as expected when settingsDisplay is set to tabs.

The field remains editable. However, when settingsDisplay is set to fieldsets, the field is correctly disabled and appears non-editable.

"settingsDisplay": "tabs",
"config": [
    {
        "name": "fieldName",
        "label": "Field name",
        "group": "Group name",
        "value": "default value",
        "type": "text",
        "disabled": true
    }
]

Steps to reproduce

  1. Define a Text Input field in the plugin.json file with the disabled property set to true.
  2. Set settingsDisplay to "tabs".
  3. Observe that the Text Input field is still editable.
  4. Change settingsDisplay to "fieldsets".
  5. Observe that the Text Input field is now correctly disabled and non-editable.

Relevant log output

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

No branches or pull requests

1 participant