Search
Results (18298)
- Help: RE: Internal error trying to list issues or view a specific issue
- I don't think so, but I did download a fresh ... p-0.0.4 acts_as_searchable engines
- Help: RE: Internal error trying to list issues or view a specific issue
- Did you use some kind of issue hierarchy plugin with 0.9.3 or did you apply one of the patches posted with #443 ?
- Help: RE: Internal error trying to list issues or view a specific issue
- Actually, I never had an empty db, instead of ... dumped a backup and went on with the install.
- Help: RE: Why I can not get Issue update from RSS (from Outlook)?
- If you want to monitor global activity (all projects), go to Projects -> Overall activity.
- Help: RE: Why I can not get Issue update from RSS (from Outlook)?
- Got it! Just subscribe the project's activity page's Atom. Many thanks to Etienne!
- Open discussion: RE: any way to hide completed issues in roadmap?
- You can zoom in opened (or closed) issues only by using on the tiny links just behind the version progress bar.
- Help: RE: Why I can not get Issue update from RSS (from Outlook)?
- You can use email notifications or monitor issues only in activity feed.
- Help: RE: Why I can not get Issue update from RSS (from Outlook)?
- No. I used the Issues page's Atom which list all issues. I just wonder in this case, only new issue will be received via RSS and the status of each issue will not be received? Do I have to go to one issue page which I want to monitor and use that Atom to monitor that issue's status? That will be tedious. I hope I can be notified if any issue's status is changed. How can I do that? Thanks.
- Help: RE: Internal error trying to list issues or view a specific issue
- Here is the migration file : source:trunk/db/migrate/20100313132032_add_issues_nested_sets_columns.rb It both adds the hierarchy columns and update them for all existing issues. Is it possible that you ran db:migrate on the empty db before re-importing the dump ?
- Help: RE: Internal error trying to list issues or view a specific issue
- That SQL-query worked very well, thank you @E ... . The migration performed was 0.9.3 -> 1.1.1.
- Help: RE: Internal error trying to list issues or view a specific issue
- You can only if you don't have any subtasks. ... gt@ = 2 : <pre> <code class="sql"> UPDATE issues SET root_id = id, lft = 1, rgt = 2 WHERE COALESCE(root_id, lft, rgt) IS NULL</code> </pre>
- Help: RE: Internal error trying to list issues or view a specific issue
- @Etienne: Your second statement is true: o ... ull values => should be a data export/import issue Do I need to manually fill these in?
- Help: RE: Internal error trying to list issues or view a specific issue
- Check your @issues@ table : * either columns @root_id@, @lft@ and @rgt@ do not exist => should be a db:migrate issue * or these columns contain Null values => should be a data export/import issue
- Help: RE: Internal error trying to list issues or view a specific issue
- Forgot to mention: the error still exists even after the db:migrate
- Help: RE: Internal error trying to list issues or view a specific issue
- @Etienne: I thought I had the updates righ ... Invoke environment ** Execute db:schema:dump
- Help: RE: Internal error trying to list issues or view a specific issue
- Already seen that not a long time ago. I t ... [RedmineUpgrade#Step-4-Update-the-database]].
- Help: RE: Internal error trying to list issues or view a specific issue
- I tried to remove the - on line 16 but I gues ... l -f log/production.log -n 0 Processing IssuesController#index (for 62.119.100.69 at 2011- ... "forever", "action"=>"index", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/index.rhtml ActionView::TemplateError (u ... ' for nil:NilClass) on line #16 of app/views/issues/_list.rhtml: 13: </tr></thead> 14: ... roup = false %> 15: <tbody> 16: <% issue_list(issues) do |issue, level| %> 17: <% if @query.grouped? && (group = @query.group_by_column.value(issue)) != previous_group %> 18: <% reset_cyc ... <tr class="group open"> app/helpers/issues_helper.rb:28:in `issue...
- Help: RE: Internal error trying to list issues or view a specific issue
- @Etienne Massip: Hi! You are correct, I w ... ine/log/production.log -n 0* Processing IssuesController#index (for 62.119.100.69 at 2011- ... "forever", "action"=>"index", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/index.rhtml ActionView::TemplateError (u ... ' for nil:NilClass) on line #16 of app/views/issues/_list.rhtml: 13: </tr></thead> 14: ... roup = false %> 15: <tbody> 16: <% issue_list(issues) do |issue, level| -%> 17: <% if @query.grouped? && (group = @query.group_by_column.value(issue)) != previous_group %> 18: <% reset_cyc ... <tr class="group open"> app/helpers/issues_helper.rb:28:in `issue...
- Help: RE: Why I can not get Issue update from RSS (from Outlook)?
- Are you using activity feed ?
- Hi All, I use Outlook RSS to subscribe Redmine RSS. I can successfully get new issues but fail to get any update of the existing issue (for example, issue status change). Could somebody help? Thanks.
- Help: RE: Internal error trying to list issues or view a specific issue
- Is there a @log/production.log@ in your Redmine directory ?
- Hello! After upgrading Redmine from 0.9.something to 1.1.1, I have a problem with "issues". I can browse every project and all other pages, except the two dedicated views listing issues and view a issue. I can see the issue in the outline for a project's activity but ... ssenger if that matters. Cheers! //Carl
- Help: RE: Redmine - Internal Server error?
- hey thanks i copied this plugin to my vend ... sting a screenshot from the clipboard on the issue form. Jean-Philippe Lang 1.0.2 If i w ... configured -- resuming normal operations
- Help: RE: Redmine - Internal Server error?
- You should really paste here the result of ta ... ? Is this "this one":http://www.redmine.org/issues/3816#note-65 ?
- Open discussion: RE: Required fields depending on status
- I would strongly vote for such a feature. We ... should be propagated to "mandatory" when the issue is being closed. We currently have to rely on the issue worker to supply the value when closing the issue and with the feature we could let Redmine enforce that the value is supplied for closed issues.