- Sep 09, 2020
-
-
Benjamin Franzke authored
With the introduction of symfony/event-dispatcher-contracts in https://git.typo3.org/Packages/TYPO3.CMS.git/commit/e4a1ae8762ee99712 we forced usage of symfony5 in composer-based installations where installation with symfony4 was possible before. This is because event contracts v2 is only compatible with symfony v5, but contracts v1 needs to be supported for symfony4 compatibility. Note: although non-composer-based installations used symfony5 bundled already, composer mode could still use symfony v4 if needed. We now add a new intermediate composer package that is available in two different versions, and offers a compatible symfony event dispatcher adapter for the respective interfaces in symfony v4 and symfony v5 in each of these version. typo3/cms-core allows to install both versions which means we can provide a compatible adapter for both, symfony v4 and v5. This change allows composer-based installations to support both versions (v5/v4) again, so extensions like EXT:solr (which requires a package called solarium) to work with the dependency constraints of TYPO3 Core. Commands used: composer require --no-update --working-dir=typo3/sysext/core \ "symfony/event-dispatcher-contracts:^1.1 || ^2.0" \ "typo3/symfony-psr-event-dispatcher-adapter:^1.0 || ^2.0" composer require --no-update \ "symfony/event-dispatcher-contracts:^1.1 || ^2.0" \ "typo3/symfony-psr-event-dispatcher-adapter:^1.0 || ^2.0" composer update --lock Resolves: #92229 Releases: master, 10.4 Change-Id: I4ff6c6589833cbfea3c4b327a8580fd5fbf45468 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65644 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
Simon Gilli <typo3@gilbertsoft.org> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
-
Oliver Bartsch authored
The underling JavaScript of the Drag&Drop functionality in the page module passes the columns language, the element is dropped in, to the DataHandler. This results in L=-1 elements gets changed to L=0 when moved around in their column. This is now fixed by using the language uid of the dragged element instead of the column if elements language is -1. Resolves: #87148 Releases: master, 10.4 Change-Id: I6663341daadc228480b6dc8ac935b71f117dbfd9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65614 Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
Alexander Schnitzler authored
Replace ObjectManager->get() with GeneralUtility::makeInstance() Releases: master Resolves: #92244 Change-Id: I76ebcb67ba7e9e6cb1bd3a5ef3d8d793ed46af2a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65652 Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
-
Benjamin Franzke authored
This reverts commit e2b1148c. Our Event dispatcher adapter is currently not compatible with symfony/event-dispatcher-contracts:v1 (type declaration mismatch) and therefore results in a runtime fatal error with symfony v4. Compatibility with symfony v4 will be added in a new revision of the reverted patch. Releases: master, 10.4 Reverts: #92229 Resolves: #92239 Change-Id: Ifc920b839cb1cdaaf90f3afcfa0c961b59c0f343 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65648 Tested-by:
-
Torben Hansen authored
* Namespace should be "Command" * Removed superfluous comma Resolves: #92233 Releases: master, 10.4 Change-Id: I6bcdeb0528ef6d1fc3d6f129572f18b7979d7fe5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65642 Tested-by:
Jörg Bösche <typo3@joergboesche.de> Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Tested-by:
-
Alexander Schnitzler authored
This patch fixes incompatible type usage in function arguments and is preparatory work for introducing native type hints and strict mode in all core files. Releases: master, 10.4 Resolves: #92112 Change-Id: Iecb483c2575bd479ee9126034e7390691c954d13 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65467 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Daniel Goerz <daniel.goerz@posteo.de> Reviewed-by:
-
- Sep 08, 2020
-
-
Benni Mack authored
The results of the hook in PageRepository->enableFields and of PageRepository->getMultipleGroupsWhereClause may be different, depending on the Context state for usergroups. In TYPO3 v9, PageRepository was also used when resolving pages during Routing (where there is no user / group resolved yet), which is why we may face different states of usergroups in PageRepository. Resolves: #91714 Releases: master, 10.4, 9.5 Change-Id: If6c535efce27e2a07b803ac101d59b8baa5bbd51 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65276 Tested-by:
-
Sybille Peters authored
TYPO3 now uses eslint instead of tslint to lint Typescript files in the core. Resolves: #92223 Releases: master, 10.4 Change-Id: Ie8adc13d738b81b2971332fa73be15266aec7d1a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65637 Tested-by:
-
Daniel Windloff authored
Streamline translation fetching: To get a better overview, the fetching of the translations for each record has been moved to the `getTable()` method. Therewith, the main translation related queries are together, as the workspace overlay is already there. The translations are now handed over to the methods that render the list of records. This allows to remove the properties `translations` and `selFieldList` as the fields to select are already in the `getTable()` method and the translation must no longer be transferred back to the `getTable()` from the `makeLocalizationPanel()` method. Furthermore, this also avoids a db query for each translated record (in strict translation mode). Previously, a query with an always empty result set was in place. Streamline localization (all records excluding pages): The localization of each record (excluding pages) depends on the available languages of the site configuration and the already translated pages. This information is collected in the `getPossibleTranslations()` method, which depends on the current page uid and replaces the `initializeLanguages()` method. It is used to set the possible translations to the `possibleTranslations` property in the `start()` method. The property `possibleTranslations` replaces the properties `pageOverlays` and `systemLanguagesOnPage`. Streamline localization for pages: The localization of page records does not depend on the translation status of the parent page, because otherwise the first translation of one page would not be possible. The restriction for the page translations is now the same as in the `languageSelector()`. Streamline `makeLocalizationPanel()` method: This method is now only used to create the possible localization buttons. Releases: master Resolves: #92133 Change-Id: Iaf5f9f8cee795c4245d8201b20617df5d95570a7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65505 Tested-by:
-
Alexander Nitsche authored
In order to run TYPO3 Core acceptance tests not only in the TYPO3 Core own docker environment but in an arbitrary environment the web server url of the testing environment should be configurable by the environment variable "typo3TestingAcceptanceBaseUrl". For example, having a LEMP stack with an Nginx web server available at http://nginx:8080 you would set the variable "typo3TestingAcceptanceBaseUrl=http://nginx:8080" in the environment of the acceptance tests runner. Resolves: #92205 Releases: master, 10.4 Change-Id: Ia890ed813d1e46af0b9010f325b13f08f9863ab2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65585 Tested-by:
-
Daniel Windloff authored
In order to be consistent with other views, the backend user's avatar and name is displayed instead of the uid. Releases: master Resolves: #92227 Change-Id: I585f5d851352822bee2909d92259942eadfcefe8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65634 Tested-by:
-
Benni Mack authored
With the introduction of symfony/event-dispatcher-contracts in https://git.typo3.org/Packages/TYPO3.CMS.git/commit/e4a1ae8762ee99712e4e5c9c2f8a3876bce97620 this change forced support for symfony5 in composer-based installations (although non-composer-based installations use symfony5 bundled already), as contracts v2 is only compatible with symfony v5, but contracts v1 is used for symfony4. This change allows composer-based installations to support both versions (v5/v4) again, so extensions like EXT:solr (which requires a package called solarium) to work with the dependency constraints of TYPO3 Core. - composer require "symfony/event-dispatcher-contracts:^1.1 || ^2.0" --no-update \ --working-dir=typo3/sysext/core - composer require "symfony/event-dispatcher-contracts:^1.1 || ^2.0" --no-update - composer update --lock Resolves: #92229 Releases: master, 10.4 Change-Id: I5f501e9ed9d6a844de942c2ca96c9d52e0bd5e89 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65635 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Richard Haeser <richard@richardhaeser.com> Reviewed-by:
-
Daniel Windloff authored
After the removal of TCA [ctrl][thumbnails] in #92118, the method 'getVisibleColumns()' isn't used any more. Therefore, it has been removed. Releases: master Resolves: #92226 Change-Id: Iff0ad528e96a0f89fc1f59d9728d9a96374f793f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65629 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
-
Daniel Windloff authored
The property `showIcon` was always 1. Therefore, it has been removed. Releases: master Resolves: #92211 Change-Id: I852bc2c007f77522b3b80423f92f28a5be3c22b5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65591 Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Reviewed-by:
-
Daniel Windloff authored
Releases: master Resolves: #92210 Change-Id: Ie8c160fae548ae8cf013200e4a6d2e6344244f23 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65590 Tested-by:
-
- Sep 07, 2020
-
-
Christian Kuhn authored
Adding an image to a workspace content element adds two sys_refindex entries: One for the sys_file_reference t3ver_state=-1 and one for the t3ver_state=1 record. Deleting the image reference again in workspaces only sets one of the two to deleted in sys_refindex, leading to orphan sys_refindex entries. The patch fixes this by adding a 'redo refindex' call at the appropriate place. There are more issues when 'discard changes' is used together with multi-level relations (tt_content->hotel->offer->price): Discard does not properly cascade in those cases, yet. The patch touches this as a side-effect and does not improve the situation. The .csv files are marked with @todo accordingly and will be fixed with further patches. Those scenarios are more seldom than a broken sys_refindex for FAL images which is the primary goal of this patch. Analyzing the test scenarios, the patch actually removes various rows from sys_refindex where the left part of the relation is set to deleted. This is correct and wanted: In the end we don't want sys_refindex to contain reference to deleted rows at all. This strategy will be further followed with other patches. Resolves: #61917 Related: #67676 Releases: master, 10.4 Change-Id: I3246f263e393c6b384c2d98b0dbbcf4dbbeeccad Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65510 Tested-by:
-
Oliver Hader authored
HTTP responses having a status code not in 200-299 are basically still responses. In order to allow general response handling ResponseError is dropped in favor of AjaxResponse. Besides that `AjaxResponse.dereference()` has been introduced which allows to forward relevant data (status, headers, body) in events or broadcast messages to other `window` instances or frames. Resolves: #92222 Releases: master, 10.4 Change-Id: I3ac986980fe53bb528046f58bc19392744122ee7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65625 Tested-by:
-
Oliver Hader authored
Resolves: #92221 Releases: master, 10.4 Change-Id: Ic172280bfeb65e89c340b55330d345a9252a8838 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65623 Tested-by:
-
Nikita Hovratov authored
In some setups the conf array is null and throws an error. This patch adds the ?? operator with an empty array as fallback value. Resolves: #92216 Related: #91657 Related: #91834 Releases: master Change-Id: I95df9ad491f1284867a683a6980dbb1f6c3f3381 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65618 Tested-by:
-
Christian Kuhn authored
The PlainDataResolver is used to find overlay id's of live id's in workspace context. One usage is the ReferenceIndex. In scenarios 'modify content, discard content, modify again' with relations, the PlainDataResolver sometimes fetches rows that have been set to deleted (discarded) already together with the rows that should be fetched. Depending on the order of the result rows - which depends on the DBMS - wrong overlay rows are calculated sometimes. The patch adds a database DeletedRestriction at 3 of 4 places in the PlainDataResolver to only fetch correct rows. The last place triggers another side-effect that needs to be tackled with another patch and is commented as @todo for now. The tests add missing sys_refindex rows to the 6 tests that failed on postgres before. Additionally, for some other IRRE/CSV workspace tests, the sys_refindex changes slightly and is more correct now. Resolves: #92190 Releases: master, 10.4 Change-Id: I14f5211b5996d7f53738b9e086c3866aa1a4eaeb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65617 Tested-by:
-
Oliver Bartsch authored
Furthermore the text constants are moved to the locallang file. Resolves: #92212 Releases: master, 10.4 Change-Id: I9fd33ce977879f5f2a4b515850a214d249b8d028 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65615 Tested-by:
-
Alexander Schnitzler authored
This patch fixes incompatible type usage in function arguments and is preparatory work for introducing native type hints and strict mode in all core files. Releases: master, 10.4 Resolves: #92108 Change-Id: I9aa59588a183ee3cb43091fadd6eab2491a7cbdb Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65463 Tested-by:
-
Alexander Schnitzler authored
ext:extensionmanager This patch fixes incompatible type usage in function arguments and is preparatory work for introducing native type hints and strict mode in all core files. Releases: master, 10.4 Resolves: #92158 Change-Id: I6e5b182dde2a748312ccc39fe7cde262d331dc50 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65537 Tested-by:
-
- Sep 06, 2020
-
-
Helmut Hummel authored
For building URIs using the Symfony routing, array URL arguments are deflated (foo[bar] -> foo__bar). In case the final URI contains a remaining query string, the arguments get inflated again. However the query string of the URI is currently only updated, when at least one of the remaining arguments require a cHash. In case remaining arguments exist, the query string needs to be always updated, whether the URI requires a cHash or not. Resolves: #92183 Releases: master, 10.4, 9.5 Change-Id: I1966b4b1e8e09716733b3357922cf857543c14e4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65543 Tested-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
-
Helmut Hummel authored
In http://review.typo3.org/11011 a plain DB call that fetched the storage record was replaced with usage of StorageRepository::findByUid, which in turn calls ResourceFactory::getStorageObject again. This leads to all events also called twice. To avoid this a new internal method is introduced on StorageRepository, which only fetches the storage row again. Resolves: #92201 Releases: master, 10.4, 9.5 Change-Id: Ibce6e8d9a0b5ce7abb0f86d80ac42a1a86d47e35 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65580 Reviewed-by:
-
- Sep 05, 2020
-
-
Oliver Bartsch authored
Since #90854 the siteLanguages array also contains the -1 language which must be skipped because it otherwise falls back and generates another default language column. Resolves: #91986 Relates: #90854 Releases: master, 10.4 Change-Id: I5b1388bb9a8af7a3c14827d3aa714e23d670dcd1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65545 Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
-
Daniel Windloff authored
The `fieldArray` related configuration has been moved to the `getTable` method. The configuration handling for the `fieldArray` has been changed, in order to avoid later unset on the `fieldArray`. The `fieldArray` is only in the `getTable` and subordinated render methods. Therefore, the implicit configuration transfer like `fieldArray[0]` for the label column has been replaced. Releases: master Resolves: #92154 Change-Id: I04287e90e8cffc2ab768bd5399a8155f823fdfe1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65534 Tested-by:
-
Alexander Schnitzler authored
This patch fixes incompatible type usage in function arguments and is preparatory work for introducing native type hints and strict mode in all core files. Releases: master, 10.4 Resolves: #92106 Change-Id: I089376b6b77a0ac5f67244a19e12994ce4cdecaf Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65462 Tested-by:
-
Christian Kuhn authored
CSV fixture files are a straight way to feed test database with stuff and to assert database state after operations. Script Build/Scripts/checkIntegrityCsvFixtures.php tests those files for integrity, making sure all lines have the same number of columns. Maintaining the number of commas when fiddling with functional tests however is annoying. The patch adds options to checkIntegrityCsvFixtures.php: * '--fix' simply fixes files with broken integrity * '--fixAll' goes through all files and looks for details like superfluous comma. While --fixAll is used once now to establish a good baseline on all .csv fixtutre files, --fix can be used whenever the integrity script mumbles about broken stuff: Build/Scripts/checkIntegrityCsvFixtures.php --fix It is also added to runTests.sh: Build/Scripts/runTests.sh -s fixCsvFixtures Change-Id: Idee2a97094f56d059b02f801ffecb50a7ce21a5c Resolves: #92207 Releases: master, 10.4, 9.5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65584 Tested-by:
-
Benni Mack authored
The functionality of "exchanging" a versioned record in a workspace with a live version, is not used, and has certain downsides (e.g. it is not clear what exchange happened, not event stream to understand when was what changed, and especially when swapping single/selected items multiple times it gets really messy). Also, swapping is conceptually not working (when activated) for newly created records and leaves an inconsistent state. For these reasons, the feature is dropped. What was removed: * The option sys_workspace.swap_modes * The option to only swap on auto-publish * The option to swap in workspace module In the future it would be really beneficial to rename internal "swap" variables to "publish" to streamline this logic. Resolves: #92206 Releases: master Change-Id: Ie153a890e5d0dc6ac0b8707a2739c89922e017d7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65318 Tested-by:
-
Nikita Hovratov authored
This is the second part to replace stdWrap calls where stdWrapValue is possible instead. The type int is now a possible return type for stdWrapValue. In addition stdWrapValue can return now the string "0" if returned by stdWrap operation. Resolves: #91834 Related: #91657 Releases: master Change-Id: I70749fdb9f9cd56b86ed602afc9b742c1ed0046c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65064 Tested-by:
-
Christian Kuhn authored
The backend shortcut / bookmark handlig API was designed to hand over relevant get/post arguments as key only (eg. 'id'). The underlying code then pulled values from GET/POST or from SOBE->MOD_SETTINGS. This is ugly, there shouldn't be such magic: Only controllers know relevant keys and values, so it should hand them over directly to the shortcut API. The patch changes this: * Old and unused ViewHelper f:be.buttons.shortcut is deprecated. * ViewHelper be:moduleLayout.button.shortcutButton deprecates argument 'getVars' and adds new argument 'arguments'. * Class ShortcutButton has a new setter 'setArguments' that accepts all relevant argument key/value pairs to create a shortcut. Existing get/set related methods are deprecated. * Helper methods 'makeShortcutIcon' and 'makeShortcutUrl' of class ModuleTemplate are deprecated and implemented in class ShortcutButton directly. * All core usages are adapted to new API. * Shortcut handling was the last core usage of SOBE, so last $GLOBALS['SOBE'] = $this assignments can be finally removed. Impact: * Shortcuts to modules not directly reachable via main menu do not work due to limits of the module registration API. An example is the 'create multiple pages' controller. This issue exists before the patch, affected controllers no longer render a shortcut button for now. * The old code usually added the 'route' argument twice for shortcuts. This has been resolved. As a side effect, the comparison if a shortcuts exists (yellow shortcut icon) fails currently for existing shortcuts when the patch is applied: The comparison relies on direct string equality since shortcuts always store the final url in the database. This storage strategy should be changed with another patch that will solve the 'no yellow icon' issue at the same time. Change-Id: I3ccd2b8f6adab8e7780c5f9911fdea013ccfa99b Resolves: #92132 Releases: master Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65503 Tested-by:
-
Anja Leichsenring authored
Since symfony/mailer:5.0.8 the message object requires valid content to be accepted, so a couple of unit test have to comply to this requirement. Resolves: #92204 Releases: master, 10.4 Change-Id: I2108eb031659817c67c1c28f84e5f30ebed078a7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65583 Tested-by:
-
- Sep 04, 2020
-
-
Daniel Windloff authored
The method `listURL()` is used to set the `returnUrl` for all actions in the `DatabaseRecordList`. It replaces the usages of the method `makeReturnUrl`. Therefore, this method has been removed. Furthermore, `GeneralUtility::getIndpEnv('REQUEST_URI')` has been replaced by `listURL()`. This leads to a consistent behaviour after performing any kind of action in the `DatabaseRecordList`. Releases: master Resolves: #92192 Resolves: #83758 Change-Id: I2dc84a2c4e4103d5b4e77ebb646158e8c15f3202 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65574 Tested-by: -
Alexander Schnitzler authored
ext:linkvalidator This patch fixes incompatible type usage in function arguments and is preparatory work for introducing native type hints and strict mode in all core files. Releases: master, 10.4 Resolves: #92160 Change-Id: Ibef28b44294cd16b7fe83628490ebb556d13f083 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65539 Tested-by:
-
Oliver Bartsch authored
By creating new records the EditDocumentController did not take the default values fetched via GET / Post variables into account. This led to multiple issues when defining columns to be readOnly, disabled or hideForNonAdmins as the values are then stored in defVals parameter but never added to the final datamap. The default values are now being added to the Datahandler prior to process_datamap call. Resolves: #92119 Resolves: #88456 Resolves: #75514 Releases: master, 10.4 Change-Id: I0975dfd2417711813e1701247e8b68d8805c890b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65536 Tested-by:
Loek Hilgersom <loek@netcoop.nl> Tested-by:
-
Markus Klein authored
This change corrects the Install Tool cookie handling in various ways: 1.) It is ensured that the cookie is removed on log off 2.) Session files (var/session/*) are always removed 3.) No cookie is set until it is really needed (during login) 4.) Session expire calculation is centralized into a single method This is done by adjusting the SessionService: - Move session_start() from the constructor to a dedicated method - Session existence check employs a cookie existence check before loading an existing session into memory and validating it - destroySession() now explicitly removes the cookie - renewSession() lets session_regenerate_id() deleted old session data The Install Tool is adjusted to separate action treatment for actions requiring session interaction and those not. Resolves: #92035 Releases: master, 10.4 Change-Id: Ie666831c3eb97279fad7870638b028a577fb68f7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65358 Tested-by:
-
Oliver Bartsch authored
The divider element in the TCA option for "tt_content.imageorient" does not reflect the current state of the functionality anymore and can be removed, since the "no wrap" is not very appealing for editors to understand, and other options (e.g. above) are also without wrapping, so this div element is removed. Resolves: #50570 Releases: master Change-Id: If41b3baf2ca768521dcabc08b2e9287b9a792fa9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65579 Tested-by:
-
Alexander Schnitzler authored
Instead of using the be.widget.paginate widget, extensions are now paginated with a QueryResultPaginator and the pagination is build with the help of a SimplePagination instance. Since there is an ArrayPaginator in the core as well, the search result list is now paginated as well. Releases: master Resolves: #92003 Change-Id: I80f1d34b363d25176961139e3ded48e9ab2c165e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64524 Tested-by:
-
Timo Poppinga authored
Add mixed annotation of parameter $value in ExtensionConfiguration of method set. The static code analysis tools line phpstan can deal with it Resolves: #92181 Releases: master, 10.4 Change-Id: I9dc39737a7f6009c2dcb736c04131018a88ee36b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/65541 Tested-by:
-
