Closed NiTRoeSE closed 4 months ago
I'm seeing the same behaviour without having a custom CSS file.
Things I tried:
bundle exec vite upgrade
as indicated by the bundle install
prompt: no changenode_modules
directory as per forum, which also includes more possible commands to run: fixed this problem, but made me run into rollup errorsyarn cache clean && rake vite:clobber
: Same rollup error. In the end, I had to manually fix the incorrect import in the ts file to match the released versionSo tl;dr: remove your node_packages and you should be fine.
Things I tried:
* Ran `bundle exec vite upgrade`as indicated by the `bundle install` prompt: no change * Removed the `node_modules` directory [as per forum](https://community.zammad.org/t/error-during-update-from-6-2-to-6-3/14044/9), which also includes more possible commands to run: fixed this problem, but made me run into [rollup errors](https://community.zammad.org/t/error-vite-plugin-pwa-build-vite-rollup-failed-to-resolve-import/14730/4) * Ran `yarn cache clean && rake vite:clobber`: Same rollup error. In the end, I had to manually fix the incorrect import in the ts file to match the [released version](https://github.com/zammad/zammad/blob/6.3.1/app/frontend/apps/mobile/components/Form/fields/FieldFile/FieldFileInput.vue#L7)
So tl;dr: remove your node_packages and you should be fine.
Thanks for investigating and the hint! Following fixed it for me without any other errors:
rm -rf /opt/zammad/node_modules/
zammad run yarn cache clean
zammad run rake vite:clobber
zammad run rake assets:precompile
/closed
Used Zammad Version
6.3.1-1720073544.96130907.jammy
Environment
Actual behaviour
Running
zammad run rake assets:precompile --trace
fails with error message:Expected behaviour
Running
zammad run rake assets:precompile --trace
works.Steps to reproduce the behaviour
/opt/zammad/app/assets/stylesheets/custom/custom.css
and/or modify/opt/zammad/app/assets/javascripts/app/views/login.jst.eco
zammad run rake assets:precompile --trace
to apply your changesSupport Ticket
No response
I'm sure this is a bug and no feature request or a general question.
yes