Bug #52285
closed
CategoryCollection must handle multiple category fields per table
Added by Francois Suter about 11 years ago.
Updated about 7 years ago.
Description
Feature #51921 introduced the possibility to have multiple category selectors per table. The CategoryCollection class was not updated accordingly and - in the current state - will retrieve relations for all fields. The CategoryCollection must be modified to take the field name into account.
This also has an impact on the recently introduced category-based page menu, which needs to show a field selector on top of the category selector.
- Status changed from Accepted to Under Review
More detailed testing instructions:
- install extension "examples" (from https://git.typo3.org/TYPO3CMS/Extensions/examples.git)
- edit a few pages and assign them to different categories using both selectors
- create a category-based page menu, and choose any of the two selectors as reference field
- view it and observe that pages selection was based on relations created in both selectors
- apply the patch
- view the page menu again: it should contain only pages related to categories from the correct reference field
- create a category-based page menu, and choose any of the two selectors as reference field
Just for making it more straightforward, patch https://review.typo3.org/#/c/23905/ must be applied beforehand.
Fabien Udriot wrote:
- create a category-based page menu, and choose any of the two selectors as reference field
Just for making it more straightforward, patch https://review.typo3.org/#/c/23905/ must be applied beforehand.
No, that's wrong! The category-based page menu already exists in the Core. The patch you point to introduces a tt_content menu. So no need to apply another patch to test this one.
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Under Review
- Status changed from Under Review to Resolved
- Status changed from Resolved to Closed
Also available in: Atom
PDF