- Sep 11, 2024
-
-
Oliver Bartsch authored
Resolves: #104891 Releases: main, 12.4 Change-Id: I7431cd142a1b92e7ca14dcfe1b5720f9a627be04 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/86002 Reviewed-by:
Guido Schmechel <guido.schmechel@brandung.de> Tested-by:
core-ci <typo3@b13.com> Reviewed-by:
Jochen Roth <rothjochen@gmail.com> Tested-by:
Nikita Hovratov <nikita.h@live.de> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Andreas Kienast <a.fernandez@scripting-base.de> Tested-by:
-
- Jul 06, 2024
-
-
Christian Kuhn authored
This patch adds a layer to the "load and create final TCA" process. When "base" TCA files in 'Configuration/TCA' define 'ctrl' capabilities like 'languageField=sys_language_uid', these fields need according 'columns' definitions. The core now adds default definitions of such columns if they do not exist after loading 'Configuration/TCA' files, and before loading 'Configuration/TCA/Overrides' files. Developers no longer need to define such columns and can rely on core adding them, if a capability is enabled in 'ctrl'. There are two advantages: First, it adds a level of control for these columns away from extensions to the core, which is good for future development in this area. Secondly, extension developers no longer need to take care of nasty configuration details of these columns and can remove lots of boilerplace TCA definitions that had to be maintained manually before. The patch shows this: About 6000 lines of TCA definitions can be removed. These columm...
-
- Jun 13, 2024
-
-
Christian Kuhn authored
Tables with TCA columns set to type="input" do not need an ext_tables.sql entry anymore. The core now creates this field automatically. This is one of many patches in this area: The v13 goal is to obsolete ext_tables.sql in most cases by creating default "business" fields of TCA tables automatically. The patch adds the main magic in class DefaultTcaSchema and removes own ext_tables.sql definitions having type=input. Resolves: #102279 Related: #101553 Releases: main Change-Id: Ia371638bb10d0521cec01542e3a5fc7a364609f1 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/83183 Reviewed-by:
Stefan Bürk <stefan@buerk.tech> Tested-by:
Benni Mack <benni@typo3.org> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
-
- Dec 19, 2023
-
-
Anja Leichsenring authored
Tables with TCA columns set to type="select" do not need an ext_tables.sql entry anymore. The core now creates this field automatically. This is one of many patches in this area: The v13 goal is to obsolete ext_tables.sql in most cases by creating default "business" fields of TCA tables automatically. The patch adds the main magic in class DefaultTcaSchema and removes own ext_tables.sql definitions having type=select. Resolves: #102279 Related: #101553 Releases: main Change-Id: I600d0be1b2452b93d46c6b0d8317460607988fee Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/81604 Reviewed-by:
Garvin Hicking <gh@faktor-e.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by: Anja Leichsenring <aleichsenrin...
-
- Nov 20, 2023
-
-
Garvin Hicking authored
This patch tries to address the issue of several core DB fields being set to 'integer signed' (1901 to 2038), specifically: * `be_users.lastlogin` * `fe_users.lastlogin` * `pages.lastUpdated` * `pages.newUntil` * `sys_redirect.lasthiton` * `index_config.timer_next_indexing` * `tx_extensionmanager_domain_model_extension.last_updated` * `sys_workspace.publish_time` These fields currently have a cut-off for 2038. Those are now changed to 'bigint unsigned' and can survive until 2106. Additionally, these fields: * `sys_file_metadata.content_creation_date` * `tt_content.date` did not allow any dates before 1901, however certain systems might want to use FAL metadata of i.e. 1799 (historical paintings), or content elements of historic sites. Resolves: #99937 Related: #101553 Releases: main Change-Id: I56e747aba166dc4eaf5b5b603d9b161bb56b5f85 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/80668 Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
-
- Apr 04, 2023
-
-
Oliver Bartsch authored
To centralize workflows, reaction and webhook records should only be managed in their dedicated backend module. Resolves: #100434 Releases: main Change-Id: Iae76c6d559b30127677af601af303e85bc0e5bf8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/78442 Tested-by:
-
- Mar 24, 2023
-
-
Frank Naegler authored
A webhook is an automated message sent from one application to another via HTTP. Most modern web applications have the ability to communicate either via outgoing or incoming webhooks. This way of communication allows application users to integrate multiple systems without writing code (so-called no-code/low-code integrations). TYPO3 provides the incoming webhooks part via the system extension "reactions". This feature now allows configuring outgoing webhooks in the TYPO3 backend - completing the round trip. A new backend module is added called "Webhooks" where any administrative user can create a webhook. At its' core a webhook consists of a trigger (when something should happen) and a target URL (what should happen). Every time the webhook is triggered, an HTTP request is sent to the target URL. With this feature, the request can be either a POST or a GET request. POST requests commonly contain data, and GET requests can trigger actions in third-party systems. The...
-
