hello try to modify the huraga template, but when you modify the base CSS of the template manually it gives an ingrity error SHA-384, I put image. How can I clone or modify the huraga template without causing a crash in the client area
I certainly loved this implementation I will also do it in my future developments
(12-30-2024, 06:30 PM)dev_1239 Wrote: [ -> ]hello try to modify the huraga template, but when you modify the base CSS of the template manually it gives an ingrity error SHA-384, I put image. How can I clone or modify the huraga template without causing a crash in the client area
I certainly loved this implementation I will also do it in my future developments
The lack of templates makes the project not very popular if we managed to modify the template I would surely even want to use it. Hopefully someone knows how to do it. By the way, they are doing a great job in Foosbilling.
I have not been able to repair this failure the only template that works well is the huraga and because I modified the css it has crashed and gives a token error I am if anyone knows how to fix it I will appreciate it.
I'm already thinking about moving to another platform there is practically no documentation of anything to use that token.
The Error is: "None of the “sha384” hashes in the integrity attribute match the content of the subresource. The computed hash is"
and block
https://x/themes/huraga/build/js/huraga-....146798.js
https://x/themes/huraga/build/css/huraga...6cd008.css
The CSS for our default themes are built with webpack and can't be modified after the fact.
There's content integrity hashes that we actually can't remove and are forced by a dependency, so any change to them will cause that hash to be broken.
Even if we could remove that, any direct changes would be lost the moment you updated.
You can create a custom default_layout template (in a html_custom folder as
described here at item #1) and then replace the default CSS inclusion with your own
The line that includes our default CSS:
Code:
{{ encore_entry_link_tags('huraga') }}
You could also split huraga off into your own theme, or if these are changes which would be widely applicable you can modify the source code directly and submit a pull request to get them shipped within FOSSBilling.
The relevant source files are here:
https://github.com/FOSSBilling/FOSSBilli...aga/assets.
There's also paid themes which from my understand work by being injected into the existing theme, though I can't personally comment on the quality of this, I just know it exists.
https://www.zomex.com/products/fossbilling-templates/
(01-01-2025, 09:52 PM)BelleNottelling Wrote: [ -> ]The CSS for our default themes are built with webpack and can't be modified after the fact.
There's content integrity hashes that we actually can't remove and are forced by a dependency, so any change to them will cause that hash to be broken.
Even if we could remove that, any direct changes would be lost the moment you updated.
You can create a custom default_layout template (in a html_custom folder as described here at item #1) and then replace the default CSS inclusion with your own
The line that includes our default CSS:
Code:
{{ encore_entry_link_tags('huraga') }}
You could also split huraga off into your own theme, or if these are changes which would be widely applicable you can modify the source code directly and submit a pull request to get them shipped within FOSSBilling.
The relevant source files are here:
https://github.com/FOSSBilling/FOSSBilli...aga/assets.
There's also paid themes which from my understand work by being injected into the existing theme, though I can't personally comment on the quality of this, I just know it exists.
https://www.zomex.com/products/fossbilling-templates/
I see that I have to learn a little more about the system, It helped me a lot to understand how the system works. Thanks a lot
