Project

General

Profile

Backlogs plugin 0.0.1 (scrum/agile)

Added by Mark Maglana over 14 years ago

Please see the new thread for the current Backlogs plugin.


Hi all,

I'm very happy to release the Backlogs Plugin under the MIT license. The latest version, 0.0.1, may be found out github: http://github.com/relaxdiego/backlogs/tree/0.0.1

For a demo, may go to http://backlogsplugin.morphexchange.com/projects/demo/backlogs. Log-in as demo/demo

Regards,

Mark


Replies (91)

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Eric Davis over 14 years ago

Wieland Lindenthal wrote:

I have a question about the licence you used. I allways thought -- and, honestly, disliked -- that Redmine plugins have to be under the GPL as Redmine is under GPL, too. You use the MIT licence -- which is much more business friendly from my point of you --. How do these two licences, GPL and MIT, go together?

That's a very good question Wieland. I haven't gotten a definate answer from my attorney and the GPL is pretty silent on this topic. I'm not an attorney, so you should check with one to find out about the laws in your area. But here is how I understand things:

Lets assume that the plugin isn't using any of the code from a GPL source (e.g. Redmine). The problem area comes how the "program" is defined. If the program is Redmine and all the code loaded by Redmine, then it sounds like the plugin would have to be GPL (but then so would be Rails I think and it's not). If the program is Redmine and plugins are considered libraries (thus the GPL considers them separately) then they can be licensed any way.

A personal problem for me, is that I'm a contributor to Redmine (GPL) so it's difficult for me to write any plugin that hasn't used any GPL code. Since a lot of other plugins have used my code (as an example or actually copied and modified it), there is a good chance that they would fall under the GPL also.

Reading the GPL FAQ would probably be a good start.

Eric Davis

P.S. I'd be happy to license my plugins under the MIT if I legally can. It's just complex and not something I've cared about enough to dig into that deeply.

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Eric Davis over 14 years ago

Just found this thread also, which is old but talks about licensing plugins. Still best to check with an attorney. :)

http://www.techlists.org/archives/programming/railslist/2006-04/msg02292.shtml

Eric Davis

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Wieland Lindenthal over 14 years ago

Thank you, Eric, for your reply. Your comparison of Rails (MIT license) and a Redmine plugin (proprietary licence) is interesting:

Redmine uses Rails software libraries, but that obviously does not force Rails to be under GNU GPL v2, too.

Let us say we create a new system, Redmine+, that consists of Redmine and our Redmine plugin. Redmine+ uses both source code libraries, Rails (MIT) and the Plugin (proprietary licence). The question is: If it is OK to combine Redmine with Rails, why should it not be OK to combine Redmine with our plugin?

However, I think I need to do some deeper google investigation. My experience with attornies was not successfull, so far. They never could give me a clear answer. I might better search google for a good attorney, too :-)

Wieland

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by S Reid over 14 years ago

Hi,

Any comments on my post of yesterday. I'd really like to get this plugin (or another scrum type plugin) working asap.

Sandy

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Mark Maglana over 14 years ago

Hi Weiland,

I'm not an attorney either (in fact, legal stuff make my nose bleed) so I may not be of much help. I'm interested on how MIT and GPL really work with each other though and if there's anything I need to fix in the plugin's license, I'd be more than happy to fix it. If it helps, here's another resource I found on the net: https://fossbazaar.org/content/can-mit-app-include-gpl-chunks#comment-258

Hi Sandy,

Can you post the relevant parts of the error log here.

Regards,

Mark

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Hans Kazan over 14 years ago

Hi,

Mixing licenses GPL/MIT/LGPL/BSD or any other form is difficult without good analysis up front.
On the blog of the author of article mentioned in the last post, he explains a lot on mixing licenses:
http://www.iusmentis.com/computerprograms/opensourcesoftware/mixedsource/

The main page offers a good overview of all types of (copy)rights / patents / trademarks etc

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Mark Maglana over 14 years ago

By the way guys, really sorry for taking so long to fix that demo site. At any rate, it's back online. https://backlogsdemo.morphexchange.com/projects/demo/backlogs

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by S Reid over 14 years ago

Just tried logging into demo. Getting a 403 - not authorized using demo/demo.

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Mark Maglana over 14 years ago

try this page: http://backlogsdemo.morphexchange.com/projects/demo

I managed to log in there using demo/demo

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by S Reid over 14 years ago

Hi Mark,

Thanks - that link works.

Any idea why drag and drop doesn't work on my site. I've enabled backlogs in permissions - is there something else I need to do to allow editing features on the backlog tab ?

Sandy

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Mark Maglana over 14 years ago

Hi Sandy,

Not sure. Might help if you provide the error messages in the log file as well. Using FireBug's Network pane can also provide some hints.

Regards,

Mark

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by S Reid over 14 years ago

Hi Mark,

When I try drag/drop, nothing happens. No errors in production.log. Nothing in firebugs network pane.

The backlog tab is enabled, but all edit type operation are disabled. Is there some sort of permissions setting which distinguishes between viewing of backlog, and editing backlog ?

Sandy

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Tord Softeland over 14 years ago

Hi,

This is a great plugin.
I have the same problem as Sandy. Running 0.8.6.stable from a BitNami Redmine Stack (with OpenSuse/MySQL)

Best regards,
Tord

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Ezequiel G. B. over 14 years ago

Hello there Mark!

Me and another guy around the globe found a little bug when we installed the Backlogs plugin and tried to delete an issue from Redmine.

You can read the posts here:

http://www.redmine.org/boards/2/topics/9412
http://www.redmine.org/boards/3/topics/9550

It would be great if you could have a look at it and just let me know if you want to try something or need more information.

Greetings, and thank you for this great plugin!
Ezequiel.

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Eric Doughty-Papassideris over 14 years ago

Hi Sandy and Tord,

When I try drag/drop, nothing happens. No errors in production.log. Nothing in firebugs network pane.

The backlog tab is enabled, but all edit type operation are disabled. Is there some sort of permissions setting which distinguishes between viewing of backlog, and editing backlog ?

I had the same problem, and noticed that public/javascripts/backlogsjs/all.js was empty.
I really dont do any rails or ruby, so I have no idea about the right answer (probably a migration thing I guess), but running this command from the redmine root folder solved my problem:

cat vendor/plugins/redmine_backlogs/assets/javascripts/{main,item,task,backlog}.js > public/javascripts/backlogsjs/all.js

An alternative would be to get the js from a running installation, but I'm not sure about versions and stuff.

Good luck,
Regards

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Martin S. over 14 years ago

Aloa'he,

I got a problem installing backlogs on redmine 8.7
when I execute: rake db:migration_pligins RAILS_ENV="production"

i'm getting the following error:

rake aborted!
Missing session secret. Please run "rake config/initializers/session_store.rb" to generate one

The problem is, this command does not work :/ to I don't know what to do - please advice.
Because the only way to make redmine back to work is to delete redmin_backlogs folder out of the plugins folder.

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Tord Softeland over 14 years ago

Eric Doughty-Papassideris wrote:

Hi Sandy and Tord,

When I try drag/drop, nothing happens. No errors in production.log. Nothing in firebugs network pane.

The backlog tab is enabled, but all edit type operation are disabled. Is there some sort of permissions setting which distinguishes between viewing of backlog, and editing backlog ?

I had the same problem, and noticed that public/javascripts/backlogsjs/all.js was empty.
I really dont do any rails or ruby, so I have no idea about the right answer (probably a migration thing I guess), but running this command from the redmine root folder solved my problem:
[...]

An alternative would be to get the js from a running installation, but I'm not sure about versions and stuff.

Good luck,
Regards

Thanks Eric, now I can edit stuff, but saving does not work. Hitting Ctrl-Enter enables the wait-icon but nothing else seems to happen.

Regards,
Tord

RE: Inheriting Versions from Parent Projects? - Added by Jeff Thorn over 14 years ago

Great plugin Mark! We are using it to manage a project that has many components - a server, 3 clients, a web interface, etc. In Redmine, we have this setup as one main project (ie - "the platform"), and 5 sub projects (back end server, web client, mobile client, etc.)

I'd really love to create sprints at the main project level. Then have the sub projects "inherit" the versions. That way I can attach tasks on the sub projects to the version of the main project.

I have seen some discussion of "sub tasks". Is this the same thing? Would it be difficult to allow sub projects to inherit versions from parent projects as described above?

Thanks,
Jeff

RE: Inheriting Versions from Parent Projects? - Added by Jeff Thorn over 14 years ago

Jeff Thorn wrote:

Great plugin Mark! We are using it to manage a project that has many components - a server, 3 clients, a web interface, etc. In Redmine, we have this setup as one main project (ie - "the platform"), and 5 sub projects (back end server, web client, mobile client, etc.)

I'd really love to create sprints at the main project level. Then have the sub projects "inherit" the versions. That way I can attach tasks on the sub projects to the version of the main project.

I have seen some discussion of "sub tasks". Is this the same thing? Would it be difficult to allow sub projects to inherit versions from parent projects as described above?

Thanks,
Jeff

FYI.... the way we are handling the sub projects now is to create the same versions on main project and all the sub projects. That way we can keep them in sync. Unfortunately, we cannot see the backlog across the entire project - just on each sub project. Is there a better way of doing this?

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Shoaibi . over 14 years ago

When i click the "Backlogs" tab under a project first time i get an internal server error with the following logs.

(/var/www/vhosts.d/redmine.stagging.me/public/javascripts/backlogsjs doesn't even exist)

ActionView::TemplateError (Permission denied - /var/www/vhosts.d/redmine.stagging.me/public/javascripts/backlogsjs) on line #3 of vendor/plugins/redmine_backlogs/app/views/backlogs/index.html.erb:
1: <% content_for :header_tags do %>
2:     <%= stylesheet_link_tag 'index', 'item', :plugin => 'redmine_backlogs', :media => 'screen, print' %>
3:     <%= javascript_include_tag  'main', 'backlog', 'item', 'task', :plugin => 'redmine_backlogs', :cache => 'backlogsjs/all' %>
4: <% end %>
5: <div class="backlog_toolbar">
6:   <select id="move_items" class="actions">
    /usr/lib/ruby/1.8/fileutils.rb:243:in `mkdir'
    /usr/lib/ruby/1.8/fileutils.rb:243:in `fu_mkdir'
    /usr/lib/ruby/1.8/fileutils.rb:217:in `mkdir_p'
    /usr/lib/ruby/1.8/fileutils.rb:215:in `reverse_each'
    /usr/lib/ruby/1.8/fileutils.rb:215:in `mkdir_p'
    /usr/lib/ruby/1.8/fileutils.rb:201:in `each'
    /usr/lib/ruby/1.8/fileutils.rb:201:in `mkdir_p'
    vendor/rails/actionpack/lib/action_view/helpers/asset_tag_helper.rb:608:in `write_asset_file_contents'
    vendor/rails/actionpack/lib/action_view/helpers/asset_tag_helper.rb:246:in `javascript_include_tag_without_engine_additions'
    vendor/plugins/engines/lib/engines/rails_extensions/asset_helpers.rb:72:in `javascript_include_tag'
    vendor/plugins/redmine_backlogs/app/views/backlogs/index.html.erb:3:in `_run_erb_47vendor47plugins47redmine_backlogs47app47views47backlogs47index46html46erb'
    vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:141:in `call'
    vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:141:in `capture_erb_with_buffer'
    vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:44:in `capture'
    vendor/rails/actionpack/lib/action_view/helpers/capture_helper.rb:125:in `content_for'
    app/helpers/application_helper.rb:599:in `content_for'
    vendor/plugins/redmine_backlogs/app/views/backlogs/index.html.erb:1:in `_run_erb_47vendor47plugins47redmine_backlogs47app47views47backlogs47index46html46erb'
    vendor/rails/actionpack/lib/action_view/base.rb:342:in `send'
    vendor/rails/actionpack/lib/action_view/base.rb:342:in `execute'
    vendor/rails/actionpack/lib/action_view/template_handlers/compilable.rb:29:in `send'
    vendor/rails/actionpack/lib/action_view/template_handlers/compilable.rb:29:in `render'
    vendor/rails/actionpack/lib/action_view/template.rb:35:in `render'
    vendor/rails/actionpack/lib/action_view/template.rb:22:in `render_template'
    vendor/rails/actionpack/lib/action_view/base.rb:248:in `render_file'
    vendor/rails/actionpack/lib/action_controller/base.rb:1112:in `render_for_file'
    vendor/rails/actionpack/lib/action_controller/base.rb:845:in `render_with_no_layout'
    vendor/rails/actionpack/lib/action_controller/layout.rb:251:in `render_without_benchmark'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
    vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:8:in `realtime'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
    vendor/rails/actionpack/lib/action_controller/base.rb:1161:in `default_render'
    vendor/rails/actionpack/lib/action_controller/base.rb:1167:in `perform_action_without_filters'
    vendor/rails/actionpack/lib/action_controller/filters.rb:579:in `call_filters'
    vendor/rails/actionpack/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    /usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
    vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
    vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in `perform_action_without_caching'
    vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `passenger_orig_perform_action'
    vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache'
    vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
    vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `passenger_orig_perform_action'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/request_handler.rb:65:in `perform_action'
    vendor/rails/actionpack/lib/action_controller/base.rb:529:in `send'
    vendor/rails/actionpack/lib/action_controller/base.rb:529:in `process_without_filters'
    vendor/rails/actionpack/lib/action_controller/filters.rb:568:in `process_without_session_management_support'
    vendor/rails/actionpack/lib/action_controller/session_management.rb:130:in `process'
    vendor/rails/actionpack/lib/action_controller/base.rb:389:in `process'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:149:in `handle_request'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:107:in `dispatch'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `synchronize'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `dispatch'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi'
    vendor/rails/actionpack/lib/action_controller/dispatcher.rb:35:in `dispatch'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/request_handler.rb:50:in `process_request'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:374:in `start_request_handler'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:332:in `handle_spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/utils.rb:184:in `safe_fork'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:330:in `handle_spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:163:in `start'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:209:in `start'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:154:in `spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/bin/passenger-spawn-server:61

Rendering /var/www/vhosts.d/redmine.stagging.me/public/500.html (500 Internal Server Error)

If i refresh or try to visit Backlogs tab again, it is accessible but logs still say this:

ActionController::RoutingError (No route matches "/javascripts/backlogsjs/all.js" with {:method=>:get}):
    /vendor/rails/actionpack/lib/action_controller/routing/recognition_optimisation.rb:67:in `recognize_path'
    /vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:385:in `recognize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:148:in `handle_request'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:107:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `synchronize'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `dispatch'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi'
    /vendor/rails/actionpack/lib/action_controller/dispatcher.rb:35:in `dispatch'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/request_handler.rb:50:in `process_request'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_request_handler.rb:207:in `main_loop'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:374:in `start_request_handler'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:332:in `handle_spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/utils.rb:184:in `safe_fork'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:330:in `handle_spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:163:in `start'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/railz/application_spawner.rb:209:in `start'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server_collection.rb:80:in `synchronize'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server_collection.rb:79:in `synchronize'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:154:in `spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `__send__'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:352:in `main_loop'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/lib/phusion_passenger/abstract_server.rb:196:in `start_synchronously'
    /usr/lib/ruby/gems/1.8/gems/passenger-2.2.7/bin/passenger-spawn-server:61

Rendering /var/www/vhosts.d/redmine.stagging.me/public/404.html (404 Not Found)

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Kevin Bosman over 14 years ago

Shoaibi . wrote:

When i click the "Backlogs" tab under a project first time i get an internal server error with the following logs.

(/var/www/vhosts.d/redmine.stagging.me/public/javascripts/backlogsjs doesn't even exist)
[...]

The first time the backlogs plugin is invoked, it tries to create the folder /public/javascripts/backlogsjs and copies it's js assets there. If it doesn't have write/create permission in the public/javascripts folder, I would imagine it might give the error you've encountered.

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Shoaibi . over 14 years ago

i changed the user to apache:apache of the public directory with 755 permission but it didn't work, and now i did it with a 777, works for some reason...

Anyways, thanks a lot for such a quick response, really appreciate it.
you Rock :)

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Nate Lowrie over 14 years ago

Great plugin. I have been using it for about a week now with good success. My one issue is that I have several labels that span more than one line of text and it would be useful if the backlogs plug would expand the story line size to accommodate them. This is especially true on the backlog stories because the description is only about 50 characters before it wraps.

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Eric Doughty-Papassideris over 14 years ago

Tord Softeland, @Sandy, Martin Liu Stopczynski

My previous fix is insufficient, as Tord says, it does not fix anything but the client interaction.
The problem I had was because I cloned backlogs with its git name (/vendor/plugins/backlogs instead of ...plugins/redmine_backlogs ), and migrated from there.
I was never fully able to recover from that, and so I deleted everything redmine related (including the DB), and reinstalled with the correct folder name.
I then had a problems with the authenticity token which showed up as ActionController::InvalidAuthenticityToken in log/production.log, for my work around was to add :

protect_from_forgery :only => []

in the following controllers:
#    modified:   app/controllers/backlogs_controller.rb
#    modified:   app/controllers/charts_controller.rb
#    modified:   app/controllers/comments_controller.rb
#    modified:   app/controllers/items_controller.rb
#    modified:   app/controllers/tasks_controller.rb

I suspect this a less than ideal solution, but it works for me.
You can find the corresponding patch here: http://vim.pastey.net/130584

Please, I am neither a ruby developper, nor am I remotely qualified to help with this project, this all the information I have.

RE: Backlogs plugin 0.0.1 (scrum/agile) - Added by Martin S. over 14 years ago

hey eric,

thx 4 the info - but the change didn't fix the problem :/ still can't edit nor dragNdrop....

(51-75/91)