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 .
- 23 Apr, 2018 1 commit
-
-
This ensures maximum compatibility with all available graphics commands. Resolves: #78600 Releases: master, 8.7 Change-Id: Id7a95fbdf7782fef59e18de3dc4522d7c68b690a Reviewed-on: https://review.typo3.org/56622 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Florian Weiss <typo3org@leblanc.at> Tested-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
Frans Saris <franssaris@gmail.com> Tested-by:
-
- 20 Apr, 2018 1 commit
-
-
The labels of a labeledToggleCheckbox are now localizable using the well known LLL syntax. Resolves: #84803 Releases: master Change-Id: Iaaa3c84393ce1b998752b5db18dafc2aa7d385d3 Reviewed-on: https://review.typo3.org/56745 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Michael Oehlhof <typo3@oehlhof.de> Reviewed-by:
Riny van Tiggelen <info@online-gamer.nl> Reviewed-by:
Jan Delius <me@jandelius.eu> Tested-by:
Richard Haeser <richard@maxserv.com> Tested-by:
Jan Stockfisch <jan.stockfisch@googlemail.com> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
- 18 Apr, 2018 1 commit
-
-
The division is rounded by a `floor()` call. Since `floor()` returns a value of type `double`, the result must get casted to an integer to have the strict comparisons functional again. Resolves: #84782 Related: #83556 Releases: master Change-Id: Ief5d154f0447d2826c013c8cadb792ceb2288320 Reviewed-on: https://review.typo3.org/56726 Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
-
- 16 Apr, 2018 1 commit
-
-
In order to improve code quality, the following code sniffers are added: - cast_spaces - declare_equal_normalize - dir_constant Resolves: #84590 Releases: master, 8.7 Change-Id: Ib8a353b9ec47bff146b5decc3d5f97d242672efa Reviewed-on: https://review.typo3.org/56533 Tested-by:
Sybille Peters <sypets@gmx.de>
Tested-by: Sybille Peters <sypets@gmx.de>
Reviewed-by:
-
- 09 Apr, 2018 1 commit
-
-
- add void return types - add access modifiers for constants - fix some null coalescing - remove superfluous comments - add newline before namespace Resolves: #84662 Releases: master Change-Id: I1288b27b1edbd99b0624a66a5fb01cd02547b5ec Reviewed-on: https://review.typo3.org/56602 Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
-
- 06 Apr, 2018 1 commit
-
-
TYPO3 is famously known for the "multi-site" functionality, allowing multiple websites running within one TYPO3 instance. However, configuring a multi-site had various downsides, mostly regarding to domain/entrypoint handling for a site, and if lots of languages were in place. Concepts like "absRefPrefix", "baseURL", various language related TypoScript settings, and the infamous "L" GET parameter can now be seen obsolete. Also, handling page-not-found or access-denied errors have never been easier, as every admin/integrator is able to configure this. What TYPO3 calls a "site" is a entrypoint / pagetree, and contains both configuration values relevant for Backend and Frontend. A site configuration has a unique (human-readable) "site identifier" and the following additional values: * Root page ID This is a page on the root level (pid=0) or having "is_siteroot" checked. * The base path / base URL This HTTP entry point e.g. https://www.mydomain.com/ ("Base URL" / HTTP entry point, like https://www.mydomain.com/) -- This allows to fully identify a pagetree with an entrypoint without having to guess during "runtime". * The definition of all available languages for this pagetree, including the default language for this specific pagetree. -- This includes both values for backend-related as well as information, previously only settable via TypoScript. This way, it is possible to have a TYPO3 installation with 20 languages, but only using 5 languages within one pagetree (site), using 15 different languages in another site, while also giving meaning for all records within one site. A site configuration can be added or edited within the TYPO3 Backend in a new backend module for admins, and is then persisted in "typo3conf/sites/site-identifier/config.yaml". The configuration format yaml is chosen as it minimizes the risk of doing hacks, but the concept of a SiteConfiguration can be adapted / exchanged to be overloaded or found in various other places in the future. Adding a site configuration for a project has various benefits: - Configuration is in one place, stored in the file system thus, is deployable. - Configuration can be done by an integrator/admin without any programming skills => in one place. - The necessity to query sys_language is only needed when configuring a site. - No need to configure TSconfig options like "previewDomains" and "defaultLanguageLabel" are gone. is - No need to configure any TypoScript conditions, or even TypoScript settings related to language handling. - It is possible to configure error handling on a per-site level, even language-dependant, without having to code or configure anything. However, if no site is configured for a pagetree, the previous behaviour is still in place, allowing to migrate slowly to the sites handling, as some key functionality like URL path handling for speaking URLs is not in place yet. It is important to understand that adding a site configuration comes with various restrictions: - "sys_domain" handling is not necessary anymore, as a page is resolved via the domain+base URL given in the configuration - Any previously configured TypoScript conditions based on L parameter do not apply anymore if a site is configured - This also applies to any config.*language* related TypoScript setting. - It is necessary to use a URI with scheme and path to configure a site, where as previously, TYPO3 would work without a base URL. - mod_rewrite or something similar is a requirement for sites to work properly. Further improvements not yet implemented: - Ensure backend modules like Web->Page, Web->View, Web->List and Web->Info only show records in the configured site languages. - Enable the possibility to handle "domain entry aliases", also for multi-server setups with different domain names. - Ensure the new Site module can handle "read-only" / deployable site configurations. - Allow to activate a language for a site to be editable in the Backend but not be available in the Frontend for everybody. - Handling "Storage Folder" on the top level with different language entries. - Improve URL generation in frontend to skip sys_domain resolving. - TypoScript conditions for [site = my-identifier] and [siteLanguage = dk]. - Improve proper caching for rootline resolving of pages without restrictions. - Improve resolving of siteLanguage from the current request. - Linking from one site to a page of a different site. - Centralizing access to sys_language and sys_domain. - Handle copying/moving of records to a different site with different languages and language settings. - Handle configuration change (like deleting a language in the configuration - what should happen to the translated records?) Next up for 9.3: - Adding "Routers" on top of sites for URL resolving of pages and records. - Handle Storage Folders on top level rootline - Handle Mount Points New API: - New Entity classes "Site" and "SiteLanguage" are resolved as part of a PSR-15 middleware and available for pages in FE and BE when possible. - A SiteFinder object is used to query Site and SiteLanguage objects and used in various places. - The new PageUriBuilder allows to create links to pages without any relation to the current request, and are already in use in Frontend links and Backend preview links. - A PageErrorHandlerInterface allows to custom error handlers to be introduced by extensions and configured on any site. Site handling is considered still "under development" until TYPO3 9 LTS, and implementation as well as the configuration format might change in the next sprint releases, in order to gather feedback on what is missing in the implementation. As a site configuration will be mandatory for TYPO3 v10.0, some changes regarding sys_language and sys_domain will follow. Beware: - Due to the definition of every record of default language (language=0), it might be possible to switch to locales for languages and get rid of the language ID. - sys_domain won't make it any much longer. Resolves: #84581 Releases: master Change-Id: Iabeeb6835a98c8f5a71d502379ed63a68dfad6dd Reviewed-on: https://review.typo3.org/56505 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
- 05 Apr, 2018 1 commit
-
-
To be able to improve the layout of field information, the span tag is added to the list of allowed tags in html. Resolves: #84633 Releases: master, 8.7 Change-Id: If3a60002cb8b7a7473e96820bdb35ac9c8111bab Reviewed-on: https://review.typo3.org/56573 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
- 01 Apr, 2018 1 commit
-
-
Show the description as a placeholder when an image is added as a reference. Resolves: #81235 Releases: master, 8.7 Change-Id: I75363f74ba72bf4fd95b2a2e9a2a061ad250f825 Reviewed-on: https://review.typo3.org/56438 Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
Jigal van Hemert <jigal.van.hemert@typo3.org> Tested-by:
-
- 30 Mar, 2018 1 commit
-
-
Resolves: #84530 Releases: master Change-Id: Idb8fc143d7126840f0d964697b2a6dbe71e72cb3 Reviewed-on: https://review.typo3.org/56443 Tested-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Tobi Kretschmann <tobi@tobishome.de> Reviewed-by:
Steffen Frese <steffenf14@gmail.com> Reviewed-by:
Alexander Opitz <opitz.alexander@googlemail.com> Tested-by:
-
- 22 Mar, 2018 1 commit
-
-
Unify the space before the colon of return type. Resolves: #84515 Releases: master, 8.7 Change-Id: Ie107e574965f834c8fcaa8c2aa4f44f7cc41d7c5 Reviewed-on: https://review.typo3.org/56414 Tested-by:
-
- 21 Mar, 2018 1 commit
-
-
Christian Kuhn authored
Solves a todo in FormEngine: A data provider still fetched data from _GP instead of relying of this data being set by a controller: "defaultValues" for new records can now be set by controllers as input $result array key. Resolves: #84506 Releases: master Change-Id: I174eea2d5954b7ac29edef1007c1446c7816b0ed Reviewed-on: https://review.typo3.org/56390 Tested-by:
-
- 17 Mar, 2018 1 commit
-
-
Change-Id: Ibb5038049780edcf70aae442b9f9933feeed5589 Resolves: #84409 Releases: master Reviewed-on: https://review.typo3.org/56316 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
- 15 Mar, 2018 1 commit
-
-
If the configuration `['BE']['debug']` is enabled and the current user is an administrator, the value of select, radio and checkbox fields which are generated by the `FormEngine` is appended to its label. Resolves: #83748 Releases: master Change-Id: I735bd3c83b5b12eb3cddcc66d1b92d48cf5e5991 Reviewed-on: https://review.typo3.org/56147 Tested-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
- 08 Mar, 2018 1 commit
-
-
Date and time fields can contain ISO-8601 values. To apply lower and upper limits the value must first be converted to a UNIX timestamp. Resolves: #83240 Releases: master, 8.7 Change-Id: Ic15e9486cf7a4bcdf557c8a197d957ad88302b61 Reviewed-on: https://review.typo3.org/56020 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
-
- 03 Mar, 2018 1 commit
-
-
Whether a class or functionality is not available or available differently in v4 or FLOW is not relevant for TYPO3 CMS. Remove them. Occurrences have been searched using: git grep "TYPO3 4" git grep " v4" git grep -l "FLOW" | grep php$ Change-Id: I1e690c2b8eee2af0ade831600ee9a3e1cfe6437a Releases: master Resolves: #84126 Reviewed-on: https://review.typo3.org/55994 Tested-by:
-
- 02 Mar, 2018 1 commit
-
-
These parentheses are redundant and may be safely removed. Resolves: #84092 Releases: master Change-Id: I59f2b7454316ecd05f57d28e344f03a65d13e5c5 Reviewed-on: https://review.typo3.org/55952 Reviewed-by:
-
- 01 Mar, 2018 1 commit
-
-
Resolves: #84091 Releases: master Change-Id: I61c24937b919ec54c6547c07d1c4460186725c96 Reviewed-on: https://review.typo3.org/55950 Reviewed-by:
-
- 21 Feb, 2018 1 commit
-
-
ImageManipulationWizard now returns a proper HTMLResponse instead of a JsonResponse. Furthermore an missing import has been added in LocalizationController. Resolves: #84005 Releases: master Change-Id: Ie02cdaca84afa0c7fcde109e0fbbe5237ee69600 Reviewed-on: https://review.typo3.org/55856 Tested-by:
-
- 20 Feb, 2018 2 commits
-
-
Christian Kuhn authored
Similar solutions as in issue #83975 Change-Id: I04c06f0e73f5e7d44f225ad9b60c9cbed1016308 Resolves: #83981 Related: #83975 Releases: master Reviewed-on: https://review.typo3.org/55834 Reviewed-by:
-
Christian Kuhn authored
Making FormEngine data providers notice free is a mixture of fixing notices in the test subject, and improving test setup: * It is assumed that stuff like BE_USER and LANG object exists, $subject access to these globals which throw notices is not fixed, instead the test setup is changed to mock these where needed. * Data provider which have dependencies to other data prodivers assume their data is properly set, too. In those cases the test setup porperly sets this dependent data. * Various other "real" notice fixes in test subject and code called by the test subject is actually fixed. Change-Id: I7ae6444dc646ec114c15b2738ef4e30f67f88595 Resolves: #83975 Releases: master Reviewed-on: https://review.typo3.org/55823 Reviewed-by:
-
- 18 Feb, 2018 1 commit
-
-
If the linked record wasn't found (wrong uid, removed from database) we check before trying to gather an icon for the non-existing record. Resolves: #81804 Releases: master, 8.7 Change-Id: Ie06ec8a614650d8147f143cda8d8e6a9cb3e98e9 Reviewed-on: https://review.typo3.org/55751 Reviewed-by:
Andreas Wolf <andreas.wolf@typo3.org> Tested-by:
-
- 17 Feb, 2018 2 commits
-
-
Christian Kuhn authored
To manipulate the FormEngine data provider list by extensions, it can be helpful to just set a data provider as disabled and add an own one after the disabled one and before the next one. This avoids funny array munging and dependency shuffling if an extension author needs to substitute an entire data provider with an own solution. The concept has been implemented for node expansion render types in a similar way and is repeated here. Change-Id: Ia1f2de94940248b60e851c7b9968539f5ab0ef79 Resolves: #83906 Releases: master Reviewed-on: https://review.typo3.org/55724 Reviewed-by:
-
Due to the recent changes in the commit: e487cf52 [TASK] Create own response instance in controller actions ..ajax routes and eID handlers that used a *pre-generated* Response object (from the RequestHandler) now return different Content-Type headers than before. For backend ajax request applicaton/json was set by default, for eID scripts no Content-Type was set (by default). Change these controllers to use JsonResponse or a plain Response to reflect the previous state.. The changes in this commit were intended to be squashed into the mentioned commit – but this commit was too late. Therefore other (a bit) unrelated optimizations to changes that patch made are included. Change-Id: Icfdcd02d353dfaf48ad959c50be4802349eaaacd Releases: master Resolves: #83946 Related: #83939 Reviewed-on: https://review.typo3.org/55766 Tested-by:
-
- 16 Feb, 2018 1 commit
-
-
Christian Kuhn authored
To further support the PSR-7 / PSR-15 and removal of GeneralUtility::_GP() and friends efforts, all controllers no longer use the second 'ResponseInterface $response' argument given by dispatchers: Dispatchers should not assume which type of response a controller returns, there is no point in preparing this object. Instead, controllers now always create one of HtmlResponse, JsonResponse or RedirectResponse on their own and return these objects. Changes overview: * Always use "new" to instantiate a response, PSR-15 middlewares allow fiddling with the object if needed, xclassing these classes is never needed, we instead can rely on proper API usage. * All controller actions drop the second $response argument and add ResponseInterface return type hint. * Some controllers action also drop first $request argument, but only if the action does not need access to ServerParams at all. Those controllers that access _GP or _POST or similar currently, keep $request for now - they have to be refactored later anyway and then need $request. Change-Id: Icce283b3c19be14ef1adeec761cfd63c90ab24c5 Resolves: #83939 Releases: master Reviewed-on: https://review.typo3.org/55754 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
- 15 Feb, 2018 1 commit
-
-
Change-Id: I77a4782f250a4b37051eb321fd5c6670b4366e24 Resolves: #83908 Releases: master Reviewed-on: https://review.typo3.org/55726 Tested-by:
-
- 12 Feb, 2018 4 commits
-
-
It's now possible again to add and remove items via pageTSconfig after itemsProcFunc has been processed for TCA select fields. Resolves: #75834 Releases: master Change-Id: I6535f73c951a03abf3548c84877a08c4ea1ee2fa Reviewed-on: https://review.typo3.org/55513 Reviewed-by:
Reiner Teubner <rteubner@me.com> Reviewed-by:
-
For the default language it was possible to view the field, but on translating the dataset, the following exception is thrown: 'PHP Warning: Invalid argument supplied for foreach() in backend/Classes/Form/Element/SelectMultipleSideBySideElement.php line 66' As the defaultLanguageRow keeps to be "unparsed", the $selectedItems could be a comma separated string within the method TYPO3\CMS\Backend\Form\Element\SelectMultipleSideBySideElement::renderReadOnly if the TCA configuration of a field is set to 'defaultAsReadonly'. Resolves: #77155 Releases: master, 8.7, 7.6 Change-Id: Id9380fe3761e683352166565ed1a7e56f5e64190 Reviewed-on: https://review.typo3.org/55607 Reviewed-by:
Manuel Selbach <manuel_selbach@yahoo.de> Tested-by:
-
Resolves: #83844 Releases: master Change-Id: I5fef80a48d52da9800a7a9a2a23445d60168e8b5 Reviewed-on: https://review.typo3.org/55659 Tested-by:
-
Adjusts comment-indentions for else/elseif. Commands used: * composer update friendsofphp/php-cs-fixer --with-dependencies * Build/Scripts/cglFixMyCommit.sh (modified to run on all php-files) Resolves: #83851 Releases: master Change-Id: I0390b3fd612ea2c495696faf9364418a078cd586 Reviewed-on: https://review.typo3.org/55669 Tested-by:
-
- 09 Feb, 2018 1 commit
-
-
Highlight the selected icon. This useful feature has been removed with the FormEngine rewrite. Resolves: #83781 Releases: master, 8.7 Change-Id: I06376b073585d39d14de6f40bd02172168425944 Reviewed-on: https://review.typo3.org/55568 Tested-by:
-
- 04 Feb, 2018 3 commits
-
-
In order to give FormEngine a fresher look we add the following renderTypes to type=checkbox * checkboxToggle * checkboxLabeledToggle Furthermore, checkboxes are now displayed with icons provided via the IconFactory and can be changed. Resolves: #83556 Release: master Change-Id: I24570dc4ee8cb672a5f961399b709fe7da05e2f0 Reviewed-on: https://review.typo3.org/55351 Reviewed-by:
-
The Suggest Wizard now allows to search for multiple terms in field by splitting the searchterm by +. This allows to search for a combination of values which is helpful when dealing with large data sets. Resolves: #61981 Releases: master Change-Id: I764039a575ca5d9ccbd97dd3dc57f3947906a5c3 Reviewed-on: https://review.typo3.org/55546 Reviewed-by:
-
The SuggestWizard no longer returns translated pages. For the sake of database relations, relating directly to a translated page makes no sense and will most likely result in unintended behavior. Resolves: #83771 Releases: master Change-Id: Ibfa8dfa3082245726e0a519e77f26849507e421b Reviewed-on: https://review.typo3.org/55550 Reviewed-by:
-
- 27 Jan, 2018 1 commit
-
-
Editing a record with a deleted related record leads to an uncaught DatabaseRecordException. This patch catches the exception and ignores such records, but logs a warning. Due to possible errors occurring with certain DBMS (e.g. MySQL strict) columns may require a default value now in TCA. Resolves: #83412 Releases: master, 8.7 Change-Id: I5adaf385443350ce245dd83da6e5f1a16d9c9afb Reviewed-on: https://review.typo3.org/55197 Tested-by:
-
- 13 Jan, 2018 3 commits
-
-
Christian Kuhn authored
Apply a series of CGL whitespace fixes, mostly: * No whitespace after type cast * One space around '=' Change-Id: I6279e083a4bd867bfb70c9567c35b6bab1412043 Resolves: #83557 Releases: master Reviewed-on: https://review.typo3.org/55352 Tested-by:
-
Christian Kuhn authored
Apply various minor indentation CGL fixes, as suggested by scrutinizer-ci, mostly related to places where indentation is done with 1 or 3 spaces instead of 4. Change-Id: Ie3345c7391c0735e8074fd633dd9523616a6b82d Resolves: #83555 Releases: master Reviewed-on: https://review.typo3.org/55350 Reviewed-by:
-
This cosmetical CGL change just substitutes all declare(strict_types=1); with declare(strict_types = 1); to be in line with the general 'spaces around =' rule. While that is cosmetical, it makes scrutinizer-ci a bit more happy and prevents it from creating auto-patches for these cases. Change-Id: Ic754b3fd2a0f06624909e6188ed270bd2797745c Resolves: #83554 Releases: master Reviewed-on: https://review.typo3.org/55349 Tested-by:
-
- 04 Jan, 2018 1 commit
-
-
Georg Ringer authored
Improve the life of integrators and developers by showing the field name next to the title. Resolves: #83461 Releases: master Change-Id: I100022fb33facefe5f70cf99c2304fb080361427 Reviewed-on: https://review.typo3.org/55254 Tested-by:
-
- 27 Dec, 2017 2 commits
-
-
Using null coalescing operator in PHP 7 simplifies code structure. Resolves: #83129 Releases: master Change-Id: I449415c99ccb0ea158d3943800bc824514f7629c Reviewed-on: https://review.typo3.org/54810 Reviewed-by:
-
Some PHP classes still contain unused use statements. They have been removed. Thanks to @cd on his initial patch https://review.typo3.org/52014/ Resolves: 83432 Releases: master Change-Id: I9020f505a826c40fcf11f75f87245293e7c6154f Reviewed-on: https://review.typo3.org/55217 Reviewed-by:
-
