Thanks to visit codestin.com
Credit goes to github.com

Skip to content

compatibility with Security component split #16133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 6, 2015

Conversation

xabbuh
Copy link
Member

@xabbuh xabbuh commented Oct 5, 2015

Q A
Bug fix? yes
New feature? no
BC breaks? no
Deprecations? no
Tests pass? yes
Fixed tickets
License MIT
Doc PR

The FrameworkBundle in version 2.3 can be used with recent versions of
the Security component. However, after the Security component has been
split with Symfony 2.4, translations resources have been moved to the
symfony/security-core package. Thus, the changed location must be
taken into account.

The FrameworkBundle in version 2.3 can be used with recent versions of
the Security component. However, after the Security component has been
split with Symfony 2.4, translations resources have been moved to the
`symfony/security-core` package. Thus, the changed location must be
taken into account.
@javiereguiluz
Copy link
Member

👍 we are being hit by this bug when testing our bundle with deps=low

@ogizanagi
Copy link
Contributor

👍

@fabpot
Copy link
Member

fabpot commented Oct 6, 2015

Thank you @xabbuh.

@fabpot fabpot merged commit 7bc836c into symfony:2.3 Oct 6, 2015
fabpot added a commit that referenced this pull request Oct 6, 2015
This PR was merged into the 2.3 branch.

Discussion
----------

compatibility with Security component split

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets |
| License       | MIT
| Doc PR        |

The FrameworkBundle in version 2.3 can be used with recent versions of
the Security component. However, after the Security component has been
split with Symfony 2.4, translations resources have been moved to the
`symfony/security-core` package. Thus, the changed location must be
taken into account.

Commits
-------

7bc836c compatibility with Security component split
@xabbuh xabbuh deleted the security-translations-location branch October 6, 2015 06:31
@stof
Copy link
Member

stof commented Oct 6, 2015

the check is in the wrong order here: in case both location exist, the new one should be used, while you are using the legacy one here

@nicolas-grekas
Copy link
Member

@stof see #16139

nicolas-grekas added a commit that referenced this pull request Oct 6, 2015
…s-grekas)

This PR was merged into the 2.3 branch.

Discussion
----------

[FrameworkBundle] Fix translations dir discovery

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #16133
| License       | MIT
| Doc PR        | -

Commits
-------

f37ceef [FrameworkBundle] Fix translations dir discovery
nicolas-grekas added a commit that referenced this pull request Oct 6, 2015
…ity/core in 2.3 & dir loading (ogizanagi)

This PR was merged into the 2.3 branch.

Discussion
----------

[FrameworkBundle] [Security] Remove trans from the security/core in 2.3 & dir loading

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | no
| BC breaks?    | no
| Deprecations? | yes
| Tests pass?   | yes
| Fixed tickets | #16139, #16133
| License       | MIT
| Doc PR        | -

See #16139 (comment).

I think the most efficient solution is to remove translations from `Security/Core` in 2.3 only (should not be propagated to newest branches!) and load both folders if they exist.

Commits
-------

1ed07a0 [FrameworkBundle] [Security] Remove trans from the security/core in 2.3 & dir loading
This was referenced Oct 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants