-
Notifications
You must be signed in to change notification settings - Fork 119
Fix Redmine 5.0 / Rails 6.1 / Zeitwerk #233
base: master
Are you sure you want to change the base?
Conversation
Added fixes for REST API. |
I get the following error when navigating to
|
I merged the migration to GitHub Actions in #236. It is failing for now, but if you rebase this PR on top of master, then the tests should eventually pass. |
controller_issues_new_after_save raises "ActiveRecord::StaleObjectError Attempted to update a stale object: Issue." in Rails 6.1. This exception can be suppressed by calling reload first, but the existence of this method seems unnecessary. Because it seems that after_save does not call reload from Redmine 4.0.
… expected 1))" (#29914). See: redmine/redmine@7de9711
@PowerKiKi Wow, great job! |
@taikii if you are able to get this working, I will merge it. However, I won't spend more time myself on this. I will migrate to https://github.com/AlphaNodes/additional_tags. It can migrate data from |
@PowerKiKi It seems the error in CI is not caused by this PR. Sorry I don't have time to investigate the error. |
Fair enough 👍 Maybe someone else can help fix the CI, and then I'll merge it. |
update_attributes was removed on Rails 6.1.
controller_issues_new_after_save raises "ActiveRecord::StaleObjectError Attempted to update a stale object: Issue." in Rails 6.1.
This exception can be suppressed by calling reload first, but the existence of this method seems unnecessary.
Because it seems that after_save does not call reload from Redmine 4.0.
Regards