- Dec 18, 2017
-
-
Stephan Großberndt authored
Releases: master Resolves: #83380 Change-Id: Ic90db1b6ee239841586ab100be6d8d312a94e859 Reviewed-on: https://review.typo3.org/55152 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Alexander Opitz <opitz.alexander@googlemail.com> Tested-by:
-
- Nov 30, 2017
-
-
Stephan Großberndt authored
The table and column name quoting method {#tableName}.{#columnName} introduced for TypoScript in issue #80506 is now used to quote identifiers in TCA column definitions known to possibly contain SQL fragments. Missing quotes for identifiers containing e.g. uppercase letters lead to exceptions when performing a query in PostgreSQL. In order to achieve this a new Class TcaPreparation is added as this is not a typical TcaMigration. Releases: master, 8.7 Resolves: #81751 Related: #80506 Change-Id: I230be317c7088e5de5343634fac507b4ab994b28 Reviewed-on: https://review.typo3.org/53360 Reviewed-by:Susanne Moog <susanne.moog@typo3.org> Tested-by:
Andreas Wolf <andreas.wolf@typo3.org> Tested-by:
-
- Nov 29, 2017
-
-
Benni Mack authored
The last place in TYPO3 Core to use internal_type=file (backend_layout.icon) is now moved to FAL with sys_file_reference. An upgrade wizard is in place to migrate existing icons from uploads/media to sys_file. FormEngine is migrated to also allow to use sys_file_references for the TCA ctrl property "selicon_field". With this change, a followup could be integrated to deprecate "old-style" internal_type=file code, and also to not create the uploads/ folder at all anymore within TYPO3 installations. Additionally, the functionality of "selicon_field_path" should be deprecated in the future. Resolves: #83153 Releases: master Change-Id: I578fd68b7e1f7bc6a1991b90e7750b903d3ec28b Reviewed-on: https://review.typo3.org/54830 Tested-by:
Sebastian Hofer <sebastian.hofer@marit.ag> Tested-by:
Pawel Cieslik <p.cieslik@macopedia.pl> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
-
- Nov 08, 2017
-
-
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:
Frans Saris <franssaris@gmail.com> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
-
Benni Mack authored
The DB setting "sys_domain.forced" is confusing and does not make sense nowadays, especially with nested domain records - where the rootline is now correctly traversed with the RootLine utility. Resolves: #82926 Releases: master Change-Id: I874c54aeb03c0b62c9a1cebc9d629cee7550ec0b Reviewed-on: https://review.typo3.org/54540 Tested-by:
Daniel Gorges <daniel.gorges@b13.de> Tested-by:
Stefan Neufeind <typo3.neufeind@speedpartner.de> Tested-by:
-
- Oct 20, 2017
-
-
Christian Kuhn authored
Allow 'label' within the 'palettes' array in TCA next to 'showitem'. This defines a default label rendered as the palette label in FormEngine if not overridden in a 'types' definition like '--palette--;labelReference;thePalette'. The patch introduces this feature in PaletteAndSingleContainer of FormEngine code and adapts core TCA definitions to introduce the default labels for palettes. This makes the 'types' definitions shorter and much better readable and gives the core an opportunity to steer the labels for palettes which are often re-used by extension authors. Change-Id: I185340d4e037d713eebbb6cd676287e6fe85705b Resolves: #82826 Releases: master Reviewed-on: https://review.typo3.org/54449 Reviewed-by:
Benjamin Kott <benjamin.kott@outlook.com> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
-
- Sep 20, 2017
-
-
Georg Ringer authored
Allow 255 chars for a domain to be in sync with RFC 1035. Resolves: #82515 Releases: master, 8.7, 7.6 Change-Id: I63916cb115b00e50c62c1926cf890e29bf89de77 Reviewed-on: https://review.typo3.org/54186 Reviewed-by:
Patrik Karisch <p.karisch@pixelart.at> Tested-by:
Alexander Schnitzler <review.typo3.org@alexanderschnitzler.de> Tested-by:
-
- Sep 09, 2017
-
-
Mathias Brodala authored
Resolves: #82350 Releases: master Change-Id: I60280df8d62cc65250bf5edbf8c26a65dbb5f250 Reviewed-on: https://review.typo3.org/53961 Reviewed-by:
Daniel Lorenz <daniel.lorenz@extco.de> Tested-by:
Riccardo De Contardi <erredeco@gmail.com> Tested-by:
-
- Aug 25, 2017
-
-
Benni Mack authored
The field pages.urltype contains "0", "1", "2" which maps to a protocol, however most people want to just paste the url in the "pages.url" field. This change drops the DB field "pages.urltype" and merges the value into "pages.url" directly. Resolves: #71306 Releases: master Change-Id: I309724ba48ac9c5674a75e79da6cbb6e4880e521 Reviewed-on: https://review.typo3.org/53198 Tested-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
-
- Aug 23, 2017
-
-
Christian Kuhn authored
Change a series of cgl details after update of php-cs-fixer from 1.0 to 1.4. Change-Id: Iba289f530e2df2c6fc73e5f5b705a673b4b3db0f Resolves: #82171 Related: #82164 Releases: master, 8.7 Reviewed-on: https://review.typo3.org/53776 Tested-by:
-
- Aug 18, 2017
-
-
Georg Ringer authored
Instead of using 2020 use the technical limit of 32bit which is 2038. Resolves: #81940 Releases: master, 8.7 Change-Id: If0b1bee101b4917d7a974dd0e91f79bc24139227 Reviewed-on: https://review.typo3.org/53582 Tested-by:
Henning Liebe <h.liebe@neusta.de> Reviewed-by:
Sascha Rademacher <sascha.rademacher+typo3@gmail.com> Reviewed-by:
Sascha Egerer <sascha@sascha-egerer.de> Reviewed-by:
Steffen Frese <steffenf14@gmail.com> Reviewed-by:
Sonja Großewinkelmann <s.grossewinkelmann@neusta.de> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
-
- Aug 14, 2017
-
-
Wolfgang Klinger authored
Adds ‘Sort by creation date’ and ‘Sort by modification date’ options and a new option to set a sorting direction in the file links content element. Corrects the sorting option labels in English. Resolves: #65403 Resolves: #63509 Releases: master Change-Id: I0e0b474ee49e2be5e4111b6841a36f27d35f3b71 Reviewed-on: https://review.typo3.org/53667 Tested-by:
-
- Jun 03, 2017
-
-
Jasmina Liessmann authored
Resolves: #81352 Releases: master, 8.7 Change-Id: I7f55e6998ebde5d8d90e7b6bcd05f4550f6ce09a Reviewed-on: https://review.typo3.org/53064 Tested-by:
Mona Muzaffar <mona.muzaffar@gmx.de> Tested-by:
-
- Mar 25, 2017
-
-
Helmut Hummel authored
The configuration possibilities to override child TCA from the TCA of an inline parent foreign_types foreign_record_defaults foreign_selector_fieldTcaOverride overrideCropVariants Are now replaced with a new generic one overrideChildTca The old TCA is migrated to the new version. Resolves: #80000 Releases: master Change-Id: Iebe4e0794517bc51f8bb2406aec80d95dfcb374e Reviewed-on: https://review.typo3.org/52130 Reviewed-by:
-
- Mar 22, 2017
-
-
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:
Josef Glatz <josef.glatz@typo3.org> Tested-by:
Jan Helke <typo3@helke.de> Tested-by:
-
- Mar 20, 2017
-
-
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:
Markus Klein <markus.klein@typo3.org> Tested-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:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
-
- Feb 28, 2017
-
-
Josef Glatz authored
An already deprecated TCA ctrl field requestUpdate was apparently introduced by accident while streamlining FSC and CSC. Resolves: #80049 Related: #78899 Related: #79622 Releases: master Change-Id: I41e613ffc99b17124deeb446ff6b5e24ec464f36 Reviewed-on: https://review.typo3.org/51880 Tested-by:
Thomas Hohn <thomas@hohn.dk> Reviewed-by:
-
- Feb 24, 2017
-
-
Josef Glatz authored
Add a description field also for fe_users records which could be used as for already known other record types. Resolves: #79894 Releases: master Change-Id: Ia1d7ad7746a0b7dd3ebb809864e290db97ac228d Reviewed-on: https://review.typo3.org/51745 Tested-by:
-
- Feb 07, 2017
-
-
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:
-
- 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 pr...
-
- Jan 27, 2017
-
-
Georg Ringer authored
The field `select_key` is not used by the core and is moved to the EXT:compatibility7. Resolves: #77934 Releases: master Change-Id: Ied7fa722c1bccb314fd02229da407613fbce7dfe Reviewed-on: https://review.typo3.org/49934 Reviewed-by:
-
- Jan 26, 2017
-
-
Christian Kuhn authored
The patch introduces a new API on FormEngine element level that substitutes the old "wizards" / renderWizard() API with a more powerful system. Single wizards are now split into one of three categories: * An informational wizard * A control button / icon * A true wizard with additonal functionality Method renderWizards() is still called in elements for compatibility reasons if people added own scrip/popup/userFunc wizards, but all core wizards are migrated. The patch significantly cleans the HTML of single elements, especially HTML stuff that was added by the SingleFieldContainer is now put down to single elements, while main HTML wraps formerly done by renderWizards() is fetched "up" to single elements. This gives single elements full control about the main HTML it is producing, which is a must have preparation in order to further advance in this area and to switch single elements to fluid rendering in one of the next steps. The patch brings a prett...
-
- Jan 18, 2017
-
-
Georg Ringer authored
To improve usability the naming and sorting of content element types for the content element wizard and the select box are unified. Resolves: #77961 Releases: master Change-Id: I6a0aa4a824992e062ba14931a7712eaafadeb8ab Reviewed-on: https://review.typo3.org/49948 Reviewed-by:
Alexander Stehlik <alexander.stehlik@gmail.com> Tested-by:
Claus Due <claus@phpmind.net> Reviewed-by:
-
- Jan 12, 2017
-
-
Tymoteusz Motylewski authored
A new field which is a ctrl-based field for any TCA table called "translationSource" set to a DB field name (used for the new field tt_content.l10n_source) is added and filled as it contains the uid of the record of where a translation record came from. This is different to "transOrigPointerField" as it contains not the record to a record in the default language or the one where a record was copied from, but rather the information what the translation source was made. Releases: master Resolves: #78169 Change-Id: I3ecfeedb656c64681e5e3021cad6b708482520dc Reviewed-on: https://review.typo3.org/51070 Tested-by:
-
- Jan 03, 2017
-
-
Christian Kuhn authored
The patch adapts a series of nasty form engine areas to more solid code. The evaluate condition code is rewritten and works much better in flex form scenarios. The suggest wizard and svg tree are much more solid in flex forms. The group element is rewritten towards a better readable and easier to refactor code, dropping method dbFileIcons(). A bunch of issues is resolved along the way. * TCA "default" now works in flex form section container elements * The "displayCond" parser is now strict and throws exceptions on invalid syntax and wrong referenced fields to help debugging faulty display conditions * TCA displayCond on flex fields can now be prefixed with the sheet name and can reference field values from neighbor sheets * TCA displayCond now works with flex section containers * TCA flex section container now throw an exception if select or group fields configure a MM relation - this is not supported * TCA ctrl requestUpdate field is dropped, onChange=reload is now allowed not only on flex form fields, but also on normal columns fields * TCA tree now works as section container element and initializes correctly on new records and new containers * GroupElement rewrite to drop dbFileIcons() * config option maxitems now optional for type=group and type=select and defaults to "many items allowed" * inline now works in "fancy" flex situations with "new" records by handing the final dataStructureIdentifier around * FormEngine no longer loads extJS Change-Id: Id1d081627529cc1502bb198389e5bd69372815cd Resolves: #78899 Resolves: #72307 Resolves: #75646 Resolves: #76637 Resolves: #72106 Resolves: #78824 Resolves: #76793 Resolves: #68247 Resolves: #69715 Related: #78460 Related: #67198 Related: #72294 Releases: master Reviewed-on: https://review.typo3.org/50879 Tested-by:
-
- Dec 14, 2016
-
-
Helmut Hummel authored
Fix some typos and a leading newline in a PHP file Related: #78383 Releases: master Change-Id: I483b09abf02a9f109350284e31cba15848004e5c Reviewed-on: https://review.typo3.org/50961 Reviewed-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
-
- Dec 03, 2016
-
-
Christian Kuhn authored
This reverts commit 36f8765a. Change-Id: Ida5c32b33e8953bd1172c9886af16b66e3c2297f Reviewed-on: https://review.typo3.org/50878 Reviewed-by:
-
Alexander Stehlik authored
Allow the the method CategoryRegistry->getCategoryFieldItems() to be used as itemsProcFunc for select fields in the TCA in arbitary contexts by introducing a new categoryFieldsTable configuration in the config section of a column in the TCA. This configuration key can either consist of a single string containing the name of the table or a configuration array to define additional conditions that need to be true so that a configured table is used. The condition matching is based on the displayCond functionality of the TCA. To make use of the existing functionality the code for matching the display conditions is extracted from the form data provider to a new DisplayConditionEvaluator utility class. Resolves: #53045 Releases: master Change-Id: I128cbeb6747a8f83e68cdaaaafbc3ab5901353d4 Reviewed-on: https://review.typo3.org/24968 Tested-by:
-
Daniel Windloff authored
In TYPO3 there are some recurring field definitions shared by a lot of records. These fields are mostly defined in the control section of TCA. These fields are used as well by the core as by records introduced by third party extensions. In order to get a consistent behaviour (from editor's perspective) these fields should have a generic position in tabs. Resolves: #78383 Releases: master Change-Id: I365538b8e6013e3911710b113bec7d41314809b2 Reviewed-on: https://review.typo3.org/50364 Reviewed-by:
-
- Dec 01, 2016
-
-
Johannes Goslar authored
Remove support for transForeignTable and transOrigPointerTable in TCA. More details in Breaking-78191-RemoveSupportForTransForeignTableInTCA.rst Resolves: #78191 Releases: master Change-Id: Ibd7e1a963fdbf84ca7f4b5926b4a8cd02ba24631 Reviewed-on: https://review.typo3.org/50819 Reviewed-by:
Valentin Funk <valentin.funk@computerfabrik.de> Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
-
Wouter Wolters authored
Move languages files from the root of ext:lang to Resources/Private/Language/ Resolves: #78647 Releases: master Change-Id: I9271442c98f2fcf705a38a639a6d503caeba1759 Reviewed-on: https://review.typo3.org/50584 Reviewed-by:
-
- Nov 13, 2016
-
-
Frank Naegler authored
Adding items for type selectTree with pageTsConfig does not work as documented. The TCA tree needs multi-root handling to handle that. Additionally, some slight changes in the order of elements when items are calculated are needed. Resolves: #78628 Releases: master Change-Id: Iecf0225c0eeaab8ea661997cad26e68d255d8460 Reviewed-on: https://review.typo3.org/50565 Tested-by:
-
- Nov 01, 2016
-
-
Benni Mack authored
There are several places within EXT:version and DataHandler which try to do "pageVersionizing" but it's not possible anymore (see removed code in "new" section of DataHandlerHook) since TYPO3 v7. This also means that the `versioning_followPages` option is removed completely from the Core. Resolves: #78524 Releases: master Change-Id: I6166e198fc74922aa34e2ae49440e4c0fe4354a6 Reviewed-on: https://review.typo3.org/50462 Tested-by:
-
- Sep 28, 2016
-
-
Georg Ringer authored
To improve the usability, the suggest wizard is added to the field file_collections of tt_content. Resolves: #78084 Releases: master, 7.6 Change-Id: Ia2c2ebdeb70ba96e1f5cc8a9dc4fa11bbfd704e1 Reviewed-on: https://review.typo3.org/50034 Tested-by:
-
- Sep 26, 2016
-
-
Georg Ringer authored
Move the configuration to EXT:impexp. Resolves: #77941 Releases: master Change-Id: I1e87ba5eb1f9abf52abcd7f2e345ced9093c2a27 Reviewed-on: https://review.typo3.org/49935 Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
-
- Aug 31, 2016
-
-
Georg Ringer authored
The following icons are removed from EXT:backend/Resources/Public/Images/FormFieldWizard/: - wizard_add.gif - wizard_edit.gif - wizard_list.gif - wizard_table.gif The TCA migration migrates it to the proper icon fonts. For 7.6, the patch will be applied without removing the icons. Resolves: #77630 Resolves: #77629 Releases: master, 7.6 Change-Id: I9e73fb6d1f7197d5c35309fa98093eeee44ccb02 Reviewed-on: https://review.typo3.org/49589 Reviewed-by:
Bamboo TYPO3com <info@typo3.com> Reviewed-by:
-
- Aug 30, 2016
-
-
Wouter Wolters authored
As decided during T3ACME we will use the short array syntax in master. The 7.6 branch will also be done to make backporting easier. Resolves: #77692 Releases: master,7.6 Change-Id: I37e9484b1012fc9161148257a842054c24d162ba Reviewed-on: https://review.typo3.org/49651 Reviewed-by:
-
- Aug 22, 2016
-
-
Georg Ringer authored
FAL relations in translated pages must have the same properties as in regular pages which includes link fields and the cropping editor. Resolves: #77541 Releases: master, 7.6 Change-Id: Ice77cd6c752e46ee048d07ca60c9b76cfc5509e8 Reviewed-on: https://review.typo3.org/49531 Reviewed-by:
Morton Jonuschat <m.jonuschat@mojocode.de> Tested-by:
-
- Aug 03, 2016
-
-
pythondetective authored
Using the File Abstraction Layer for this field as well, like it is handled within tt_content.image and pages.media already. Also, the patch adds a migration wizard in the install tool to move existing images to the File Abstraction Layer. Resolves: #74375 Releases: master Change-Id: I157d619dec18ef24e7d1e2d8694ed150304549d7 Reviewed-on: https://review.typo3.org/47139 Tested-by:
-
