Skip to content
Snippets Groups Projects
Select Git revision
  • 12.4
  • main default
  • 11.5
  • 13.3
  • l10n_main
  • 13.1
  • 13.0
  • l10n_12.4
  • 10.4
  • 12.1
  • 9.5
  • 11.3
  • master
  • 11.1
  • TYPO3_8-7
  • 10.2
  • 9.3
  • 9.2
  • TYPO3_7-6
  • TYPO3_7-0
  • v13.3.1
  • v12.4.21
  • v11.5.40
  • v13.3.0
  • v12.4.20
  • v12.4.19
  • v12.4.18
  • v11.5.39
  • v12.4.17
  • v13.2.1
  • v13.2.0
  • v12.4.16
  • v11.5.38
  • v13.1.1
  • v12.4.15
  • v11.5.37
  • v13.1.0
  • v12.4.14
  • v12.4.13
  • v12.4.12
40 results
Search by author
  • Any Author
  • Daniel Hürtgen Daniel Hürtgen higidi
  • Jenkins Jenkins jenkins
  • **** **** project_53_bot
3 authors
  1. Jun 20, 2024
  3. Jun 18, 2024
  5. Jun 17, 2024
  7. Jun 11, 2024
  9. Jun 09, 2024
  11. Jun 01, 2024
  13. May 17, 2024
  15. May 14, 2024
  17. May 13, 2024
  19. May 05, 2024
  21. May 03, 2024
  23. Apr 26, 2024
  25. Apr 23, 2024
  27. Apr 09, 2024
  29. Apr 08, 2024
  31. Apr 03, 2024
  33. Apr 02, 2024
  35. Mar 21, 2024
  37. Mar 06, 2024
  39. Feb 28, 2024
  41. Feb 26, 2024
  43. Feb 24, 2024
  45. Feb 13, 2024
  47. Feb 12, 2024
  49. Feb 06, 2024
  51. Feb 03, 2024
  53. Jan 30, 2024
  55. Jan 29, 2024
  57. Jan 27, 2024
    • Stefan Bürk's avatar
      [TASK] Upgrade to `doctrine/dbal:4.0.0-RC2` · 3b563e58
      Stefan Bürk authored 
      Doctrine DBAL has been upgraded to the next
major version using the development version
as a intermediate solution. Recently, the
second release candidate has been released.

This change upgraded to that candidate now.
Adding the release candidate to a project
root composer.json is still needed as a
workaround - or lowering the minimum stability.

Used command(s):

> \
  composer req --no-update --no-install \
    -d typo3/sysext/redirects \
    "doctrine/dbal":"4.0.0-RC2@rc" ; \
  composer req --no-update --no-install \
    -d typo3/sysext/core \
    "doctrine/dbal":"4.0.0-RC2@rc" ; \
  composer req --no-update --no-install \
    -d typo3/sysext/install \
    "doctrine/dbal":"4.0.0-RC2@rc" ; \
  composer req -W \
    "doctrine/dbal":"4.0.0-RC2@rc" ; \
  COMPOSER=composer.dist.json composer req --no-update \
    -d Build/composer \
    "doctrine/dbal":"4.0.0-RC2@rc"

Resolves: #102959
Releated: #102875
Releases: main

Change-Id: Ia4c4c39234c68d6382fd6bebcc359eac6a8ab51e
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82674


Tested-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
Tested-by: default avatarBenni Mack <benni@typo3.org>
Tested-by: default avatarcore-ci <typo3@b13.com>
Reviewed-by: default avatarBenni Mack <benni@typo3.org>
Reviewed-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
      3b563e58
  59. Jan 26, 2024
    • Christian Kuhn's avatar
      [TASK] Move 'extension download' upgrade wizard to EM · 3e6b817a
      Christian Kuhn authored 
      The install tool has just a few dependencies to
ext:extensionmanager. Most notably, it ships the
AbstractDownloadExtensionUpdate upgrade wizard,
which is used when core extracts stuff to dedicated
extensions that are removed from monorepo.

The v12 upgrade wizard for 'fe_login_mode' uses this.

These upgrade wizards are tailored for non-composer-mode
only, just like the extensionmanager, which essentially
does nothing in composer mode.

To loosen the dependency from ext:install to
ext:extensionmanager, the patch moves the abstract, a
model class for this case, plus the fe_login_mode
implementation to ext:extensionmanager.

Class aliases are established, so a casual deprecation
is enough in this case. A few extensions rely on the
class, typically those that try to extend the upgrade
range of core by forward porting wizards older than
two major core versions. Those shoud continue to work
with v13, and will have to adapt the class namespace
of the abstract with v14 latest.

Moving the fe_login_mode wizard around does not make the
wizard show up again in case the wizard has been marked
'done' during v12 upgrade already, since usually the
according DB field does not exist anymore. We don't need
special handling for this case.

Resolves: #102943
Releases: main
Change-Id: Idb5e6c90900ffad7f9c3c383fff58a05c6728aa9
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/82659


Tested-by: default avatarAndreas Kienast <a.fernandez@scripting-base.de>
Tested-by: default avatarcore-ci <typo3@b13.com>
Tested-by: default avatarNikita Hovratov <nikita.h@live.de>
Reviewed-by: default avatarAndreas Kienast <a.fernandez@scripting-base.de>
Reviewed-by: default avatarNikita Hovratov <nikita.h@live.de>
      3e6b817a
  61. Jan 25, 2024
  63. Jan 24, 2024
    • Benjamin Franzke's avatar
      [FEATURE] Make backend URL configurable · a94b7b5f
      Benjamin Franzke authored 
      The TYPO3 Backend URL is made configurable in order to enable optional
protection against application admin interface infrastructure
enumeration (WSTG-CONF-05). Both, frontend and backend requests are
now handled by the PHP script `/index.php` to enable virtual admin
interface URLs.

The default TYPO3 Backend entrypoint path `/typo3` can be changed by
specifying a custom URL path or domain name in
`$GLOBALS['TYPO3_CONF_VARS']['BE']['entryPoint']`.

This change requires web server adaption. A silent migration and
according documentation for custom web server configurations is added.
A deprecation layer (for non-adapted systems) is in place that rewrites
the server environment variables passed to `/typo3/index.php` as if
`/index.php` was used directly. This layer will be removed in TYPO3 v14.

This change does not take assets into account, only routing is adapted.
That means composer mode will use assets provided via _assets as before
and TYPO3 classic mode will serve backend assets from /typo3/* even if
another backend URL is used and configured.

In composer mode there is an additional opt-out for the installation of
the legacy entrypoint for that can be defined in composer.json:

  "extra": {
    "typo3/cms": {
      "install-deprecated-typo3-index-php": false
    }
  }

The application flow is slightly adapted by moving common middlewares
into a separate core middleware chain. This chain is dispatched by a
distinct core HTTP application (which is invoked by index.php).
These middlewares are suitable for proxy determination or generic
access control – basically everything not needed for subrequests.
The core HTTP request handler then decides whether the request is to be
routed to the frontend or backend application. Frontend and backend
appplications are still designed to work independently with a plain
PSR-7 Server Request in order for sub requests from backend to frontend
(or vice versa) to work.

The following diagram outlines the new application workflow including
flow of possible sub requests (not yet used from backend to frontend,
but it shows how they are intended to be invoked):

                         +-------------------+
                         |                   |
                         |  Core HTTP        |
                         |  Application      |
                         |                   |
                         +---------+---------+
                                   |
                                   |
                                   v
                         +---------+---------+
                         |                   |
                         |  Core HTTP        |
                         |  Middlewares      |
                         |                   |
                         +---------+---------+
                                   |
                                   |
                                   v
                         +---------+---------+
                         |                   |
                         |  Core HTTP        |
           +-------------+  Request Handler  +--------------+
           |             |                   |              |
           |             +-------------------+              |
           |                                                |
           v                                                v
  +--------+----------+                           +---------+---------+
  |                   | (Sub Request)             |                   |
  |  Frontend HTTP    +<-------------+            |  Backend HTTP     |
  |  Application      +<-----------+ |            |  Application      |
  |                   |            | |            |                   |
  +---------+---------+            | |            +---------+---------+
            |                      | |                      |
            |                      | |                      |
            v                      | |                      v
  +---------+---------+            | |            +---------+---------+
  |                   |            | |            |                   |
  |  Frontend HTTP    |            | |            |  Backend HTTP     |
  |  Middlewares      |            | |            |  Middlewares      |
  |                   |            | |            |                   |
  +---------+---------+            | |            +---------+---------+
            |                      | |                      |
            |                      | |                      |
            v                      | |                      v
  +---------+---------+            | |            +---------+---------+
  |                   |            | |            |                   |
  |  Frontend HTTP    |            | |            |  Backend HTTP     |
  |  Request Handler  |            | |            |  Request Handler  |
  |                   |            | |            |                   |
  +---------+---------+            | |            +---------+---------+
            |                      | |                      |
            |                      | |                      |
            v                      | |                      v
  +---------+---------+            | |            +---------+---------+
  |                   |            | |            |                   |
  |  TypoScript       |            | |            |  Backend Route    |
  |  Frontend         +------------+ |            |  Dispatcher       |
  |  Controller       |              |            |                   |
  |                   |              |            +---------+---------+
  +-------------------+              |                      |
                                     |                      |
                                     |                      v
                                     |            +---------+---------+
                                     |            |                   |
                                     |            |  Backend          |
                                     +------------+  Controller       |
                                                  |                   |
                                                  +-------------------+

Commands executed:
  # For changed in https://github.com/TYPO3/testing-framework/pull/533
  composer req --dev "typo3/testing-framework":"dev-main"

Resolves: #87889
Releases: main
Change-Id: I3c96d4d7c58f08ed302ee35eb75d28afbf77686a
Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74366


Reviewed-by: default avatarOliver Hader <oliver.hader@typo3.org>
Reviewed-by: default avatarStefan Bürk <stefan@buerk.tech>
Tested-by: default avatarcore-ci <typo3@b13.com>
Tested-by: default avatarStefan Bürk <stefan@buerk.tech>
Tested-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
Reviewed-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
Tested-by: default avatarOliver Hader <oliver.hader@typo3.org>
Reviewed-by: default avatarBenni Mack <benni@typo3.org>
Tested-by: default avatarBenni Mack <benni@typo3.org>
      a94b7b5f