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

Impossible to create color_picker fields with different configuration #4844

Closed
CodaKris opened this issue Dec 15, 2022 · 2 comments
Closed
Labels

Comments

@CodaKris
Copy link

Bug report

color_picker.blade.php uses
@loadOnce('bpFieldInitColorPickerElement')

What I did

CRUD::addField([
'type' => 'color_picker',
'name' => 'background_colour',
'default' => 'rgba(0, 0, 0, 0)',
'color_picker_options' => [
'useAlpha' => true,
'format' => null,
'horizontal' => true,
]
]);
CRUD::addField([
'type' => 'color_picker',
'name' => 'border_colour',
'default' => 'rgba(0, 0, 0)',
'color_picker_options' => [
'useAlpha' => false,
'format' => null,
'horizontal' => true,
]
]);

What I expected to happen

Have 1 field that allows transparency and 1 that doesn't.

What happened

They both allow transparency.

What I've already tried to fix it

Worked around it by overriding the default color_picker.blade.php file, remove the load once and give each init function a unique name.

Is it a bug in the latest version of Backpack? Yes

After I run composer update backpack/crud the bug... is it still there? Yes

Backpack, Laravel, PHP, DB version 5.4.11,8.x,8.1,mysql 5.7

When I run php artisan backpack:version the output is: 5.4.11@ffbadcdb6478822646600b2cd763490caa927155

@welcome
Copy link

welcome bot commented Dec 15, 2022

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 channels:

  • 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;
  • Showing off something you've made, asking for opinion on Backpack/Laravel matters - Reddit;

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

@pxpm
Copy link
Contributor

pxpm commented Dec 20, 2022

Thanks @greatsaltlake for the report 🙏

You are totally right! At the moment that's not possible.

I've submitted a PR to backpack PRO that will enable this to work.

It's already merged and you can get it with a composer update. 💪

Wish you the best 🎅

@pxpm pxpm closed this as completed Dec 20, 2022
@pxpm pxpm moved this to Done in This week Dec 20, 2022
@tabacitu tabacitu removed this from This week Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants