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

[Feature Request]: Hide some partial views ("new" buttons) or help removing them from the code #15876

Open
eickeh opened this issue Nov 24, 2024 · 2 comments

Comments

@eickeh
Copy link

eickeh commented Nov 24, 2024

Is your feature request related to a problem? Please describe.

Hi there, thanks for everything!
We use the attributes of models a lot to not have to set them for each corresponding asset. That includes some custom attribute, of which we some want to pre-fill per model. That's super useful!
However, when creating a new asset and use the "new" button we lack the possibility to pre-fill some of wanted attributes.

Describe the solution you'd like

So it would be really nice to be able to configure somewhere to either
a) open a new tab to get to the full-fledged "new model" view or
b) hide the button from the "new asset" view.

Describe alternatives you've considered

I would already be happy to just throw that out manually in the code. I tried some things but either I'm doing it wrong or just didn't succeed.
What I tried:

  • In the code in some partials there is a condition only to show this if the "hide_new" variable is not set. However, I couldn't find a way to set it.
  • Just setting the whole condition to "false" in "resources/views/partials/forms/edit/model-select.blade.php", which somehow also didn't work.
    I've tried to clear some caches with artisan like cache:clear, config:clear and view:clear but none did work.

Can you help me achieve something of this? =)

Additional context

No response

Copy link

welcome bot commented Nov 24, 2024

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it. We get a lot of issues on this repo, so please be patient and we will get back to you as soon as we can.

@eickeh
Copy link
Author

eickeh commented Dec 5, 2024

Doesn't anyone have a clue? It would really also be enough to alter the php sources on our server to remove it. However, I had no luck with that so far.

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