Project

General

Profile

Forums » Plugins »

Plugin support totally broken with new install (2.2.x and master)

Added by Tommaso Visconti almost 12 years ago

I'd like to update to 2.2.x the production redmine installation (1.4.x) so I'm trying the new version. I made a fresh install but the plugins support seems totally broken. I tried a couple of plugins and none worked.
All the configuration pages results in a 404 error, I opened an issue http://www.redmine.org/issues/13140
All the translations, including english, are broken. If i try to open a plugin page I get a "Page not found". This is the error of the Knowledgebase plugin:

Started GET "/knowledgebase" for 127.0.0.1 at 2013-02-13 11:54:29 +0100

ActionController::RoutingError (uninitialized constant KnowledgebaseController):

It seems that redmine isn't loading the plugin resources from the plugins folder.

I tried adding

config.plugins = [ :all ]

in environment.rb, nothing changed

My environment:

RAILS_ENV development and production
ruby-1.9.3-p374 with RVM
Mysql2 gem
Fresh redmine install from git, branches 2.2-stable and master
I also tryied updating the 1.4.x installation. The upgrade worked as a charm, but all the plugins (after their update to 2.2.x compatible versions) stopped working with the same errors.

What's wrong here?
Thanks in advance


Replies (7)

RE: Plugin support totally broken with new install (2.2.x and master) - Added by Dhanasingh Krishnapandian almost 12 years ago

Are you installing the plugins under <REDMINE_DIR>/plugins folder ?
prior to 2.0.2, the plugins go to <REDMINE_DIR>/vendor/plugins folder

Dhanasingh

RE: Plugin support totally broken with new install (2.2.x and master) - Added by Rachid B almost 12 years ago

i have the same problem. All plugin views generate a 404 "page not found" since Release 2.x

RE: Plugin support totally broken with new install (2.2.x and master) - Added by Jan Niggemann (redmine.org team member) almost 12 years ago

Lots of people recently went from 1.x to 2.x, there were occassional glitches but if you read the threads here, most problems were sorted out. People didn't complain about "totally broken plugin support", so I imagine that people (including myself) don't have problems with their plugins.

tried a couple of plugins and none worked.

Were all plugins you tested explicitly compatible with the latest version of redmine? Which ones did you test? In which version?

#13140: Gitolite is supposed to work, on github it reads "CURRENT HEAD VERSION WORKS WITH TRUNK REDMINE", did you try HEAD with TRUNK?

Remove all plugins, then chose one and add it to redmine. Migrate, check for errors. If there's an error, post back here and we'll try to solve it.

RE: Plugin support totally broken with new install (2.2.x and master) - Added by Tommaso Visconti almost 12 years ago

Thanks Jan for the answer. For specific problem I opened an issue, actually without any response: http://www.redmine.org/issues/13140
In this thread I'm asking for general status of plugins with the new redmine, because after the upgrade, with a new installation and with different plugins I got always the same error, so I'm starting to think probably some operation is needed and I'm not finding it (or it's not present in the documentation). Or, I'm guessing, recent patches to Rails and/or Redmine introduced some bug

RE: Plugin support totally broken with new install (2.2.x and master) - Added by Jan Niggemann (redmine.org team member) almost 12 years ago

Tommaso Visconti wrote:

In this thread I'm asking for general status of plugins with the new redmine

General status: No problems known. If a plugin doesn't work, check with the author.

Or, I'm guessing, recent patches to Rails and/or Redmine introduced some bug

I don't think so, I already wrote it in my last post: In the last weeks I read a lot of threads here that dealt with minor problems after migration from 1.x to 2.x. Until now, there were no general problems with plugin support.

Why don't you follow my advice to find the cause of your problems?
Please remove all plugins, add a single one back, and post the error you get along with excerpts from your logfile!

    (1-7/7)