- 18 12月, 2010 2 次提交
-
-
由 Don Wilson 提交于
-
由 Aaron Patterson 提交于
-
- 17 12月, 2010 3 次提交
-
-
由 Piotr Sarnacki 提交于
This reverts commit 006ec77e.
-
由 Don Wilson 提交于
-
由 Piotr Sarnacki 提交于
-
- 16 12月, 2010 2 次提交
-
-
由 brainopia 提交于
Dont set explicit domain for cookies if host is not a domain name [#6002 state:committed] Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
由 Piotr Sarnacki 提交于
When using stylesheet_link_tag(:all) or javascript_include_tag(:all), assets directories are searched for css or js files. When config.serve_static_assets is set to true, those files can be served directly from engine's directories. That's why assets paths should be set individually for controllers inside engine if we want to serve static assets with ActionDispatch::Static
-
- 15 12月, 2010 3 次提交
-
-
由 brainopia 提交于
Dont set explicit domain for cookies if host is not a domain name [#6002 state:committed] Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>
-
由 Aditya Sanghi 提交于
-
由 Piotr Sarnacki 提交于
When using stylesheet_link_tag(:all) or javascript_include_tag(:all), assets directories are searched for css or js files. When config.serve_static_assets is set to true, those files can be served directly from engine's directories. That's why assets paths should be set individually for controllers inside engine if we want to serve static assets with ActionDispatch::Static
-
- 13 12月, 2010 3 次提交
- 11 12月, 2010 1 次提交
-
-
由 Ryan Bigg 提交于
-
- 10 12月, 2010 2 次提交
- 09 12月, 2010 9 次提交
-
-
由 Neeraj Singh 提交于
account the resolved mime type for the request [#6110 state:resolved] Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 Ryan Bigg 提交于
root route should go at the *top* of the routes file, because it is the most popular route and should be matched first
-
由 Ryan Bigg 提交于
-
由 Ryan Bigg 提交于
-
由 Xavier Noria 提交于
-
- 07 12月, 2010 1 次提交
-
-
由 Neeraj Singh 提交于
handle HTTP_ACCEPT attribute properly and might provide wrong result. Use params[:format] to avoid this issue.
-
- 05 12月, 2010 4 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Santiago Pastorino 提交于
-
由 Santiago Pastorino 提交于
-
由 Sven Fuchs 提交于
Don't catch exceptions here. Instead only declare that we want exceptions to be rescued as :html, but also let users configure reactions to exceptions in I18n. Signed-off-by: NJosé Valim <jose.valim@gmail.com>
-
- 03 12月, 2010 1 次提交
-
-
由 José Valim 提交于
-
- 01 12月, 2010 3 次提交
-
-
由 José Valim 提交于
Deprecate handler_class_for_extension as template handlers can be any Ruby object, not necessarily a class.
-
由 Aaron Patterson 提交于
-
由 Josh Kalderimis 提交于
Added documentation explaining the new additional supported syntaxes for the routing redirect method, a small changelog note, and two extra tests for path interpolation when using the hash option syntax.
-
- 30 11月, 2010 3 次提交
-
-
由 Josh Kalderimis 提交于
The redirect routing method now allows for a hash of options which only changes the relevant parts of the url, or an object which responds to call can be supplied so common redirect rules can be easily reused. This commit includes a change where url generation from parts has been moved to AD::Http::URL as a class method.
-
由 Neeraj Singh 提交于
-
由 Neeraj Singh 提交于
-
- 28 11月, 2010 3 次提交
-
-
由 José Valim 提交于
-
由 José Valim 提交于
-
由 Neeraj Singh 提交于
development mode
-