| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If using a `DATABASE_URL` and a `database.yml`. The connection information in `DATABASE_URL` should be merged into whatever environment we are in. As released in 4.1.0rc1 if someone has a database.yml but is missing a key like production:
```yml
development:
host: localhost
```
Then the check for blank config will return false so the information from the `DATABASE_URL` will not be used when attempting to connect to the `production` database and the connection will incorrectly fail.
This commit fixes this problem and adds a test for the behavior.
In addition the ability to specify a connection url in a `database.yml` like this:
```
production: postgres://localhost/foo
```
Was introduced in 4.1.0rc1 though should not be used, instead using a url sub key
```
production:
url: postgres://localhost/foo
```
This url sub key was also introduced in 4.1.0rc1 though the `production: postgres://localhost/foo` was not removed. As a result we should not test this behavior.
|
|\
| |
| | |
Prevent foreign_key_for? from evaluating all attributes
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit e0a521cfcd13e4d1f0ae8ab96004289e1c020f71.
Conflicts:
railties/CHANGELOG.md
We expect loggers to quack like stdlib logger. If log4r needs different
level= assignment, using a Logger-quacking wrapper is the way to do it.
Fixes #14114.
|
|
|
|
|
|
| |
GitHub is now able to notify tag creation, I have configured the webhook
for the docs server to receive that event. Therefore, we no longer need
to trigger docs generation manually when releasing.
|
|\
| |
| | |
update guides to new version of rails 3.2.x, i.e. 3.2.17 [skip ci]
|
|/ |
|
| |
|
|
|
|
| |
This reverts commit 5e3d466d52fa4e9a42c3a1f8773a7c31da875e48.
|
|\
| |
| | |
Fix `render_to_string` when called via manually instantiated controllers
|
| |
| |
| |
| | |
closes #14125
|
|\ \
| | |
| | | |
Fix the javascript path in guide for asset modules [skip ci]
|
| | | |
|
|\ \ \
| |_|/
|/| | |
Fix collection proxy exists? regression
|
| | |
| | |
| | |
| | | |
[related #14116]
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
constructor"
This reverts commit f9e4c3c7c0c4152b62fe9202a9d12262884bb118.
[fixes #14116]
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
a piece of documentation.
This can be useful for trying out combinations of markup and code, as
discussed in rails/rails@225bcad
|
|\ \ \
| | | |
| | | | |
change 'assert !' to 'assert_not' in guides [ci skip]
|
|/ / / |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Add note to silence_stream and quietly. [skip ci]
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
State that on the doc.
[fixes #11954]
|
|\ \ \ \
| | | | |
| | | | | |
Close the meta tag with '/>' instead of '>'
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This change fixes the 42 instances of `end tag for "meta" omitted, but
OMITTAG NO was specified` error message that comes up when the full
railsguides are validated.
Full error list at
https://gist.github.com/prakashmurthy/9086679.
|
| | | |
| | | |
| | | | |
The errors were introduced in e220a34e39
|
|\ \ \ \
| | | | |
| | | | | |
Update Docs in favor to use render plain instead of text option
|
|/ / / /
| | | |
| | | |
| | | | |
ref #14062
|
|\ \ \ \
| | | | |
| | | | | |
Typo fix for unscope [ci skip]
|
|/ / / / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Before we were calling to_sym in the mime type, even when it is unknown
what can cause denial of service since symbols are not removed by the
garbage collector.
Fixes: CVE-2014-0082
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Conflicts:
actionview/CHANGELOG.md
activerecord/CHANGELOG.md
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Thanks Godfrey Chan for reporting this!
Fixes: CVE-2014-0080
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously the values of these options were trusted leading to
potential XSS vulnerabilities.
Fixes: CVE-2014-0081
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Sync 4.1 release notes with changes since 7f648bc7
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Introduce `:plain`, `:html`, and `:body` render options.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Setting this attribute to `true` will remove the content type header
from the request. This is use in `render :body` feature.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* Introduces `:plain`, `:html`, `:body` render option.
* Update guide to use `render :plain` instead of `render :text`.
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This test were assuming that the list of render options will always be
the same. Fixing that so this doesn't break when we add/remove render
option in the future.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is an option for to HTML content with a content type of
`text/html`. This rendering option calls `ERB::Util.html_escape`
internally to escape unsafe HTML string, so you will have to mark your
string as html safe if you have any HTML tag in it.
Please see #12374 for more detail.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This is as an option to render content with a content type of
`text/plain`. This is the preferred option if you are planning to render
a plain text content.
Please see #12374 for more detail.
|
| | | | | | |
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This is an option for sending a raw content back to browser. Note that
this rendering option will unset the default content type and does not
include "Content-Type" header back in the response.
You should only use this option if you are expecting the "Content-Type"
header to not be set. More information on "Content-Type" header can be
found on RFC 2616, section 7.2.1.
Please see #12374 for more detail.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Document `default_scope` changes
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|