- Mar 22, 2017
-
-
Anders Kostending authored
Release notes: * Added support for custom CSS properties (#3144). * Deprecated jQuery.holdReady (#3288). * Deprecated jQuery.nodeName (#3475). * Deprecated jQuery.inArray (#2961). * Fixed a bug in .width(), .height(), and related methods where CSS transforms were included in the calculations. For instance, an element with the style transform: scale(2x) should not have its width and height values doubled (#3193). * Added support for <template> elements to the .contents() method (#3436). * Added back the deprecated module to the slim build. This change is largely insignificant given the module’s small size. We believe it makes more sense to remove deprecated pieces from the slim build at the same time as the main jQuery build (#3237). * Ensure jQuery.holdReady is in the right place (#3573) * Ensure we get proper values for width and height on elements with display “inline” (#3571) * Ensure trigger data is passed to radio click event handlers (#3579) * Revert: Trigger checkbox and radio click events identically * Revert: Add radio click triggering tests ChangeLog Compare: https://github.com/jquery/jquery/compare/3.1.1...3.2.1 Resolves: #80313 Releases: master Change-Id: I3f98247f28279bf68a0af4787aee996209ed1833 Reviewed-on: https://review.typo3.org/52069 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Kasper Ligaard <kasperligaard+typo3.org@gmail.com> Reviewed-by:
Anders Kostending <aha@systime.dk> Reviewed-by:
Faton Haliti <fha@systime.dk> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
Anders Kostending authored
Release notes: 4.7.2 * Optimize d3.pack. * Fix string coercion in transition.style and transition.attr. * Update dependencies. 4.7.3 * Fix the Mercator projection’s built-in clipping when projection.rotate is used. * Fix the transverse Mercator projection’s built-in clipping when projection.rotate is used. * Fix the transverse Mercator projection’s built-in clipping when projection.clipExtent is used. Resolves: #80320 Releases: master Change-Id: Ief0e4c58506e162062e32fc166df9edcac9f87d2 Reviewed-on: https://review.typo3.org/52073 Tested-by:
Josef Glatz <josef.glatz@typo3.org> Reviewed-by:
-
Josef Glatz authored
Fix js tooltip after permission settings are changed in the permissions backend module. Resolves: #80387 Releases: master, 7.6 Change-Id: I6be57ff0a48b3245c5e2d1aabc4260720c480e5f Reviewed-on: https://review.typo3.org/52115 Tested-by:
Thomas Hohn <thomas@hohn.dk> Reviewed-by:
Mona Muzaffar <mona.muzaffar@gmx.de> Tested-by:
-
Christian Kuhn authored
Rename .rst file since the colons give headaches on windows. Change-Id: I710a030ce7335b294d081e237a019cec6b7ca74f Resolves: #80317 Releases: master Reviewed-on: https://review.typo3.org/52125 Reviewed-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
-
Benni Mack authored
The constants within `styles.content` were cleared via CSS Styled Content which did not allow to define any constants before the TypoScript template was included in that space. Releases: master Resolves: #80391 Change-Id: Ia96c3a3883d87eb9dba3f0a2b193738d9252d263 Reviewed-on: https://review.typo3.org/52118 Tested-by:
-
Manuel Selbach authored
Since we follow the principle of "prepared statement", the method getRecordRaw will break this behaviour. Within the "where" parameter of the function it is possible to pass a malformed query part. Thus we should remove it, as the queryBuilder should be used everywhere in the future to increase visiblity of which query will be processed at a concrete point of code and to force the concept of prepared statements. Resolves: #80317 Releases: master Change-Id: If0028bf897ddee4517228a9e399390fe7266215e Reviewed-on: https://review.typo3.org/52075 Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
Christian Kuhn authored
The "create new flex form section container" ajax request fails to set initialized data values of the data compiler to the render engine. As a result, data values that expect to be at least an empty array are null and for instance the GroupElement stumbles. Properly assign calculated container data to the render engine to fix this. Change-Id: I1205c2814608bbb23d4842333f0b047bc356b02a Resolves: #80222 Releases: master Reviewed-on: https://review.typo3.org/52105 Tested-by:
Jan Helke <typo3@helke.de> Tested-by:
Frank Nägler <frank.naegler@typo3.org> Tested-by:
-
Christian Kuhn authored
Loading additional stylesheets from elements in inline scope fails if using 'EXT:' syntax, for flex section containers, this was not evaluated at all. The patch adds code to resolve an EXT: prefix stylesheet file from an element result array ['stylesheetFiles'] to properly handle loading of this CSS in JS, and uses it in both inline and flex ajax controller. This issue is easily reproducible with ext:styleguide 'elements_t3editor', which registers t3editor.css to load. Without patch, This fail (404) in 'in inline' 't3editor_inline_1' 'Create New'. Additionally, additional language file handling was not implemented for flex section container ajax calls, which is also added by the patch, similar to the solution done in inline ajax. Change-Id: I617b9f1ed3e0c4718fb0867a42f2c37b604d7afe Resolves: #80335 Releases: master Reviewed-on: https://review.typo3.org/52089 Tested-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
-
Christian Kuhn authored
sortby: An integer field with an explicit sorting value default_sortby: A query->orderBy statement to sort records if no explicit sortby field is given. default_sortby is ignored if sortby is given. The patch removes a couple of TCA ['ctrl']['default_sortby'] declarations where both were defined. default_sortby needs no "ORDER BY" prefix. The patch removes it from those TCA tables where this prefix was still defined. Additionally, the TCA reference docs have been improved in this area to hint about both fields and their correlation. It is especially evil if that is confused and a field like 'title' is set as sortby: The DataHandler would happily write integers into that field on save. Change-Id: Ib5c38a538cd3f60d3e05033488363a144f756505 Resolves: #80361 Releases: master Reviewed-on: https://review.typo3.org/52108 Tested-by:
Steffen Kamper <info@sk-typo3.de> Reviewed-by:
-
Susanne Moog authored
The view module already adds simTime to pages that have a publish date set. With this change all places generating page preview links behave in the same way, namely adding the simTime commands if the page has publish date restrictions. This change reverts f012052f and implements the behavior in a less intrusive way. Resolves: #66451 Releases: master Change-Id: Idc740477d821ac32cd74dbec7b616b2794165ea9 Reviewed-on: https://review.typo3.org/52098 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
Ralf Zimmermann authored
Resolves: #80333 Releases: master Change-Id: I201392bc67228864e31d9e7117880fbb401af279 Reviewed-on: https://review.typo3.org/52088 Tested-by:
Bjoern Jacob <bjoern.jacob@tritum.de> Tested-by:
Jurian Janssen <jurian.janssen@gmail.com> Reviewed-by:
Ralf Zimmermann <ralf.zimmermann@tritum.de> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
-
- Mar 20, 2017
-
-
Martin Kutschker authored
Fix incompatible return types of getRendererClassName() Make sure it is a string in all interfaces and implementations. Resolves: #80230 Releases: master Change-Id: I59cd0a1222e3aa67c742ca41331af2ddc4a1ee51 Reviewed-on: https://review.typo3.org/51997 Tested-by:
-
Michael Stucki authored
The is_file() check got lost during the refactoring in d855b470. Change-Id: Ia1688099a7ccd32667562e8c7f83fd54bb669f4a Resolves: #80354 Releases: master, 7.6 Reviewed-on: https://review.typo3.org/52100 Tested-by:
-
Josef Glatz authored
* remove/update inline comments * improve legibility by proper indentation and CGL Resolves: #80346 Releases: master Change-Id: I51207c0a54b18f78b1a0dd4313b398908ea2f021 Reviewed-on: https://review.typo3.org/52095 Tested-by:
Johannes Kasberger <johannes.kasberger@reelworx.at> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
-
Martin Kutschker authored
Do not double-encode name with HTML entities. Resolves: #80343 Releases: master Change-Id: If8e3757f0d34712f0daf03122e61b6ef06a1ccd0 Reviewed-on: https://review.typo3.org/52094 Reviewed-by:
-
Christian Kuhn authored
Using the signed parent tca config incoming via ajax request in the inline ajax controller solves a series of issues in 'new' and other scopes. The expensive calculation of inline parent TCA config within the controller can be dropped. Change-Id: I4ff31d0398ebfa1bb311bbe6ea97c839aa2df1ac Resolves: #80325 Resolves: #76671 Releases: master Reviewed-on: https://review.typo3.org/52077 Reviewed-by:
Tobi Kretschmann <tobi@tobishome.de> Tested-by:
-
Georg Ringer authored
Since #77652 the languages are sorted manually using a sorting field. Use this field also in the language selection of pages_language_overlay. Resolves: #80351 Releases: master Change-Id: I490aa5c477cc2c45110a658e05b42e75f0528610 Reviewed-on: https://review.typo3.org/52099 Reviewed-by:
-
Christian Kuhn authored
TCA property l10n_cat has been there since ever and nobody understood it. The docs about it never said what it really does and the according arguments from EditDocumentController were never used. The patch removes l10n_cat and some left over handling in EditDocumentController. Do not confuse this l10n_cat related localizationMode text/media with the localizationMode select/keep from inline: The inline part is not touched by the patch. Change-Id: Ia7b54bddabffcad3e38df76731d7fe9f6b8ff40f Resolves: #80331 Releases: master Reviewed-on: https://review.typo3.org/52086 Reviewed-by:
-
Thomas Hohn authored
Check for EXT:Compatibility7 instead of EXT:Compatibility6 in the Typo3Status Report. Resolves: #80348 Releases: master Change-Id: Iec4b7faa5eacd6007d0871278eeb23aa8e2b8448 Reviewed-on: https://review.typo3.org/52096 Tested-by:
-
Georg Ringer authored
The previous change disabled the lookup on the parent UID which resulted in getting all possible relations due to the missing constraint. Now the behavior is mitigated by resetting non-numeric values to zero which will lead to an empty result set - like implicitly for MySQL before. Resolved: #80172 Releases: master Change-Id: If6c8d2e3b2c2b2ddf15727196f7da294fe2ada06 Reviewed-on: https://review.typo3.org/51978 Tested-by:
Marcus Schwemer <ms@schwemer.de> Tested-by:
Markus Sommer <markussom@posteo.de> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
-
Oliver Hader authored
This change is focussed on runtime processing of l10n_mode which is not required anymore. Thus accordant internal functionality is deprecated. Change-Id: I19b8eabdfc98bfe83ff80d8205b0c9f029330ed5 Resolves: #80345 Releases: master Reviewed-on: https://review.typo3.org/52013 Tested-by:
-
Oliver Hader authored
TCA type's inline localizationMode can either be "keep" or "select". At least "keep" is counter-productive if allowLanguageSynchronization is enabled. That's why the whole localizationMode behaviour setting shall be deprecated and ignored in case allowLanguageSynchronization is enabled for the very same TCA field. This change does not migrate non-conflicting localizationMode settings automatically, since this potentially might be breaking and cannot be done without side-effects. Besides that calls to the static function BackendUtility::getInlineLocalizationMode() do not trigger a new entry in the deprectation log since the usage of localizationMode in TCA is logged already. Resolves: #79770 Releases: master Change-Id: Ic2072877d08bb880e9e957d6d31f0527333c2cc5 Reviewed-on: https://review.typo3.org/51650 Tested-by:
-
- Mar 19, 2017
-
-
Gianluigi Martino authored
The inline styles were removed from CSS Styled Content but not in Fluid Styled Content. Now this is also removed in EXT:fluid_styled_content. Releases: master Resolves: #80171 Change-Id: I91343b803d6da0b651b6984c8c94c2583730aa40 Reviewed-on: https://review.typo3.org/52059 Reviewed-by:
-
- Mar 18, 2017
-
-
Anja Leichsenring authored
Upon DuplicationBehaviour::RENAME and ~::REPLACE, the according function is called for the given file. For DuplicationBehaviour::CANCEL, the same exception as before is thrown. For a better UX, the existance of a possible duplicate is checked and a modal window is rendered to the users to let them choose the desired action if a duplicate was found. Resolves: #80282 Releases: master Change-Id: Ie67f04184a232fc23a3cda648692783771ba5171 Reviewed-on: https://review.typo3.org/52048 Tested-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
-
Christian Kuhn authored
While the two NodeExpansion API's allow the usual returnArray from single expansion nodes, fieldControl does not, due to its restricted format. The patch improves the single return value result merging and adds support especially for 'requireJsModules' to fieldControl. Change-Id: I7b8e44076aadd27fa5b9780ff97c1bab7141b55f Resolves: #80330 Releases: master Reviewed-on: https://review.typo3.org/52085 Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
-
- Mar 17, 2017
-
-
Christian Kuhn authored
Add the 'valuePicker' functionality to the colorpicker. This is useful for editors to have a series of defaults. A similar configuration worked in the past based on 'select' wizard. Example TCA from styleguide master input_37: 'config' => [ 'type' => 'input', 'renderType' => 'colorpicker', 'size' => 10, 'valuePicker' => [ 'items' => [ [ 'blue', '#0000FF', ], [ 'red', '#FF0000', ], [ 'typo3 orange', '#FF8700', ], ], ], ], Change-Id: Idf24ecc1b47e84f6e4aa985191beebeb3631b202 Resolves: #80337 Releases: master Reviewed-on: https://review.typo3.org/52090 Reviewed-by: -
Ralf Zimmermann authored
Add method for setting the identifier for renderables. Resolves: #80319 Releases: master Change-Id: I9103068aef1b71eb86e589ddb7d107d7a738621e Reviewed-on: https://review.typo3.org/52076 Tested-by:
Martin Kutschker <martin.kutschker@ymail.com> Tested-by:
-
Ralf Zimmermann authored
Move this fluid form VH attributes into the EXT:form configuration * f:form -> additionalParams * f:form -> addQueryString * f:form -> argumentsToBeExcludedFromQueryString * f:form -> action * f:form -> enctype * f:form -> method Resolves: #80236 Releases: master Change-Id: Id820e06678ec18ea6013c451ab5f42458863adb3 Reviewed-on: https://review.typo3.org/52005 Tested-by:
-
Christian Kuhn authored
Deprecation should be Feature to fix the list on https://docs.typo3.org/typo3cms/extensions/core/8-dev/Changelog/8.6/Index.html Change-Id: Ic514b1adbb6e624ff9f740a0a9f020f848d7b0df Resolves: #80332 Releases: master Reviewed-on: https://review.typo3.org/52087 Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
-
Oliver Hader authored
Fix PHPdoc comments of return types. Change-Id: I58686de41b135694305ca146590cba1c66ee6716 Resolves: #80271 Releases: master Reviewed-on: https://review.typo3.org/52081 Tested-by:
-
Christian Kuhn authored
This reverts commit 51b5fad9. The patch introduced some delays and the acceptance tests fail, reverted for now. Change-Id: I2214932f4aadb8cb98c1e44752111dbaeaf04587 Resolves: #80328 Reverts: #80058 Releases: master Reviewed-on: https://review.typo3.org/52083 Reviewed-by:
-
Georg Ringer authored
To make inline proper working in JS, the name of the field must be escaped as it can contain dots. Resolves: #78985 Releases: master, 7.6 Change-Id: I18c1d85906b9710c25b326b89e8104f3ea3c8a29 Reviewed-on: https://review.typo3.org/51014 Tested-by:
-
Josef Glatz authored
Improve the error message for non valid index keywords in changelog RST files. Resolves: #80310 Releases: master Change-Id: Ibca4f135a7f43c7c936fd57c14b1f7b7fc0a9d1f Reviewed-on: https://review.typo3.org/52068 Tested-by:
-
Christian Kuhn authored
Merging columnsOverrides into columns in FormEngine data provider TcaColumnsOverrides is done via ArrayUtility::mergeRecursiveWithOverrule() which supports the '__UNSET' feature to kick array parts from the original array. This is problematic since TCA should be additive only, for instance the 'isloaded' display condition has been removed for that reason, too. Specific issue is here that using __UNSET stops working if there is a second mergeRecursiveWithOverrule() later, for instance in the element expansion classes. This leads to hard to track issues and almost always does not end up with a result a developer expects. Solution is switching to php built-in array_replace_recursive() instead which does not do __UNSET magic. In general, always only add things to the columns array in columnsOverrides, columns should have the common dominator of all overrides. Disabling of specific features can be done only by adding a new key 'disableFoo' = true or similar, the according TCA feature has to explicitely support that. Change-Id: Ieba262c899ae2df2e3aa2c63d7dfa6b86e3fa4f4 Resolves: #80321 Releases: master Reviewed-on: https://review.typo3.org/52074 Tested-by:
Helmut Hummel <typo3@helhum.io> Tested-by:
-
Oliver Hader authored
l10n_state fields are not created automatically when installing an extension since there is no slot defined for the according signal InstallUtility::tablesDefinitionIsBeingBuilt. Change-Id: Ib4d05d3c3a2dde9b6d0a77f89dee650a3872544d Resolves: #80271 Releases: master Reviewed-on: https://review.typo3.org/52080 Tested-by:
-
Benni Mack authored
* Register "formvh:" as global namespace, simplifying the templates * Remove formvh:be.pageRenderer and add the missing files to EXT:fluid * Migrate callbacks to signal slots and deprecate the callbacks * Fix plain mail viewhelper, and deprecated it as it can be done in Fluid directly * Code cleanup (fix indention, unused variables etc.) * Deprecate custom checkbox VH because the fluid bug is gone * Change tx_form view properties to ".0" instead of ".5" to be in line with FSC * Streamline fluid VH additionalAttributes usage; add compatibility for previous configuration; Add BE form editor auto migration * Fix small JavaScript bugs * Fix small configuration bugs Resolves: #80301 Resolves: #80287 Releases: master Change-Id: Icf68b8a9a6876805af7bf273735d3d30984136ed Reviewed-on: https://review.typo3.org/51972 Tested-by:
-
Mathias Brodala authored
We're only deprecating these two methods, not the whole file. Resolves: #80316 Releases: master Change-Id: Ia1727c0996f53caa35d4755d2d5caa04bc48de46 Reviewed-on: https://review.typo3.org/52071 Reviewed-by:
-
- Mar 16, 2017
-
-
Thorben Nissen authored
Opening a record with a FormEngine field type='select' and renderType='selectTree' just renders boilerplate HTML that triggers an ajax request to fetch actual tree node data for each field. The server side ajax controller reduces the TCA to contain only the field the items should be calculated for to reduce parse times. In flex form context, if now that tree field has a FIELD display condition, the standard data group 'tcaDatabaseRecord' which calls 'all' providers fails, since it can't find a database value of the condition target. Solution is to create an own data provider group for this 'fetch tree data' ajax context: This group contains only providers needed by the 'TcaSelectTreeItems' provider and ignores everything else, most importantly the EvaluateDisplayConditions provider. Leaving out a series of other not needed data providers gives an additional performance improvement in this context. Resolves: #79657 Releases: master Change-Id: I29bdd659d5f5ee28f8ae017c47df0233abefd6f5 Reviewed-on: https://review.typo3.org/51574 Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
-
Claus Due authored
This patch moves frontend-editing intialisation from the EditDocumentController (EXT:backend) to a signal listener in EXT:feedit. Step towards extracting EXT:feedit to TER. Change-Id: I09a7e5a2205e7020e7145023d7d63c61d9be508c Resolves: #80244 Releases: master Reviewed-on: https://review.typo3.org/52011 Tested-by:
-
- Mar 15, 2017
-
-
Josef Glatz authored
Add the current content element as section to the un-/hide link. Releases: master, 7.6 Resolves: #80274 Change-Id: I0d6ec4ea8274f82f6d4c66a4e9e77860819d4d15 Reviewed-on: https://review.typo3.org/52045 Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Reviewed-by:
-
