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

Description (settings.description) isn't reflected in the Backpack Settings UI #142

Open
emjayess opened this issue Aug 28, 2024 · 1 comment

Comments

@emjayess
Copy link

Bug report

I'm just deploying and employing this package for the first time and in so doing, noticed that while it supplies a database column for describing a setting (settings.description) along with a name field for the setting, only the name is reflected in the UI.

Both name and description are varchars; so with a descriptive enough name/label, the description is a tad redundant. Since it exists tho, it may be desirable to supply it in the UI (as I expected it to be) and thus allow us to keep names brief, and descriptions more explanatory.

What I did:

Installed and deployed this Settings package, and seeded the first couple of settings to view them in Backpack's admin UI.

What I expected to happen:

I expected to see the Setting name, description, and form field while interacting with any given setting.

What happened:

I see only the setting name and form field, but not the description.

What I've already tried to fix it:

Nothing, except to use more descriptive names, to compensate for absence of description in the Settings UI.

Backpack, Laravel, PHP, DB version:

  • Backpack/crud: 6.5
  • Backpack/settings: 3.1
  • Laravel: 10
  • Php: 8.3
  • MySQL: 8.x

setting-screen
Copy link

welcome bot commented Aug 28, 2024

Hello there! Thanks for opening your first issue on this repo!

Just a heads-up: Here at Backpack we use Github Issues only for tracking bugs. Talk about new features is also acceptable. This helps a lot in keeping our focus on improving Backpack. If you issue is not a bug/feature, please help us out by closing the issue yourself and posting in the appropriate medium (see below). If you're not sure where it fits, it's ok, a community member will probably reply to help you with that.

Backpack communication mediums:

  • Bug Reports, Feature Requests - Github Issues (here);
  • Quick help (How do I do X) - Gitter Chatroom;
  • Long questions (I have done X and Y and it won't do Z wtf) - Stackoverflow, using the backpack-for-laravel tag;

Please keep in mind Backpack offers no official / paid support. Whatever help you receive here, on Gitter, Slack or Stackoverflow is thanks to our awesome awesome community members, who give up some of their time to help their peers. If you want to join our community, just start pitching in. We take pride in being a welcoming bunch.

Thank you!

--
Justin Case
The Backpack Robot

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

3 participants