Projects: Issueshttp://projects.andriylesyuk.com/http://projects.andriylesyuk.com/plugin_assets/andriy_lesyuk/images/s-andy.ico2012-02-19T10:44:05ZProjects
Redmine WikiNG - Bug #1980 (Open): Problem running plugin in development modehttp://projects.andriylesyuk.com/issues/19802012-02-19T10:44:05ZOleg Kandaurov
<p>I am using redmine 1.3.0 with WikiNG 0.0.1b. It works well in production environment with following settings:<br /><pre>
config.cache_classes = true
config.action_controller.consider_all_requests_local = false
config.action_controller.perform_caching = true
config.action_mailer.raise_delivery_errors = false
config.action_mailer.logger = nil
</pre></p>
<p>But when I switch server to development environment it loads page successfully only once. I see following error:<br /><pre>
NameError in Projects#index
Showing app/views/layouts/base.html.erb where line #13 raised:
undefined local variable or method `heads_for_theme' for #<ActionView::Base:0xb6026ff0>
Extracted source (around line #13):
10: <%= stylesheet_link_tag 'application', :media => 'all' %>
11: <%= stylesheet_link_tag 'rtl', :media => 'all' if l(:direction) == 'rtl' %>
12: <%= javascript_heads %>
13: <%= heads_for_theme %>
14: <!--[if IE 6]>
15: <style type="text/css">
16: * html body{ width: expression( document.documentElement.clientWidth < 900 ? '900px' : '100%' ); }
</pre></p>
<pre>
/home/f0y/workspace-ruby/redmine-1.3.0/app/views/layouts/base.html.erb:13:in `_run_erb_app47views47layouts47base46html46erb'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `send'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/renderable.rb:34:in `render'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/base.rb:306:in `with_template'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/renderable.rb:30:in `render'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/template.rb:205:in `render_template'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/base.rb:265:in `render'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/base.rb:352:in `_render_with_layout'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_view/base.rb:262:in `render'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:1252:in `render_for_file'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:936:in `render_without_benchmark'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:51:in `render'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:1328:in `default_render'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:1334:in `perform_action_without_filters'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/filters.rb:617:in `call_filters'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/filters.rb:610:in `perform_action_without_benchmark'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/benchmark.rb:308:in `realtime'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activesupport/lib/active_support/core_ext/benchmark.rb:17:in `ms'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/rescue.rb:160:in `perform_action_without_flash'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/flash.rb:151:in `perform_action'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `send'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:532:in `process_without_filters'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/filters.rb:606:in `process'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:391:in `process'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/base.rb:386:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/routing/route_set.rb:438:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:87:in `dispatch'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:121:in `_call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:29:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:9:in `cache'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activerecord/lib/active_record/query_cache.rb:28:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/string_coercion.rb:25:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/head.rb:9:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/methodoverride.rb:24:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/params_parser.rb:15:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/session/cookie_store.rb:99:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/failsafe.rb:26:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/lock.rb:11:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/lock.rb:11:in `synchronize'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/lock.rb:11:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:114:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/reloader.rb:34:in `run'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:108:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/railties/lib/rails/rack/static.rb:31:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/urlmap.rb:47:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/urlmap.rb:41:in `each'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/urlmap.rb:41:in `call'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/railties/lib/rails/rack/log_tailer.rb:17:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/content_length.rb:13:in `call'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/handler/webrick.rb:48:in `service'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/httpserver.rb:104:in `service'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/httpserver.rb:65:in `run'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:173:in `start_thread'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:162:in `start'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:162:in `start_thread'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:95:in `start'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:92:in `each'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:92:in `start'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:23:in `start'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/1.8/webrick/server.rb:82:in `start'
/home/f0y/.rvm/gems/ruby-1.8.7-p358@redmine-debian/gems/rack-1.1.1/lib/rack/handler/webrick.rb:14:in `run'
/home/f0y/workspace-ruby/redmine-1.3.0/vendor/rails/railties/lib/commands/server.rb:111
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `gem_original_require'
/home/f0y/.rvm/rubies/ruby-1.8.7-p358/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:36:in `require'
script/server:3
</pre>
<p>Configuration of development environment:<br /><pre>
config.cache_classes = false
config.whiny_nils = true
config.action_controller.consider_all_requests_local = true
config.action_controller.perform_caching = false
config.action_mailer.raise_delivery_errors = false
</pre></p>
<p>A reason of the error is caching but I’m not sure.</p> Orangutan - Improvement #1298 (Open): Context help for some Orangutan messageshttp://projects.andriylesyuk.com/issues/12982010-11-25T19:05:40ZOleh Demyanyukolkobg@gmail.com
<p>Could you please add addition info for information returned from orangutan<br />For example if I get tickets. <br />you could print additinal info(commands) how to update tickect or add one or else</p> Orangutan::Redmine - Improvement #1159 (Open): Support using numbers for project listhttp://projects.andriylesyuk.com/issues/11592010-11-10T12:43:20ZOleh Demyanyukolkobg@gmail.com
<p>could you please create request string or alias for fetching sub projects of projects by ordering number of parent projects...</p>
<p>Thanks</p> Orangutan::Redmine - Improvement #1107 (Open): Change default project/issue/activity if no task i...http://projects.andriylesyuk.com/issues/11072010-11-09T13:43:37ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Currently we have these six contexts: MainProject, MainIssue, MainActivity... Project, Issue and Activity. Main* contexts allow setting default project, issue and activity. And Project, Issue and Activity contexts allow setting project, issue and activity for a task.</p>
Task context work the following way:
<ul>
<li>If there is a current task - set project, issue or activity for this task</li>
<li>If there is no current task but last task was finished less than 30 minutes ago - set project, issue or activity for last task</li>
</ul>
However sometimes users are trying to set default project, issue or activity using Project, Issue or Activity contexts... So looks like a good idea is to allow setting them. So another "option" should be added:
<ul>
<li>If no current task and last task is too old - set default project, issue or activity...</li>
</ul>
<p>Of course, in this case and in case of setting project, issue or activity for a last task a warning should be written, e.g.:<br /><pre>
Orangutan: No current task so setting it for last task...
Orangutan: No current task so setting default ...
</pre></p>
<p>Maybe also merge MainProject and Project contexts into a single one, MainIssue and Issue into a single one etc...</p> Orangutan::Redmine - Feature #1104 (Incomplete): Automatic overtime trackinghttp://projects.andriylesyuk.com/issues/11042010-11-08T13:43:14ZAndriy Lesyuks-andy@andriylesyuk.com
<p>I just thought that it can be useful to track overtime automatically... How do I see this (just an example):</p>
<p>In <a href="http://www.softjourn.com" class="external">Softjourn</a> we have a single activity - “Normal” (on the project we have more but anyway). There can be added another activity “Overtime”... Then saying when user starts working for more than 8 hous Orangutan saves current task with user’s activity (Normal) and creates new task (with all the same info) with activity “Overtime”. This can be done transparently to user (user won’t know this happened).</p>
<p>Of course, this should be configured, e.g.:<br /><pre>
User: Track overtime with activity "Overtime"
</pre></p>
<p>Just an idea - not sure if we need this...</p> Orangutan::Redmine - Improvement #1038 (Open): More flexible syntax for adding past tasks/entrieshttp://projects.andriylesyuk.com/issues/10382010-10-25T14:15:56ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Right now the syntax is:<br /><pre>
<Date> <start time> - <end time>: <description> on <issue> (<activity>)
</pre><br />e.g.<br /><pre>
From 10:00 to 11:00 I was working on #999
</pre><br />Actually the following is also corrent:<br /><pre>
I was working from 10:00 to 11:00 on #999
</pre><br />So users do try to use such requests... And the problem is that Orangutan does not recognize them correctly...<br />The problem is also that the following is correcnt too:<br /><pre>
On Monday I was working from 10:00 to 11:00 on #999
I was working from 10:00 to 11:00 on Monday on #999
I was working on Monday from 10:00 to 11:00 on #999
...
</pre><br />In other words - this syntax is too complicated... I could recognize by parts but... in this case the following:<br /><pre>
I was working on Monday and fixed bugs from 10:00 to 11:00 on my favourite issue #999
</pre><br />will be added as:<br /><pre>
"I was working and fixed bugs on my favourite" on Monday 10:00-11:00 on #999
</pre><br />This time it looks good. But sometimes the description will be ugly..</p>
<p>So I need to think how to improve this syntax...</p> Orangutan::Redmine - Feature #1022 (Incomplete): Changing issue status depending on user presencehttp://projects.andriylesyuk.com/issues/10222010-10-20T17:49:02ZAndriy Lesyuks-andy@andriylesyuk.com
<p>I figured out that Redmine messenger is able to change status to “In progress” when user comes online (and task is active). Then when user lefts/goes away the messenger changes status to some different value (we can use “Paused” or whatever).</p>
<p>Not sure how is it wanted but idea looks interesting... This way viewers will be able to check if anyone works on the issue right now...</p> Orangutan - Feature #984 (Open): Survey contexthttp://projects.andriylesyuk.com/issues/9842010-10-12T19:31:28ZAndriy Lesyuks-andy@andriylesyuk.com
<p>I personally like to ask people what do they think about some feature or similar... There are many other situations where surveys are needed... For example, one could create a survey: “Are you going to cinema this evening with me?”... <span class="wiking smiley smiley-smiley" title=":)"></span></p>
<p>Orangutan could help here... Theoretically it’s quite possible to create a context which would be responsible for creating and (this can be another context) carrying out surveys. Let’s check sample:</p>
<pre>
Author: I want to create a survey
Orangutan: Give it a question!
Author: Are you going to cinema this evening with me?
Orangutan: What can be an answer?
1. Yes/No/Maybe
2. Text
3. Number
Author: 1.
Orangutan: Ok... Going to carry it out.
</pre>
<pre>
Orangutan: User author@jabber.sjua wants you to answer the following:
Are you going to cinema this evening with me?
Orangutan: What would you answer?
User: Yes
Orangutan: Ok... I'll let him know.
</pre>
<p>Crazy idea, isn’t it? <span class="wiking smiley smiley-smiley" title=":)"></span> Just an idea!..</p> Orangutan - Feature #941 (Open): Support Google calendarhttp://projects.andriylesyuk.com/issues/9412010-10-01T12:47:35ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Orangutan can notify users about Google events (when they are added, in a hour before event etc).</p>
<p>For this there should be developed a special “monkey” - separate system process (maybe there are such programms already or programms which can be used?) which will notify Orangutan about events.</p>
<p>In addition a special context can ask users whether they are going to attend an event:</p>
<pre>
Orangutan: User user@host.com added an event "Company meeting" on Thu 15:00 - 16:00.
Orangutan: Are you going?
User: Maybe
Orangutan: Understood.
</pre>
<p>Also a mapping should be used to determine which user “owns” a Google email account used in calendar...</p> Orangutan - Improvement #936 (In Progress): Documentationhttp://projects.andriylesyuk.com/issues/9362010-09-30T12:33:25ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Orangutan sources should include documentation...</p>
The documents which should be included:
<ul>
<li>Syntax description, usage</li>
<li>Context development tutorial</li>
<li>Installation (does not exist yet)</li>
</ul> Orangutan - Feature #935 (Open): Invalid keyboard layout translatorhttp://projects.andriylesyuk.com/issues/9352010-09-30T12:18:33ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Sometimes when you chat you forget to switch keyboeard layout... and get unreadable text.</p>
<p>Orangutan could help here...</p>
<p>Check:</p>
<pre>
User: Translate: "ерші еуче ші шт утпдшір"
Orangutan: This means: "this text is in english"
User: Translate: "ye zr dfv nfrf sltqrf&"
Orangutan: This means: "ну як вам така ідейка?"
</pre> Orangutan - Feature #892 (Open): Tip of the day / Did you know that?..http://projects.andriylesyuk.com/issues/8922010-09-08T14:16:53ZAndriy Lesyuks-andy@andriylesyuk.com
<p>While I hate things like this in other software... such context would be very helpful for new users. Of course there should be possibility to turn off this feature.</p>
<p>For this context new member should be added to Orangutan::Context object:</p>
<pre>
help => {
tips => [
'Tip #1...',
'Tip #2...',
]
}
</pre>
<p>Then when user comes online Orangutan randomly selects a tip and shows it to user...</p> Orangutan - Feature #863 (Open): Personal TODO listhttp://projects.andriylesyuk.com/issues/8632010-08-31T13:55:24ZAndriy Lesyuks-andy@andriylesyuk.com
<p>There was issue like this in the old version of Orangutan. After moving to Redmine I decided that Redmine’s issues can replace this...</p>
<p>Now I believe I was wrong...</p>
<p>Issues cannot replace TODO list. TODO list can contain a very short task or even not official personal task. For example, “Go and buy a mug”, “Talk with Mykola about his troubles and discipline” etc.</p>
<p>The TODO list should be sortable...</p> Orangutan::Redmine - Enhancement #215 (Incomplete): Support issue subject as an answer to the iss...http://projects.andriylesyuk.com/issues/2152010-04-08T22:06:38ZAndriy Lesyuks-andy@andriylesyuk.com
<p>When Orangutan asks to enter issue some people think that they should enter issue subject. Therefore issue subject as an answer perhaps should be supported. This feature should be added to Issue and MainIssue contexts.</p> Orangutan::Redmine - Feature #20 (Open): Let user specify what he did during a breakhttp://projects.andriylesyuk.com/issues/202009-10-08T19:01:00ZAndriy Lesyuks-andy@andriylesyuk.com
<p>Saying I’m working on something and suddenly my manager asks me to attend a meeting. Saying the meeting lasts for an hour. When I get back Orangutan asks me if he should record a break. That’s fine! But it would be cool if I could answer something like: “Yes... I had a meeting with my manager.”. And he would add this as a task.</p>