Open danowar2k opened 1 year ago
Sorry, I'm using additional_tags, too, so I botched the version number.
Hi @danowar2k, I cannot reproduce this warnings with the current additionals version and ruby 2.7.6. I also used symlinks for testing.
RAILS_ENV=production RUBYOPT='' rails s
=> Booting Puma
=> Rails 6.1.7.2 application starting in production
=> Run `bin/rails server --help` for more startup options
[17461] Puma starting in cluster mode...
[17461] * Puma version: 6.0.2 (ruby 2.7.6-p219) ("Sunflower")
[17461] * Min threads: 2
[17461] * Max threads: 5
[17461] * Environment: production
[17461] * Master PID: 17461
[17461] * Workers: 2
[17461] * Restarts: (✔) hot (✖) phased
[17461] * Preloading application
[17461] * Listening on http://0.0.0.0:3000
[17461] Use Ctrl-C to stop
[17461] - Worker 0 (PID: 17479) booted in 0.01s, phase: 0
[17461] - Worker 1 (PID: 17481) booted in 0.0s, phase: 0
Can you try it with the latest additionals version?
PS: we do not offer support for old version with Redmine 4.x.
With Redmine 5.0.4 on Ruby 3.0 and additionals 3.0.8, the messages don't crop up.
I don't know if this is removed in later versions, but I've installed Additionals 3.0.5.2 on my Redmine 4.2.8, and when starting the service my logs say
I install Redmine plugins by linking the version directories inside the Redmine plugins dir. Is that bad practice or why does it seem like the additionals plugin sees redefinitions by both looking at the real plugin dir and the symlinked dir?
Meaning: /var/redmine/code/4.2.8/plugins/additionals is a symlink to /var/redmine/plugins/additionals/3.0.5.2