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 or owner.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
- 24 Jan, 2018 9 commits
-
-
The language parameter was not set if the "View webpage" button was used within the context menu of an element in the page module or the "View webpage" button in the record list of a desired language. Resolves: #80599 Releases: master, 8.7 Change-Id: I40fb5749cbd56c0075a8aa2c5ec3b2d8dea66501 Reviewed-on: https://review.typo3.org/52341 Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Reiner Teubner <reiner.teubner@me.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
-
With this patch the html chars inside the "ApacheThreadStackSize" flashmessage during the installation are displayed correctly Resolves: #83413 Releases: master Change-Id: If49ea5cd96ca8c0ef005e7a23b917b44149a88cd Reviewed-on: https://review.typo3.org/55198 Tested-by:
-
BackendUtility::getPagesTSconfig() uses local method static properties as cache. This prevents dedicated flushing, which may be needed in rare cases to prevent for instance from exceeded memory during huge imports. The patch switches that to cache framework cache_runtime which is already used at other places within BackendUtility. Resolves: #82473 Related: #63629 Releases: master, 8.7 Change-Id: I4d54819f05a6c7b8ce175bc827b626277e2d4c04 Reviewed-on: https://review.typo3.org/54133 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
Resolves: #83661 Release: master Change-Id: I8a7307986896fa2d68b5013d1defc235eff1d3e4 Reviewed-on: https://review.typo3.org/55443 Tested-by:
-
The field data_page_reg1 of table index_phash is defined as integer. Therefore the default value must be 0 instead of an empty string. Resolves: #83641 Releases: master, 8.7, 7.6 Change-Id: I4c1f115b8c8bbcb961627d7f5a5a413a8d5cf419 Reviewed-on: https://review.typo3.org/55428 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
-
The correct typography is to use the character "…" instead of "...". Resolves: #83614 Releases: master, 8.7 Change-Id: I151db0f1edb290d2a3aeff3236e1be1e9c19fa8a Reviewed-on: https://review.typo3.org/55441 Tested-by:
-
The cut and copy buttons were shown twice in filelist module. Once in “Extended view” and once in “Show clipboard” Resolves: #83575 Releases: master, 8.7 Change-Id: I8cbb9b516aaa1ff42a363d4daf4ffa7e20c9d461 Reviewed-on: https://review.typo3.org/55369 Tested-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
-
Resolves: #82386 Releases: master Change-Id: I40b83041149b8955b51c3a2c54d8690392356ae1 Reviewed-on: https://review.typo3.org/54024 Reviewed-by:
-
- Resolves a wrong variable definition in phpdoc - Adds type safe method parameter - Adds return type string to method Resolves: #83665 Releases: master Change-Id: I0ed52e0b2086d6d006885964f480b3c99b7942e7 Reviewed-on: https://review.typo3.org/55440 Tested-by:
Henning Liebe <h.liebe@neusta.de> Reviewed-by:
-
- 23 Jan, 2018 9 commits
-
-
Uid lists in the relation handler can be very big. To avoid exceeding query limits like maximum number of placeholder per query or the max allowed statement length these large lists are split into chunks of safe length before processing. Change-Id: I176acb85feb91c6162a77016c1918cf5a992625c Resolves: #81555 References: #80875 Releases: master, 8.7 Reviewed-on: https://review.typo3.org/53193 Tested-by:
Manuel Selbach <manuel_selbach@yahoo.de> Tested-by:
-
Add an additional hook to the EXT:recordlist which makes it possible to add content above any other content. Resolves: #61170 Releases: master Change-Id: I2f6ad79cfb5ff19f57da63346735b743947ddf99 Reviewed-on: https://review.typo3.org/55423 Tested-by:
Peter Kraume <peter.kraume@gmx.de> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
-
Change-Id: I59846db22964a26f610a304fab85f570884b063d Resolves: #83651 Releases: master Reviewed-on: https://review.typo3.org/55438 Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
Similar to getValueByPath(), removeByPath() now throws a specific exception if the path to remove does not exist in given array to avoid catching global \RuntimeException' in consuming code. The same "MissingArrayPathException" is used here since both cases have identical semantic. Change-Id: I69447c47d24e28110cf03929ea5ed28cf5e43024 Resolves: #83636 Related: #83615 Releases: master Reviewed-on: https://review.typo3.org/55424 Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
The existing functionality of sys_domain database records that redirect to a different target has been migrated into the new "redirects" core extension. An upgrade wizard ensures that old (and even deleted) sys_domain records with a redirect target (database field "redirectTo") are properly migrated into the redirects extension. The following database fields have been dropped: - sys_domain.redirectTo - sys_domain.redirectHttpStatusCode - sys_domain.prepend_params These values are not evaluated anymore in the TYPO3 Frontend. Resolves: #83638 Releases: master Change-Id: I0577a5bfb9db9e0b5d06b7c5f2d0c6f428c8a4ba Reviewed-on: https://review.typo3.org/55427 Tested-by:
-
After clicking on the filter button in the page tree, the focus is set on the input field allowing to type search word right away. Resolves: #83535 Releases: master Change-Id: I78c9b81e7c9e23efb4f9e8bf2d2a222a5e97436c Reviewed-on: https://review.typo3.org/55436 Tested-by:
-
A new system extension "redirects" is added, which ships a flexible handling of HTTP redirects, useful both for marketeers and site administrators. It adds a new module called "Site Management => Redirects". Site Management will be the starting point also for templating and domain setups in the future. A new DB table "sys_redirect" is added, which allows to configure a redirect from a source (host+path) to a destination target. The destination target can be any kind of Uri (used by the LinkService). In the short run, redirects superseeds the redirect logic from sys_domain.redirectTo (see followup patch), but more features are already sketched out, however, this change only adds the basic functionality. Any time a redirect is added or modified, a list of all redirects is added to the cache management, allowing to fetch all redirects at once, reducing the number of queries to the DB in the frontend to 1 query (or to one query to the FS, as the power lies in the caching framework). A simple hit statistics counter is implemented as well. The redirects functionality later will serve for URL Routing if a page will be registered under a different URL, and a redirect could automatically be added. Further improvements (out of scope for this change): - Move icons into the TYPO3 iconset - Check for recursive / loops, or existing redirects - Add further conditions for redirects - Export redirects as VCL, nginx or .htaccess rules for performance reasons - Bulk import of redirects - Selection of existing sys_domain redirects in source_ - Sanitize source_host to only include a domain name, and/or allow ports - Allow query parameters in source_path Resolves: #83631 Releases: master Change-Id: Ibf25c2ee07f41edbaf14b97a7f115d36f901cc62 Reviewed-on: https://review.typo3.org/55358 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Tobi Kretschmann <tobi@tobishome.de> Tested-by:
-
Nicole Cordes authored
This patch corrects how file references (from softrefs) are stored in sys_refindex table as this was changed with patch https://review.typo3.org/53219/. Resolves: #81831 Related: #80991 Related: #80988 Releases: master, 8.7 Change-Id: I776d2db47dffd83217a3c5527860093ddbca58c6 Reviewed-on: https://review.typo3.org/55158 Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Benjamin Kluge <b.kluge@neusta.de> Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Reviewed-by:
Sascha Rademacher <sascha.rademacher+typo3@gmail.com> Tested-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
-
Andreas Fernandez authored
Resolves: #83644 Related: #83637 Releases: master Change-Id: Ifdee387950181b869c9dfa1df2644bd5b51e6ce0 Reviewed-on: https://review.typo3.org/55429 Reviewed-by:
-
- 22 Jan, 2018 3 commits
-
-
With current fluid, the TypoScriptConstantsViewHelper is instantiated only once and re-used if called multiple times. $this->tag is then polluted from previous runs and creates funny results. Fix by re-initializing that property each call. Resolves: #83319 Releases: master Change-Id: Idf9e14ca69e76278bd0d6eaca1fec9b93c238fd5 Reviewed-on: https://review.typo3.org/55273 Tested-by:
Jan Stockfisch <jan.stockfisch@googlemail.com> Reviewed-by:
-
When a user successfully logs in to the backend of TYPO3, registered hooks are executed. This allows for the development of further actions such as notification services. Resolves: #83529 Releases: master Change-Id: I26b060463ae76075a4d40f25c8e695534fe69875 Reviewed-on: https://review.typo3.org/55319 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Michael Schams <typo3@2018.schams.net> Tested-by:
-
A new main module for the TYPO3 Backend is introduced, named "site", which serves a main entry point for integrators and site admins to configure the "Frontend" and the "How" of a TYPO3 website, and not the "what" (= content). The site management module's purpose for now is to include Redirect Management, but will be extended during v9 development to also contain Domain/Site/404 URL handling, TypoScript and Templating / Fluid configuration. Resolves: #83637 Releases: master Change-Id: I06c88d09fa16a40fa8c0f6176ed05f002629498c Reviewed-on: https://review.typo3.org/55425 Tested-by:
-
- 20 Jan, 2018 2 commits
-
-
The rootID holds the page ID where the root sys_template record was found. As this is crucial for some hooks this property should be publically available but is marked as deprecated during v9 development, a getter is added to provide a public API. Resolves: #83619 Releases: master Change-Id: Ief651f2e2d758350f0620b3104dd47e0c06fa2f4 Reviewed-on: https://review.typo3.org/55415 Reviewed-by:
-
Resolves: #83620 Releases: master Change-Id: I903207c22daa20312447c18d6b9ddd8f1cd61a5a Reviewed-on: https://review.typo3.org/55416 Reviewed-by:
Stephan Großberndt <stephan@grossberndt.de>
Reviewed-by: Riccardo De Contardi <erredeco@gmail.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
-
- 19 Jan, 2018 4 commits
-
-
The extension configuration is currently written by the install tool silent updater each time the install tool is entered, even if no configuration detail changed. This is unfortunate on systems with read-only LocalConfiguration since the install tool then throws an early fatal. Prevent that write operation in case nothing changed. Change-Id: I70d419690bcb633049ffcc9546e660d2f3b75a4c Resolves: #83616 Releases: master Reviewed-on: https://review.typo3.org/55413 Tested-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
-
Christian Kuhn authored
If ArrayUtility::getValueByPath() does not find a given path in an array structure, it currently throws a generic \RuntimeException. Checking the path is one of the key components of the method and consuming code may not know if the path exists at all, which is fine. Throwing global \RuntimeException thus forces various places to catch \RuntimeException which possibly hides away programming errors and mis-uses. The patch makes getValueByPath() throw a specific exception if path does not exists. Catching that specific exception reduces the number of global 'catch \RuntimeException' significantly. The patch also adds another catch in early install tool to fix a not recoverable fatal if LocalConfiguration 'EXTENSIONS' array does not yet exist, for instance if upgrading from v8 to v9. Change-Id: If65b1b6ba2181b4cd7de2ce41776c0d78a5b513f Resolves: #83615 Resolves: #83590 Releases: master Reviewed-on: https://review.typo3.org/55412 Reviewed-by:
Mathias Brodala <mbrodala@pagemachine.de> Tested-by:
-
Christian Kuhn authored
Various changes throughout the system improving method annotations here and there or sanitizing code a bit better. Change-Id: Ieeee41ede160e301a59aa8a534ca26e3499a4fcd Resolves: #83612 Releases: master Reviewed-on: https://review.typo3.org/55411 Tested-by:
-
Some rewording on a .rst file and some additional information to make more clear what is meant. Releases: master Resolves: #83610 Resolves: #69316 Related: #33071 Change-Id: Ie87ecb212f51158cb721a3133a49955096000ca3 Reviewed-on: https://review.typo3.org/55410 Reviewed-by:
-
- 18 Jan, 2018 5 commits
-
-
Brings back the possibility to filter pages by uid in the new SVG page tree. Resolves: #83245 Releases: master Change-Id: Ideded401d222c812fd0fcab1892082d2bd63a7c6 Reviewed-on: https://review.typo3.org/55405 Reviewed-by:
Alexander Opitz <opitz.alexander@googlemail.com> Tested-by:
-
Christian Kuhn authored
ext:impexp has a "size" display and adds size information to export formats for records file sizes. This is entirely removed with the patch - both from interface and .xml/.t3d exports: * The size handling on db records always made little sense, the default maximum size of 1MB was "never" hit, there wasn't even an input box to raise that limit, ever. This information is now just removed from the export formats. * The size handling on files is rather irrelevant with FAL, since FAL file integrity is checked with sha1 already. The size display during export in the interface for FAL files never worked since FAL migration in core v6.0 - It always displayed 0. Nobody ever cared, there is not even a forge issue about that. * Removing the 'size' column in the export interface - which only carried rather irrelevant information on record "size" only - simplifies the interface a bit. * The record size information in exports depends on used dbms due to different internal database types. Removing that makes exports more dbms agnostic. This can be seen with all the functional test fixture file changes coming with the patch - removing that reduces a maintenance nightmare in this area and improves the chance to align exports in between the functional testes on different dbms again. Note that exporting .xml/.t3d in v9 and importing it in a v8 instance does not work anyway due to more significant DB field related changes in v9 already. The effects of this patch could be easily mitigated on v8, but we were unable to create anything in v9 that is able to be imported in v8 again - and ext:impexp is not created to be an upgrade / download helper in the first place. Thus, ignoring size checks in v8 to mitigate effects of the file format change does not seem to be necessary and is not done. Change-Id: I0cae7b371b6ac027e27c9192ffa273dabc9795c7 Resolves: #83606 Releases: master Reviewed-on: https://review.typo3.org/55391 Reviewed-by:
Reiner Teubner <rteubner@me.com> Tested-by:
-
This patch streamlines the position and layout for the content help buttons in ext:impexp. Like already done in FormEngine, the CSH now wraps around field labels. Resolves: #83602 Releases: master Change-Id: Iccfdd8f26649176004a17967d7a05d6f76c6d021 Reviewed-on: https://review.typo3.org/55386 Tested-by:
-
This patch fix a wrong position of sortable elements in inline records. This is a known issue which was never fixed in jquery-ui. For this reason this patch aplly the changes to the sortable lib. Resolves: #83593 Releases: master, 8.7 Change-Id: I5efeee6202b0b181f04e71538a5bc72b306cd02e Reviewed-on: https://review.typo3.org/55389 Tested-by:
-
Composer license definition GPL-2.0+ has been deprecated and has to be replaced with GPL-2.0-or-later. Resolves: #83607 Releases: master, 8.7, 7.6, 6.2 Change-Id: I6113bc3a90cb6a56830b930522dde2eaacd5025e Reviewed-on: https://review.typo3.org/55404 Tested-by:
-
- 17 Jan, 2018 7 commits
-
-
File list table needs a wrapper div to have borders and shadows to look alike tables of the list module. Change-Id: Id68f9b328c65e3d2dc59281a730bebd0430a179d Resolves: #83604 Releases: master Reviewed-on: https://review.typo3.org/55388 Reviewed-by:
-
Resolves: #83578 Related: #83580 Releases: master Change-Id: I2c97edd4bac854b33501ba571ed479bdefc288d7 Reviewed-on: https://review.typo3.org/55373 Reviewed-by:
Jigal van Hemert <jigal.van.hemert@typo3.org> Tested-by:
-
The export modules has a file size restriction that skips file exports if they are bigger than by default 1MB. This can be raised with an input field. The patch removes that input field: * Configured maximum file sizes are checked during upload already. A well configured system should expect existing files are ok and just export everything * The 1MB default size is old fashioned. Typical images are often bigger in size and resized only during FE rendering * Skipping arbitrary files in export has a negative impact on data consistency of the export. * Single files can still be excluded from export if needed * Users up until now usually had manually raised the limit to some value high enough to make all files fit Change-Id: Ib70dc48de44d215067474b4c3f6fff8988ab7712 Resolves: #83596 Releases: master Reviewed-on: https://review.typo3.org/55382 Reviewed-by:
-
Uploading import files broke with patch for issue #81763 Fix by renaming POST array back from 'data' to 'file'. Change-Id: I8de880775e2949951ef8a3f45b0a704c2ef3ac76 Resolves: #83599 Related: #81763 Releases: master Reviewed-on: https://review.typo3.org/55385 Reviewed-by:
-
The TYPO3 specific .t3d export format is a funny binary format and rather hard to read and decipher, even if not compressed. The XML format is at least some easy to read text file instead of a binary format and exists for quite some time in the system. Use XML as default export format by just swapping the option box entries. Change-Id: I5b25d8dc0b33158e98d1aafba27ab7669edeb725 Resolves: #83597 Releases: master Reviewed-on: https://review.typo3.org/55383 Tested-by:
-
Christian Kuhn authored
The 'export' module has a restriction to limit the number of exported records. The patch removes this from the interface: * The default limit is arbitrary, removing that limit declutters the interface a little bit * Users probably always did just set this to some number high enough to export everything they wanted * It was not clear what exactly is counted. At least it was not the total number of exported records ... * The error and flash messages were unclear and sometimes not shown at all * The limit could lead to data integrity issues in the export file, for example if a page links to some other page that is not exported * Presets that increased the limit still work * To prevent a breaking patch, the affected PHP method arguments deprecate some arguments instead of fully removing them in v9 Change-Id: Iadb365ff2ccd77ed38cbde81b76e37990a0c6f17 Resolves: #83592 Releases: master Reviewed-on: https://review.typo3.org/55381 Tested-by:
-
Avoid spamming the log in PHP 7.2 due to get_class(null) if fetching the image in ImageService->getImage() fails. Resolves: #83570 Releases: master, 8.7, 7.6 Change-Id: Icc3c78f5b747842cee89d184134ff298b8e04a3a Reviewed-on: https://review.typo3.org/55370 Reviewed-by:
Stephan Großberndt <stephan@grossberndt.de>
Reviewed-by: Mattia D <mattia.dorigatti@brandnamic.com> Reviewed-by:
-
- 16 Jan, 2018 1 commit
-
-
With #83267 a JSON response object was introduced. The patch has the side effect that any response is now an array but some usages in JavaScript were not adjusted. This patch does two things: - `FileController::fileExistsInFolderAction()` does now either return an array for falsy results OR the file object. - The JavaScript code is adjusted to check for a valid file object by requiring the `uid` property instead. Resolves: #83568 Related: #83267 Releases: master Change-Id: I9878f5f70b8af3ba8ec151a6ed514780547ec1ea Reviewed-on: https://review.typo3.org/55371 Tested-by:
Frans Saris <franssaris@gmail.com> Tested-by:
-
