- Feb 07, 2017
-
-
Wouter Wolters authored
Resolves: #79668 Releases: master Change-Id: I78b9b85a5af2170ddb725dee969f090be1d444e3 Reviewed-on: https://review.typo3.org/51566 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
Thomas Hohn authored
Adds two new configuration options to Install Tool which are used when saving records using the DataHandler: * disable the validation of records after saving them * if validating, make a strict value comparison ('' !== 0) instead of the default loose comparison ('' == 0) Fixes: #79438 Releases: master Change-Id: I01dfae57b046db00a531dfdfc386e43fe32329e4 Reviewed-on: https://review.typo3.org/51405 Tested-by:Claus Due <claus@phpmind.net> Reviewed-by:
Frans Saris <franssaris@gmail.com> Tested-by:
-
Wouter Wolters authored
Status codes are only returned when running in dry-run mode. Resolves: #79641 Releases: master,7.6 Change-Id: I3ca770d3f8c0af5aba5793cd4155722b8b68298c Reviewed-on: https://review.typo3.org/51554 Tested-by:
-
Helmut Hummel authored
This feature extends the image cropping tool in the backend so that editors can now not only select one crop area, but multiple ones per image. Within the crop are now also a focus are can be selected and to preview areas that will be covered once the image is rendered in the frontend one or more cover areas can be configured to be shown inside the crop area. This change also adds a format.json view helper and a view helper to generate backend URIs that are used in the now fully Fluid rendered imageManipulation element. This is the TYPO3 integration part. TypeScript and CSS will be done in a second commit. Resolves: #75880 Releases: master Change-Id: I646f0f0a149d05d1f3d8283bcc92ab09aede768e Reviewed-on: https://review.typo3.org/51515 Tested-by:
-
Raphael Okon authored
This adds the necessary TypeScript and CSS changes for the new imageManipulation element. Resolves: #75880 Releases: master Change-Id: I56c5042c6e6de7141ba59014ab31051c5c9cc34f Reviewed-on: https://review.typo3.org/51565 Tested-by:
-
Marco Huber authored
With this patch you can set a customWidgetId parameter in the widget viewhelper. This id is used in the widget identifier in addition to the nextWidgetNumber. With this patch two equal widgets in different content elements don't influence each other. A good value for the customWidgetId is the {contentObjectData.uid}. Example: <f:widget.paginate customWidgetId="{contentObjectData.uid}" ... Resolves: #47006 Releases: master Change-Id: Ief1d38457da73a35e652f11d82f441898e0394d3 Reviewed-on: https://review.typo3.org/51518 Reviewed-by:Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
Michael Oehlhof authored
Resolves: #12211 Releases: master Change-Id: I382945cd92dd8ca6c99ea200f93ea3ca2dfdef41 Reviewed-on: https://review.typo3.org/50926 Reviewed-by:
-
Michael Oehlhof authored
If a page is selected in page module which content is also shown on other pages, now a notice is shown with the titles and pid of these pages. Resolves: #69572 Releases: master Change-Id: Ie66564da98160825f5759c6ac4937fbbeaafdce0 Reviewed-on: https://review.typo3.org/51049 Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Reviewed-by:
-
Philipp Kitzberger authored
Resolves: #79337 Releases: master Change-Id: Ib93ac38f944d6ca74f6162e705f6bfa4fa3214a9 Reviewed-on: https://review.typo3.org/51324 Tested-by:
Mona Muzaffar <mona.muzaffar@gmx.de> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
-
Tymoteusz Motylewski authored
This change unifies the ClickMenu functionality of the pagetree (ExtJS) with the ClickMenu code given in other areas of the TYPO3 Backend. The following changes are made: * Unify the naming, it's "ContextMenu" not "ClickMenu" anymore * Configuration for record types are unified, the clickmenu shows the same entries in the same order in any place. * ExtJS-based ContextMenu is removed, all based on the new ContextMenu functionality. * A new way for extending the items inside the ContextMenu is handled via ItemProviders, which can easily be extended. * Configuring clickmenu items is not done based on PageTS (as it was handled with the ExtJS pagetree), however certain items can be disabled via PageTS. Resolves: #78192 Releases: master Change-Id: I380ac73ced10fdc7b1fdec7261e2d56da3d7d938 Reviewed-on: https://review.typo3.org/50124 Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
-
Jo Hasenau authored
Resolves: #13749 Releases: master Change-Id: Iba428acf25875479aa703ad4a93832331ed0b0be Reviewed-on: https://review.typo3.org/47135 Reviewed-by:
Jo Hasenau <info@cybercraft.de> Tested-by:
Bjoern Jacob <bjoern.jacob@tritum.de> Tested-by:
-
Claus Due authored
Given the assumption that this particular resource is not one that changes very often one can benefit from storing this in the cache_runtime in order to avoid fetching the same avator more than one in a request. Change-Id: Idc39c59dc8213f861ef4da7c9da4f5a95cfab9ac Resolves: #79547 Releases: master Reviewed-on: https://review.typo3.org/51467 Reviewed-by:
-
Oliver Hader authored
This feature introduces a new functionality called "allowLanguageSynchronization" which can be set on a field configuration of a TCA column. This is the successor of "l10n_mode=mergeIfNotBlank" as the old option had several conceptual downsides: 1) "mergeIfNotBlank" took the value of the default record during runtime, but only if the translation field was empty. This means it was not possible to see what the record actually contained without having all fields of the parent at hand. 2) It was not possible to have a value "santa" in the original record but remove the option in a translation (because an empty string "" implicitly triggered the runtime call in the frontend) 3) "mergeIfNotBlank" did not work on relations except for files fetched via the FileRepository API calls, but for no other inline elements. 4) "mergeIfNotBlank" did the overlay functionality in the frontend, but only FormEngine and DataHandler took care of the option. Custom backend modules had to implement the same functionality. 5) In FormEngine, there was an icon in the translation record that if the record kept empty the value of the original language was taken, but this is not optimal in terms of usability. 6) "mergeIfNotBlank" did not take the new l10n_source option into account, where localizations could be made from other records than the default language "0". The new feature can be set on any TCA column setting: $GLOBALS['TCA'][<table-name>]['columns'] [<field-name>]['config']['behaviour'] ['allowLanguageSynchronization'] = true; This brings an option to records with translations (both from l10n_parent and l10n_source) to have the value for all translations synchronized or explictly have a checkbox to use a custom value. The information whether a field is custom filled, or kept in sync from l10n_parent/l10n_source is stored in a separate field called "l10n_state" inside the database. The introduced upgrade wizard and TCA migration to remove "l10n_mode=mergeIfNotBlank" has been modified to migrate to this option and add a l10n_state database field if a TCA table used "mergeIfNotBlank" but did not add the l10n_state field manually via ext_tables.sql yet. New extensions can easily use the new option right away, extensions that need to stay compatible with v7 and v8 can add both options right away to have the same output. The main goals to achieve with this change is now: * Have consistent database values for all records regardless of l10n_mode=mergeIfNotBlank paving the way to fetch translated records without having to overlay (once l10n_mode=exclude is also copying values and relations) * Be more explicit for editors about records that have a different or the same state as their l10n_parent/l10n_source as a benefit for bigger instances with a lot of languages * Avoid hidden magic when retrieving localized records in the TYPO3 Frontend. Resolves: #79658 Related: #79243 Releases: master Change-Id: I6c2dbfeb09b47f958a536c9ab050c24ba4bbcbbd Reviewed-on: https://review.typo3.org/51291 Tested-by:
-
Frans Saris authored
Resolves: #79661 Releases: master Change-Id: I9639ad35764090aa38128671084e239b53639850 Reviewed-on: https://review.typo3.org/51563 Tested-by:
-
Philipp Gampe authored
Ignored files require the full path to a file for resurrection, not just the headline. Resolves: #79659 Releaes: master Change-Id: I7f4ea9a0b2080c71dcd7d708c1c0ffccb30f15be Reviewed-on: https://review.typo3.org/51562 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
Andreas Fernandez authored
TypeScript is updated to at least version 2.2.0. Existing code is recompiled due do changes of defaults in TypeScript. Resolves: #79653 Releases: master Change-Id: Id656c0319ee021c8475e607e5dbe35a21074dd79 Reviewed-on: https://review.typo3.org/51560 Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
- Feb 06, 2017
-
-
Benjamin Kott authored
CSS Styled Content has been a long time the preferred way of rendering content in the frontend. Fluid Styled Content was introduced as successor of CSC, but the feature set diverged from the beginning. The lack of flexibility and incomplete feature set in comparision to CSC made it hard to migrate existing instances. Since TYPO3 CMS 7.6 Fluid-Templates are the defined standard and official recommendation for content rendering. The feature set of FSC is now matching CSC. Both content renderings are now streamlined to be fully compatible with each other. For the period of CMS 8 LTS CSC will share the same capabilities to make an transition as easy as possible. CSC is now deprecated and goes into maintenance mode and will be removed with CMS 9. For compatibility, CSC is now supporting Textmedia that was before exclusive to FSC. But also FSC has learned some tricks from CSC. Fluid Styled Content has now support for all content elements prior existing only in CSC, this includes "Text", "Text and Images" and "Images". Also for example "Frames", "Space before" and "Space after" are now again featured across both content rendering methods. Releases: master Resolves: #79622 Resolves: #72422 Resolves: #75466 Resolves: #71570 Resolves: #71484 Change-Id: I7d2a9072baad508b6b87470b847444b91e7323fb Reviewed-on: https://review.typo3.org/51065 Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
Andreas Fernandez authored
When validating input fields of the FormEngine fails, a button is now rendered into the least possible button bar in the module document header. Clicking the button renders a list of all input elements whose validation failed. Clicking onto a field in that list automatically focuses the field in the form. Resolves: #79521 Releases: master Change-Id: I9e232f4d1b27216ccf4a1c7b88d4a9c70b49f4f0 Reviewed-on: https://review.typo3.org/51452 Reviewed-by:
Frank Nägler <frank.naegler@typo3.org> Tested-by:
-
Stephan Großberndt authored
Fixes: #79639 Releases: master Change-Id: Ib1a963a4110114de4e2db533e610635a3a47cb6b Reviewed-on: https://review.typo3.org/51551 Tested-by:
-
Claus Due authored
This patch adds a new method on ActionController, initializeAssetsForRequest($request) which comes with a default implementation and allows overriding in subclasses. The default implementation of this new feature will try to render sections HeaderAssets and FooterAssets from the Fluid template that is resolved, assigning the output (if not empty) to either header or footer, by using the PageRenderer. The feature only works for TemplateView and subclasses thereof, since `renderSection` is not a required method for ViewInterface implementations; it only exists on the (MVC-centric) TemplateView. Change-Id: Ia815410637982c077236e12a848bdd26ead22e69 Releases: master Resolves: #79409 Reviewed-on: https://review.typo3.org/51380 Reviewed-by:
-
Markus Klein authored
If the configuration for a linkhandler has an empty label put a warning label there instead to give the integrator a hint that the configuration is evaluated correctly. Resolves: #79621 Releases: master, 7.6 Change-Id: Ib00a86be339908408c4e31eedb3c8ea57468fa87 Reviewed-on: https://review.typo3.org/51529 Reviewed-by:
-
Georg Ringer authored
Render link information below a link field to help editors. Instead of 't3://page?uid=92 _top "a class" "a title"' the user will get relevant information. Resolves: #28171 Releases: master Change-Id: Ic285a10e1de67bf60dd5235885a8d0037792999a Reviewed-on: https://review.typo3.org/51479 Reviewed-by:
-
Markus Klein authored
A new session framework is introduced. The goal is to provide interoperability between different session storages (called "backends"), like database, Redis, etc. An integrator may enforce a specific session backend by configuring SYS/session in LocalConfiguration.php. It is also possible to use custom session backends by implementing the interface "SessionBackendInterface". Resolves: #70316 Releases: master Change-Id: I90a4f84344e75f13b2f46245162e749ed3505ec3 Reviewed-on: https://review.typo3.org/51549 Reviewed-by:
-
Ralf Zimmermann authored
This feature extends the SaveToDatabase finisher with the following functions: * Perform multiple database operations * Access the inserted uids from previous database inserts * Add a special option value '{__currentTimestamp}' * Add a variable container object which is passed through all finishers The issue contains examples for testing. Resolves: #79530 Releases: master Change-Id: Ic2a569194d69434e0320c670cd879744c864b911 Reviewed-on: https://review.typo3.org/51456 Tested-by:Daniel Lorenz <daniel.lorenz@extco.de> Tested-by:
Andreas Steiger <typo3@andreassteiger.de> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
Frans Saris authored
Use correct field to determine page uid Resolves: #78917 Releases: master Change-Id: I01101640ff8ac1d801ef1619f8bc3c885aee2713 Reviewed-on: https://review.typo3.org/51555 Reviewed-by:
-
Mona Muzaffar authored
- Updating doctrine/collections (v1.3.0) to doctrine/collections (v1.4.0) - Updating doctrine/annotations (v1.3.0) to doctrine/annotations (v1.3.1) - Updating doctrine/common (v2.6.2) to doctrine/common (v2.7.2) - Updating doctrine/dbal (v2.5.5) to doctrine/dbal (v2.5.11) - Updating symfony/yaml (v3.2.0) to symfony/yaml (v3.2.2) - Updating symfony/finder (v3.2.0) to symfony/finder (v3.2.2) - Updating symfony/event-dispatcher (v3.2.0) to symfony/event-dispatcher (v3.2.2) - Updating symfony/dom-crawler (v3.2.0) to symfony/dom-crawler (v3.2.2) - Updating symfony/css-selector (v3.2.0) to symfony/css-selector (v3.2.2) - Updating symfony/debug (v3.2.0) to symfony/debug (v3.2.2) - Updating symfony/console (v3.2.0) to symfony/console (v3.2.2) - Updating symfony/browser-kit (v3.2.0) to symfony/browser-kit (v3.2.2) - Updating sebastian/comparator (1.2.2) to sebastian/comparator (1.2.4) - Updating phpunit/phpunit-mock-objects (3.4.2) to phpunit/phpunit-mock-objects (3.4.3) - Updating phpunit/php-code-coverage (4.0.3) to phpunit/php-code-coverage (4.0.5) - Updating myclabs/deep-copy (1.5.5) to myclabs/deep-copy (1.6.0) - Updating phpunit/phpunit (5.7.5) to phpunit/phpunit (5.7.11) - Updating guzzlehttp/promises (1.3.0) to guzzlehttp/promises (v1.3.1) - Updating symfony/process (v3.2.0) to symfony/process (v3.2.2) - Updating facebook/webdriver (1.2.0) to facebook/webdriver (1.3.0) - Updating codeception/codeception (2.2.8) to codeception/codeception (2.2.9) - Updating symfony/filesystem (v3.2.0) to symfony/filesystem (v3.2.2) - Updating symfony/stopwatch (v3.2.0) to symfony/stopwatch (v3.2.2) Resolves: #79614 Releases: master Change-Id: Ibbefff219570421d8b0037aef5788b07bb3fb4e4 Reviewed-on: https://review.typo3.org/51520 Reviewed-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
-
Stefan Froemken authored
As storeIncomingData depends on some data, which is generated in init, the init method has to be called before. Resolves: #79374 Releases: master, 7.6 Change-Id: I55e9f1317db83205b3a9ad0105eb8b493203ced7 Reviewed-on: https://review.typo3.org/51344 Tested-by:
Thomas Hohn <thomas@hohn.dk> Reviewed-by:
-
Claus Due authored
This patch adds a new feature for FLUIDTEMPLATE content objects, allowing two new sections named `HeaderAsstes` and `FooterAssets` to be defined. When rendering the content object, those sections then get rendered and assigned as either header or footer data via PageRenderer. Both sections are optional and can be combined. Change-Id: I981f2148050b972ef42d9b18a1b428f874407615 Resolves: #79413 Releases: master Reviewed-on: https://review.typo3.org/51382 Tested-by:
-
- Feb 05, 2017
-
-
Ralf Zimmermann authored
* add more configuration options to the DatePicker element within the form editor * render the frontend JavaScript as inline JavaScript within the page footer * fix small bugs Resolves: #79539 Releases: master Change-Id: I7a33abbc3502dbad37e228313b93e32ae5b19bf5 Reviewed-on: https://review.typo3.org/51461 Tested-by:
-
Michael Oehlhof authored
Resolves: #67243 Releases: master Change-Id: Ic3d1bc45b9db9ae3eb6fd8f13a03fcf9125d7422 Reviewed-on: https://review.typo3.org/51037 Tested-by:
Philipp Gampe <philipp.gampe@typo3.org> Tested-by:
-
Anja Leichsenring authored
User can mark each file as 'hide from my view'. This selection is stored in registry and applies for every user alike. All hidden files are accessible via a section and can be restored. This selection again applies for all users. Change-Id: Ia3108977ca5cb180dd0e1925ff918ffb03452249 Resolves: #79420 Releases: master Reviewed-on: https://review.typo3.org/51050 Tested-by:
-
Christian Kuhn authored
Opening a collapsed inline relation containing null placeholders does not correctly initialize and both the value field as well as the placeholder field are shown. Easily reproducible with a FAL relation on a page record. Fix JavaScript to initialize correctly. Change-Id: I27b52b9f69beb24d0309422cbcf2b67cc8190e07 Resolves: #79632 Related: #79440 Releases: master Reviewed-on: https://review.typo3.org/51542 Tested-by:
Alex Kellner <alexander.kellner@einpraegsam.net> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
-
Christian Kuhn authored
A broken variable access is fixed to hand over correct data to the type=group suggest wizard. Change-Id: I0c6dbf3d7da114f633e779eb594b6457a5e4fac6 Resolves: #79574 Related: #79440 Releases: master Reviewed-on: https://review.typo3.org/51543 Tested-by:
-
Markus Klein authored
Resolves: #79623 Releases: master Change-Id: Iefef14b968d4edfbfbe221ee5b58e3947d5f0d9c Reviewed-on: https://review.typo3.org/51530 Reviewed-by:
-
Christian Kuhn authored
Change-Id: I0660bddb5411c8b02fe2cf2e285343f90f49e4d9 Resolves: #79631 Related: #79518 Releases: master Reviewed-on: https://review.typo3.org/51541 Tested-by:
-
- Feb 04, 2017
-
-
Christian Kuhn authored
Patch for issue #79566 increased the field length of ses_name in fe_session and be_session table from 32 to 255. This field is used together with ses_id as primary key. With utf8, this now exceeds maximum key length of 757 bytes. To fix the issue, ses_name is cut down to 100 for the time being, the patch should be fine for master and 7.6 this way. Change-Id: I06abecca0f8df483590cf0a3c193134083e8f5f1 Resolves: #79628 Related: #79566 Releases: master, 7.6 Reviewed-on: https://review.typo3.org/51538 Tested-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
-
Susanne Moog authored
As the main test case files are now in subfolders, we need to correct the namespaces. Change-Id: Ie06edc099c5d3e42ff842eded03cde1ddf34c0ca Releases: master Resolves: #79629 Reviewed-on: https://review.typo3.org/51535 Tested-by:
-
- Feb 03, 2017
-
-
Markus Klein authored
https://review.typo3.org/49750 introduced code that lacks proper variable initialization. Get this straight. Resolves: #79620 Releases: master, 7.6 Change-Id: I1b5735807f7f0fc476a5370f23d6b7d4654e4599 Reviewed-on: https://review.typo3.org/51527 Reviewed-by:
-
Christian Kuhn authored
Fix travis Change-Id: Ib28fdfdfd87c3643e06fee4a67b9332b17227e48 Resolves: #79518 Releases: master Reviewed-on: https://review.typo3.org/51525 Reviewed-by:
-
Susanne Moog authored
- Removal of the CMS part from the namespace - Distinguish Classes / Resources For background information see https://decisions.typo3.org/t/testing-framework-extraction-next-steps/50 Change-Id: I3f73baeb16bbef82c9626add063c9edde41b47a6 Resolves: #79518 Releases: master Reviewed-on: https://review.typo3.org/51449 Tested-by:
-
