FAQ » History » Version 20
  Eric Davis, 2008-03-21 06:55 
  Added notes on related issues
| 1 | 1 | Jean-Philippe Lang | h1. Frequently Asked Questions | 
|---|---|---|---|
| 2 | |||
| 3 | 2 | Jean-Philippe Lang | {{TOC}} | 
| 4 | 1 | Jean-Philippe Lang | |
| 5 | h2. Installing and Running Redmine | ||
| 6 | |||
| 7 | 18 | Jean-Philippe Lang | h3. When I start the application, I get this error "in 'gem_original_require': no such file to load -- initializer (LoadError)" | 
| 8 | 10 | Jean-Philippe Lang | |
| 9 | Make sure "Ruby on Rails":http://rubyonrails.org/ is properly installed on your machine. | ||
| 10 | |||
| 11 | 1 | Jean-Philippe Lang | h3. The application seems to work fine but some pages (eg. login form) have no content. | 
| 12 | |||
| 13 | 18 | Jean-Philippe Lang | You're running Rails 1.1.x but Redmine requires 1.2.2. | 
| 14 | 9 | Jean-Philippe Lang | Upgrade Rails (if you're using gem package system, run the command @gem update@ as root/administrator). | 
| 15 | 3 | Thomas Lecavelier | |
| 16 | 9 | Jean-Philippe Lang | h3. The application freeze after a long time of inactivity. | 
| 17 | 3 | Thomas Lecavelier | |
| 18 | 9 | Jean-Philippe Lang | There's a bug in ruby/mysql adapter < 2.7.3 that leads to loose the database connection. Please update your adapter. | 
| 19 | 7 | Jean-Philippe Lang | You can see thread at: http://rubyforge.org/forum/message.php?msg_id=25951. | 
| 20 | 1 | Jean-Philippe Lang | |
| 21 | 18 | Jean-Philippe Lang | h3. I upgraded Rails to 2.0, but Redmine doesn't work anymore! | 
| 22 | 17 | Jean-Philippe Lang | |
| 23 | 18 | Jean-Philippe Lang | Redmine 0.6.3 is Rails 2.0 compatible, but prior versions are not. | 
| 24 | |||
| 25 | The best solution is to upgrade Redmine to the latest version. But if you really want to use Redmine 0.6.0 on a box running Rails 2.0, please freeze your Rails version for Redmine (it won't affect your other Rails applications) by typing this command from your Redmine directory: | ||
| 26 | 15 | Thomas Lecavelier | |
| 27 | rake rails:freeze:edge TAG=rel_1-2-6 | ||
| 28 | |||
| 29 | Don't forget to restart your server. | ||
| 30 | |||
| 31 | 7 | Jean-Philippe Lang | h2. Issue tracking | 
| 32 | |||
| 33 | h3. I've created a new issue status but I can't use it, it doesn't show up in the status drop-down list. | ||
| 34 | |||
| 35 | 8 | Jean-Philippe Lang | Once you've created a new issue status, you need to include it in the workflow. | 
| 36 | 7 | Jean-Philippe Lang | |
| 37 | 13 | Jean-Philippe Lang | Say you have created a status named 'In progress' and you want the developers to be able to change bugs from 'New' to 'In progress'. | 
| 38 | 7 | Jean-Philippe Lang | Go to "Admin -> Issue tracking -> Workflow", select 'Bug' and 'Developer' then click edit. | 
| 39 | 1 | Jean-Philippe Lang | You now see all the transitions allowed for developers on bugs. Check the 'New' -> 'In progress' checkbox and save. | 
| 40 | 13 | Jean-Philippe Lang | |
| 41 | See [[RedmineIssueTrackingSetup|Workflow setup]]. | ||
| 42 | 11 | Thomas Lecavelier | |
| 43 | 20 | Eric Davis | h3. How does "Related issues" work? | 
| 44 | |||
| 45 | Using Issue #100 as the one you set the relationship and Issue #101 as the "related to" | ||
| 46 | |||
| 47 | * Related - Just adds a link to the other issue | ||
| 48 | * Duplicates - Links issues so that changing the status of one, will change the other (e.g. closing #100 will close #101) | ||
| 49 | * Blocks - Forces an issue to be completed before working on the next. I think it might affect the Gnatt chart but I don't know. | ||
| 50 | * Precedes - Defines an "order", where issue #100 needs to be completed x days before y can be started on. | ||
| 51 | |||
| 52 | 12 | Jean-Philippe Lang | h2. Repositories | 
| 53 | |||
| 54 | h3. Commits don't show up in the activity until I click on 'Repository' | ||
| 55 | |||
| 56 | By default, Redmine fetches the new commits from the repository only when you browse it. | ||
| 57 | |||
| 58 | If you want the commits to be retrieved periodically by Redmine in the background for all your repositories, uncheck 'Autofetch commits' setting and add a cron that runs (with appropriate environment): | ||
| 59 | |||
| 60 | ruby script/runner "Repository.fetch_changesets" -e production | ||
| 61 | |||
| 62 | 19 | Thomas Lecavelier | h3. I can't browse my svn repository through redmine | 
| 63 | |||
| 64 | Please check that you're using a svn client >= 1.3. And the server you're attacking, too. Redmine parse the -xml output from subversion, which is a svn 1.3 feature. | ||
| 65 | |||
| 66 | 11 | Thomas Lecavelier | h2. Performance | 
| 67 | |||
| 68 | 14 | Jean-Philippe Lang | h3. When I create a new issue, Redmine freeze during one minute. | 
| 69 | 11 | Thomas Lecavelier | |
| 70 | 14 | Jean-Philippe Lang | You have to configure email notification, or desactivate it. Please turn off *email notification* feature if you don't use it. In config/environment.rb replace the line | 
| 71 | 11 | Thomas Lecavelier | |
| 72 | config.action_mailer.perform_deliveries = true | ||
| 73 | |||
| 74 | to | ||
| 75 | |||
| 76 | config.action_mailer.perform_deliveries = false | ||
| 77 | |||
| 78 | and restart redmine. |