This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | fixes#15668, #12330 |
| License | MIT |
Commits
-------
[Admin] Do not disable channel base currency when none set
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12. |
| Bug fix? | yes. |
| New feature? | no. |
| BC breaks? | no. |
| Deprecations? | no. |
| Related tickets | #15938 |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
**Description**
As described in: #15938
When you upload a file in the image widget the uploaded image has no spacing between the choose file button. Therfore it looks a bit squeezed which doesent look very nice.
To make it look consistent i added a CSS class arround the button with a `margin-bottom` that has the same spacing as between the Type input, and the choose file button.
<img width="421" alt="before_and_after" src="https://github.com/Sylius/Sylius/assets/39345336/4ec1fcf4-fccb-4ed3-9124-075401815c51">
Commits
-------
BUGFIX: #15938 add spacing between choose file button and uploaded image in image_widget
TASK: adjust naming of css class
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
Moving information about GUS to a more appropriate place.
Commits
-------
e41d1081b1 [Docs] refactor information about GUS
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12|
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | #15956 and #15957 |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
[Admin] Remove info about forum from Admin panel
[Documentation] Remove remaining info about forum
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
Sylius Forum is no longer alive
Commits
-------
319acfde7f Update README.md remove info about forum
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no |
| Related tickets | |
| License | MIT |
Sylius Forum is no longer alive, it should not be mentioned in the docs anymore.
Commits
-------
Forum has retired
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes. |
| New feature? | no. |
| BC breaks? | no. |
| Deprecations? | no |
| Related tickets | fixes#15908 |
| License | MIT |
**Description**
As described in #15908
In the media tab in the new product dialog there is a button for uploading multiple media files. But right now the button has no spacing so the button looks very squizzed to the header:

In the Taxons management there is also a media section for uploading multiple media files. Its in a different twig template. And there, is a `<br>` tag which provides the distance between the button, and the header. With my change it looks like:

Commits
-------
BUGFIX: #15908 missing br tag for spacing for product media tab button
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 <!-- see the comment below --> |
| Bug fix? | yes. |
| New feature? | no. |
| BC breaks? | no. |
| Deprecations? | no. <!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | fixes#12681. |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
## Description
As described in #12681:
Currently when you choose a country with configured provinces, the province select input isnt visualy marked as required with a `*`. When you try to submit the address form without choosing a province, it will tell you:

With this change, the `required` class will be added to the `provinceContainer`. Then it becomes visible again:

Commits
-------
BUGFIX: #12681 add missing required class to ProvinceCode Select input
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 <!-- see the comment below --> |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no <!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | fixes https://github.com/Sylius/Sylius/issues/15442 |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
Fix zoneMembers not unique ID
Update upgrade file
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 |
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no <!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | fixes#15852 |
| License | MIT |
See #15852, depending on language, some attribute value appears in different order.
When we apply to all, there is a mismatch of selected value.
This fix check the value of option before copying if it selected or not.
https://github.com/Sylius/Sylius/assets/3168281/1f75bdf8-d3ec-4b21-9083-bf24853db3bdhttps://github.com/Sylius/Sylius/assets/3168281/fe9edb9c-548a-4e9d-8089-23b7dfd43c51
Commits
-------
[ProductAttribute] Use value of options when use "Apply to all"
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | N/A
| License | MIT
Currently, the local `sylius.storage` configuration for Flysystem creates folders in `media/image` with 700 permissions.Using the option `directory_visibility: public`, it creates them with 755 permission.
Commits
-------
[FLYSYSTEM] Add directory visibility as public to local storage
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12|
| Bug fix? | yes |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
Bump up symfony/flex version
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | N?A
| License | MIT
Commits
-------
0c54f067c0 Update the branch-aliases
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12|
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | |
| License | MIT |
Inspired by [Symfony](https://github.com/symfony/symfony/pull/49088) 😅
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
Update the license years for the last time
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12
Commits
-------
Add the @Sylius/development-team as a codeowner
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | n/a
| License | MIT
Commits
-------
Add builds checking whether the frontend can be built with all supported nodejs versions
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12
| Bug fix? | no
| New feature? | no
| BC breaks? | no
| Deprecations? | no
| Related tickets | N/A
| License | MIT

Commits
-------
9ee3433eac [Admin] Add Sylius certification to menu
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12|
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| Deprecations? | no<!-- don't forget to update the UPGRADE-*.md file --> |
| Related tickets | |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
[Documentation] Extend the maintenance date of 1.12 and update future releases
[Documentation] Add alabaster to build requirements
This PR was merged into the 1.12 branch.
Discussion
----------
| Q | A |
|-----------------|--------------------------------------------------------------|
| Branch? | 1.12 <!-- see the comment below --> |
| Bug fix? | no |
| New feature? | no |
| BC breaks? | no |
| License | MIT |
<!--
- Bug fixes must be submitted against the 1.12 branch
- Features and deprecations must be submitted against the 1.13 branch
- Make sure that the correct base branch is set
To be sure you are not breaking any Backward Compatibilities, check the documentation:
https://docs.sylius.com/en/latest/book/organization/backward-compatibility-promise.html
-->
Commits
-------
New year 2024