Showing results 1501 to 1525 of 1561

Bug
New Orphaned TYPO3 CMS 10

#90962 Cache and Dependency Injection in Upgrade module

In my schema extension I injected a frontend cache with DI into a class.

The cache is defined in the ext_localconf.php:

    $coreCacheIdentifier = 'tx_' . $extensionKey . '_core';
    if (!is_array($GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier])) {
        $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier] = [];
    }
    if (!isset($GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier]['frontend'])) {
        $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier]['frontend'] = \TYPO3\CMS\Core\Cache\Frontend\PhpFrontend::class;
    }
    if (!isset($GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier]['backend'])) {
        $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier]['backend'] = \TYPO3\CMS\Core\Cache\Backend\SimpleFileBackend::class;
    }
    if (!isset($GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier]['options'])) {
        $GLOBALS['TYPO3_CONF_VARS']['SYS']['caching']['cacheConfigurations'][$coreCacheIdentifier]['options']['defaultLifetime'] = 0;
    }

and listed correctly in the Configuration module.

Definition in Services.yaml:

services:
  cache.tx_schema_core:
    class: TYPO3\CMS\Core\Cache\Frontend\FrontendInterface
    factory: ['@TYPO3\CMS\Core\Cache\CacheManager', 'getCache']
    arguments: ['tx_schema_core']

  Brotkrueml\Schema\Registry\TypeRegistry:
    arguments:
      $cache: '@cache.tx_schema_core'
      $packageManager: '@TYPO3\CMS\Core\Package\PackageManager'

In the TypeRegistry class itself, the the constructor looks like:

public function __construct(FrontendInterface $cache = null, PackageManager $packageManager = null)

The injection works for most cases in frontend and backend. However, executing two routines in the Upgrade module fail:

- Check TCA in ext_tables.php
- Check TCA Migrations

But: When I define the cache in the AdditionalConfiguration.php instead of localconf.php it works. Also when deactivating DI in Services.yaml

The behaviour can be reproduced with the schema extension (commit af18687d from April 5th):
https://github.com/brotkrueml/schema

Author Chris Müller
Created 04/06/20, 16:05
Updated 06/10/20, 10:54
Feature
New Orphaned Site Handling, Site Sets & Routing

#90832 Resolve routePath by _aspects in Plugin RouteEnhancer

With the “type: Extbase” Route Enhancer, it is possible to have various URL paths by mapping an “_arguments” to a “_controller”.

  routes:
      - { routePath: '/list/{page}', _controller: 'News::list', _arguments: {'page': '@widget_0/currentPage'} }
      - { routePath: '/tag/{tag_name}', _controller: 'News::list', _arguments: {'tag_name': 'overwriteDemand/tags'}}

With “type: Plugin” it is not possible to create various routes.
A possible configuration would be to map an aspect to the path:

SomePlugin:
    type: Plugin
    routes:
        - { routePath: "/{producer}", _aspect: { "producer": "producer" } }
        - { routePath: "/{category}", _aspect: { "category": "category" } }
        - { routePath: "/{producer}/{category}", _aspect: { "producer": "producer", "category": "category" } }
    namespace: "tx_ext_pi1"
    aspects:
        producer:
            ...
        category: 
            ...
Author Patrick Crausaz
Created 03/26/20, 05:54
Updated 06/02/20, 15:51
Bug
New Orphaned TYPO3 CMS 10

#91408 Improvements for slug handling of records in global storage

The fix for uniqueInSite handling and the resulting troubles some limitations in flexibiltiy regarding URL generation when records are stored in a global folder.

The issue here is, that one cannot know in which site a record, that is stored anywhere, is eventually rendered and URLs are generated/resolved for.

Therefore we cannot:

1. Know based on which site(s) de-dulpication needst to be performed on
2. Know which total URLs this slug will finally have and thus cannot add a preview for editors

One idea to address that would be to evaluate TSConfig on the record storage, which holds the required information.

We could for example re-use the preview page ID configuration to assume a single site.
But to cover the case that records might be shown on multiple sites, we would need to introduce TSConfig setting
which lets developers add multiple sites in which these records will be rendered.

Additionally, if feasible, it would be nice to also disallow adding a storage page to plugin settings, which is not suitable for the site this plugin is on.

Author Helmut Hummel
Created 05/14/20, 18:19
Updated 05/14/20, 18:19
Bug
New Orphaned Backend User Interface TYPO3 CMS 10

#91331 List module: Mass editing of content shows permission error messages if permissions restricted by languages

System

  • TYPO3 9.5.16

Reproduce

In my example, German is the default language, English is the translation. The BE user should have only write access to records in English and not to records in the default language.

  1. Create page with several content elements and translate it to the target language
  2. Create BE group and user with permissions for only 1 language (not the default language)
  3. As this user, go to list module
  4. Click “Page content”
  5. Use clipboard mode “Normal” and prepare to edit all content.
  6. click “Edit all shown fields of the listed records”

Now “mass editing” of all content elements on the page will be invoked (both languages).

Actual result

For each content element in the original language, there is an error message:

Sorry, you didn't have proper permissions to perform this change.
ERROR: Language was not allowed.

Expected result

It is correct that we cannot edit the records in the original language, but that should not be an error. The error messages are misleading.

Technically, the error messages are correct since all records are edited. But from the point of view of usability, this should by default not happen IMHO. By default, only the records the editor has permissions to should be edited.

In any case, it is currently (afaik) not possible to choose for which language to do the mass-editing. You can either mass-edit all. Or you have to use clipboard mode and tediously select every single record you want to edit.

Author Sybille Peters
Created 05/07/20, 13:06
Updated 05/07/20, 13:06
Task
New Orphaned Security TYPO3 CMS 9

#91283 Integrate HTTP Sec-Fetch header policy

Example headers:

  • HTTP fetch
    • HTTP_SEC_FETCH_DEST: “empty”
    • HTTP_SEC_FETCH_MODE: “cors”
    • HTTP_SEC_FETCH_SITE: “same-origin”
  • IFRAME fetch
    • HTTP_SEC_FETCH_DEST: “iframe”
    • HTTP_SEC_FETCH_MODE: “navigate”
    • HTTP_SEC_FETCH_SITE: “cross-site”

Resources:

——-

Integrate RequestPolicy and FetchPolicy

$requestPolicy = (new RequestPolicy())
  ->withFetchPolicy((new FetchPolicy())
    ->withAllowedAbsence(bool)
    ->withFetchDest(string[])
    ->withFetchSite(string[])
    ->withFetchUser(string[])
    ->withFetchMode(string[])
  );
Author Oliver Hader
Assigned to Oliver Hader
Created 05/03/20, 20:08
Updated 05/03/20, 20:08
Bug
New Orphaned Database API (Doctrine DBAL) TYPO3 CMS 10

#91247 FrontendRestrictionContainer does not take language into account / There is no doctrine-dbal LanguageRestriction

This might be either:

Obviously an implementation of the missing feature would be desirable.

Said documentation page contains the following intro:

> The ctrl section of a tables TCA array specifies optional framework internal handling of soft deletes and language overlays: For instance, if a row in the backend is deleted using the page or list module, many tables are configured to not entirely drop that row from the table, instead a field (often deleted) is set from zero to one for that row. Similar mechanics kick in for start- and endtime as well as language and workspace overlays. See the [‘ctrl’] chapter in the TCA reference for details on this topic.
>
> These mechanics however come with a price tag attached to it: Extension developers dealing with low-level query stuff must take care overlayed or deleted rows are not in the result set of a casual query.
>
> This is where this “automatic restriction” stuff kicks in: The construct is created on top of native doctrine-dbal as TYPO3 CMS specific extension. It automatically adds WHERE expressions that suppress rows which are marked as deleted or exceeded their “active” life cycle. All that is based on the TCA configuration of the affected table.

Almost all of what is described here has been implemented via Query Restrictions. (And the API is really nicely designed and very usable.)
The only TCA feature which is missing in the existing Query Restrictions implementation is Language.

The ideal solution:

  • Language Overlays should be implemented for the query builder. At least, akin to the WorkspaceRestriction, a sys_language_uid restriction based on the translation (& fallback) mode and current frontend page language should be made.

Minimally:

  • The documentation page should be updated, stating clearly that for multi-language sites the Query Builder cannot be used; or better stating which steps exactly a developer must take if she wants to select only records in the current language (and automatically apply language overlays), like one would do via $cObj->getRecords().
Author Leonie Philine
Created 04/30/20, 18:10
Updated 04/30/20, 18:11
Feature
Accepted Orphaned File Abstraction Layer (FAL)

#89156 Allow to (un)zip folder in file list module

A nice feature will be to allow a user to zip or unzip part of the file system directly in the file list module like a real file system.

Thanks

Author Eric Chavaillaz
Created 09/12/19, 10:31
Updated 03/27/20, 12:55
Feature
New Orphaned FormEngine aka TCEforms

#85331 TCA renderMode "selectTree": make the initial state of "hide-unchecked" configurable

It would be nice if one could toggle the initial state of a tree-view wrt. the unchecked visibility (via TCA and/or TSconfig). It seems this is not possible atm (at least it is not documented, but I couldn’t also find anything by looking through the code).

Author S P
Created 06/21/18, 15:21
Updated 03/25/20, 14:09
Feature
New Orphaned Authentication

#77080 Make permanent anonymous fe_sessions working (set cookie with lifetime)

I expect that my fe_typo_user session is permanent and my fe_session_data is available for the time configured in [lifetime] and [sessionDataLifetime]. [sessionDataLifetime] describes: “Integer: positive. If >0, the session data will timeout and be removed after the number of seconds given (86400 seconds represents 24 hours).” which suggests this should be the case.

When you create fe_session_date like:

$GLOBALS['TSFE']->fe_user->setKey('ses', 'uniqueKey', 'test: '.time());
$GLOBALS['TSFE']->fe_user->storeSessionData();

It seems that there is a cookie set named “fe_typo_user” without a expiration date. So if you close your browser completely and return to the website the “fe_typo_user” cookie was destroyed.

This is because:
”\TYPO3\CMS\Frontend\Authentication\FrontendUserAuthentication->isRefreshTimeBasedCookie()” which is called by “AbstractUserAuthentication->setSessionCookie()” depends on $this->user for setting a expiration date on the cookie.

Can you guys please check/fix this one?

A simple workaround for now was to create a custom user (but didn’t check if there were any complications).

$GLOBALS['TSFE']->fe_user->setKey('ses', 'uniqueKey', 'test: '.time());
$GLOBALS['TSFE']->fe_user->user = ['ses_permanent' => TRUE];
$GLOBALS['TSFE']->fe_user->storeSessionData();
Author Arek van Schaijk
Created 07/13/16, 14:34
Updated 03/25/20, 13:56
Feature
Accepted Orphaned AdminPanel

#86549 Allow Backend URL to be specified for Admin Panel

This feature request is related to #86548

Imagine you have a multi-domain install:

  • domain1.example.com
  • domain2.example.com
  • domain3.example.com

You want (for whichever – good – reason) to force (or at least highly suggest) the webmasters to access the Backend through admin.example.com.

In order for Admin Panel to work, the trick is to force the FE/BE cookies like that (typically in AdditionalConfiguration.php):

$GLOBALS['TYPO3_CONF_VARS']['BE']['cookieDomain'] = '.example.com';
$GLOBALS['TYPO3_CONF_VARS']['FE']['cookieDomain'] = '.example.com';

This will effectively allow the Admin Panel to show up whenever you are authenticated into the Backend (on admin.example.com) while browsing, say, domain1.example.com.

So far so good!

However then try to click on the admin panel button to edit the page:

The Backend will open up but using domain1.example.com/typo3 and not admin.example.com/admin (because there is no such configurable setting).

Note: the jump link is generated in typo3/sysext/frontend/Classes/View/AdminPanelView.php around line 654 and generates an absolute link starting with a / (slash), thus effectively reusing the current domain. Trying to hardcode (to test) some scheme + domain at this place won’t work since the security token will not be correct.

Author Xavier Perseguers
Created 10/02/18, 21:48
Updated 03/24/20, 11:26
Epic
Accepted Orphaned Database API (Doctrine DBAL)

#90719 PostgreSQL related issues

Author Christian Eßl
Created 03/10/20, 14:28
Updated 03/11/20, 19:58
Bug
On Hold Orphaned Pagetree TYPO3 CMS 8

#85099 Attempt to delete without permission - error message shows up, but action works

Hi,

I have to notice that issue #30229 still not solved completely.
https://forge.typo3.org/issues/30229

If an editor (non-admin) deletes a page in the page tree (e.g. via context menu), AND that page as at least 1 translation (alternative page language) and a translated element on it (see attachment), then the red flashMessage “1: Attempt to delete record without delete-permissions” (see attachment).
I have checked the “Access” Module: What we have set is a “770” for the pages (see attachment).
It does not matter if the editor has created the page (and translation) or an admin did that.

The reloaded page tree then shows that the page has been deleted anyways. But because of the error message, the editor thinks his action went wrong.

TYPO3 8.7.15

As mentioned in issue #30229 I must reopen this bug with this issue.

Thank you for taking care and regards
Ralf – merzilla

Author Ralf Merz
Created 05/28/18, 16:39
Updated 03/07/20, 17:15
Feature
New Orphaned Backend User Interface

#90659 Default not displayed for "Installation-Wide Options" + make switching to default easier

Default not displayed

The default is not displayed for all options. In some cases, the default is written in the text, e.g. for [SYS][exceptionalErrors] “ Default is 4096 = E_ALL & …”.

The default is available in the DefaultConfiguration.php, so maybe this is easily possible to do to automatically display the default.

Also, because of #90658 the displayed current value does not always reflect the saved state.

Often, the default value is just empty string. But for values with a selection (e.g. cookieSecure, cookieSameSite), how do you know which is the default and how do you switch to the default if you don’t know?

Some ideas:

  • display the default value in a different style
  • or display the default, only if the current version is different from default, along with current value, e.g.
[BE][cookieDomain] = mydomain (default: '')

How do you switch to the default?

  • if you want to change a specific setting to the default, you often can if there is a text field by emptying the text field. But, this is not immediately intuitive.
  • Having a button “Set to default” or “Set all values to default” might be helpful
Author Sybille Peters
Created 03/06/20, 12:20
Updated 03/06/20, 12:22
Feature
New Orphaned Form Framework

#90615 Support embedding images in HTML-emails

It is already possible to add attachments to emails. But there is no (at least not obvious?) way to embed images in HTML-emails.

Author Stefan Neufeind
Created 03/02/20, 13:37
Updated 03/02/20, 14:13
Feature
New Orphaned File Abstraction Layer (FAL)

#90545 Add videofile_ext, audiofile_ext and applicationfile_ext

I’ve seen there is already https://forge.typo3.org/issues/90305… Perhaps the following might be another improvement:

Currently there is no variable for plain “audio”, “video” or “application” file extensions. So getFalFieldTcaConfig()’s 3rd parameter needs to get passed hardcoded when dealing only with those certain file types. This is not upgrade-safe.

By introducing an additional “videofile_ext”, “audiofile_ext” and “applicationfile_ext” variable, backend definitions could be done straight with frontend behaviour (fluid media rendering). The abstract file class already contains all 5 types…

\TYPO3\CMS\Core\Resource\File::FILETYPE_TEXT
\TYPO3\CMS\Core\Resource\File::FILETYPE_IMAGE
\TYPO3\CMS\Core\Resource\File::FILETYPE_AUDIO
\TYPO3\CMS\Core\Resource\File::FILETYPE_VIDEO
\TYPO3\CMS\Core\Resource\File::FILETYPE_APPLICATION

…and perhaps in near future, FSC’s integrated media rendering will be extended with the missing types related to this :)

Author Jan Kornblum
Created 02/27/20, 03:03
Updated 02/27/20, 07:39
Feature
New Orphaned Site Handling, Site Sets & Routing

#90130 Introduce option for syncing fields with slug in TCA type "slug"

I propose a new option for the “generatorOptions” config in a TCA slug type to automatically sync changes made in one of the configured fields with the slug. (defaulting to false)

'type' => 'slug',
    'config' => [
        'generatorOptions' => [
            'fields' => ['title'],
            'sync' => true,
            'replacements' => [
                '/' => ''
            ],
        ]
        'fallbackCharacter' => '-',
        'prependSlash' => true,
        'eval' => 'uniqueInPid'
    ]

So if “sync” is set to true, changing the “title” field in a backend form would automatically trigger a “recreate” for the connected slug, to keep the changes in sync.

Author Christian Eßl
Created 01/16/20, 12:33
Updated 02/19/20, 19:08
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#90405 Slugs are not maintained reasonable when copying pages/pagetrees

If you copy a page (or smaller portion of the pagetree) from one page to another, the resulting slugs are not really maintained in reasonable way.

Example:

- Main X
— Submain X
—- Subsub X
- Main Y
— Copy of Submain X
—- Copy of Subsub X -> resulting slug: main-x/submain-x/subsub-x-1

This behaviour is irritating and not SEO friendly.
ATM one could only resolve by cleaning all slugs via DB and regenerating them with the update-wizard.
Non-core solutions are e.g. EXT:sluggi

Author Clemens Riccabona
Created 02/17/20, 11:58
Updated 02/17/20, 13:26
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 10

#90170 Datahandler localize translates inline records with non-translatable parent record

As an example we have here:
  • a custom content element “Slider” (tt_content)
  • This “Slider” have 1:n inline records of type “Slider-Item” (tx_theme_domain_model_slideritem)
  • Those “Slider-Items” again have 1:n inline records of type “File Reference” (sys_file_reference)

How these look in the TCA:

// Configuration/TCA/Overrides/tt_content.php 
'tx_theme_slider' => [
            'exclude' => 0,
            'label'   => $themeBeLanguageFilePrefix.'tt_content.tx_theme_slider',
            'config'  => [
                'type'          => 'inline',
                'foreign_table' => 'tx_theme_slider_item',
                'foreign_field' => 'tt_content',
                'appearance'    => [
                    'useSortable'                     => true,
                    'showSynchronizationLink'         => true,
                    'showAllLocalizationLink'         => true,
                    'showPossibleLocalizationRecords' => true,
                    'showRemovedLocalizationRecords'  => false,
                    'expandSingle'                    => true,
                    'enabledControls'                 => [
                        'localize' => true,
                    ],
                ],
                'behaviour' => [
                    'mode' => 'select',
                ],
                'maxitems' => 20,
            ],
        ],
// Configuration/TCA/tx_theme_slider_item.php 
'media' => [
            'label'  => $ll.'tx_theme_slider_item.media',
            'config' => TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig(
                'media',
                [
                    'maxitems' => 999,
                    'minitems' => 0,
                ],
                $GLOBALS['TYPO3_CONF_VARS']['GFX']['imagefile_ext']
            ),
        ],
Now the setup:
  • Site config with languages “default” and “german”
  • An editor with edit permissions only for “german”
  • The editor has edit permissions configured for tt_content and sys_file_reference, but NOT for tx_theme_domain_model_slideritem
  • Now we create a content element “Slider”, add some “Slider Items” as inline relations, those slider items again get some media file references as inline relations.
  • Now log in as the editor and translate the slider element to “german”.
Expected result:
  • Content element is translated
  • no slider items translations are created (because the editor has no permissions for them)
  • no file references are created. (because those are connected to the tx_theme_domain_model_slideritem record)
Actual result:
  • The content element is translated.
  • no slider items translations are created (correct)
  • File references are created (wrong)

This translation made by the editor now leaves us with orphan translated sys_file_references, that have no tx_theme_domain_model_slideritem, they are connected to. Those will now instead be shown in the default translation of the slideritem. (leaving us with duplicated file references)
It looks like the DataHandler ignores this case: If a record is not translatable, its 1:n children of other tables should NOT be translated as well.

Author Christian Eßl
Created 01/22/20, 12:27
Updated 01/22/20, 12:28
Bug
Accepted Orphaned Extbase TYPO3 CMS 9

#88636 Controller action does not accept ObjectStorage<Model> parameter

When I use parameter annotation for controller action like this:

    /**
     * @param ObjectStorage<Model> $param
     */
    public function someAction(ObjectStorage $param = null)
    {
        //...
    }

In ObjectStorageConverter target type is ObjectStorag and <model></model> is stripped off so converter is not able to handle converting.
Looks like it’s stripped off in TYPO3\CMS\Extbase\Mvc\Controller::initializeActionMethodArguments by reflection service

$methodParameters = $this->reflectionService
                ->getClassSchema(static::class)
                ->getMethod($this->actionMethodName)['params'] ?? [];

See slack thread about this [[https://typo3.slack.com/archives/C0CRS7RFH/p1561101916230200]]

PHP: 7.2
Typo3: 9.5.7

Author ondro no-lastname-given
Assigned to Alexander Schnitzler
Created 06/27/19, 09:28
Updated 01/15/20, 19:24
Bug
Accepted Orphaned Extbase TYPO3 CMS 8

#89671 Allow for Collation in extbase repository queries

We are experiencing issues with sorting database results.
We use utf8_unicode_ci as collation in all our databases and string columns.

utf8_unicode_ci do not support the danish characters Æ,Ø,Å.
The character Å as sorted as A – giving us wrong sortings.

For example:
SELECT header FROM `tt_content` ORDER BY header ASC
A is the first letter in danish alphabet
Å is the last letter in danish alphabet
B
C

SELECT header FROM `tt_content` ORDER BY header COLLATE utf8_danish_ci ASC
A is the first letter in danish alphabet
B
C
Å is the last letter in danish alphabet

The easy fix is of course to change the database collation to utf8_danish_ci and get the sortings correct.

But we have quite a few multilanguagal sites using the same db and tables. So it would sort correctly in one language
but not in others and we would very much like to control the sorting from the typo3 side.

The problem: You can´t use COLLATE in Extbase repository queries for sort order using the query object.

So in a extbase repository you can do:

$orderings[‘title’] = QueryInterface::ORDER_DESCENDING;

But this will not work:
$orderings[‘title’] = ‘COLLATE utf8_danish_ci ‘.QueryInterface::ORDER_ASCENDING;

$query->setOrderings(
$orderings
);

https://api.typo3.org/TYPO3_8-7/_typo3_db_query_parser_8php_source.html#l00261
protected function parseOrderings(array $orderings, Qom\SourceInterface $source) {
foreach ($orderings as $propertyName => $order) {
if ($order !== QueryInterface::ORDER_ASCENDING && $order !== QueryInterface::ORDER_DESCENDING) {
throw new UnsupportedOrderException(‘Unsupported order encountered.’, 1242816074);
}
….

What is the reason for this check in the parseOrderings function ?

Regards
Henrik

Author Henrik Jensen
Created 11/13/19, 13:31
Updated 01/14/20, 10:10
Feature
New Orphaned DataHandler aka TCEmain

#89375 TCA settings for cache invalidation and to run Handler for related records

I like to have new TCA setting(s) in select and group fields for

1) Automatic cache invalidation of related tables or
2) Running Datahandler Hooks (Trigger re-indexing of relations, etc.)

This should be realized in core to make extension development easier.

Maybe 2) is enough

'tags' => [
    'label' => 'select_single_12 foreign_table selicon_field',
    'config' => [
        'type' => 'select',
        'renderType' => 'selectSingle',
        'foreign_table' => 'xy_tags',
        'runHandlers' => 1                          <-- Run Handlers for "modified relations" 
        'flushCache' => 1                            <-- Flush cache for "modified relations"
   ],
],

Modified relations can be received from \TYPO3\CMS\Core\DataHandling\DataHandler::$mmHistoryRecords

What do you think about it?

Author Christoph Lehmann
Created 10/08/19, 15:34
Updated 10/08/19, 15:35
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 9

#88929 TCAM:N relation -> leave record with unsaved changes redirects to list instead to create wizard

Hey,

changing items on a TCA m:n table relation and then trying to add create new items from a specfic type (the “+” button) will show the modal “you are leaving the page with unsaved changes”. If you click “save and close” you expect to go to the wizard which will enable you to create a new item. you will get redirect to the list view instead.

I’ve shot a video which I think can describe this better

Possibly related to https://forge.typo3.org/issues/88875, however I have not yet tried the fix.

- Pascal

Author Pascal Querner
Created 08/07/19, 15:34
Updated 10/01/19, 20:36
Feature
New Orphaned FormEngine aka TCEforms

#88448 Allow 'placeholder' and 'mode' => 'useOrOverridePlaceholder' in all TCA column types

Placeholder and override functionality like this

'placeholder' => '__row|my_field',
'mode' => 'useOrOverridePlaceholder',

just works in fields with type “input” and “text”. This should be possible also with selects and so on.

Author Anonymous
Created 05/28/19, 08:45
Updated 10/01/19, 20:25
Feature
New Orphaned Image Cropping

#86310 Fallback logic for image viewhelpers

To simplify the management of crop variants a fallback logic for image viewhelpers could be implemented.

Let’s suppose we have 4 variants (bootstrap_package case): default, medium, small, extrasmall.

If the editor crops only the ‘default’ variant there’s no way to make this crop to be used in every case (breakpoints). In this case the FE will crop the image in large resolutions (‘default’ variant) but not in smaller resolutions (medium, small, extrasmall).

So the editor is forced to crop and maintain all the 4 variants if (s)he wants that the default crop is valid for every breakpoint.

This is inconvenient.

There should be an option to set the fallback like:
’cropVariantsFallback’ => ‘extrasmall,small,medium,default’
so when TYPO3 renders the ‘extrasmall’ variant, it checks if there’s a crop, if not it checks ‘small’, if not ‘medium’ and finally, if also ‘medium’ is not cropped, it crops as ‘default’ is cropped. If also ‘default’ is not cropped then it renders the image without crop.

Or simply there could be a switch like:
’cropVariantsFallback’ => true
and TYPO3 checks the crop variants sorted by declaration order.

Author Christian Toffolo
Created 09/19/18, 11:30
Updated 10/01/19, 19:15
Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 9

#89141 Filelist renaming a folder does not update related fields from TCA configs with new name

Renaming a folder in the FAL list (Filelist) does not update related fields from TCA config with the new folder name. Old folder names are retained and lead to exceptions in the output in the frontend.

There are two possibilities to define folder links with the TCA config.

'config' => [
                'type' => 'input',
                'renderType' => 'inputLink',
                'size' => 50,
                'max' => 1024,
                'eval' => 'trim',
                'fieldControl' => [
                    'linkPopup' => [
                        'options' => [
                            'blindLinkFields' => 'class,target,title',
                            'blindLinkOptions' => 'mail,url,page,file'
                        ],
                    ],
                ],
                'softref' => 'typolink'
            ]
 'config' => [
                'type' => 'group',
                'internal_type' => 'folder',
                'size' => 1,
                'maxItems' => 1,
                'softref' => 'typolink'
            ]

*Expected behavior:*
If a folder in the FAL filelist is renamed, moved or deleted, all related TCA config fields getting involved in the changes.

Author Joerg Boesche
Created 09/11/19, 08:38
Updated 09/11/19, 08:38

Showing results 1501 to 1525 of 1561