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

Custom fields asset versioning #6500

Open
vitaliyb opened this issue Aug 14, 2024 · 1 comment
Open

Custom fields asset versioning #6500

vitaliyb opened this issue Aug 14, 2024 · 1 comment
Labels
Milestone

Comments

@vitaliyb
Copy link

vitaliyb commented Aug 14, 2024

  • Laravel Version: 10.48.16
  • Nova Version: 4.34.3
  • PHP Version: 8.2

Description:

Recently, our team encountered a significant problem. We have multiple custom [fields (https://nova.laravel.com/docs/customization/fields.html)

After making adjustments to some fields and pushing changes to production, many of our clients did not receive refreshed assets and experienced crashes while using our product.

Currently, we are forced to manually calculate the MD5 hash of assets and add it as a postfix for the script/style name. However, this is not an ideal solution as it is custom.

Perhaps it would be a good idea to implement such mechanisms inside Nova?
If script/style content is changed - generate version
href="/nova-api/styles/field-$hash"
instead of
href="/nova-api/styles/field"

This will ensure that assets are always up to date.

@webard
Copy link

webard commented Aug 15, 2024

It should definitely be in core, but for now you can try https://github.com/Muetze42/nova-assets-versioning

@crynobone crynobone added the next label Aug 15, 2024
@crynobone crynobone added this to the 5.x milestone Aug 15, 2024
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

3 participants