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] Call to undefined function views_path() WHEN STTING NEW CUSTOM THEME #5694

Closed
azeddine-hf opened this issue Oct 17, 2024 · 8 comments · Fixed by Laravel-Backpack/docs#611
Labels

Comments

@azeddine-hf
Copy link

in documentation :
The my-cool-theme/inc/theme_styles.blade.php file should hold all custom CSS that your theme needs. For example:

{{-- You can load files directly from CDNs, they will get cached and loaded from local --}}
@basset('https://cdn.jsdelivr.net/npm/[email protected]/dist/css/bootstrap.min.css')

{{-- You can also load files from any place in your application directories --}}
@basset(views_path('my-cool-theme/assets/css/extra.css'))

{{-- You can also write inline CSS blocks --}}
@bassetBlock('my-cool-theme/custom-styling')

<style> .something { border: 1px solid red; } </style>

@endBassetBlock
but in usage shows an error : Call to undefined function views_path()

Copy link

welcome bot commented Oct 17, 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 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 Oct 17, 2024

yeah, you right @azeddine-hf, thanks for the heads up 🙏

please use resource_path('assets/css/my-cool-theme/whatever.css'). (need to put the whatever.css in resources/assets/css/my-cool-theme/ directory.

I will send a PR to fix the docs 👍

@azeddine-hf
Copy link
Author

azeddine-hf commented Oct 17, 2024

@pxpm how can i set it on blade file :
{{ resource_path('assets/css/my-cool-theme/whatever.css') }} LIKE THIS or inside <link ... /> ??

@pxpm
Copy link
Contributor

pxpm commented Oct 17, 2024

On blade you use @basset() directive 👍 Basset will output the correct import tag for it, either link, script etc. eg:

@basset(base_path('vendor/backpack/crud/src/resources/assets/libs/jquery.mjs.nestedSortable2.js'))

@azeddine-hf
Copy link
Author

@pxpm please theme_scripts.blade.php doesn't load why ?

@pxpm
Copy link
Contributor

pxpm commented Oct 17, 2024

@pxpm please theme_scripts.blade.php doesn't load why ?

No clue, where do you have the file ? How are you including it ?

It's just a blade file, it should just load as any other blade file in the application 🤷

@azeddine-hf
Copy link
Author

@pxpm the theme_styles it included automaticly but the theme_scripts does not
i have include it in default.blade.php file manually thank you @pxpm

@pxpm
Copy link
Contributor

pxpm commented Oct 17, 2024

Yes, in the layout it's where we include them: https://github.com/Laravel-Backpack/theme-coreuiv2/blob/11ec0cbaecefd3272601a7fb0d32457533a09ce6/resources/views/layouts/top_left.blade.php#L50

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

Successfully merging a pull request may close this issue.

2 participants