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

Fails to install on docker redmine image #6

Open
phuicy opened this issue Jun 7, 2018 · 6 comments
Open

Fails to install on docker redmine image #6

phuicy opened this issue Jun 7, 2018 · 6 comments

Comments

@phuicy
Copy link

phuicy commented Jun 7, 2018

Using https://github.com/sameersbn/docker-redmine image
I cannot get the risk management plugin to work.

Getting the error:

Migrating redmine_risk_management (Redmine Risk Management plugin) ...
== 6 Add Default Risk Statues: migrating ====================
exited with code 1

thanks,
Guy

@Sousa5
Copy link
Contributor

Sousa5 commented Jun 7, 2018

Hi @phuicy

Thanks for the report.

What version of Redmine is on your setup? Have you follow our installation guide?

Thanks!

@phuicy
Copy link
Author

phuicy commented Aug 13, 2018

the master on the docker image

@alterdaemon
Copy link

I have the same problem.
Redmine 3.4.6

@phuicy
Copy link
Author

phuicy commented Jul 26, 2019

So I found this repo again, and tried to install the plugin and then had an issue, went to check the issues and then found my past self.

The issue appears to be here

RiskStatus.update_all({ is_default: false }, ['id <> ?', id]) if self.is_default?

    RiskStatus.update_all( is_default: false , id : id) if self.is_default?

Works to resolve this issue on this line, but then:

throws:
undefined method `id' for nil:NilClass".

@phuicy
Copy link
Author

phuicy commented Jul 26, 2019

Risk.where(risk_status_id: nil).update_all(risk_status_id: default_risk_status.id)

Commenting out this line seems to fix this issue. Hmmm, I wonder what I broke.

@phuicy
Copy link
Author

phuicy commented Aug 22, 2019

So the server with this hotfixed plugin and many other has now been in production and stable for 30 days. So this hotfix seems safe.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants