Showing results 1326 to 1350 of 1561

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
Needs Feedback Orphaned Link Handling & Redirect Handling TYPO3 CMS 12

#102137 Problems due to automatic redirects

When you regenerate the URL segment for a page, a redirect is automatically created. This can cause redirects / a redirect loop. The editor will not notice because no warning is displayed.

## Scenario

A possible scenario (which happens in real life and can be reproduced easily):

  • editor copies page “X” -> new name “X1”
  • generated slug: “/x-1”
  • editor renames page “X1” to “Y”
  • generated slug: “/y”
  • auto-generated redirect: “/x-1” auf “/y”
  • editor renames page “Y” to “Z”
  • generated slug: “/z”
  • auto-generated redirect: “/y” auf “/z”
  • editor creates a new page “Y”
  • generated slug: “/y”

## Result

Page “Y” is not accessible because the redirect from “/y” to “/z”, which was automatically generated earlier, is still active.

## Current solution

Editor has to open the list of redirects and look for the corresponding entry. After that, the editor has to delete the redirect and everything works as expected.

It would be great if there could be checks installed which will warn the editor about this scenario and behaviour.

Author Björn Jacob
Created 10/10/23, 10:16
Updated 10/12/23, 08:38
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
Bug
New Orphaned Caching TYPO3 CMS 11

#102123 Duplicate cache & dependency injection cache corruption in chroot environment

TYPO3’s core cache identifiers are partially based on the directory it is run in, like the dependency injection cache identifier is generated like

// TYPO3\CMS\Core\Package\Cache\PackageDependentCacheIdenifier, line 37
$this->baseIdentifier = (new Typo3Version())->getVersion() . Environment::getProjectPath() . ($packageManager->getCacheIdentifier() ?? '');

The webserver with PHP-FPM runs in the normal root environment, having a full path like /var/www/vhost/…/sites/mysite/…. The scheduler runs in the chroot environment with a path like /sites/mysite/….

This leads to two different cache identifiers for the the DI cache container as well as cached TCA, ext_localconf.php and more. The Problem with the DI cache is that it purges other files, when the cache is written with a new identifier leading to problems with dependency injection.

The behaviour is the same in TYPO3 CMS 11, 12 and current main branch.

Author Thorben Nissen
Created 10/09/23, 08:53
Updated 10/09/23, 08:53
Feature
Accepted Orphaned Image Generation / GIFBUILDER

#101446 Prevent re processing images with "same" processing instructions

Foremost I’m not sure if TYPO3 should change that. Still I try to explain our scenario and a possible solution. I’m fine if TYPO3 decides to reject the issue.

Environment:
TYPO3 11.5.23
PHP 8.1

Our scenario:
We had a small code that called applyProcessingInstructions() of TYPO3\CMS\Extbase\Service\ImageService
The code looked like this:

$cropParam = ($crop)?'c':'';
$processingInstructions = [
    'width' => $imageWidth . $cropParam,
    'crop' => $this->getCropArea($imageObj, $cropVariant),
];
if ($forceRatio > 0) {
    $processingInstructions['height'] = ($crop) ? $imageWidth / $forceRatio . $cropParam : null;
}
$processedImage = $this->imageService->applyProcessingInstructions($imageObj, $processingInstructions);

We than needed to make changes to the code base and ended up with the following code:

$cropParam = ($crop) ? 'c' : '';
$processingInstructions = [
    'width' => $imageWidth . $cropParam,
    'height' => null,
    'crop' => $this->getCropArea($image, $cropVariant),
];
if ($forceRatio > 0 && $crop) {
    $processingInstructions['height'] = ($imageWidth / $forceRatio) . $cropParam;
}

return $this->imageService->applyProcessingInstructions(
    $image,
    $processingInstructions
);

We didn’t expect anything bad from that change. Once deployed our system went down due to heavy system load, caused by many gm (=graphics magick) processed.
We reverted the change and thanks to Hannes with his experience we found the root cause. We modified the $processingInstructions that is used to create a hash in order to find entries from database table sys_file_processedfile. Our modifications lead to a different array (height before, crop and height now always was set). That lead to a different hash leading to not finding processed images, leading to re-processing all images.

My proposal:
Add some streamlining to the incoming processing instructions. E.g. alphabetical sorting, array filter to filter out empty values like `null`. Something in that regard should prevent such issues for systems.
It forces an update wizard in order to update all existing entries with the sanitized and updated hash version in order to prevent re processing all images after system update.

Author Daniel Siepmann
Created 07/26/23, 06:23
Updated 09/21/23, 13:47
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
Feature
New Orphaned Linkvalidator

#101935 Better handling of curl error codes in linkvalidator

Unfortunately, one curl error codes may be used for several different problems, e.g.

1. Certificate does not have matching target host name
2. Missing intermediate certificate – incomplete certificate chain

The text which is displayed by command line curl / or using Guzzle with libcurl does contain a different text in this case, but the error code is still the same (60 for the examples above).

A number of error codes were localized and the internal linkvalidator text is displayed, not the full error message supplied by curl.

Solution

(preliminary ideas)

  • We should find a way to make this configurable, so that the full curl error message will be displayed
  • show both (e.g. show shorter, localized message by default and show full message as detail view

Info

Examples

curl -LI "https://www.rea.ru"
curl: (60) SSL certificate problem: unable to get local issuer certificate
curl -I https://t3coredev13
curl: (60) SSL: no alternative certificate subject name matches target host name 't3coredev13'
Author Sybille Peters
Assigned to Sybille Peters
Created 09/17/23, 14:38
Updated 09/17/23, 15:01
Bug
New Orphaned AdminPanel TYPO3 CMS 11

#101849 AdminPanel preview_simulateDate does not respect date.timezone settings

What have I done?

  • Use AdminPanel simulate time functionality
  • change time
  • click “update settings”

What have I expected?

  • The set time is used to display the data.

What has happened?

  • In the time field, the set time minus 2h is displayed.

Technical preconditions

  • date.timezone Europe/Berlin is set
Author Annett Jähnichen
Created 09/05/23, 12:28
Updated 09/05/23, 12:29
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
Bug
New Orphaned Backend User Interface TYPO3 CMS 6.2

#72974 "Copy default content elements"-Button is shown even if an editor hasn't access to this CType

Currently TYPO3 doesn’t check if an editor has access* for a specific CType before showing the “Copy default content elements”-Button.
It would be nice if the button only shows up if the editor actually can copy the content element.

*I restrict some CTypes to specific user groups with the “Explicitly allow/deny field values:” option.

Author Christoph Bessei
Created 01/27/16, 18:09
Updated 08/16/23, 21:12
Bug
New Orphaned Localization TYPO3 CMS 11

#99554 After I've installed patch lvl 11.5.18, mount points with non translated slugs stoped working and shows 404 in the FE.

My customer has a multi-side-domain-language installation, so he has multiple sites, multiple language and multiple domain in use.

Site config A:
  • domain-A.com/en/, language 0
  • domain-B.com/de/, language 1
    …
  • domain-G.com/cns/, language 6
Site config B:
  • domain-H.com/en/, language 0
  • domain-I.com/cns/, language 6

In the page tree using site config B he uses mount points to pages of the tree using site config A. In versions before 11.5.18 it is working as expected, in version 11.5.18 it starts delivering a 404 for mount points which has a non translated slug in the none default value (translation overlay). Eg. domain-I.com/cns/page315/page430.html is a mount point to a page in the tree using site config A and the slug is not translated. In 11.5.17 and earlier it was working, for 11.5.18 and alter it shows a 404. If I translate the slug eg. domain-I.com/cns/page315-translated/page430-translated.html it starts working again.

I’ve checked the commits and saw a fix for #88715 and #96010 was applied with the commit:

2022-11-08 d2c466b04d [BUGFIX] Prevent resolving translated page with default slug (thanks to Stefan Bürk)

typo3/sysext/core/Classes/Routing/PageRouter.php#202

    if ($this->isRouteReallyValidForLanguage($matchedRoute, $language)) {
        return $this->buildPageArguments($matchedRoute, $result, $request->getQueryParams());
    }

The additional check isRouteReallyValidForLanguage causes the issue for me. After reverting back from 11.5.18 to 11.5.17 it works, upgrading again to 11.5.18 or later delivers 404 status in the FE.

Regards, Jens

Author Jens Zscheile
Created 01/16/23, 14:56
Updated 08/03/23, 21:19
Bug
New Orphaned Localization TYPO3 CMS 11

#100816 Translations for bidirectional relations are not output reliably.

When I create a bidirectional relation using the TCA option ‘MM_opposite_field’, the translation of this and all objects linked to it from the repository seems to be output correctly only randomly.
I tried to debug it with xDebug, but unfortunately didn’t get far.
My observations so far are as follows.
The first record is always output correctly. A findByUid therefore seems to work correctly at first sight, but already the relations in this object are partly not translated.
With findAll the first object works, after that it seems random, but most objects don’t get translated. I played with the ordering, and if I move the 2. object to the first position, it gets translated, and the other element that got translated before don’t get translated anymore.

With xDebug I got as far as typo3/sysext/extbase/Classes/Persistence/Generic/Backend.php line 178. Here everything still seems to fit on the first run, I get a list with all objects translated correctly. From line 179 my xDebug crashes unfortunately very often, in the cases in which I get through there, the method getObjectDataByQuery seems to output first everything correctly. However, the whole thing then starts all over again with a subset of the data. I suspect that here for the relations again the data are fetched. Due to the frequent xDebug crashes at this point, and many other relations such as sys_file, I could not understand this more precisely, but I suspect that when retrieving the relations, the original objects are overwritten again with the default language.

Author Kevin Quiatkowski
Created 05/05/23, 10:07
Updated 08/03/23, 20:31
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 Link Handling & Redirect Handling

#98567 Check for redirects without existing target page

Problem/Description

It’s possible that sys_redirect records are getting conflicting when the configured target (like a page with t3://page… schema) is deleted. At least the symfony command `redirects:checkintegrity` reports them.

ToDo(s)

  • Add a schedulable command to check/cleanup such orphaned sys_redirect records

Acceptance Criteria

  • It’s possible to cleanup redirect records in an automatic way if the target isn’t available anymore within the TYPO3 instance.
Author Josef Glatz
Created 10/10/22, 15:13
Updated 08/02/23, 13:05
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#97263 findPageCandidatesOfMountPoint breaks slugs if mount points to a folder and slugs start with the same string

Example Configuration:

1 Site 1: www.example.com
2 —- Folder: “Example” with Slug: “/example“
3 ———- Page: “Example 1” with Slug: “/example-1”

4 Site 2: subdomain.example.com
5 —- Cross site mount: “Example mount” with slug “/example-mount” mounting folder 2

When a menu of subpages is generated for 5 the resulting url of mounted page 3 will be:
https://subdomain.example.com/example-mount/-1 instead of https://subdomain.example.com/example-mount/example-1

*Reason:*
In method findPageCandidatesOfMountPoint of core/Classes/Routing/PageRouter.php the $commonSlugPrefixOfMountedPage will be removed from $slugOfSubpage even if the mounted page is a folder or spacer.

// Rewrite the slug of the subpage to match the PageRouter matching again
// This is done by first removing the "common" prefix possibly provided by the Mounted Page
// But more importantly adding the $slugOfMountPoint of the MountPoint Page
$slugOfSubpage = $pageCandidate['slug'];
if ($mountedPage['doktype'] === 1 && $commonSlugPrefixOfMountedPage && strpos($slugOfSubpage, $commonSlugPrefixOfMountedPage) === 0) {
    $slugOfSubpage = substr($slugOfSubpage, strlen($commonSlugPrefixOfMountedPage));
}

*Possible solution:*
Check doktype of mounted page before removing $commonSlugPrefixOfMountedPage.

Author Dominik Steinborn
Created 03/31/22, 08:53
Updated 08/02/23, 13:05
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#97914 Slug fields should be initialized or re-evaluated after record creation

Hi,

The SlugHelper incorrectly evaluates the field value on record creation when it depends on dynamic fields like the UID.

Setup example:

        'path_segment' => [
            'label' => $ll . '.path_segment',
            'config' => [
                'type' => 'slug',
                'size' => 50,
                'generatorOptions' => [
                    'fields' => ['title','uid'],
                    'fieldSeparator' => '-',
                    'replacements' => [
                        '/' => '-'
                    ],
                ],
                'fallbackCharacter' => '-',
                'eval' => $configuration->getSlugBehaviour(),
                'default' => ''
            ]
        ],

Current result: test-1

Expected result: test-4742 (value obtained with the recalculate button)

Thanks

Author Cyril Janody
Created 07/12/22, 19:07
Updated 08/02/23, 13:05
Feature
New Orphaned Site Handling, Site Sets & Routing

#93875 Populate site settings depending on language to TypoScript constants

The TypoScript constants can be defined in the page’s config.yaml. It is not possible to set the constants language dependent.

Example:
A page has multiple languages.
ID 0: english
ID 1: german

Default settings:

[...]
settings:
   theme: client

For the language German (ID: 0) the value “client-German” for the constant “theme” should be used.

languages:
  - title: German
    enabled: true
    languageId: '1'
    base: /de/
    typo3Language: de
    locale: de_DE.UTF-8
    iso-639-1: de
    navigationTitle: Deutsch
    hreflang: de-DE
    direction: ''
    flag: de
    settings:
      theme: client-german

Currently a mixture of SiteConfiguration Yaml and TypoScript Condition (siteLanguage == 1 …) has to be created. In order to configure this in one place, the “settings” in the Yaml file should be able to be set depending on the language.

—-
Populate site settings to TS constants was introduced with: #91080

Author Joerg Boesche
Created 04/07/21, 14:59
Updated 08/02/23, 13:05
Bug
Accepted Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#94670 Redirects module: RecordLinkHandler can't resolve storagePid if value is site configuration variable

We found out that the Redirects module can’t handle it if a site configuration variable (so for example storagePid = {$pids.news}) is used for the storagePids in the linkHandler instead of a hardcoded UID (so for example storagePid = 5).

The main problem is that in the context of the redirects module the getPagesTSconfig function of the BackendUtility has PID 0 (because the redirects are on PID 0), therefore no (default) page configuration is found and accordingly the parsing of the TSConfig cannot take place correctly.

The corresponding variable in the RecordLinkHandler ($this->expandPage) falls back to pid 0 (because the redirects are on PID 0, see above), which is adverse for non-admin users because they are not allowed to access the page. The non-admin user cannot use the LinkHandler accordingly.

Author Benjamin Gries Gries
Created 07/30/21, 09:29
Updated 08/02/23, 13:05
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
Feature
Accepted Orphaned Site Handling, Site Sets & Routing

#91672 Inform user if a redirect exists when creating a new page

Given the following real life scenario:

root-page (/)
- parent (/parent)
  - child (/parent/child)

When an editor moves “child” one level up:

root-page (/)
- child (/child)
- parent (/parent)

a redirect /parent/child => /child will be created.

If another editor then creates a page with the exact same title as before and at the same location as before, like so:

root-page (/)
- child (/child)
- parent (/parent)
  - child (/parent/child)

the created page /parent/child will still be redirected to /child.

Expected:
The user should be informed that a redirect for the created slug already exists and if he wants to remove the redirect or adjust the slug. Or something like that.

Author Uwe Trotzek
Created 06/18/20, 15:11
Updated 08/02/23, 13:05

Showing results 1326 to 1350 of 1561