This project is mirrored from https://git.typo3.org/typo3/typo3.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
- 19 Dec, 2017 1 commit
-
-
Instead of integers, the permission constants should be used throughout the TYPO3 Core. Resolves: #83383 Releases: master Change-Id: I00c10f97fc800d9533866c98284bbd22cd1bb575 Reviewed-on: https://review.typo3.org/55156 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 16 Dec, 2017 1 commit
-
-
The "self_accessor" fixer is more strict with younger php-cs-fixer releases and changes method argument type hints to self if a class object of the same class is expected. It also changes return type hints to self in this case. This fixer now may collide with the "xclass" system of the core and is thus deactivated. We shoud decide manually if self or class name is used. Change-Id: I3a8c20bea1d79ac2c7bc1e9ecbc2d435c4047843 Resolves: #83360 Related: #83331 Releases: master, 8.7 Reviewed-on: https://review.typo3.org/55121 Reviewed-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Stephan Großberndt <stephan@grossberndt.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
- 15 Dec, 2017 1 commit
-
-
To prevent timing-attacks on hash-comparions it is advised to use hash_equals. Resolves: #83329 Releases: master, 8.7 Change-Id: I7539ed27538d7d81767bfce582d568cff09d1610 Reviewed-on: https://review.typo3.org/55074 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:
Stephan Großberndt <stephan@grossberndt.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
Helmut Hummel <typo3@helhum.io>
-
- 12 Dec, 2017 1 commit
-
-
A wrong type given to JsonResponse->setPayload() fatals the return type on expanding the filelist folder tree. Change-Id: I7510ba7d5098b8b91c5016472487f73c6ca77e2c Resolves: #83303 Releases: master Reviewed-on: https://review.typo3.org/55053 Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com>
-
- 11 Dec, 2017 1 commit
-
-
Michael Oehlhof authored
The page title was shown htmlescaped in the new page tree. Resolves: #83277 Releases: master Change-Id: I34a06e06d35d435d13d00d3d0a715a25deec384c Reviewed-on: https://review.typo3.org/55017 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de>
-
- 09 Dec, 2017 3 commits
-
-
If the access to the element information is not allowed, show some information to the user instead of returning an empty string. Resolves: #83067 Releases: master, 8.7 Change-Id: Ie4ca3ba41556813a44802fc60befe164a17c4178 Reviewed-on: https://review.typo3.org/54811 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Henning Liebe <h.liebe@neusta.de> Reviewed-by:
Michael Oehlhof <typo3@oehlhof.de> Tested-by:
Michael Oehlhof <typo3@oehlhof.de> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
Instead of doing manual queries for each tree level, and checking for children on each tree level, the page tree now fetches all pages the user has access to, and checks if this works out. Resolves: #83233 Releases: master Change-Id: I45a6b834ef1fe71e5748dfc8de9bcf6dad8172c9 Reviewed-on: https://review.typo3.org/54887 Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
The new JsonResponse object should be used throughout the TYPO3 Backend in order to properly call json_encode() with the right flags automatically, making the code inside the controllers simpler. Resolves: #83267 Releases: master Change-Id: Ie03fb1414a965a61632897f0e25645a67f3225a5 Reviewed-on: https://review.typo3.org/54995 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
- 08 Dec, 2017 3 commits
-
-
Stephan Großberndt authored
Clicking the close button in a editing popup accesses Close.html in Resources/Public/Html/ which is a folder accessible by a web user instead of Resources/Private/Templates/ which lead to a HTTP 403 error on closing the popup. Releases: master, 8.7, 7.6 Resolves: #83258 Related: #68108 Change-Id: Ibe7e328936240df436a3c9585e53122f1577dc6e Reviewed-on: https://review.typo3.org/54983 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> Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de>
-
With #82254 LocalConfiguration serialized array EXT/extConf has been changed to a not serialized array in EXTENSIONS. This patch follows up on this task an finishes various tasks: * An install tool silent upgrader upmerges given EXT/extConf settings to EXTENSIONS array. The resulting EXTENSIONS array does not contain dots for sub paths in its array key anymore and is accessible with a new ExtensionConfiguration->get() API to fetch values and whole extension config. * A new API is introduced to get() and set() extension specific configuration, is documented and used throughout the core to not unserialize old EXT/extConf anymore. Setting values updates legacy EXT/extConf to new values including compatible 'dot' ending on nested array configurations. * If extensions come with new configuration items in ext_conf_template.txt a silent upgrader of the install tool synchronizes these to the EXTENSIONS and old extConf array. Extension authors can rely on that and always fetch new keys from the new ExtensionConfiguration->get() API right away. The synchronization is also triggered when new extensions are loaded or extensions are updated via the extension manager. * Core usages are adapted to the new API. * Next to the main get() / set() API, the extension configuration form is extracted from the extension manager and put into the install tool as a new card in "Settings". The code below is streamlined and encapsulated with just a couple of public methods in class 'ExtensionConfigurationService' as internal class for use in install tool and extension manager. Resolves: #82368 Related: #82254 Releases: master Change-Id: I88568fa355f8f6fd5acc9850dcdd718fdd9a1b2e Reviewed-on: https://review.typo3.org/54034 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Daniel Gorges <daniel.gorges@b13.de> Tested-by:
Daniel Gorges <daniel.gorges@b13.de> Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
The „list“ wizard now checks whether the redirectUrl was given with the request and uses this, otherwise it falls back to REQUEST_URI. Resolves: #83146 Releases: master, 8.7 Change-Id: I0572e6f20c89f77bf11a1c7c2257e4a2c10f4f12 Reviewed-on: https://review.typo3.org/54841 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Wolfgang Klinger <wolfgang@wazum.com> Reviewed-by:
Alexander Opitz <opitz.alexander@googlemail.com> Tested-by:
Alexander Opitz <opitz.alexander@googlemail.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
- 04 Dec, 2017 1 commit
-
-
Since the page tree change, some default labels are not available anymore. This patch re-adds missing labels for debugger and module wizards. Resolves: #83208 Releases: master Change-Id: I2be56c573b7099ee1bedab0238b839bf9867f73e Reviewed-on: https://review.typo3.org/54922 Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 30 Nov, 2017 4 commits
-
-
This patch resolves problem with the injured workspace encapsulation for removed records while fetching the record localize summary in page module within a workspace. Resolves: #78841 Releases: master, 8.7 Change-Id: I734a32c7b52ed4a2a3ab49c63d45df46472a99a4 Reviewed-on: https://review.typo3.org/50881 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Hader <oliver.hader@typo3.org>
-
The ExtJS/ExtDirect based page tree has been replaced with new implementation based on SVG. Refactoring and performance improvement of the PHP side (tree data provider) will be done in the followup patch. Releases: master Resolves: #82426 Change-Id: I502a085da939ebe2561d2b7a17cc8347e5101623 Reviewed-on: https://review.typo3.org/51594 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> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
Change-Id: I3f74892da6c82a7213b7f77d5027160ee118eabb Resolves: #83174 Releases: master Reviewed-on: https://review.typo3.org/54886 Reviewed-by:
Sebastian Hofer <sebastian.hofer@marit.ag> Tested-by:
Sebastian Hofer <sebastian.hofer@marit.ag> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
The new PSR-7-based solution since TYPO3 v7 should be used everywhere instead of "BackendUtility::getModuleUrl()". This is possible because modules can be addressed via the "route" GET parameter instead of the "M" parameter since a few months. The patch changes all occurrences within TYPO3 Core to use the new API. Resolves: #83172 Releases: master Change-Id: Iec40e8ae00f1d900d7479b84a3a62827ddba653b Reviewed-on: https://review.typo3.org/54755 Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@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>
-
- 29 Nov, 2017 4 commits
-
-
Releases: master Resolves: #83023 Change-Id: I9fe436f94a1223020b5fd0c308fa5bdb1b81ec39 Reviewed-on: https://review.typo3.org/54671 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Nicole Cordes <typo3@cordes.co> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org>
-
Remove TYPO3.LLL after moving to new JS API for translations TYPO3.lang Resolves: #83161 Releases: master Change-Id: I815b15349c8bfe6ca71f4d1ce59b7b01e670eae2 Reviewed-on: https://review.typo3.org/54860 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org>
-
TYPO3 core uses new JS api for fetching language labels - TYPO3.lang. Resolves: #83142 Releases: master Change-Id: I690b667b27d1152556b147e7198260fae018c62b Reviewed-on: https://review.typo3.org/54836 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Łukasz Uznański <l.uznanski@macopedia.pl> Tested-by:
Łukasz Uznański <l.uznanski@macopedia.pl> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com>
-
It was not possible due to a form name mixup to add online media files via the FileList in TYPO3 v9 anymore. Related: #82436 Related: #81763 Resolves: #83151 Releases: master Change-Id: Ica0ed049f685bf20b98f0a599adf61ec3874017a Reviewed-on: https://review.typo3.org/54847 Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Andreas Fernandez <typo3@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>
-
- 28 Nov, 2017 2 commits
-
-
Due to the change of the pages_language_overlay migration, a lot of hard-coded "l10n_parent" and "sys_language_uid" fields for pages have been introduced. This should be changed into a common function in DataHandler and the TCA option should be used instead. Resolves: #83013 Releases: master Change-Id: I43a33aac1015436109d1ca7b3ea200c78d2a2fb9 Reviewed-on: https://review.typo3.org/54664 Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
`top.TYPO3.Storage` is now globally available again, it's not necessary to load this module via RequireJS. Please keep in mind this module is deprecated. Resolves: #83049 Related: #82603 Releases: master Change-Id: I72796f377063c683f024a223818a599edade5367 Reviewed-on: https://review.typo3.org/54704 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:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org>
-
- 27 Nov, 2017 5 commits
-
-
When IRRE actions (localize/synchronize) are triggered that result in a DataHandler error (e.g. "Localization failed, "languageField" and "transOrigPointerField" must be defined for the table") because of a missing configuration, the current implementation does not evaluate DataHandler results in the JSON response. The change adds the same functionality as for other DataHandler calls to evaluate the JSON response. Resolves: #83011 Releases: master, 8.7 Change-Id: I7a2069b78cd9c3fa031b7ac194ae5b18596b6a3e Reviewed-on: https://review.typo3.org/54659 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de> Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com>
-
Clicking on the Save & Close button in the FileList text file editing form redirects back to the list view. Releases: master Resolves: #83090 Change-Id: I14576da7a77835232ca9573a8964f0d754f52aff Reviewed-on: https://review.typo3.org/54757 Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Andreas Fernandez <typo3@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>
-
Several hundred function calls and vast numbers of indentations can be saved by using the null coalesce operator instead of checking empty/array. Change-Id: I38f2ce2de83a454aaa0d16c771014b6de84b3f7a Releases: master Resolves: #80812 Reviewed-on: https://review.typo3.org/52416 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:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
This patch applies the phpdoc_types_order rule of the php-cs-fixer. See http://cs.sensiolabs.org/ -> phpdoc_types_order Releases: master, 8.7 Resolves: #83109 Change-Id: I57291fb0b113ad01e2a171c1cfd6a9943d6302ad Reviewed-on: https://review.typo3.org/54779 Reviewed-by:
Alexander Opitz <opitz.alexander@googlemail.com> Tested-by:
Alexander Opitz <opitz.alexander@googlemail.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
This patch applies the phpdoc_types rule of the php-cs-fixer. See http://cs.sensiolabs.org/ -> phpdoc_types Releases: master, 8.7 Resolves: #83106 Change-Id: I958b75d85a08169a987afe9eed0baa4d86139770 Reviewed-on: https://review.typo3.org/54770 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 26 Nov, 2017 1 commit
-
-
Over the years many different non-standard phpdoc anotations made it into that core which will now break the AnnotationReader of doctrine. Therefore either all these annotations need to be ignored or removed/replaced. As it is easier to actually solve the issues instead of hiding them this patch removes or replaces most non-standard annotations and configures to ignore some of them like @extensionScannerIgnoreFile and @extensionScannerIgnoreLine which are introduced by TYPO3 but cannot be replaced as they provide a decent functionality Releases: master Resolves: #83103 Change-Id: Iba8f39600fe7273dd560592cef40ad56f83a5e73 Reviewed-on: https://review.typo3.org/54768 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:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
- 16 Nov, 2017 2 commits
-
-
TSConfig properties keepItems and removeItems are checked with a weak in_array() test (third argument not set to true), which leads to the situation, that arbitrary string values are treated equal to integer 0 This is now fixed by flipping the array and check for the array index. This works nicely because PHP silently converts strings which look like integer to integer for the keys. Tests are added which cover these cases and demonstrate the failure before the change. Resolves: #82980 Releases: 8.7, master Change-Id: I544a221674fa89d302cb6c1bcca506847c6f7f0f Reviewed-on: https://review.typo3.org/54623 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Henning Liebe <h.liebe@neusta.de> Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Reviewed-by:
Jan Stockfisch <jan.stockfisch@googlemail.com> Tested-by:
Jan Stockfisch <jan.stockfisch@googlemail.com> Reviewed-by:
Jigal van Hemert <jigal.van.hemert@typo3.org> Tested-by:
Jigal van Hemert <jigal.van.hemert@typo3.org>
-
Resolves: #82921 Releases: master, 8.7 Change-Id: Id26239e65321aa3653de849932a0be7e626bd653 Reviewed-on: https://review.typo3.org/54558 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frans Saris <franssaris@gmail.com> Tested-by:
Frans Saris <franssaris@gmail.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
- 09 Nov, 2017 1 commit
-
-
Because users have no access to deleted pages, the access check always fails, leading to delete page actions not being shown in the history despite being properly tracked. We now check this case and do a more lightweight check so that we still have the permissions checked, but can show deleted pages without disclosing unwanted information. Resolves: #45056 Releases: 7.6, 8.7, master Change-Id: Id919a24651c18a351f9723e86610b525a4f4726c Reviewed-on: https://review.typo3.org/54580 Reviewed-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org>
-
- 08 Nov, 2017 4 commits
-
-
Ensure that jQuery is available in NewRecordController. Resolves: #75676 Releases: master Change-Id: Idf437554fb136e8e4ae18ce0d229d6b3ed8a58e4 Reviewed-on: https://review.typo3.org/54587 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org> Reviewed-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
Benjamin Kott <benjamin.kott@outlook.com>
-
Instead of having the new content element wizard in a separate module page it will be opened in a modal now. Resolves: #75676 Releases: master Change-Id: If117fe3f2d55a4163bcb5c153b47938953050348 Reviewed-on: https://review.typo3.org/52999 Tested-by:
Bjoern Jacob <bjoern.jacob@tritum.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Andreas Fernandez <typo3@scripting-base.de> Reviewed-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
Benjamin Kott <benjamin.kott@outlook.com>
-
Benni Mack authored
The patch migrates all data from pages_language_overlay into pages, and moves all API calls to overlay pages. The following restrictions are set: * Backend is always showing pages only for "sys_language_uid=0" for the page tree, element browser (e.g. "linking to default language page"), except where explicitly requested like the Page Module => Languages view. * pid and sorting are always the same for all translations and their default language page * Elements on a page are always keeping the field "pid" to the default language page (no change) * Permission checks for Backend users are always made against the default language page (perms_* fields and webmounts) Resolves: #82445 Releases: master Change-Id: I62536e21d7110fa434c75fbd4470a3f53b79d260 Reviewed-on: https://review.typo3.org/51272 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Frans Saris <franssaris@gmail.com> Tested-by:
Frans Saris <franssaris@gmail.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Andreas Fernandez <typo3@scripting-base.de>
-
The title of a translated page must be overlayed with the workspace version. Resolves: #65607 Releases: master, 8.7, 7.6 Change-Id: If10260f196776a16a53968b78542827ecbc145fe Reviewed-on: https://review.typo3.org/54583 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
- 06 Nov, 2017 1 commit
-
-
The following pageTSconfig options are removed: - options.pageTree.excludeDoktypes No doktypes are exclueded anymore in search. - options.pageTree.disableIconLinkToContextmenu Icon Links are always selected (option had no effect anymore). - options.pageTree.searchInAlias Alias is now always searched for. - options.pageTree.hideFilter The filter is always shown, this feature should not be available on a per-user basis. Resolves: #82919 Releases: master Change-Id: Ie0031fef9948bf758e880b04662210d74e27688b Reviewed-on: https://review.typo3.org/54560 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
TYPO3com <no-reply@typo3.com> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Eugene Kenah Djomo <kdeugene@yahoo.fr> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 03 Nov, 2017 1 commit
-
-
If an inline child, opened via ajax request, generates links leaving the current records and opening a different one, on closing that record the returnUrl is wrong and points to the url of the inline ajax request. The original return url of the main record is lost in the compile chain. The returnUrl data provider sets $data['returnUrl'] to current url if not otherwise given. The patch hands over the original return url to the inline ajax controller and lets it 'sink down' in the data compile chain to inline children so the original return url is available when container or elements generate urls. Additionally some broken 'returnURL' handling in InlineRecordContainer and jsfunc.inline.js is cleaned up and removed. Change-Id: Ia47dc8cee068fc9c4d1c5e16c1960b1a58fcb2f5 Resolves: #82525 Releases: master, 8.7 Reviewed-on: https://review.typo3.org/54543 Tested-by:
TYPO3com <no-reply@typo3.com> Tested-by:
Kjeld Schumacher <k.schumacher@familie-redlich.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
- 02 Nov, 2017 1 commit
-
-
The following functionality within this API class is marked as deprecated: - siteRelPath() - getExtensionKeyByPrefix() - removeCacheFiles() - second parameter of isLoaded() Additionally, the following more strict rules apply now: - addNavigationComponent() always requires an $extensionKey - First parameter of addLLrefForTCAdescr() must not be empty - addService() requires $serviceType and $info to be non-empty - addPlugin() always requires an $extensionKey - addStaticFile() throws exceptions if no extension key or path is set - addTypoScript() expects $type to be either "setup" or "constants" This is meant for extension developers using the current API more properly than before. Resolves: #82899 Releases: master Change-Id: Ie5beddd4787da25f05f76ff37c6ec55a92257001 Reviewed-on: https://review.typo3.org/54523 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org>
-
- 19 Oct, 2017 1 commit
-
-
The AjaxLoginHandler which does AJAX logic for login timeouts is be moved to the proper location, as it is a controller. A class alias is in place. Resolves: #82805 Releases: master Change-Id: I6a9fed6236d6d82150dec2ac7c2ce61bd194b8ec Reviewed-on: https://review.typo3.org/54441 Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Tested-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
- 17 Oct, 2017 1 commit
-
-
Move calls to addInlineSettings out of the foreach loop, and place them together with other similar calls. Resolves: #82781 Releases: master Change-Id: Ia2269833f7649559a1552a9290773984bebcc102 Reviewed-on: https://review.typo3.org/54413 Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-