- Sep 29, 2018
-
-
Josef Glatz authored
This patch re-adds a missing functionality to CKEditor. Due to the move from htmlArea to CKEditor, the well-known wordcount information was gone. The wordcount information is added to all existing CKEditor presets per default. In addition, it is now possible to customize the displayed information below the editor. - It's possible to switch paragraph-, word- and/or character count. - You can define if spaces are counted as charactars. - You can define if HTML tags are taken into account. - You can define if linebreaks are taken into account. Beside that, the used plugin enables also setting up maximum values for word- and/or character count. This can be easily used for custom RTE presets. The fact that the global configuration is located in the Base.yaml makes it possible to overwrite settings partially or completely in any inherited RTE preset. With that it is easy possible to realize word/character limits. Following commands were used to add the external package as a dependency and copy the plugin files/folders to the final location: `yarn add --dev ckeditor-wordcount-plugin && yarn build` Resolves: #86395 Releases: master Change-Id: I2c76d7bfebc9a5a57c1f105788af206bdffb00f2 Reviewed-on: https://review.typo3.org/58405 Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
TYPO3com <no-reply@typo3.com> Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
Normalized Params only needs serverParams and $TYPO3_CONF_VARS[SYS] to work with, so the object is modified in order to simplify further work on the object. Resolves: #86454 Releases: master Change-Id: I30f2c6195468b275e61570c1de67b39f281bb494 Reviewed-on: https://review.typo3.org/58471 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
Nikita Hovratov authored
The tooltip has to be removed at that point, because as soon as any data is deleted the row disappears and it's not possible to trigger the mouseout event manually. Resolves: #81856 Releases: master, 8.7 Change-Id: I2f7388b6a278de9ba19e81ec20ed3ae0052b1698 Reviewed-on: https://review.typo3.org/58463 Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <no-reply@typo3.com>
-
Georg Ringer authored
Sort the extension settings by the extension key. Resolves: #86452 Releases: master Change-Id: I6fb0110820d4a8406f01b617b3279640be9aa743 Reviewed-on: https://review.typo3.org/58470 Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
Benni Mack authored
Instead of explicitly call loadJQuery() this should be handled by requireJS or - even better - use vanilla JavaScript instead. Resolves: #86438 Releases: master Change-Id: Iecc2ceb7fa01578b00a63262f393bd1b92fa13e1 Reviewed-on: https://review.typo3.org/58455 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com>
-
Benni Mack authored
The following methods will trigger a deprecation warning if they are called from the outside: - TemplateService->prependStaticExtra() - TemplateService->versionOL() - TemplateService->processIncludes() - TemplateService->mergeConstantsFromPageTSconfig() - TemplateService->flattenSetup() - TemplateService->substituteConstants() Several other methods have been marked as internal. Resolves: #86439 Releases: master Change-Id: Ifabbda8048449e6919d054da4111f01065a5eeab Reviewed-on: https://review.typo3.org/58456 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
Install Tool still uses TYPO3's own RequestHandler interface which exists since TYPO3 v7, but is superseded with PSR-15's RequestHandler concept. Install Tool now uses PSR-15 and the old interface in order to still use the priority concept. In a further step, both RequestHandlers should be migrated to Middleware+RequestHandler concept. Resolves: #86451 Releases: master Change-Id: I55cf31a2b803951491ba072969a4cff68ef2c2ac Reviewed-on: https://review.typo3.org/58469 Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
Benni Mack authored
The phpDoc comment "@internal" is used in most places during the development of TYPO3 v7, TYPO3 v8 and TYPO3 v9 and denotes that this specific method, class or property is not part of the Public API, and does not even need any notice if it is removed. However, we still have/had various places in TYPO3 core where "@access private" was used. This is now migrated to "@internal". "@access public" is not needed and is removed. Resolves: #86446 Releases: master Change-Id: Iaef206b04aee13c280d62b107dd7eac04a38c700 Reviewed-on: https://review.typo3.org/58462 Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
Susanne Moog authored
As the core uses American English, 'analyze' should be spelled with a `z`. This looked especially strange in the install tool, where both spellings were mixed on one card. Resolves: #86447 Releases: master Change-Id: I484f75a05d3cf988baaebf91df30cd936f454eac Reviewed-on: https://review.typo3.org/58454 Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
Benni Mack authored
The property "checkWorkspaceCurrent_cache" is now protected. Second method argument of "modAccess()" is deprecated. "isPSet()" is not in use anymore, and will be removed in TYPO3 v10.0. Some other methods, which are workspace-related, are marked as internal in order to properly move them into EXT:workspaces in the next version. Resolves: #86441 Releases: master Change-Id: Ie776e71cdc7485937b2a38e7cfc93c13aba925ab Reviewed-on: https://review.typo3.org/58458 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
Benni Mack authored
Use @internal where access private was marked, also add some meaning to currently public methods that should only be used by TYPO3 Core. Resolves: #86442 Releases: master Change-Id: If90f1a6dc6cad1edb0db2179cb87f5e6eb18f2ec Reviewed-on: https://review.typo3.org/58459 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Reviewed-by:
Ralf Zimmermann <ralf.zimmermann@tritum.de> Tested-by:
Ralf Zimmermann <ralf.zimmermann@tritum.de>
-
Benni Mack authored
Page-based routing can now be configured within a site configuration to add so-called "route enhancers" which allow to add more placeholders to a route for a page. There are three Enhancers that TYPO3 now ships with: - SimpleEnhancer - PluginEnhancer - ExtbasePluginEnhancer It is also possible to add custom enhancers by third- party extensions. Each placeholder within an enhancer can receive a so-called "Aspect", usually used for mapping speaking values instead of IDs, or month-names in an archive link, and "modifiers" to modify a placeholder. The simple enhancer transfers a link parameter, previously maybe used to add a `&product=123`, which will now result into `/product/123` for a page. PluginEnhancer adds a namespace, common for simple plugins or Pi-Based plugins, and the ExtbasePluginEnhancer adds logic for multiple route variants to be added, depending on the controller/action combinations. Aspects are processors / modifiers / mappers to transfer a placeholder value back & forth to make each placeholder value more "speaking". TYPO3 Core ships with the following aspects: * LocaleModifier (for localized path segments) * StaticValueMapper (for path segments with a static list) * StaticRangeMapper (for pagination) * PersistedAliasMapper (for slug fields) * PersistedPatternMapper (for database records without slug fields) Routing now returns a so-called "PageArguments" object which is then used for evaluating site-based URL handling and the cHash calculation. It is highly discouraged to access _GET or _POST variables within any kind of code now, instead the PSR-7 request object should be used as much as possible. Releases: master Resolves: #86365 Change-Id: I77e001a5790f1ab3bce75695ef0e1615411e2bd9 Reviewed-on: https://review.typo3.org/58384 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Hader <oliver.hader@typo3.org>
-
Christian Kuhn authored
With the new routing, TYPO3 relies on a default redirect to index.php for FE requests. The patch checks during installation if apache or IIS are used and creates the default .htaccess / web.config files. Change-Id: I9406a7e4d91050d3f5bf96dd63e4bf63e8f71250 Resolves: #86173 Releases: master Reviewed-on: https://review.typo3.org/58451 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Anja authored
Change-Id: I6fccf8db0ab996139692a07be8d08ceb8feee86f Releases: master Resolves: #86434 Reviewed-on: https://review.typo3.org/58448 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de> Reviewed-by:
Michael Oehlhof <typo3@oehlhof.de> Tested-by:
Michael Oehlhof <typo3@oehlhof.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
lsascha authored
Releases: master, 8.7 Resolves: #86396 Change-Id: I198fe52a8024dcf392582a78c3fce0f134ed6b7a Reviewed-on: https://review.typo3.org/58406 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com>
-
Christian Kuhn authored
This adds a dummy wizard to remind admins during upgrade to check the live system for argon2i support if the local instance uses it, or to select a different hash algorithm. Having this wizard gives this information to admins early in the upgrade phase, so they have time to check the live system or to select a different mechanism before too many passwords have been upgraded. Resolves: #86402 Releases: master Change-Id: I2b1f75ecf079dc2e29d2675dda558c79b67f77e0 Reviewed-on: https://review.typo3.org/58411 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
Helmut Hummel authored
During generation of processed files a wrong processed folder is evaluated when the processed folder resides on a different storage. We now ensure to ask the correct storage for the processed folder. Also ensure that correct storage is used for checking file existence when original file and processed files are on different storages. Fixes: #86399 Releases: master, 8.7 Change-Id: I254b9a0bf86a156ae135510a4439e87737ec1a29 Reviewed-on: https://review.typo3.org/58410 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
Nicole Cordes <typo3@cordes.co>
-
Benni Mack authored
Most of the occurrences have been replaced by using Environment API. On top, labels are now moved into "var/labels" for existing composer-based installations, moving XLF files out of the document root when the environment is configured to allow files outside of the document root. For non-composer-based installations, labels are still available under "typo3conf/l10n". Resolves: #85560 Releases: master Change-Id: Ib0a9e8e3dcd685109b9d922aee1970e68b265179 Reviewed-on: https://review.typo3.org/57600 Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
Benni Mack authored
We recently removed the "site" base prefix within the yaml configuration file of a site configuration. However, the indention is wrong when using FormEngine to edit the site configuration within the "old" syntax. Resolves: #86437 Related: #86323 Releases: master Change-Id: I487940188b04c4977d179337cb142f2452c3bace Reviewed-on: https://review.typo3.org/58449 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Hader <oliver.hader@typo3.org>
-
Benni Mack authored
We want the latest dependencies in our LTS version, so this should ship the latest versions in the zip/tarballs. Used command: composer update symfony/* \ doctrine/* \ friendsofphp/* \ nikic/php-parser \ --with-dependencies Resolves: #86432 Releases: master Change-Id: I46b7ea46033d4f2c4d0148de537728d2b9ff22c2 Reviewed-on: https://review.typo3.org/58447 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
Anja authored
Provide a silent upgrader the same way as for BE/loginSecurityLevel to avoid FE login to fail after upgrade. Change-Id: I8c27c370206effc1f88fd5334b9f20f01a628757 Resolves: #86417 Releases: master Reviewed-on: https://review.typo3.org/58429 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
Josef Glatz <josef.glatz@typo3.org> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de>
-
Benni Mack authored
The following legacy TypoScript options have been deprecated - stdWrap.filelist - stdWrap.filelink - stdWrap.addParams The acompanied methods are deprecated as well - cObj->stdWrap_addParams - cObj->stdWrap_filelink - cObj->stdWrap_filelist - cObj->addParams - cObj->filelink - cObj->filelist - cObj->typolinkWrap - cObj->currentPageUrl These are not in use anymore, due to removal of CSS Styled Content. Resolves: #86433 Releases: master Change-Id: Ie90dce49c050092c1a359491301ad3f3dd04ee4f Reviewed-on: https://review.typo3.org/58418 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de>
-
- Sep 28, 2018
-
-
Benni Mack authored
In order to be in line with the new PageArguments object, this newly introduced class is now renamed. Resolves: #86431 Releases: master Change-Id: I96575338538641fc27a578c49868b21100b61ed3 Reviewed-on: https://review.typo3.org/58446 Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
Tymoteusz Motylewski authored
Resolves: #86423 Releases: master, 8.7 Change-Id: I5c1e0f92fe5f9d28eaaf0250677cd3dedcbd6082 Reviewed-on: https://review.typo3.org/58436 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
Andreas Fernandez authored
To render the „Executing foo“ text in the progress bar when a upgrade wizard is executed correctly, a missing `data-title` attribute is added. Resolves: #86430 Releases: master Change-Id: I53f6f1a551de132452695a400561e46e9c1e4fb4 Reviewed-on: https://review.typo3.org/58442 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
Josef Glatz <josef.glatz@typo3.org> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com>
-
Georg Ringer authored
The cropping element shows an information if no dimensions are known. The styling of this information is now improved. Resolves: #86429 Releases: master, 8.7 Change-Id: I28b6e4da560e591a57e6c849488f59ddf5cd5736 Reviewed-on: https://review.typo3.org/58441 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
Josef Glatz <josef.glatz@typo3.org> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com>
-
Oliver Hader authored
When previewing translated pages in the backend, URLs contain `&L=x` at the end. This is due to a missing transformation into the `_language` parameter as well a missing SiteLanguage resolving. Resolves: #86421 Releases: master Change-Id: I5da496d0224635b1ee849dd7a724145ad2c0d408 Reviewed-on: https://review.typo3.org/58438 Reviewed-by:
Richard Haeser <richard@maxserv.com> Tested-by:
Richard Haeser <richard@maxserv.com> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Josef Glatz <josef.glatz@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
Frank Naegler authored
Resolves: #86427 Related: #86404 Releases: master Change-Id: Iec990bd910ac62805d4584c468b265f57c0fd17d Reviewed-on: https://review.typo3.org/58437 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
Susanne Moog authored
A new key "site" for TypoScript "getText" has been introduced which allows accessing site configuration. Resolves: #86422 Releases: master Change-Id: Id0efae08445b8890021fb2b68a88c4ac8db5a6fa Reviewed-on: https://review.typo3.org/58434 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
Tobi Kretschmann <tobi@tobishome.de> Tested-by:
Tobi Kretschmann <tobi@tobishome.de> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
Christian Kuhn authored
Using the element browser for a type=group, internal_type=file_reference TCA field leads to an exception due to a missing registration for this mode. Register the file browser, similar to internal_type=file. Resolves: #80541 Releases: master, 8.7 Change-Id: I54be7084f10d63ed262e903c296294589521f3df Reviewed-on: https://review.typo3.org/58431 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Christian Kuhn authored
Properties $MOD_SETTINGS and $modTSconfig of RecordListController are still used by DatabaseRecordList through $GLOBALS['SOBE']. These two have to stay public for the time being to not trigger a bunch of deprecation log entries on each call of the list module. Change-Id: I87188b2065f4933e45203de58027f92db98bf840 Resolves: #86418 Related: #86198 Releases: master Reviewed-on: https://review.typo3.org/58430 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Tested-by:
Mathias Brodala <mbrodala@pagemachine.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
Gianluigi Martino authored
During the translation process the option "disablePrependAtCopy" is not respected. With this patch the option is respected again for pages and tt_content. Resolves: #86293 Releases: master, 8.7 Change-Id: I821f3fed7d3e0637298262c4bd2c11003618f1c5 Reviewed-on: https://review.typo3.org/58424 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
Guido Schmechel authored
Now it is also possible to add private Vimeo links. Releases: master, 8.7 Resolves: #83852 Change-Id: Icb425d4aea98a687b91216fefcd69b5fecc1a01e Reviewed-on: https://review.typo3.org/58404 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jörg Bösche <typo3@joergboesche.de> Tested-by:
Jörg Bösche <typo3@joergboesche.de> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org>
-
Jigal van Hemert authored
The Create Multiple Pages action now only displays the new structure in the default language and hides pages in other languages that are already in the pagetree. Resolves: #86378 Releases: master Change-Id: I14e45436d62300465d93ee87408523372007e394 Reviewed-on: https://review.typo3.org/58393 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
Josef Glatz <josef.glatz@typo3.org> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
Benjamin Franzke authored
FailsafePackageManager prevents saving PackageStates.php in failsafe mode by overwriting sortAndSavePackageStates(). That works to prevent saving, but also prevents sorting when initially loading packages when PackageStates.php is missing. Currently this does not really produce problems, as the install tool creates a new PackageStates.php later on and saves (and implicitly sorts them) using forceSortAndPackageStates(). To fix the intermediate state we now only prevent saving, but not the sorting of packages. Releases: master Resolves: #86408 Change-Id: I02ccb20653700e696d89b0a6ff39253f4f1ebc73 Reviewed-on: https://review.typo3.org/58416 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
Benjamin Franzke authored
CacheManager has a design problem: The CacheManager is used to create the core_cache. That core_cache is used to read the (possibly) cached CacheManager configuration, which is then used to configure the already-being-used CacheManager. That means the initialization sequence currently is like: new CacheManager(!$failsafe) | setInitialCacheConfiguration() | loadExtLocalconf() | setFinalCachingFrameworkConfiguration() Between initial creation of the CacheManager and setFinalCachingFrameworkConfiguration() the CacheManager is in a limbo state, as it may already be used to create a cache although the final configuration (which may be configured in ext_localconf.php) for that cache has not been set. The final configuration (for that created cache) will then be ignored, as the cache has already been created. This is not a theoretical problem, but is actually happening in core for two caches (introduced due to patches in the v9 development phase, more on those later). In v10 we want to change the sequence to the following: $coreCache = createCoreCache() | loadExtLocalconf | new CacheManager(!$failsafe, $cachingConfiguration, $coreCache); We want to delay CacheManager until ext_localconf.php has been loaded (maybe also after baseTca loading) in v10. Therefore GeneralUtility::makeInstance(CacheManager::class) usage in ext_localconf.php is deprecated now. Note: The core cache cannot be modified in ext_localconf.php - that was always the case and wouldn't make sense (as that cache is used to actually load the cached ext_localconf.php) Two caches are actually loaded too early during ext_localconf.php loading currently. We fix these as a drive-by: * extbase_reflection: the extbase Object\Container is instanciated in EXT:extbase/ext_localconf.php. The Object\Container then instanciates the ReflectionService in its constructor which itself creates the extbase_reflection using the CacheManager (all of that during ext_localconf.php loading). This is actually a regression introduced in https://review.typo3.org/54381 We change the Container to load the reflection cache on demand. * assets: * IconRegistry uses the 'assets' cache and loads cached backend icons during object construction. This cache was introduced in https://review.typo3.org/c/54020/ using the core cache, and was later changed to 'assets' in https://review.typo3.org/54061 * PageRenderer loads cached requireJS configuration from 'assets' We inject assetsCache to these services from Bootstrap for now. We'll only be able to properly refactor this, when dropping support for ext_localconf.php altogether. We also adapt the ExtensionManagementUtility to retrieve the coreCache as parameter, instead of statically. Although these methods are marked @internal, we keep them for 9LTS to not break extensions (using this regardless of being @internal, e.g. helhum/typo3-console) shortly before the release. Change-Id: I22935dae3acb6e8de14fa98a6b88f3477a3ea313 Releases: master Resolves: #86353 Resolves: #86371 Resolves: #86372 Reviewed-on: https://review.typo3.org/58371 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
Benni Mack authored
The functionality is moved into a new PSR-15 middleware to base the logic on the request object directly, and to make the validation more flexible when validating page parameters for site-based routing. The previous deprecation to add the request object to the method has been reverted. Resolves: #86411 Releases: master Change-Id: I294fae7e7c0f9eb1e128a88238dabdd8ed27619f Reviewed-on: https://review.typo3.org/58420 Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
Josef Glatz authored
Make it impossible to select the page you are currently working on within the suggest wizard result set. Releases: master, 8.7 Resolves: #86412 Related: #54867 Change-Id: Ibeaacf86061f79cc3d75f181466e5caf96657401 Reviewed-on: https://review.typo3.org/58423 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Peter Kraume <peter.kraume@gmx.de> Tested-by:
Peter Kraume <peter.kraume@gmx.de> Tested-by:
Richard Haeser <richard@maxserv.com> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de>
-
Susanne Moog authored
To enable easy configuration of environment specific site setting, usage of environment variables in site configuration yaml has been introduced. The TYPO3 Core Yaml loader is now able to resolve variables from environment variables. Resolves: #86409 Releases: master Change-Id: Ic1e32d231aa7e92b3feb4ed4c31bed72520d71fb Reviewed-on: https://review.typo3.org/58358 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org>
-
nebrot authored
Releases: master Resolves: #86415 Change-Id: Ib8002843376e651446a16143699844a98baebc0b Reviewed-on: https://review.typo3.org/58425 Reviewed-by:
Daniel Siepmann <daniel.siepmann@typo3.org> Tested-by:
Daniel Siepmann <daniel.siepmann@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Tested-by:
Mathias Brodala <mbrodala@pagemachine.de>
-