- Apr 07, 2022
-
-
Alexander Nitsche authored
- align README.rst, Index.rst, Includes.txt, Includes.rst.txt, Settings.cfg - add genindex.rst, Sitemap.rst - remove outdated Targets.rst - rename Includes.txt to Includes.rst.txt - reference manual's start page with :doc:`<manual>:Index` Adding the custom label `start` to the beginning of the manual's Index.rst is redundant. Use :doc:`<manual>:Index` instead of :ref:`<manual:start>` to refer to it. - replace :ts: with :typoscript: text role The ambiguous :ts: text role has been removed to not confuse the writer with typescript and typoscript. - fix rendering warnings of EXT:core - fix rendering warnings of EXT:dashboard - fix rendering warnings of EXT:fluid_styled_content - fix rendering warnings of EXT:form - fix rendering warnings of EXT:linkvalidator - remove outdated encoding note - align reST validator at Build/Scripts/validateRstFiles.php See https://docs.typo3.org/m/typo3/docs-how-to-document/main/en-us/GeneralConventions/FileStructure.ht...
-
Michael Telgkamp authored
The context sensitive help (CSH) is not accessible and the information is often not useful or not updated for a long time. As the online documentation is now improved a lot, there is a link added in the main help menu. For short, but important additional information to explain the usage of a field the `description` field should be used. Resolves: #97312 Releases: main Change-Id: Ic0b7df90ef88c53f802bfb254023ba030ff01ee7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74191 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
-
Georg Ringer authored
Extend BackendUtility::getDropdownMenu() for the possibility to add the "id" of the select element. This allows to connect a corresponding label, improving accessibility. This is done for the info and template module. Resolves: #97318 Releases: main Change-Id: I766e55b14e58f164c06d21f4490a22a33393b6c4 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74199 Tested-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
-
- Apr 06, 2022
-
-
Nikita Hovratov authored
Resolves: #97321 Releases: main Change-Id: Ifbbd0e4961ed2c17beebadb0d2eb732fdd05f6a0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74202 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
-
Torben Hansen authored
When nullable columns are shown in filelist module, an exception is thrown, because null may be passed to htmlspecialchars(). This change ensures that an empty string is passed to htmlspecialchars(), if the column value is null. Also the last parameter from the getProcessedValueExtra() function call is removed, since it equals the functions default value for the $forceResult parameter. Resolves: #97316 Releases: main, 11.5 Change-Id: I7d82aea0ed073f6f30944d53e0803ce848e30e53 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74198 Tested-by:
-
Andreas Fernandez authored
The contents of a field of type `flex` may be NULL if the field is empty. `BackendUtility::getProcessedValue()` handles the content of such `flex` fields now only if the value is an actual string to solve deprecations related to PHP 8.1. In the same run, the content is trimmed to get rid of lots of empty lines caused by multiline XML data. Resolves: #97297 Releases: main Change-Id: I4261d16bfa819fd1151bbe6905b97f2571701fee Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74174 Tested-by:
Susanne Moog <look@susi.dev> Tested-by:
-
Shehfinaz Kadavil authored
This makes the ExtensionUtility:registerPlugin() method return the plugin signature, which might be used for further TCA adjustments, e.g. definition of FlexForms. Resolves: #82809 Releases: main Change-Id: Ia88f0b798affe6e47b4c5a4f850022e6ace18169 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74175 Tested-by:
-
Stefan Bürk authored
The check for doing the functional test splitting script and running the selected chunk used similar but different minimum chunk value to check against. Thus the splitting script has not been executed in all chunk execution contexts. This patch uses now exactly the same check in the 'Build/Scripts/runTests.sh' like it is defined in the corresponding docker-compose service config. Furthermore all previous created functional split files are now removed to avoid leftovers, which occured if re-run has lower chunksize defined. Example which is now properly fixed: > Build/Scripts/runTests.sh -s functional -c 1/1 Example with partial part files from previous run: > Build/Scripts/runTests.sh -s functional -c 1/10 > Build/Scripts/runTests.sh -s functional -c 1/8 Resolves: #97283 Releases: main, 11.5, 10.4 Change-Id: Id3a0d1c85540b4e7e46aaea69cf2d96839e8e72e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74157 Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
Oliver Bartsch authored
used command: > composer u typo3/cms-styleguide Resolves: #97314 Releases: main Change-Id: Id5fe8f81e88348c3000953d5857cc40816f47482 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74190 Tested-by:Benni Mack <benni@typo3.org> Reviewed-by:
-
Benjamin Kott authored
Releases: main Resolves: #97310 Change-Id: I8d85aa779fa82c8c8307f6e3187e1dcc701de7d7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74187 Tested-by:
-
- Apr 05, 2022
-
-
Nikita Hovratov authored
Resolves: #97311 Releases: main Change-Id: I9edda1c4ff1c28d98187e0f954a1229a46e8463b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74188 Tested-by:
-
Uwe Trotzek authored
With this new option an editor is able to view all records on a page regardless of the start and end time. This is especially helpful if one has content on a page with different start and end times and an editor wants to have an overview of all elements on that page. For example if he wants to check if the layout and everything is okay. Without this option the editor has to simulate multiple dates to be able to see all records, because records which are visible on one date, can be invisible on another. Resolves: #91082 Releases: main Change-Id: If4bd4103615f17a17fac8cb003e439bee65301da Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64208 Tested-by:
-
Oliver Bartsch authored
A couple of new TCA types have been introduced. To be able to merge duplicated code parts together, slight discrepancies are resolved first. This also includes the now cleaned up InputTextElement. Resolves: #97304 Releases: main Change-Id: I07657c63f7a0e96d7793cab951148b7319d089b9 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74184 Tested-by:
Nikita Hovratov <nikita.h@live.de> Tested-by:
-
Benjamin Kott authored
Resolves: #97306 Releases: main Change-Id: I54c6e90bf8b63e7d24fd25d62332f97a79bbe0ab Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74182 Tested-by:
Frank Nägler <frank.naegler@typo3.com> Tested-by:
André Kraus <info@andrekraus.com> Tested-by:
-
Nikita Hovratov authored
The new type "number" is a replacement for type "input" with "eval=int" or "eval=double2" set. With this, the type "input" field is now always a html "text" field and type "number" is always a html "number" field. With the new TCA option "format", a number type can be defined. Values can be either "integer" (default) or "decimal". The decimal format replaces the former "double2" eval value. In the future, a new option for precision might be added, in order to dynamically define how many decimal places should be possible. The valueSlider has been moved from InputTextElement to NumberElement, as it makes only sense with a type number field. Additionally, the JS module is migrated to a custom element. Note: There is still the eval="num" option for type "input" fields. This is solely for the purpose to ensure only numeric characters are used. Therefore, this option does not qualify anymore for the "range" option. The "range" option is now removed altogether for simple type "input" fields, as it now purely handles text values. Resolves: #97193 Releases: main Change-Id: Ia0888699f2c518917412e700e2681d9fea727340 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74067 Tested-by:
-
Andreas Fernandez authored
Textarea can be configured in TCA to be read only and to have a richtext editor enabled. If `readOnly` is enabled, ckeditor is now rendered in a read-only mode instead of rendering a plain textarea containing HTML markup. Resolves: #97296 Releases: main, 11.5 Change-Id: I9e457123811ef53ad4e3e355a68e3f1e5701dcfc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74180 Tested-by:
-
Andreas Fernandez authored
`RenderPreviewImportPageAndRecordsByUpdateWithDiff.php` has HTML markup with line breaks and tab characters. With some IDEs this may break if lines containing a tab only will get trimmed. All such characters are now replaced by explicit control characters to make sure the expectation does not break anymore when saving this file. Resolves: #97300 Releases: main, 11.5 Change-Id: Ifc5d7e39d6d69176b111d3361f741a89866f008b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74177 Reviewed-by:
Simon Gilli <typo3@gilbertsoft.org> Reviewed-by:
-
Simon Gilli authored
This patch applies the new documentation standards to the .editorconfig. Resolves: #97302 Releases: main, 11.5, 10.4 Change-Id: I798b355f71dfa7ba8ac20ad424105e99a5c870cc Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74179 Tested-by:
Lina Wolf <112@linawolf.de> Reviewed-by:
Alexander Nitsche <typo3@alexandernitsche.com> Reviewed-by:
-
Benjamin Kott authored
The "label" class was removed in bootstrap 5 and replaced through "badge". The "label" class was kept in place for a while to keep the compatibility as high as possible, but it's time to move on. Since bootstrap 5 also dropped support for severities on certain components, we are adding them again for the badge to keep the convenience as high as possible and avoid promoting the "utility css" approach that was introduced with these decisions as we try to keep markup changes as low as possible. This patch also reverts the SCSS includes back to relative paths. While it is possible to define additional lookup paths for the parser, so you can have shorter includes - it comes at a cost. The included sources are opaque to the user and the IDE, this means there is no support for auto-completion, quick navigation through included files and can lead to unintended overrides by the user. Resolves: #97291 Releases: main Change-Id: I9007af705a90db567353379146df1d76b2366a...
-
Benjamin Franzke authored
The global variable $ (window.$) has been removed with #97243. This caused the RTE link wizard to fail with a JavaScript error as $.isEmptyObject is used in typo3link.js. Resolves: #97301 Related: #97243 Releases: main Change-Id: Iaafb02fa52039f8443289c4b16123e67c25b39ce Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74178 Tested-by:
-
Oliver Bartsch authored
The creation and modification time of files is now displayed correctly again, using the file info instead of the file metadata values. Especially when sorting by those fields, this previously led to discrepancies since the driver (performing the sorting) always uses the file info. See related patch: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74158 Additionally, non-admins are now also able to select the creation and modification time "fields" in the column selector. Resolves: #97290 Releases: main, 11.5 Change-Id: Ie9b4b7dccce68efeaac20998af4eeca204710f3f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74161 Tested-by:
-
- Apr 04, 2022
-
-
Christian Kuhn authored
symfony/rate-limiter:5.4.7 has a bug [1] leading to E_DEPRECATED warnings in our functional rate limiting tests. This is mostly test related so it does not make much sense to set this version as conflict. We'll comment two tests while waiting for a patch level release 5.4.8. [1] https://github.com/symfony/symfony/issues/45924 Releases: main, 11.5 Resolves: #97298 Change-Id: Ifb80a631830bb7b50fdc7c9d58d28e0dbf208ad1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74170 Tested-by:
-
Nikita Hovratov authored
After the removal of the fourth parameter of the checkAuthMode method, the local variable $authMode has not been removed, too. In addition, the @todo is removed, as it is resolved now. Resolves: #97294 Related: #97265 Releases: main Change-Id: I0712927a8d414e9d16b4ac89f505fa7da7c81494 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74168 Tested-by:
-
Lina Wolf authored
Releases: main Resolves: #97293 Change-Id: I0f5f44fab866e54e117138d369584967da7c3655 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74167 Tested-by:
Björn Jacob <bjoern.jacob@tritum.de> Tested-by:
-
Larry Garfield authored
Simple type additions. Nothing exciting. Resolves: #97205 Related: #97210 Releases: main Change-Id: Ic38274300b22f3ce9168e98c13239934c624069a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73987 Tested-by:
Simon Schaufelberger <simonschaufi+typo3@gmail.com> Tested-by:
-
Georg Ringer authored
Implement missing sorting of files in the local driver. Resolves: #97261 Releases: main, 11.5 Change-Id: I94c04dfbd88b0f010c57ec68395f9edbc64c77c0 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74158 Tested-by:
Jochen <rothjochen@gmail.com> Tested-by:
-
Benjamin Kott authored
Executed commands: cd Build yarn add "@typo3/icons@^2.6.0" yarn build Resolves: #97292 Releases: main Change-Id: I20cebc78e4ceeebcbc1295889ac7cad51565c0ed Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74164 Tested-by:
-
Christian Kuhn authored
The ext:core and ext:workspaces data scenario functional tests are pairs: core comes with the 'Modify' scenarios and workspaces extends them with own 'Discard', 'Modify', 'Publish' and 'PublishAll' ones. The patch separates the ext:core 'Modify' scenarios into an own directory and moves the ext:workspaces pendants next to it. This gives better overview and makes more clear that most of the workspaces related handling is part of ext:core anyways. Resolves: #97279 Releases: main Change-Id: Id20b07c0dcb6818fc6881b37d38f8ee7bae87543 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74152 Tested-by:
-
linawolf authored
Remove CLI commands removed in https://forge.typo3.org/issues/97131 from the lowlevel documentation. Resolves: #97288 Related: #97131 Releases: main Change-Id: I9113b6956093a527f9c85ad4383df622055a61ba Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74160 Tested-by:
-
- Apr 01, 2022
-
-
Oliver Bartsch authored
In the process of using dedicated TCA types, the new TCA type "color" is introduced and replaces "renderType=colorpicker" of TCA type "input". Notable changes to the previous behaviour: - The maxlength is set to 7, since this is the maximum length for the hex color (#XXXXX | /#[0-9a-fA-F]{3,6}/) - The only allowed eval is "null" - "trim" is always done in DataHandler and FormEngine Note: The maxlength might change again as soon as we switch to another color picker which supports e.g. opacity specification. The TCA type is now wrapped into a custom element. Also does it now use the general ValuePicker JS module, instead of duplicating this functionality in the ColorPicker JS module. The ColorPicker JS module is furthermore refactored. Global initialization of the color pickers is deprecated. To initialize the ColorPicker for an element, it has to be provided as first argument in the initialize() method. used command: > composer u typo3/cms-styleguide Resolves: #97271 Releases: main Change-Id: I1418b100ae214499be7b01f6c94539a6cb6baa3b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74121 Tested-by: -
Oliver Bartsch authored
Resolves: #97280 Releases: main, 11.5 Change-Id: Id6b2b5bf9a200d7c0ccc6c23273bb5086d6ee50a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74154 Tested-by:
-
Jan Helke authored
Resolves: #97270 Releases: main, 11.5 Change-Id: If1c899cdfd891cda5af5a502b40ab28c29830f58 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74127 Tested-by:
-
Oliver Hader authored
Native date/time types have a zero-value, which is '0000-00-00 00:00:00' for DATETIME and '00:00:00' for TIME. For DATETIME values this position in time is really special - however, for TIME values '00:00:00' it would refer to midnight, which actually is common use case (and currently not possible in backend forms). Resolves: #97216 Releases: main, 11.5 Change-Id: Id77a3485e86008ff7c39319679120b2a73b0386c Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73999 Tested-by:
-
Christian Kuhn authored
To prepare towards a deployable backend group access rights system, some of the more obscure options are removed to reduce overall complexity. * TYPO3_CONF_VARS['BE']['explicitADmode'] is finally gone: Following a deny list approach is a flawed security system. TYPO3's default setting (explicitADmode=allow) follows the very common "Least Privileged" principle, so editors need to be explicitly given access to a CType, as is done with all other permissions. * The only valid value for TCA config option "authMode" on type="select" fields is now "explicitAllow". The previous "explicitDeny" value is abandoned following the reasoning above. The value "individual" is abandoned since it is a very rarely used setting (not a single match in TER). * With authMode="individual" being gone, the select item array keys on position six that could be set to "EXPL_DENY" and "EXPL_ALLOW" are obsolete. * Field "explicit_allowdeny" in table be_groups is simplified. This was a comma separated list of colon separated: "table:field:value:ALLOW/DENY". The last "ALLOW" or "DENY" is now obsolete. The patch removes the above handling from the core. A TCA migration scans TCA for invalid options and adapts them. An upgrade wizard is in place to clean up the be_groups explicit_allowdeny field of existing rows. Resolves: #97265 Releases: main Change-Id: I545b08fc694e9081ad79e69e7f55f684316e7b0f Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74126 Tested-by:
-
- Mar 31, 2022
-
-
Oliver Bartsch authored
Some followup adjustments to newly introduced (#97013) TCA type "email". - Remove eval "email" check in InputTextElement. - Align TCA migration with the documentation and the functionality in the element, since only "null" "unique" and "uniqueInPid" are supported. Resolves: #97267 Related: #97013 Releases: main Change-Id: Icfc92c72e4dfebacacfd50b1409bffc97c6eb34e Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74123 Tested-by:
-
Christian Kuhn authored
When core functional tests started to heavily rely on CSV based import- and assertion files, we found that editing such .csv files in Microsoft Excel leads to warnings if the number of columns is not identical for each row. Script checkIntegrityCsvFixtures.php has then been established to verify all rows of .csv fixture files have the same amount of fields per file, and has been enabled as CI job to ensure all existing fixture files follow this. Nowadays, this restriction feels archaic: Devs actively working with these CSV files typically edit them in an IDE like PhpStorm directly and don't use Excel for this anymore. The PhpStorm plugin "Rainbox CSV" also helps by coloring these files and other alternatives like libreoffice do not have this 'all rows must have same number of colums' restriction. The patch drops the script, the runTests.sh usage and the CI calls. This has the additional advantage that line breaks for single fields are now possible, which will further improve handling and readability of field values in upcoming patches. Resolves: #97274 Related: #83943 Releases: main, 11.5, 10.4 Change-Id: I2b4c2afc98c8471bccae1afb15e055182b563ee7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74129 Tested-by:
Jan Helke <jh@f7.de> Tested-by:
-
Jan Helke authored
Resolves: #97269 Releases: main, 11.5 Change-Id: Iec86d579af4fa8774f7ba6bd4d6b137ccefe3dd5 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74125 Tested-by:
-
Stefan Bürk authored
With #97232 changes in ext:styleguide has been needed, which has been provided with corresponding pull-request for that extension. Styleguide is updated to incorporate this change. used command: > composer u typo3/cms-styleguide Resolves: #97262 Related: #97232 Related PR: https://github.com/TYPO3/styleguide/pull/312. Releases: main Change-Id: I1944bdbc170ff31aac08cfbe36e2152d179623e7 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74122 Tested-by:
-
Stefan Bürk authored
Luxembourgish is considered the national language of Luxembourg and one of the three used administrative languages, alongside German and French. Also see https://en.wikipedia.org/wiki/Luxembourgish This change adds support for Luxembourgish to be selected as TYPO3 Language and to connect to TYPO3 Localizations (XLF files, Site Configuration) by default. Resolves: #97254 Releases: main Change-Id: I334c1d9c00d941754f23c6a82412702796c94339 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74119 Tested-by:
Chris Müller <typo3@krue.ml> Tested-by:
-
- Mar 30, 2022
-
-
Oliver Bartsch authored
In our process of using dedicated TCA types, the new TCA type "date" is introduced and replaces "renderType=inputDateTime" of TCA type "input". Notable changes to the previous behaviour: - the "format" option, which was already documented but never used in FormEngine, is now mandatory - TCA option "max" is no longer evaluated - The only allowed eval's are "null" and "int" The corresponding FormEngine element class is renamed from InputDateTimeElement to DatetimeElement. This is covered in the ClassAliasMap. Note: The "eval=int" seems to be superfluous since the field value should always be stored as int in case no native type ("dbType") is used. However, this would be breaking and is therefore done in a separate followup patch. This has already been kickstarted in https://review.typo3.org/c/Packages/TYPO3.CMS/+/74027/12. Resolves: #97232 Releases: main Change-Id: I94c6d12759cd7787e6185ab36d2fcd60f5dc15df Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74027 Tested-by:
-
