### What?
Removes Collapsible label from child field label in the `FieldSelect`
component (for example Bulk Edit field select dropdown)
### Why?
Including the Collapsible field label in the option label of the
FieldSelect component could potentially be confusing to a user as it
eludes to the field being nested in the Data schema.
### How?
In the reduceFields function of the FieldsLabel component, if
`field.type === 'collpasible'` the collapsible field's label will not be
combined with the child fields labels.
Fixes#10757
---------
Co-authored-by: Patrik Kozak <patrik@payloadcms.com>
### What?
Adds new `forceRenderAllFields` `admin` prop to `collection` & `global`
configs.
This new prop forces all fields in the `Edit` view to render
immediately, regardless of scroll position. By default, this is set to
`false` to improve performance, as fields are progressively rendered to
balance load times. Enabling this option can make it easier to locate
fields using browser search (e.g., CMD+F).
```
admin: {
forceRenderAllFields: true,
},
```
### Why?
Previously, fields were only rendered to a certain viewport pixel height
for performance purposes. As a result, this disallowed using the browser
search on all fields in the edit view if they were not completely loaded
in i.e in the proper viewport.
### What?
**V2 Update** – Adds support for using group fields when filtering the
list view.
### Why?
This feature was originally introduced in V3. Due to popular demand from
V2 users, we are backporting it into V2.
### How?
Updates the `WhereBuilder` to map over fields within a group and prefix
them with the parent field name. Similar to V3 PR
[here](https://github.com/payloadcms/payload/pull/6647).
#### Review & Testing
Use the `admin` test suite and the `posts` collection to see this
change.
This PR closes#6518.
Just filtering null item from the `results` array makes thing work well.
## Description
<!-- Please include a summary of the pull request and any related issues
it fixes. Please also include relevant motivation and context. -->
- [x] I have read and understand the
[CONTRIBUTING.md](https://github.com/payloadcms/payload/blob/main/CONTRIBUTING.md)
document in this repository.
## Type of change
<!-- Please delete options that are not relevant. -->
- [x] Bug fix (non-breaking change which fixes an issue)
## Checklist:
- [x] I have added tests that prove my fix is effective or that my
feature works
- [x] Existing test suite passes locally with my changes
## Description
Fixes#8109
Note this should also be merge in payload/beta!
- [X] I have read and understand the
[CONTRIBUTING.md](https://github.com/payloadcms/payload/blob/main/CONTRIBUTING.md)
document in this repository.
## Type of change
- [X] Bug fix (non-breaking change which fixes an issue)
## Checklist:
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [X] Existing test suite passes locally with my changes
Signed-off-by: NorthBlue333 <north333@free.fr>
## Description
this PR close : https://github.com/payloadcms/payload/issues/7905
delete limit when updated
-
<!-- Please include a summary of the pull request and any related issues
it fixes. Please also include relevant motivation and context. -->
- [x] I have read and understand the
[CONTRIBUTING.md](https://github.com/payloadcms/payload/blob/main/CONTRIBUTING.md)
document in this repository.
## Type of change
<!-- Please delete options that are not relevant. -->
- [ ] Chore (non-breaking change which does not add functionality)
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Change to the
[templates](https://github.com/payloadcms/payload/tree/main/templates)
directory (does not affect core functionality)
- [ ] Change to the
[examples](https://github.com/payloadcms/payload/tree/main/examples)
directory (does not affect core functionality)
- [ ] This change requires a documentation update
## Checklist:
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] Existing test suite passes locally with my changes
- [ ] I have made corresponding changes to the documentation
### What?
Fix for See #9045 - this PR adjusts the order and the style of the draft
button to be consistent with the default edit-collection view.
### Why?
If "drafts" are enabled the "draft" action button is rendered on the
- edit-many-modal: as a "primary" button, on the right side of the
"publish" button
- edit-collection view: as a "secondary" button, to the left of the
"publish" button
--> This is inconsistent and can lead to user mistakes pushing the wrong
button because muscle-memory+human-brains
### How?
Adjusted `EditMany/index.tsx`
- setting the `buttonStyle` attribute for the `SaveDraft` component
- switching the positions of the action buttons in the `EditMany`
component
### Fix
- Before
- After
---------
Co-authored-by: Patrik Kozak <patrik@payloadcms.com>
Fixes#8317
Sharp based images are auto-oriented based on the EXIF data i.e.
`.rotate()`.
This can be problematic when resizing images as the
`originalAspectRatio` calculation we do in the `imageResizer` can become
incorrect if the files dimensions are rotated from sharp.
For example, uploading an `ios` based image with dimensions of 3024 x
4032 will be auto rotated to 4032 x 3024 because the exif data gives the
image an orientation of `6` - which means it needs to be rotated 90
degrees clockwise.
As a result, the original aspect ratio goes from being `0.75` to
`1.3333` - which is incorrect.
This PR preserves the original aspect ratio to properly resize images
based on the original dimensions - not the sharp based dimensions.
