dr-itz / redmine_workflow_enhancements

Redmine workflow enhancements. UNMAINTAINED
GNU General Public License v2.0
27 stars 29 forks source link

DB errors after install #4

Closed rgeddes closed 10 years ago

rgeddes commented 10 years ago

Redmine 2.5 Ruby 2.0 Ubuntu 14.04 Thin ruby webserver

After install, getting errors in log:

Processing by WorkflowsController#edit as HTML Parameters: {"utf8"=>"✓", "role_id"=>"3", "tracker_id"=>"4", "used_statuses_only"=>"1"} Current user: rgeddes (id=1) Completed 500 Internal Server Error in 87.0ms

ActiveRecord::StatementInvalid (Mysql::Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1: SELECT issue_statuses.* FROM issue_statuses WHERE issue_statuses.id IN (1, 9, 2, 11, 3, 12, 4, 7, 5, 6, 10, 13, )): app/controllers/workflows_controller.rb:48:in `edit'

dr-itz commented 10 years ago

Just pushed a fix. The code was obviously wrong, but I wonder why my MySQL on Ubuntu 12.04 works with it? Anyway, please test. Thanks.

rgeddes commented 10 years ago

Got it installed without errors in the logs.

Maybe this is a version issue because I've seen it in another plugin, but 2 errors came up in the browser:

The browser displayed 404 errors looking for

plugin_assets/stylesheets/workflow_enhancements.css plugin_assets/javascripts/*.js

I created a soft link to those files in the appropriate directories and the error messages disappeared and a nice graph of the workflow appeared under the usual workflow table.

BTW, is there a way of moving the blocks around in the image to unhide some lines that are not clearly displayed?

dr-itz commented 10 years ago

The problem with the plugin_assets is most likely because the directory does not exist or is not writable. This should fix it (assuming 'redmine' as the user, change to match your environment):

$ mkdir -p public/plugin_assets
$ chown -R redmine. public/plugin_assets
$ chmod -R 755 public/plugin_assets

The graphic is static for now. Moving nodes around is only possible if dagre-d3 implements it.

dr-itz commented 10 years ago

Closing since the root cause is fixed.