Project

General

Profile

Actions

Defect #12217

closed

Issue with Feeds

Added by Joshua Parker over 11 years ago. Updated over 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Feeds
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

I am currently using Redmine version 2.1.2. The install is on an Ubuntu 10.04 server with Nginx 1.2.4 and Passenger. Everything on the site works really well except for the Atom Feeds. No matter which feed I click on, it redirects me to:

Page not found
The page you were trying to access doesn't exist or has been removed.

Any help with this issue is greatly appreciated. Thank you.

About your application's environment
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.8.24
Rack version 1.4
Rails version 3.2.8
Active Record version 3.2.8
Action Pack version 3.2.8
Active Resource version 3.2.8
Action Mailer version 3.2.8
Active Support version 3.2.8
Middleware Rack::Cache, ActionDispatch::Static, Rack::Lock, #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x7f1ca36a2040>, Rack::Runtime, Rack::MethodOverride, ActionDispatch::RequestId, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::DebugExceptions, ActionDispatch::RemoteIp, ActionDispatch::Callbacks, ActiveRecord::ConnectionAdapters::ConnectionManagement, ActiveRecord::QueryCache, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, ActionDispatch::Head, Rack::ConditionalGet, Rack::ETag, ActionDispatch::BestStandardsSupport, OpenIdAuthentication
Application root /usr/share/redmine
Environment production
Database adapter mysql
Database schema version 20120930112914

Actions #1

Updated by Joshua Parker over 11 years ago

I figured out that the issue is with the change I made in routes to set projects as the root:

  #root :to => 'welcome#index', :as => 'home'
  root :to => 'projects#index', :as => 'home'

Is there are way to make this work with projects as the root?

Actions #2

Updated by Jean-Philippe Lang over 11 years ago

  • Status changed from New to Closed
  • Resolution set to Invalid

You get this 404 because Rails fails to generate a root to welcome controller.
Even if you don't want it to be the default, don't comment this route, or any other routes BTW.

Actions

Also available in: Atom PDF