Showing results 101 to 125 of 1561

Bug
Under Review Orphaned DataHandler aka TCEmain TYPO3 CMS 9

#92604 Translation of child elements connected to a page record currently broken

This bug had been reported with CMS 8 already but was rejected because it was reported in conjunction with pages_language_overlay, but actually the same problem still exists.

The localize method of the DataHandler does not call the same copy action for pages as it does for any other table, that’s why any record connected via an inline field will not be translated properly.

        if ($table !== 'pages') {
            // Get the uid of record after which this localized record should be inserted
            $previousUid = $this->getPreviousLocalizedRecordUid($table, $uid, $row['pid'], $language);
            // Execute the copy:
            $newId = $this->copyRecord($table, $uid, -$previousUid, true, $overrideValues, '', $language);
            $autoVersionNewId = $this->getAutoVersionId($table, $newId);
            if ($autoVersionNewId !== null) {
                $this->triggerRemapAction($table, $newId, [$this, 'placeholderShadowing'], [$table, $autoVersionNewId], true);
            }
        } else {
            // Create new page which needs to contain the same pid as the original page
            $overrideValues['pid'] = $row['pid'];
            // Take over the hidden state of the original language state, this is done due to legacy reasons where-as
            // pages_language_overlay was set to "hidden -> default=0" but pages hidden -> default 1"
            if (!empty($GLOBALS['TCA'][$table]['ctrl']['enablecolumns']['disabled'])) {
                $hiddenFieldName = $GLOBALS['TCA'][$table]['ctrl']['enablecolumns']['disabled'];
                $overrideValues[$hiddenFieldName] = $row[$hiddenFieldName] ?? $GLOBALS['TCA'][$table]['columns'][$hiddenFieldName]['config']['default'];
            }
            $temporaryId = StringUtility::getUniqueId('NEW');
            $copyTCE = $this->getLocalTCE();
            $copyTCE->start([$table => [$temporaryId => $overrideValues]], [], $this->BE_USER);
            $copyTCE->process_datamap();
            // Getting the new UID as if it had been copied:
            $theNewSQLID = $copyTCE->substNEWwithIDs[$temporaryId];
            if ($theNewSQLID) {
                $this->copyMappingArray[$table][$uid] = $theNewSQLID;
                $newId = $theNewSQLID;
            }

Currently this has been kind of hidden by giving i.e. the media field of the pages table an additional behaviour “allowLanguageSynchronization = true”.

But this obviously just replaces the automatic creation of translated children with a manual process of adding new references.
This again contradicts the principles of the “connected mode”, since the child records of translated pages will not get a proper translation parent this way.

Disabling that “allowLanguageSynchronization” behaviour will not create the original core behaviour as it is known from i.e. the tt_content media field, but will just create an empty field value.

Trying the same with the L10nmgr, which actually correctly exports the sys_file_reference will create an additional reference to the default language page record instead of creating a new one in the target language during the import.

Author Jo Hasenau
Created 10/19/20, 20:29
Updated 02/20/24, 13:21
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 11

#103054 Incorrect link generation for shortcut page containing mountpoint subpages

Setting a page type to “shortcut” with “shortcut_mode = 1” (first subpage) and the first subpage type is type “mountpoint” with “mount_pid_ol = 1” (show mounted page) and the mounted page is within a foreign site (domain), the link (menu processor, typolink) generated for the shortcut itself incorrectly points to the mountpoint target page within the foreign site. Instead when setting “shortcut_mode = 0” and explicitly assign the mountpoint page, links are correctly generated.

- site1.domain.tld
—- Shortcut (shortcut_mode = 1) —-> wrongly resolves to “https://site2.domain.tld/Page
——— Mountpoint (mount_pid_ol = 1, mount_pid = 123)

- site2.domain.tld
—- Page (uid: 123)

Author Jan Kornblum
Created 02/05/24, 16:52
Updated 02/05/24, 16:52
Bug
New Orphaned Workspaces TYPO3 CMS 11

#102889 IRRE elements with maxitems / minitems invalid in workspaces

Problem

If I have a content element with minitems or maxitems set, the validation does not work in a workspace.

Reproduction

1. Adapt any content element with an included IRRE element to have maxitems = 1
2. Switch to LIVE workspace
3. Create this element, add one IRRE element and save it
4. Switch to non-LIVE workspace
5. Edit this element and change the element (remove the existing one and add another)
6. Save the element
7. Now the content element has two IRRE elements (the old one and the new one), which is correct because it’s not published yet. BUT the FormEngineValidation gives me an error

Solution

Validate the IRRE elements only for the elements which are in the same workspace as you’re in. If there are three IRRE elements (one from LIVE, one from one workspace, one from another) it should be validated separately as “there is one IRRE element and maxitems, which is fine”

Author Thomas Löffler
Created 01/22/24, 11:49
Updated 01/22/24, 11:49
Bug
New Orphaned Link Handling & Redirect Handling TYPO3 CMS 11

#96421 Redirects module picks "some" site when linking to target in overview

The redirects overview page behaves weird. The module is out-of site context (it has no page tree and no page, and single redirect records are not assigned to a page, either).

Scenario:

  • Create a new top level page. This will trigger the ‘CreateSiteConfiguration’ hook, which creates a ‘autogenerated-xy’ entry in site.
  • Delete that site again

-> When debugging typo3/sysext/frontend/Classes/Typolink/PageLinkBuilder.php which has been changed with #96101, forceAbsoluteUrl is true.

This is because the site that is picked in this method is the now “dangling” autogenerated-xy entry that has been created for our new page.

In effect, the link generated for the redirect is broken – The ‘target’ has no information of the target site (?), so some broken link is generated in general for the existing redirect.

This seems to be a general problem that the linked target on the redirects overview page tends to pick a wrong target site, which leads to broken links.

Author Christian Kuhn
Created 12/21/21, 15:54
Updated 11/09/23, 13:14
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 12

#96554 ImageManipulation eval required does not work

The ImageManipulationElement can have eval with required set to enforce a selected aspect ratio.
This does not work anymore (or rather has never worked in any LTS version), probably due to further refactorings in v8 to enable multiple cropping variants.

Author Nikita Hovratov
Created 01/16/22, 17:23
Updated 11/09/23, 11:00
Feature
New Orphaned Backend User Interface

#101695 Use Link Browser to link to a specific language

Hi!

While adding some 301 redirects for a TYPO3-11 Project i noticed, that the only way to add a redirect for a non-default Language is to add the &L={languageId} parameter to the URN manually. In most cases i would not want to link a foreign language content but when adding 301 Redirects this is very common.

I did not test the behaviour in TYPO3 V12, so maybe this is already solved. Unfortunately i don’t have any V12 System running to do a quick test.

Author Philipp Wrann
Created 08/16/23, 09:03
Updated 11/01/23, 21:58
Feature
New Orphaned Backend User Interface

#102296 Get translation from [languages] in page settings and files

When you translate content, then you can choose which is your source language. Thats a cool function.

It would be nice to have a similar function in the page settings (e.g. Title, Subtitle, SEO and so on) and for images (alt, title, description).
My Idea: A option to choose from a language.
„Get content from: [configured languages]“ and then the fields are filled with the content from the choosen language.

Author Mario Wilhelm
Created 10/31/23, 09:17
Updated 10/31/23, 09:17
Bug
New Orphaned felogin TYPO3 CMS 11

#102254 Unexpected redirect after login - priority of related subuser group greater than the parent usergroup of the related subuser group

The FE-login plugin states that the user groups should be used for the redirect after login.
A user is assigned to a user group X that requests a redirect to page A after login.
The user group X is related to a sub-user group Y that requests a redirect to page B after login.
When the user logs in, he or she will be redirected to page B.

Expectation:
When the user logs in, he or she will be redirected to page A, because the definition of the (parent) usergroup X should have a higher priority than the related subuser group Y.

Author Dieter Dr. Porth
Created 10/25/23, 13:37
Updated 10/25/23, 16:29
Bug
New Orphaned Caching TYPO3 CMS 9

#90600 Frontend cache inconsistency with processed images

We discovered a cache inconsistency where processed images can be removed from the filesystem, even though they are still part of a cached page. We have tested this with TYPO3 9 LTS, but it is very likely also an issue with TYPO3 10 LTS.

Steps to reproduce the issue

  1. Create two pages pageA and pageB
  2. Add an images content element to pageA and pageB and choose the same image demo_image.png
  3. Apply image processing to the image (e.g. max width 50px) on both pages
  4. Open both pages in the frontend and note the generated unique hash (e.g. /fileadmin/_processed_/d/2/csm_demo_2cb965e686.png -> 2cb965e686). The hash should be the same on both pages.
  5. Change the column modification_date in sys_file for demo_image.png, this will lead to a new hash for the processed image
  6. Clear the page cache for pageA only
  7. Open pageA in the frontend, note the new unique hash e.g. /fileadmin/_processed_/d/2/csm_demo_bf52a6057a.png -> bf52a6057a)
  8. Note that the previous processed image csm_demo_2cb965e686.png has been removed from the file system
  9. Open pageB (make sure caching is not disabled, e.g. use inkognito mode) and note that the image is missing on the page because it is still referencing csm_demo_2cb965e686.png, which has been deleted.

Proposed fix

Add page cache tags for all processed images. Whenever a processed image is removed, clear the page cache of all pages including that image using the cache tags.

Additional info

At the moment the deletion is done in TYPO3\CMS\Core\Resource\ProcessedFile in a function called needsReprocessing. Probably processed images should not be deleted in a seemingly innocent method called needsReprocessing. See https://github.com/TYPO3/TYPO3.CMS/blob/9bb994f492e75efcfe139c3d6a64ef42dbef9bd1/typo3/sysext/core/Classes/Resource/ProcessedFile.php#L513-L515

Author Markus Mächler
Created 02/29/20, 12:40
Updated 10/09/23, 15:45
Feature
New Orphaned File Abstraction Layer (FAL)

#85495 Virtual file bundles in FAL

FAL should support virtual file bundles.
E.g. for videos, responsive images.
Automatically by same file name and manually via new wizard.

This makes it possible to use the file bundle in Text+Media and own extensions.

Example “.video”: mp4 format, webm format, ogg format and poster
Example “.image”: small, medium, large

Problem with the image could be the crop wizard.
Possible solutions:
  • no crop wizard for virtual .image
  • Crop wizards in filelist because multiple file bundles could refer to the same files

This would fix #71831, #76367

Author Jan Kiesewetter
Created 07/06/18, 12:33
Updated 09/20/23, 19:48
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 11

#101708 Fields not be kept in sync with their l10n_parent value if the field is excluded for the user

When updating a record all fields of the default_language should be taken into account when synchronizing the translations.

**Example:**
Create a page, chose a backend_layout and a different backend_layout_next_level. You would do this to configure the default behaviour and make the creation of new content for the editor as easy as possible. Now the editor wants to translate all content and translates the parent page. Because he does not have the exclude-field “backend_layout_next_level” enabled the field will not be kept in synced state with the l10n_parent/l10n_source value.

In my opinion this behaviour is not correct. You could fix the situation only by allowing the editor to edit the backend_layout_next_level. But that way the editor might break things, which is the reason you may have decided to NOT enable the field.

As i see it data consistency is too important to accept this situation. My recommendation is to take ALL fields into account when syncing records with their translation source.

The update record method in pseudo code:

updateRow(type, data[uid], data);
uid = getOriginalContentUidForRecord(type, data[uid])
allContent = getAllLanguageVersionsOfRecord(type, uid)
for languageVersion of allContent
  if languageVersion[uid] === data[uid] continue
  merged = mergeLanguageVersionWithTranslationSources(languageVersion, allContent);
  updateRow(type, languageVersion[uid], merged)
Author Philipp Wrann
Created 08/18/23, 09:20
Updated 08/18/23, 09:20
Story
New Orphaned Localization TYPO3 CMS 13

#101561 DataHandler related translation issues

Author Jo Hasenau
Created 08/03/23, 19:56
Updated 08/03/23, 20:07
Feature
New Orphaned Backend User Interface

#101542 Allow move or copy of record without using clipboard 1,2 or 3

Since TYPO3 11 it is possible to mark multiple records to edit them all. If the checkboxes are used the clipboard button appears, but is only selectable if clipboard 1, 2 or 3 is used. This is very confusing for editors and needs extra explanation. Bad usability. Please allow that also for normal clipboard mode. The button is already there, so part of the work is already done.

Author Bernhard Eckl
Created 08/03/23, 09:48
Updated 08/03/23, 09:48
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 11

#94244 PageTypeSuffix Enhancer buggy

If I use PageTypeSuffix enhancer the type parameter in an url is not always respected even if it is defined. This is why ext media_upload does not work again. I I remove the PageTypeSuffix enhancer the type parameter works without problems.

Example:

Works: https://www.oth-aw.de/studieren-und-leben/campusleben/marktplatz/biete-suche/mediaupload.html

Doesn’t work: https://www.oth-aw.de/studieren-und-leben/campusleben/marktplatz/biete-suche/?type=1386871773

On the root page it works:
https://www.oth-aw.de/?type=1386871773

Config:

PageTypeSuffix:
type: PageType
default: /
index: ‘‘
map:
/: 0
…
mediaupload.html: 1386871773
mediadelete.html: 1386871774

If it is solved I would remove the urls in this issue.

Author Bernhard Eckl
Created 05/31/21, 13:49
Updated 08/02/23, 19:06
Feature
New Orphaned Site Handling, Site Sets & Routing

#93162 Allow Redirects to translated pages

The sysext redirects allows for redirects to the default language, but if you need to make a redirect to a translated version of a page there is no nice solution for that.
Instead you have to go to the list module, find the correct page and copy the uid of the translated page to manually edit the Typolink in the redirect, or use an external link to the page. Both of which are not really good solutions.

I would like to be able to select the translated page in the linkbrowser like in the list module. IMHO it would be nice to have the translated pages shown in the link browser above the content elements.
That way you could create a redirect to a translated page aswell, without leaving the redirect module in the backend.

It might be not enough though to just display the translated pages above the content elements, since than it would not be possible to create a redirect to an anchor link on a translated page. So let’s have a discussion about how to impelement this :)

Author Anonymous
Created 12/22/20, 23:19
Updated 08/02/23, 13:05
Task
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#91703 Add configuration guard for ambiguous literals in route paths

routePath: '/{value__value}/{other__}'
_arguments:
  value__value: 'value/value'
  other__: 'other__'

Given URL parameters would look like &value[value]=a&other__=b.
Literal __ using as delimiter in VariableProcessor, see https://github.com/TYPO3/TYPO3.CMS/blob/9.5/typo3/sysext/core/Classes/Routing/Enhancer/VariableProcessor.php#L24

  • add test-cases for those scenarios
  • adjust implementation, add guards based on findings
Author Oliver Hader
Assigned to Oliver Hader
Created 06/23/20, 23:57
Updated 08/02/23, 13:05
Task
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#91702 Evaluate possibility for optional route parts

The following would lead to URL parameters like &value=abc&optional=

routerPath: '{value}/{optional}'
defaults:
  optional: ''

The desired behavior would be to not expose the URL parameter optional at all, thus only having &value=abc.

routerPath: '{value}/{optional}'
defaults:
  optional: null

This example is untested – in case it works already, cool.

Author Oliver Hader
Assigned to Oliver Hader
Created 06/23/20, 23:53
Updated 08/02/23, 13:05
Bug
Needs Feedback Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#96599 Slugs with and without trailing slash are considered different but will confuse URL handling in frontend

If pages exist with the slugs “/foobar” and “/foobar/” the checks for duplicate slugs will not change one to a slug with a trailing number.

When you request the URL domain.ext/foobar one of the pages will be accessed. If that page is disabled the frontend will produce a 404 error.

- Foobar ( slug: /foobar )
- Achive
  - Foobar ( slug: /foobar/ , page hidden)

In this situation domain.ext/foobar produced a 404 error. Changing the slug of the page Foobar in the root to “/foobar-test” made that page accessible. The backend allowed the slug to be renamed back to “/foobar” (the automatic slug generator created that from the page title!).
The workaround was to change the slugs of the page in the archive. This made the active page accessible again.

Author Jigal van Hemert
Assigned to Stefan Bürk
Created 01/20/22, 10:38
Updated 08/02/23, 13:04
Bug
Accepted Orphaned Database API (Doctrine DBAL) TYPO3 CMS 8

#83074 The inSet (FIND_IN_SET) function generates invalid SQL

When building a custom query with getQueryBuilderForTable using the The inSet function in ExpressionBuilder.php, the SQL is wrong because the function returns the pair of fieldName – value in reverse order.

The solution is to change the line 364 of ExpressionBuilder.php to

return sprintf(
  'FIND_IN_SET(%s, %s)',
   $this->connection->quoteIdentifier($fieldName),
   $value
);

or to use plain sql to the query builder: ‘FIND_IN_SET(el.element_type, ‘. $allowedTypes . ‘)’, but with the addition single quotes in the argument string : “‘x,c,z’”

Author Thanos no-lastname-given
Created 11/23/17, 19:36
Updated 07/19/23, 04:07
Bug
New Orphaned Performance TYPO3 CMS 9

#88134 Lots a database queries to sys_refindex cause slow page saving

I’m maintaining a news website with intensive use of categories, which are assigned to pages. The amount of categories is not much, but some categories are assigned to a lot of pages. Some categories are assigned to over 10.000 pages.

When saving a page, the saving time can be up to 30 seconds, in which the editor has to wait until he/she can continue work.

This is due to the following:

The category references are stored in the table sys_refindex by the class ReferenceIndex. When adding or removing a reference from a page to a category, the DataHandler calls the ReferenceIndex to update the references for this certain category.

In the ReferenceIndex the following happens:
  • Fetches all current references with the right table name and uid and puts the hash in the array $currentRelationHashes.
  • Recalculates all references to the category with the uid and gives it a sorting integer according to the loading order the page has been found. This loading order defines the sorting integer for all these recalculated references. Since one is inserted somewhere, be it in the beginning, middle or end, all existing references after the new one get a loading order + 1. A hash is calculated with the loading order included.
  • A comparison is made between the hashes in $currentRelationHashes and the recalculated references

Since a lot of recalculated references have got another sorting integer, hashes don’t match anymore. Non existing hashes from the recalculated references are inserted in the database, hashes in $currentRelationHashes but not in the recalculated ones are deleted.

In our case it sometimes happens a new page-category reference is added somewhere at the beginning and 10.000 relations after that get a new sorting integer, which will cause 10.000 references deleted and 10.001 (including new reference) are inserted in the database.

Related to this issue is that the deleted references are put in an ->in() statement with 10.000 hashes. At one point the amount of characters put in the ->in() statement will exceed the max_allowed_packet value, causing errors.

This happens both in v8 and v9

Author Patrick Broens
Created 04/10/19, 22:03
Updated 07/03/23, 16:02
Task
New Orphaned Backend User Interface TYPO3 CMS 12

#99956 Backend user delete information

The backend usergroup delete modal does not schon relations of records being delete.
It would be nice to let the user about attached users/usergroups of the record to be deleted.

See this comment for details:
https://review.typo3.org/c/Packages/TYPO3.CMS/+/77772/comments/5fc5fc0d_bc44be8e

Could be related to this (abandoned) patch: https://review.typo3.org/c/Packages/TYPO3.CMS/+/75235

Author Jochen Roth
Created 02/15/23, 10:23
Updated 06/05/23, 09:23
Feature
Accepted Orphaned DataHandler aka TCEmain

#58611 TCA: Extending "behaviour" for IRRE fields with "disableCopyingChildrenWithParent"

It would be a great feature to extend the “behaviour” for IRRE fields with an option called “disableCopyingChildrenWithParent” (related to “disableMovingChildrenWithParent”). In some cases it might be neccessary to disable to copying of children, for example when having a bidirectional relation “ModelA 1:n> ModelB <n:1>“.</n:1>

$TCA[‘tx_myext_table’][‘columns’][‘field’] = array(
‘config’ => array(
‘type’ => ‘inline’,
‘foreign_table’ => ‘…’,
‘appearance’ => array(
…
),
‘behaviour’ => array(
‘disableMovingChildrenWithParent’ => 1,
*‘disableCopyingChildrenWithParent’ => 1,*
‘localizationMode’ => ‘select’,
‘localizeChildrenAtParentLocalization’ => 1,
)
),
);

Author Jan Kornblum
Assigned to Mathias Brodala
Created 05/07/14, 18:46
Updated 05/24/23, 18:53
Bug
On Hold Orphaned File Abstraction Layer (FAL) TYPO3 CMS 12

#99403 Reference count in the file list could be incorrect

TYPO3\CMS\Filelist::getFileReferenceCount() uses sys_ref_index to find amount of references to the file but this number is not always correct. For example, creating or deleting file references in frontend usually does not update sys_ref_index. This causes not only wrong numbers in the UI but also prohibits file deletion if the file is unused but reference index is not updated.

It would be more practical to count records in sys_file_reference rather than in sys_refindex. Therefore I propose to change the above mentioned method to only count how many entries with uid_local = $file->getUid() in sys_file_reference, not in sys_refindex.

Basically:

    /**
     * Counts how often the given file is referenced. This is done by
     * looking up the file in the "sys_refindex" table, while excluding
     * sys_file_metadata relations as these are no such references.
     */
    protected function getFileReferenceCount2(File $file): int
    {
        $queryBuilder = GeneralUtility::makeInstance(ConnectionPool::class)->getQueryBuilderForTable('sys_refindex');
        return (int)$queryBuilder
            ->count('*')
            ->from('sys_file_reference')
            ->where(
                $queryBuilder->expr()->eq(
                    'uid_local',
                    $queryBuilder->createNamedParameter($file->getUid(), Connection::PARAM_INT)
                )
            )
            ->executeQuery()
            ->fetchOne();
    }
Author Dmitry Dulepov
Created 12/21/22, 09:46
Updated 04/28/23, 18:46
Bug
New Orphaned Authentication TYPO3 CMS 11

#99397 Refresh login does not take MFA into account

Multi-factor authentication is activated.

Then:
- The user is logged-out of the backend in a non-active tab.
- Activating the tab later shows the refresh login modal.
- Enter the password and submit.
- The (empty) password field is displayed again.

Reloading the tab displays then the MFA field. Entering there the MFA part then the login is performed successfully.

Instead: The MFA field should be displayed directly in the modal after entering the password.

Author Chris Müller
Created 12/20/22, 10:50
Updated 03/02/23, 13:01
Bug
New Orphaned Workspaces TYPO3 CMS 11

#99755 Protect uniqueness of pages-slug during workspaces

Given: You edit in workspace draft mode the slug field of two pages in same page tree and level, and enter exactly the same string. Afterward you want to publish both changes into live workspace.

Expected: Instead of the same string for both slug fields is saved into live workspace, one should changed beyond. And redirects should created.

Actual: Pages get same slug-value. No redirects are created.

I read about, that unique fields should not be displayed in workspace mode anyway.
https://docs.typo3.org/c/typo3/cms-workspaces/main/en-us/Administration/Versioning/Index.html#unique-fields

TCA settings pages.columns.slug.config.eval = uniqueInSite

To avoid such conflicts, my question is, should I self configure a display condition for pages, when I load and use workspace, or could it be default value for pages TCA in TYPO3?

$GLOBALS['TCA']['pages']['columns']['slug']['displayCond'] = 'VERSION:IS:false';
Author Joerg Kummer
Created 01/30/23, 16:09
Updated 01/30/23, 16:12

Showing results 101 to 125 of 1561