Showing results 1201 to 1225 of 1561

Task
Accepted Orphaned Backend User Interface TYPO3 CMS 13

#104970 Make tree node label color more flexible

In #103211 the tree node labels were introcuded, which allow to define a hard coded color. On the other hand, since #103043 the page tree supports dark mode.

Both features are nice features, but should be improved. The label color should not be a hard coded color, but respect the context. At least, it should be possible to define two separate colors:

  • color to be used on light background
  • color to be used on dark background

Maybe, we even should think about a even more complex solution which also supports more user preferences like high contrast.

Author Albrecht Köhnlein
Created 09/14/24, 13:34
Updated 10/15/24, 09:46
Bug
Accepted Orphaned Database API (Doctrine DBAL) TYPO3 CMS 13

#104316 DB compare results in error with SQLite in TYPO3 13.2

Hello,

for testing TYPO3 13.2 I have set DB to SQLite. After upgrading from TYPO3 13.1 I get following error in DB compare:

Core: Exception handler (WEB): Uncaught TYPO3 Exception: Doctrine\DBAL\Schema\Index::_addColumn(): Argument #1 ($column) must be of type string, null given, called in /var/www/vhosts/jweiland-hosting.de/httpdocs/typo3retter.de/13.4/vendor/doctrine/dbal/src/Schema/Index.php on line 60 | TypeError thrown in file /var/www/vhosts/jweiland-hosting.de/httpdocs/typo3retter.de/13.4/vendor/doctrine/dbal/src/Schema/Index.php in line 68. Requested URL: https://nix-da.typo3retter.de/typo3/install.php?install%5Bcontroller%5D=maintenance&install%5Bcontext%5D=backend&install%5Baction%5D=databaseAnalyzerAnalyze

Seems that DB compare tries to create a new index:

at Doctrine\DBAL\Schema\Index->__construct()
in /var/www/vhosts/900410.jweiland-hosting.de/httpdocs/typo3retter.de/13.4/vendor/doctrine/dbal/src/Schema/AbstractSchemaManager.php line 733
        }

        $indexes = [];
        foreach ($result as $indexKey => $data) {
            $indexes[$indexKey] = new Index(
                $data['name'],
                $data['columns'],
                $data['unique'],
                $data['primary'],

Stefan

Author Stefan Froemken
Assigned to Stefan Bürk
Created 07/05/24, 17:45
Updated 10/15/24, 09:46
Feature
Under Review Orphaned Extbase

#102677 Introduce configuration file for Extbase plugin registration and configuration

It should also be possible to register an Extbase plugin with just one configuration file.

Author Torben Hansen
Assigned to Torben Hansen
Created 12/15/23, 18:33
Updated 10/15/24, 09:46
Feature
Author Torben Hansen
Created 12/16/23, 11:58
Updated 10/15/24, 09:46
Feature
Accepted Orphaned Form Framework

#101763 FormEditor: Add visibility to finisher

Context

An editor has a finisher with several options. He wants to switch it off for reasons. To do this, the editor must delete the finisher completely. Unfortunately, there is no control of the finisher.

Possible solution

The finishers get the keyword hidden in the YAML with the default value false. The FormEditor is extended with a button and controls this new value. For space reasons, the padding on the left of the finisher can be removed.

Author Guido Schmechel
Created 08/26/23, 14:23
Updated 10/15/24, 09:46
Feature
Under Review Orphaned Backend User Interface

#103758 Allow assigning users directly to the backend group from the group settings

From the perspective of a user managing backend permissions, it would be beneficial to allow the assignment and removal of backend users directly from the backend group.

This approach would enable the relationship to be managed from both sides:
- assigning or removing groups for the user
- assigning or removing users to the group

Author Marcin Sągol
Assigned to Marcin Sągol
Created 04/29/24, 07:13
Updated 10/15/24, 09:46
Task
Under Review Orphaned System/Bootstrap/Configuration TYPO3 CMS 13

#103488 Move EXT:frontend TypoScript to configuration folder

Author Benjamin Franzke
Created 03/26/24, 13:38
Updated 10/15/24, 08:19
Feature
New Orphaned Backend User Interface

#104932 Create permissions set from backend user group UI

With foundation prepared in #104672
We should add ability to create a preset directly from UI to speed up & make easier for users to create permission presets.

Backend user group UI should provide a possibility to create new preset (define name & format if system detects more than one preset provider),
and store via providers in target format (default YAML files provided by TYPO3 core).

Author Tomek W
Created 09/12/24, 09:10
Updated 10/15/24, 08:19
Feature
New Orphaned Backend User Interface

#103608 Allow to preview record form when setting permission to fields

To make the permissions to form fields a bit easier, it would be good to have an option to preview form for a given record type, while setting permissions to particular fields.

The administrator should be able to:
- click the preview button for given record type
- view the rendered record edit form based on currently edited group permissions (including subgroups)

Author Marcin Sągol
Assigned to Marcin Sągol
Created 04/11/24, 12:35
Updated 10/15/24, 08:19
Feature
Author Alexander Schnitzler
Assigned to Alexander Schnitzler
Created 07/21/23, 07:35
Updated 10/15/24, 08:19
Task
New Orphaned felogin TYPO3 CMS 13

#105269 Consider to change TypoScript configuration in ext:felogin

ext:felogin uses a plugin specific TypoScript configuration by default plugin.tx_felogin_login. This makes it impossible to override plugin settings, when the felogin plugin is includes via TypoScript (USER or EXTBASEPLUGIN), since extbase configurationManager always prefers plugin specific configuration and thereby overrides possible configuration defined in USER or EXTBASEPLUGIN.

It should therefore be considered to rename the TypoScript configuration to plugin.tx_felogin in TYPO3 v14 as a breaking change

Author Torben Hansen
Assigned to Torben Hansen
Created 10/11/24, 06:39
Updated 10/14/24, 05:27
Bug
Under Review Orphaned Form Framework TYPO3 CMS 11

#93962 Form variants for EmailToReceiver doesn't work

It is not possible to use different emails for languages.
Variants doesn’t work for EmailToReceiver.

renderingOptions:
  submitButtonLabel: Submit
type: Form
identifier: contact
label: Form
prototypeName: standard
finishers:
  -
    options:
      message: confirm
      contentElementUid: ''
    identifier: Confirmation
  -
    options:
      subject: 'Subject'
      recipients:
        first@domain.tld: ''
      senderAddress: noreply@domain.tld
      senderName: ''
      addHtmlPart: true
      attachUploads: true
      translation:
        language: ''
      useFluidEmail: true
      title: ''
    identifier: EmailToReceiver
variants:
  -
    identifier: variant-1
    condition: 'siteLanguage("twoLetterIsoCode") == "en"'
    finishers:
      -
        identifier: EmailToReceiver
        options:
          recipients:
            second@domain.tld: ''
renderables:
  -
    renderingOptions:
      previousButtonLabel: 'Previous step'
      nextButtonLabel: 'Next step'
    type: Page
    identifier: page-1
    label: ''
    renderables:
      -
        defaultValue: ''
        type: Textarea
        identifier: message
        label: Message
        properties:
          fluidAdditionalAttributes:
            required: required
        validators:
          -
            identifier: NotEmpty
Author asdasdsa maximustermax
Assigned to Mathias Brodala
Created 04/21/21, 12:15
Updated 10/11/24, 08:55
Task
New Orphaned System/Bootstrap/Configuration TYPO3 CMS 13

#104588 overwriting certain $variables in included (require) files causes Problems

This is a followup to this Ticket
https://forge.typo3.org/issues/104509

This Tickets addition (to the prior)
a) the function still allows for Static calls
b) More Files that allow these bugs
——————————
a)
I tested the scopes with this

//  /test.php
<?php

class Test
{
    public function __construct() {
        require __DIR__."/test2.php";

        $require = function ($file) { require $file; };
        $require(__DIR__."/test2.php");

        $require = static function ($file) { require $file; };
        $require(__DIR__."/test2.php");

        self::requireFile(__DIR__."/test2.php");

        requireFile(__DIR__."/test2.php");
    }

    private function objectTest()
    {
        echo 'access to Object-Context is happening'. PHP_EOL;
    }

    protected static function staticTest()
    {
        echo 'access to Static-Context is happening' . PHP_EOL;
    }

    private static function requireFile(string $string)
    {
        require $string;
    }
}

function requireFile($file)
{
    require $file;
}

new Test();

// /test2.php
<?php
self::staticTest();
$this->objectTest();

Results:
require … ;. . . . . . . . . . . . . . . . . . . . Local vars, $this and self:: accessible
$require = function () { … }; . . . . . $this and self:: accessible
$require = static function (); . . . . self:: accessible
self::requireFile() ; . . . . . . . . . . . . .self:: accessible
(global) function require() . . . . . nothing accessible

Thus a new global function require should be used to include these files

function requireFile(string $filepath): mixed
{
    return require $filepath;
}

b)
Files where this is happening:
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Package/AbstractServiceProvider.php
(from the last Ticket:) AbstractServiceProvider
Lines: 74, 93, 105, 131, 155, 172

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/dashboard/Classes/ServiceProvider.php
(from the last Ticket:) Dashboard/…/ServiceProvider
Lines: 141, 161, 180

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/ExpressionLanguage/ProviderConfigurationLoader.php#L58
ProviderConfigurationLoader Line 58 requires Configuration/ExpressionLanguage.php

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/extbase/Classes/Persistence/ClassesConfigurationFactory.php#L48
ClassesConfigurationFactory Line 48 requires Configuration/Extbase/Persistence/Classes.php

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/backend/Classes/CodeEditor/CodeEditor.php#L113
backend/…/CodeEditor Lines 113 and 121 require Configuration/Backend/T3editor/ Modes.php and Addons.php

https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Configuration/Tca/TcaFactory.php#L122
TcaFactory Lines 122 and 156 require the TCA files

ext_tables.php is loaded multiple times.
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/install/Classes/Service/LoadTcaService.php#L68
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Configuration/Extension/ExtTablesFactory.php#L99
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/install/Classes/Controller/UpgradeController.php#L1247 (?)

ext_localconf.php
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/core/Classes/Configuration/Extension/ExtLocalconfFactory.php#L100
https://github.com/TYPO3/typo3/blob/main/typo3/sysext/install/Classes/Controller/UpgradeController.php#L1235

These are just the ones I found. (there might be more)
Christian Kuhn wrote that these should be done in several patches
https://review.typo3.org/c/Packages/TYPO3.CMS/+/85501/comments/3627cbf2_5c83c3a4

thx for your work

Author Jannis Bell
Created 08/10/24, 15:09
Updated 10/07/24, 15:01
Bug
New Orphaned Backend User Interface TYPO3 CMS 13

#104679 Inconsistent behavior of form fields with .has-change class

System settings: Light mode, Windows 10, Chrome / Firefox

  1. brings a new style for .has-change CSS class of form elements. This leads to the following behavior:

+-Scenario 1:+
-When I, as a user, insert a new content element, all input and selection fields are immediately colored blue and the form label is marked with an info icon. When the mouse hovers over the icon, no further information is given as to why the info icon is there or why the field is colored blue. These are also not mandatory fields.

Wish: A note for the user when the mouse hovers over the icon would be desirable. In addition, not all fields should immediately be marked blue per se.

+Scenario 2:+
If I select a field in an existing content element, make a different selection (select field) or enter additional text (input field) and completely undo these changes, the fields are still displayed in blue with an info icon in front of them, without there being any actual change.

Wish: If no content change has been made in the field, then the field should not be marked blue and the label should not be marked with an info icon.

+Scenario 3:+
If I change a switch checkbox from deactivated to activated in an existing content element/data record, then the .has-change class has no visual influence on the field and thus the change to the field is not clear.

In addition, a change to a switch checkbox generally does not lead to an icon on the form label.

+Scenario 4:+
If I make a change in an RTE, then the field is neither colored blue nor is an info icon placed in front of the label. This is probably for technical reasons (CKEditor), but its behavior is in contrast to the now strong visual highlighting of changes in the other form fields.

Author Jasmina Ließmann
Created 08/21/24, 10:51
Updated 10/07/24, 14:24
Task
Accepted Orphaned Backend User Interface TYPO3 CMS 13

#104899 Hint administrators from the extnsion settings to the site settings

The multitude of places where administrators can configure Extensions now has become quite confusing.

If an extension provides default settings via site sets I would hint from the Extension settings in Admin Tools > Settings > Extension settings to the fact that site settings excist and might offer additional settings on a per site basis.

Maybe something like this:

As we are in install tool context here I would probably keep it simple and only check if the extension has at least one site set that contains a `settings.definitions.yaml`

Author Lina Wolf
Created 09/11/24, 09:03
Updated 10/07/24, 12:51
Bug
New Orphaned TypoScript TYPO3 CMS 12

#105136 ConfigurationManager does not resolve TypoScript Object references anymore.

It used to be possible to assign the settings to a plugin as for example described here:

https://www.typo3-snippets.de/snippets/extbase-und-fluid/extbase-plugin-per-typoscript-einbinden/

lib.include = USER
lib.include {
   userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
   vendorName = myVendor
   pluginName = MyPlugin
   extensionName = MyExtension

   settings =< plugin.tx_myExtension.settings
   persistence =< plugin.tx_myExtension.persistence
   view =< plugin.tx_myExtension.view
}

In TYPO3 12.4.20 This leads to a a TypeError:

(1/1) TypeError
TYPO3\CMS\Extbase\Configuration\ConfigurationManager::getConfiguration(): Return value must be of type array, string returned
/var/www/html/vendor/typo3/cms-extbase/Classes/Configuration/ConfigurationManager.php line 141

As the TypoScript Object reference https://docs.typo3.org/m/typo3/reference-coreapi/11.5/en-us/Configuration/TypoScriptSyntax/Syntax/TypoScriptSyntax.html#typoscript-syntax-syntax-object-referencing is not resolved.

In the affected line $configuration[‘settings’] contains a string “=< plugin.tx_myExtension.settings” which was not resolved.

Using the “<” Object copying operator in the same place works and seems to be resolved.

Not sure if this is due to changes in Extbase or in the Typoscript parsing.

Even if a string was passed by error of the integrator I would expect a meaningful Error message, not a type error.

Author Lina Wolf
Created 09/27/24, 05:52
Updated 09/27/24, 05:52
Feature
New Orphaned Site Handling, Site Sets & Routing

#105125 Add option in RedirectLoginErrorHandler to render PID

When a logged in user does not have access permissions to a page, the general 403 error is renderer. It would be nice to have a configurable option to render a custom PID instead.

Author Torben Hansen
Assigned to Torben Hansen
Created 09/26/24, 06:06
Updated 09/26/24, 06:30
Bug
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#103925 Live search pagination has no keyboard actions implemented - and is also not reachable with keyboard navigation

Tested on 13.2.0-dev (but I guess also 12 is affected)

- Open live Search
- search something that gives you a lot of results
- Use the keyboard to navigate the interface (Tab key & arrows keys)

Results

You will see that pretty everything is reachable using tab key and arrows key, except the pagination on the bottom left

Technical background

The navigation links are implemented as customElement(‘typo3-backend-live-search-result-page’)@
This custom element does not have any button or link features.
The current implementation only reacts on click events. Keyboard actions like key-press Enter or Space are not implemented.

Simply making this navigation reachable by keaboard (e.g. tabindex="0") will not make it work.

Author Riccardo De Contardi
Created 05/26/24, 15:57
Updated 09/24/24, 20:35
Task
Under Review Orphaned Backend User Interface TYPO3 CMS 12

#99599 "Page TSconfig" submodule: Change active page in page tree when clicking on a list entry on page zero

On page zero the “Page TSconfig” submodule shows a list of pages that contain values in the field “Page TSconfig” (‘TSconfig’) in their page settings.
Clicking on a list entry will take you to the selected page and show the Page TSconfig of this page, but the page tree remains the same.

Suggestion:
  • Reload the page tree / set the active state to the selected page (= list entry)
Author Jasmina Ließmann
Created 01/18/23, 10:28
Updated 09/19/24, 20:24
Task
Under Review Orphaned Backend JavaScript TYPO3 CMS 13

#104964 Column-selector-button and clipboard-panel reload the whole TYPO3-backend instead of just updating the content-frame

I’d like to refactor backend/column-selector-button and backend/clipboard-panel to implement a proper reload of the typo3-contentIframe instead of reloading the whole TYPO3-backend.

The proper reload can be done by using backend/viewport/content-container functions ContentContainer.setUrl(). This relies on backend/module/router and thereby triggers `NProgress` and gives this nice loading-bar above the typo3-contentIframe.

backend/viewport/content-container relies on backend/module/router and backend/module/iframe.

(I don’t know why ‘@ContentContainer.setUrl()@ does not make use of backend/module/router – but that is a new ticket.)

——

General issue with iframe reloads and anchors

An iframe (and also the main window) does not get reloaded if the new url contains an anchor and the old and new url are otherwise identical.
This must be fixed in and backend/module/iframe and and backend/viewport/content-container

——

Current implementation for ‘full backend reload’ in backend/column-selector-button

https://github.com/TYPO3/typo3/blob/35c9b96336d8644b52ef9045969a47475f559da5/Build/Sources/TypeScript/backend/column-selector-button.ts#L207-L209

// @todo This does not jump to the anchor (#t3-table-some_table) after the reload!!!
this.ownerDocument.location.href = this.modalTarget;
this.ownerDocument.location.reload();

E.g. go into the TYPO3-backend and open the dev-tools JS-console:
Iframes show the same behaviour as the main window.

/* First: login in to backend and load module */
window.top.document.getElementById('typo3-contentIframe').ownerDocument.location.href = '/typo3/module/web/list?id=0&table=be_groups';

/* 1: this does not refresh anything */
window.top.document.getElementById('typo3-contentIframe').ownerDocument.location.href = '/typo3/module/web/list?id=0&table=be_groups#t3-table-be_groups';

/* 2: this does not refresh anything */
window.top.document.getElementById('typo3-contentIframe').ownerDocument.location.href = '/typo3/module/web/list?id=0&table=be_groups#t3-table-be_groups';

/* 3: this does neither refresh anything */
window.top.document.getElementById('typo3-contentIframe').ownerDocument.location.href = '/typo3/module/web/list?id=0&table=be_groups#';

/* 4 this triggers the complete reload - and that's how it is implemented in 'backend/column-selector-button' right now */
window.top.document.getElementById('typo3-contentIframe').ownerDocument.location.href = '/typo3/module/web/list?id=0&table=be_groups#t3-table-be_groups';
window.top.document.getElementById('typo3-contentIframe').ownerDocument.location.reload();

/* 5: No anchor set - this always does a complete reload */
window.top.document.getElementById('typo3-contentIframe').ownerDocument.location.href = '/typo3/module/web/list?id=0&table=be_groups';
Author Ayke Halder
Created 09/13/24, 16:32
Updated 09/19/24, 19:49
Task
Under Review Orphaned Backend JavaScript TYPO3 CMS 13

#104965 General issue with non-working iframe reloads if url contains anchor

An iframe (and also the main window) does not get reloaded if the new url contains an anchor and the old and new url are otherwise identical.
This must be fixed in backend/module/iframe and and backend/viewport/content-container

Author Ayke Halder
Created 09/13/24, 16:36
Updated 09/19/24, 19:46
Bug
New Orphaned TypoScript TYPO3 CMS 12

#105039 Method ContentObjectRenderer::mergeTSRef() generates different TypoScript than shown in the backend

The method \TYPO3\CMS\Frontend\ContentObject\ContentObjectRenderer::mergeTSRef generates TypoScript which is used for Content-Elements.

The TypoScript what is visible within the backend module differs from this generated TypoScript.

The reason is, that the processing of the TypoScript within mergeTSRef() works differently and does not remove settings as expected.

This has an effect in case the fluid viewhelper to render cObjects is used.

To Reproduce

  1. Add an additional DataProcessor to lib.contentElement

    lib.contentElement {
    dataProcessing {
    42 = Acme\Example\DataProcessing\ExampleDataProcessor
    }
    }
  2. Create a new content element and reset the dataProcessing

    tt_content.tx_acme_ce =< lib.contentElement
    tt_content.tx_acme_ce {
    templateName = Example
    dataProcessing >
    dataProcessing {
    84 = Acme\Example\DataProcessing\Example2DataProcessor
    }
    }
  3. Render the cObject using the ViewHelper
    <f:cObject typoscriptObjectPath="tt_content.tx_acme_ce " data="{item}" />

As a result, the DataProcessor on position 42 was not removed.

Generated TypoScript by mergeTSRef():

tt_content.tx_acme_ce {
  templateName = Example
  dataProcessing {
    42 = Acme\Example\DataProcessing\ExampleDataProcessor
    84 = Acme\Example\DataProcessing\Example2DataProcessor
  }
}

Expected behaviour

The expected result is that the calculated TypoScript is identical to the TypoScript shown in the backend.
TypoScript that is removed should not be available.

tt_content.tx_acme_ce {
  templateName = Example
  dataProcessing {
    84 = Acme\Example\DataProcessing\Example2DataProcessor
  }
}

The DataProcessor on position 42 should not be available nor executed on the content element.

Author Lars Tode
Created 09/19/24, 09:56
Updated 09/19/24, 10:40
Task
Needs Feedback Orphaned composer / dependencies / third-party TYPO3 CMS 12

#104994 Set proper branch alias for supported release branches (incl. ELTS)

TYPO3s release branches do not have proper extra.branch-alias settings.

This leads to errors by requiring local TYPO3 mono-repo in own composer project.

All sysext/*/composer.json files must get proper aliases, to be compatible with setup like described in “Steps to reproduce”.

Steps to reproduce:

Clone the TYPO3 mono-repo into TYPO3-Core_Monorepo 12.4 branch into TYPO3-Core_Monorepo directory.

git clone -b 12.4 https://github.com/TYPO3/typo3.git TYPO3_Core_Monorepo

Copy following to root composer.json

{
  "type": "project",
  "repositories": {
    "local-typo3-monorepo": {
      "type": "path",
      "url": "TYPO3-Core_Monorepo/typo3/sysext/*",
      "options": {
        "reference": "none",
        "versions": {
          "typo3/cms-adminpanel": "dev-12.4",
          "typo3/cms-backend": "dev-12.4",
          "typo3/cms-belog": "dev-12.4",
          "typo3/cms-beuser": "dev-12.4",
          "typo3/cms-core": "dev-12.4",
          "typo3/cms-dashboard": "dev-12.4",
          "typo3/cms-extbase": "dev-12.4",
          "typo3/cms-extensionmanager": "dev-12.4",
          "typo3/cms-felogin": "dev-12.4",
          "typo3/cms-filelist": "dev-12.4",
          "typo3/cms-filemetadata": "dev-12.4",
          "typo3/cms-fluid": "dev-12.4",
          "typo3/cms-fluid_styled_content": "dev-12.4",
          "typo3/cms-form": "dev-12.4",
          "typo3/cms-frontend": "dev-12.4",
          "typo3/cms-impexp": "dev-12.4",
          "typo3/cms-indexed_search": "dev-12.4",
          "typo3/cms-info": "dev-12.4",
          "typo3/cms-install": "dev-12.4",
          "typo3/cms-linkvalidator": "dev-12.4",
          "typo3/cms-lowlevel": "dev-12.4",
          "typo3/cms-opendocs": "dev-12.4",
          "typo3/cms-reactions": "dev-12.4",
          "typo3/cms-recycler": "dev-12.4",
          "typo3/cms-redirects": "dev-12.4",
          "typo3/cms-reports": "dev-12.4",
          "typo3/cms-rte_ckeditor": "dev-12.4",
          "typo3/cms-scheduler": "dev-12.4",
          "typo3/cms-seo": "dev-12.4",
          "typo3/cms-setup": "dev-12.4",
          "typo3/cms-styleguide": "dev-12.4",
          "typo3/cms-sys_note": "dev-12.4",
          "typo3/cms-tstemplate": "dev-12.4",
          "typo3/cms-viewpage": "dev-12.4",
          "typo3/cms-webhooks": "dev-12.4",
          "typo3/cms-workspaces": "dev-12.4"
        }
      }
    }
  },
  "config": {
    "allow-plugins": true,
    "platform": {
      "php": "8.1"
    },
    "sort-packages": true,
    "preferred-install": {
      "typo3/cms-core": "source",
      "*": "dist"
    }
  },
  "require": {
    "typo3/cms-about": "12.4.x-dev",
    "typo3/cms-adminpanel": "12.4.x-dev",
    "typo3/cms-backend": "12.4.x-dev",
    "typo3/cms-belog": "12.4.x-dev",
    "typo3/cms-beuser": "12.4.x-dev",
    "typo3/cms-core": "12.4.x-dev",
    "typo3/cms-extbase": "12.4.x-dev",
    "typo3/cms-extensionmanager": "12.4.x-dev",
    "typo3/cms-felogin": "12.4.x-dev",
    "typo3/cms-filelist": "12.4.x-dev",
    "typo3/cms-filemetadata": "12.4.x-dev",
    "typo3/cms-fluid": "12.4.x-dev",
    "typo3/cms-fluid-styled-content": "12.4.x-dev",
    "typo3/cms-form": "12.4.x-dev",
    "typo3/cms-frontend": "12.4.x-dev",
    "typo3/cms-impexp": "12.4.x-dev",
    "typo3/cms-info": "12.4.x-dev",
    "typo3/cms-install": "12.4.x-dev",
    "typo3/cms-lowlevel": "12.4.x-dev",
    "typo3/cms-recordlist": "12.4.x-dev",
    "typo3/cms-redirects": "12.4.x-dev",
    "typo3/cms-reports": "12.4.x-dev",
    "typo3/cms-rte-ckeditor": "12.4.x-dev",
    "typo3/cms-scheduler": "12.4.x-dev",
    "typo3/cms-seo": "12.4.x-dev",
    "typo3/cms-setup": "12.4.x-dev",
    "typo3/cms-sys-note": "12.4.x-dev",
    "typo3/cms-t3editor": "12.4.x-dev",
    "typo3/cms-tstemplate": "12.4.x-dev",
    "typo3/cms-viewpage": "12.4.x-dev"
  },
}

Try to install that project with composer

composer install

You will get ~40 Errors about version mismatch.

Problem 1
    - Root composer.json requires typo3/cms-about 12.4.x-dev (exact version match), found typo3/cms-about[dev-main, v8.7.7, ..., 8.7.x-dev, v9.0.0, ..., 9.5.x-dev, v10.0.0, ..., 10.4.x-dev] but it does not match the constraint.
  Problem 2
    - Root composer.json requires typo3/cms-adminpanel 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-adminpanel[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-adminpanel[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 3
    - Root composer.json requires typo3/cms-backend 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-backend[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-backend[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 4
    - Root composer.json requires typo3/cms-belog 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-belog[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-belog[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 5
    - Root composer.json requires typo3/cms-beuser 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-beuser[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-beuser[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 6
    - Root composer.json requires typo3/cms-core 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-core[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-core[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 7
    - Root composer.json requires typo3/cms-extbase 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-extbase[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-extbase[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 8
    - Root composer.json requires typo3/cms-extensionmanager 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-extensionmanager[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-extensionmanager[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.
  Problem 9
    - Root composer.json requires typo3/cms-felogin 12.4.x-dev (exact version match), it is satisfiable by typo3/cms-felogin[12.4.x-dev] from composer repo (https://repo.packagist.org) but typo3/cms-felogin[dev-12.4] from path repo (TYPO3-Core_Monorepo/typo3/sysext/*) has higher repository priority. The packages from the higher priority repository do not match your constraint and are therefore not installable. That repository is canonical so the lower priority repo's packages are not installable. See https://getcomposer.org/repoprio for details and assistance.

etc. etc. .........

—-

Patch for 12.4 branch:

Just find and replace "dev-main": "12.4.x-dev" by "dev-12.4": "12.4.x-dev"

—-

Purpose/Background

I want to make a TYPO3 core patches, but test them within EXT:solr setup before pushing.

Author Rafael Kähm
Assigned to Stefan Bürk
Created 09/16/24, 19:44
Updated 09/18/24, 13:48
Bug
New Orphaned TYPO3 CMS 12

#104782 Content sliding breaks on hidden pages

I want to display content from parent pages further down the page tree. My page tree is as follows.

The “Page With Slideable Content” has the content I want to inherit in the header column (content_header, colPos = 1). Sliding works on the indicated pages in the page tree, i. e. the direct subpages and the deactivated subpage “sliding works as well”. It, however, does not work on the active subpage “sliding does not work”

So when we have an active page, a deactivated subpage, then an active subpage on the deactivated page, the content sliding breaks. The variables content_header and content_footer are then empty.

This also happens on older TYPO3 version, such as the latest 11 LTS.

Page config:

page = PAGE
page {
    10 = FLUIDTEMPLATE
    10 < lib.defaultPaths
    10 {
        templateName = Default
        variables {
            content_main < styles.content.get
            content_main.select.where = {#colPos}=0

            content_header < styles.content.get
            content_header.select.where = {#colPos}=1
            content_header.slide = -1

            content_footer < styles.content.get
            content_footer.select.where = {#colPos}=2
            content_footer.slide = -1
        }
    }
}

Backend Layout config:

mod.web_layout.BackendLayouts {
    standard {
        title = Standard
        config {
            backend_layout {
                colCount = 1
                rowCount = 3
                rows {
                    1 {
                        columns {
                            1 {
                                name = Header
                                colPos = 1
                            }
                        }
                    }

                    2 {
                        columns {
                            1 {
                                name = Main
                                colPos = 0
                            }
                        }
                    }

                    3 {
                        columns {
                            1 {
                                name = Footer
                                colPos = 2
                            }
                        }
                    }
                }
            }
        }
    }
}
Author Felix Kleber
Created 08/30/24, 09:41
Updated 08/30/24, 09:41
Task
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#93294 Improve automatic slug handling

The automatic slug updater introduced in #89115 has some backdraws that could be improved.

Reduce amount of selected pages

When the slug of a page changes, the automatic slug updater recursively tries to rename the slugs of all subpages.
To determine all subpages of a page, the process uses SlugService::resolveSubPages(). The select query in this function is too broad and selects besides regular pages (doktype = 1) also sys_folders, mount points, etc.

The query does also not respect nested sites, so unwanted changes on slugs in subsites may be processed under certain conditions as shown on the following screenshot.

If the slug of the first page “Level 1” (Site1) changes, also the slug of the page “Level 1” (Subsite) will be renamed which is unintended.

Performance improvement

On large TYPO3 websites with ten thousands of pages the function SlugService::resolveSubPages() may lead to performance/PHP memory limit problems if the slug of a page changes and the page has thousands or even ten thousands of subpages.

Improve documentation

It is not really clear how the automatic slug update process works. It should be mentioned in the documentation, that slugs of subpages only will be changed, if the slug value starts with the exact value of the renamed parent slug.

Author Torben Hansen
Created 01/15/21, 09:14
Updated 08/29/24, 15:24

Showing results 1201 to 1225 of 1561