Showing results 501 to 525 of 1561

Bug
New Orphaned Database API (Doctrine DBAL) TYPO3 CMS 10

#91178 Applying needed DB change fails in BE using PostgreSQL

On Typo3 9.5.15 using PostgreSQL.

Using “Analyse Database Structure” from the Admin Tools I get the following needed change listed

ALTER TABLE "sys_file_processedfile" ALTER "configuration" TYPE BYTEA 
Current value: configuration TEXT DEFAULT NULL

When applying the change the following error is shown

Database update failed
Error: SQLSTATE[42804]: Datatype mismatch: 7 FEHLER:  Spalte »configuration« kann nicht automatisch in Typ bytea umgewandelt werden
HINT:  Sie müssen möglicherweise »USING configuration::bytea« angeben.

I followed the documented migration from a non-composer installation to composer based installation. After the migration was done, checking the DB structure I encountered this error.

PS: I hope this is the right place to report exceptions found by normal users, if not please redirect me.

Author Tobias Diekershoff
Assigned to Stefan Bürk
Created 04/23/20, 12:09
Updated 07/31/24, 08:44
Bug
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#90436 Some weird behaviour with autogenerated site config

*Preset:*
We already have an existing page root “Root A”.

*Step 1*
Now create a new Page root “Root B”.
TYPO3 will now automatically generate new site config in the format “autogenerated-96-26657d5ff9”.
The page has the checkbox “is_siteroot” NOT checked.

*Step 2*
Move the page “Root B” somewhere inside “Root A” to make it a part of its page tree.

If you now visit the Site config module, the autogenerated site config will be now marked as unassigned.
But if you open the page in the pages module, it will still have its site config for “autogenerated-96-26657d5ff9” assigned, which can lead to many bugs.

Examples:

- My site config for “Root A” allows for translations, but I can’t translate the page “Root B”, as the autogenerated site config has no other languages than “Default”.
- If I open the page with the “view” button, the url will look something like “https://typo3.ddev.site/autogenerated-96/en/root-b”

*My conclusions:*
- Autogenerated site configs should only be created, if you create a page set with “is_siteroot” to true.
- If I delete a root page, its autogenerated (!) site config should be deleted as well.
- It’s weird, that the Site config module shows the site config as “unassigned”, but it is actually loaded in several places, as can be seen from the behaviour. My understanding was, that a page would need to have “is_siteroot” set, but that is apparently not the case?

Author Christian Eßl
Created 02/19/20, 18:01
Updated 07/19/24, 07:08
Bug
New Orphaned Extbase TYPO3 CMS 11

#104419 TCA setting "allowLanguageSynchronization" for pages records not working when using extbase model

I’ve defined an extbase model based on table “pages” in file Configuration/Extbase/Persistence/Classes.php:

return [
    \MyVendor\MyExt\Domain\Model\Teaser::class => [
        'tableName' => 'pages'
    ]
];

When I now request a translated page record…

$this->teaserRepository->findOneByUid(123)

…resulting object contains image from default language:

   media => protectedTYPO3\CMS\Extbase\Domain\Model\FileReference prototypepersistent entity (uid=350, pid=264)
      uidLocal => protected 15 (integer)
      originalResource => protected NULL
      uid => protected 350 (integer)
      _localizedUid => protected 350 (integer)
      _languageUid => protected 0 (integer)
      _versionedUid => protected 350 (integer)
      pid => protected 264 (integer)

But “media” has setting “allowLanguageSynchronization=true”, so I’ve expected the image from my translated page record here.

This is working for simple TCA fields like “type=input” and I’ve expected it’s working for images, too.

I’ve uploaded an extension where you can test the behaviour.

Author Sven Burkert
Created 07/18/24, 09:52
Updated 07/18/24, 09:52
Bug
Under Review Orphaned FormEngine aka TCEforms TYPO3 CMS 9

#82730 Opening record in backend painfully slow with foreign table and large main table

Opening a record in the backend can become painfully slow under the following circumstances:

The main table (10.000 records) has got a 1:n relation to a foreign table (3 records). When trying to open the record of the main table in the TYPO3 backend, the following SQL statement is executed that often that it takes an exceptionally long amount of time to actually open the record.

SELECT * FROM `tx_myext_domain_model_foreigntable` WHERE (`uid` = ?) AND (`tx_myext_domain_model_foreigntable`.`deleted` = 0)

TCA of main table:

'attribute' => [
    'exclude' => true,
    'label' => 'attribute',
    'config' => [
        'type' => 'select',
        'renderType' => 'selectSingle',
        'foreign_table' => 'tx_myext_domain_model_foreigntable',
    ],
],
Author Stefan Franke
Created 10/11/17, 11:30
Updated 07/12/24, 17:43
Bug
New Orphaned Localization TYPO3 CMS 9

#90790 List view - button to localize content already localized with free mode (leads to error)

This issue is present on TYPO3 8.7, 9.5 and 10.4.0-dev (latest master) and even on 7.6

Prerequisites

Multilanguage TYPO3 with at least 2 languages (e.g. Ita(default), Eng (ID=1)

Steps to reproduce

1) Create a page in 2 languages
2) Create a content element in default language and translate it using free mode

3) Switch to List view

h3, Resutls:

1) the “Localize To” button is still there (!), albeit the localization is already present

Additonal information

Clicking on it leads to an error page with the message:

 "1: Localization failed: there already are localizations (XXX) for language 1 of the "tt_content" record YYY!

Notes:
a) on TYPO3 8 and 9 the page reloads with the error message on top, but no content is created
b) on TYPO3 10.4.0-dev (latest master) an empty page with infinite spinning appears and no content is created
c) on TYPO3 7 the issue is the same but in this case a duplicate element is created

Author Riccardo De Contardi
Created 03/19/20, 21:50
Updated 07/07/24, 18:29
Bug
Accepted Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 12

#102595 Not possible to override richtextConfiguration via TSconfig if in a flexform

Normally, overriding settings in Flexform via TSconfig is possibe, for example like this:

# TCEFORM.[tableName].[fieldName].[dataStructureKey].[flexSheet].[flexFieldName with escaped dots].[propertyName]
TCEFORM.tt_content.pi_flexform.sfregister_create.sDEF.settings\.fields\.selected.addItems.ZZZ = ZZZ

see https://docs.typo3.org/m/typo3/reference-tsconfig/main/en-us/PageTsconfig/TceForm.html

But this does not seem to work with the richtextConfiguration if in a Flexform which would then be overridden with RTE, for example like this:

RTE.config.tx_news_domain_model_news.bodytext.preset = otherpreset

For a Flexform field, it should look for example like this:

RTE.config.tt_content.pi_flexform.powermail_pi1.thx.settings\.flexform\.thx\.body.preset = otherpreset

but this does not work.

Author Sybille Peters
Created 12/04/23, 05:11
Updated 06/26/24, 03:47
Feature
Accepted Orphaned Code Cleanup

#103072 Manage translation DB fields

Currently the TCA of TYPO3 knows these ctrl options to enable and manage translation behavior for tables:

- languageField (sys_language_uid by convention)
- transOrigPointerField (l10n_parent by convention, l18n_parent in tt_content)
- translationSource(l10n_source by convention)
- transOrigDiffSourceField (l10n_diffsource by convention, l18n_diffsource in tt_content)

Each of these have 2 purposes:

1. Enable translations or a related feature
2. Tell TYPO3 which DB field to use in queries

This by itself is a problem but the main question is whether the names of these DB fields need to be configurable at all.

There are recently a lot of consolidations and simplifications in TCA. The same could be applied here:

- Turn these options from string to bool, thus only enable/disable the feature. TYPO3 would then use fixed DB field names and thus fully manage these.
- Consolidate/merge these options with better and clearer names, e.g. 'enableTranslations' => true, 'trackTranslationDifferences' => true or similar.

Author Mathias Brodala
Created 02/07/24, 10:59
Updated 06/19/24, 21:01
Bug
Under Review Orphaned Caching TYPO3 CMS 11

#100360 Cache is not invalidated for referenced content via "Insert Records" / Shortcut CE

Hi everyone,

we recently stumpled upon a very annoying issue, that got not noticed since some time (years, ever?!)
The page cache is not invalidated, if there are shortcut content elements and the referenced element got changes.

*Steps to reproduce:*
- Insert a common content element on “page 1“
- Insert a shortcut CE on “page 2” and select the recently added content elment from step 1 as reference
- open new Browser or Incognito Tab
- navigate to “page 1” and “page 2“
- (have look to database and verify, that both pages got cached)
- edit the original CE on Page 1
- reload “page 2” frontend in incognito Tab
- see, that nothing changed
- open “page 1” frontend in incognito Tab – on this page everything is fine, caches got invalidated

This is reproducable on v11 and v12.

This issue gets even more complicated, when one of the extensions Container, Gridelements or Flux are in place.
In this cases child records need to be observed for changes as well. Likly the parent elements get referenced.

Kind regards
Henrik

Author Henrik Ziegenhain
Created 03/30/23, 13:35
Updated 05/17/24, 22:07
Task
Under Review Orphaned Code Cleanup TYPO3 CMS 10

#95722 Why does TYPO3 have a slug-helper?

Hello Community,

this is just to have a general understanding of a pattern on TYPO3 code, which I do not really understand.

Since TYPO3 9 we have inhouse pretty-urls. For this, as usual these days, we have fortunately slug fields on the entities. Thank you for all this.

TYPO3 is a very mature system and it is comprehensible that we have some legacy codes here and there that look weird from today’s perspective.

Now looking at the slug-helper I kind of get lost, why these kind of code-styles are still introduced on TYPO3. The slug-helper cannot be that old and at the same time TYPO3 is now enforcing dependency injection with non-public services. Therefore accessing containers and GeneralUtility::makeInstance is advised not to be done.

Well with a Helper like this it will be quite hard to obey these conventions:

$slugHelper = GeneralUtility::makeInstance(
    SlugHelper::class,
    $tableName,
    $slugFieldName,
    $fieldConfig
);

$slugHelper->generate($hereSomeArray, int $pid);
...

This way constructor injection is very hard up to not possible imho. Also it is not very intuitive to use. Why do we introduce a slug-helper in this pattern?

Imo the right way to do this would be for instance something like this:

$slugService = new SlugService();
$slugService->getGenerator($table, $fieldName)->generateByUid(int $uid)
// or
$slugService->generate($table, $fieldname, $uid)
// or 
$slugService->generate(SlugGenerateConfigurationObject)
// or
...

This is just one of many possible patterns, nevertheless this way we could

- use enforced constructor injection
- dismiss usage of general utitlity
- write tests easily by simple injection instead of registering instances on containers, …
- understand usage simply by auto-complete

I have that feeling, that there should be some code patterns which are enforced on TYPO3 Core Code. I have this feeling, that in 5 years there will be a strong dependency on this slug-helper and there will be soon a lot of work to deprecate them.

Nevertheless I don’t see exactly what kind of recommended common pattern the current implementation is following.

Please correct me with literature if I am wrong and this pattern has some advantages.

Thank you for all your great work.

Kind regards
Rozbeh Chiryai Sharahi

Author Rozbeh Chiryai Sharahi
Created 10/21/21, 13:59
Updated 04/17/24, 22:39
Bug
New Orphaned Backend User Interface TYPO3 CMS 12

#103585 History of content element does not show image deletions

Steps to reproduce

  • Create a content element with an image
  • Delete the image from the content element
  • Inspect the history of this content element

=> no mention of deleted image

Expected behaviour

The history of the CE should show that an update has occurred, which removed some image or media.

Current workaroud for a restore

Use the history of the containing page, which will list the deletion of the `sys_file_reference` record.

Author Markus Klein
Created 04/10/24, 08:39
Updated 04/10/24, 08:39
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 11

#102509 Changes in FileReferences are not copied to other languages with l10n_mode=exclude

Changes to a FileReference are not copied to the other languages after a page is saved for the first time.

e.g.:

'someImage' => [
  'label' => 'LLL:EXT:myExt/Resources/Private/Language/locallang_tca.xlf:pages.someImage',
  'l10n_mode' => 'exclude',
  'config' => \TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig('someImage')
]

Steps to reproduce:

  • Add the image to the page and save it.
  • Create the translation and save.
  • Make changes to the original FileReference and save.
  • Load the FileReference e.g. with \TYPO3\CMS\Frontend\Resource\FileCollector::getFileReferences
  • Please note that the changes are only made for the first object language and are not transferred to the translated FileReferences.

expected behaviour:
All changes to a FileReference are copied to the other existing languages when a FileReference is changed and the l10n_mode is excluded (e.g. crop, alt, etc).

Author Florian Müller
Created 11/24/23, 12:44
Updated 04/02/24, 14:30
Bug
New Orphaned Localization TYPO3 CMS 12

#103446 Overridden starttime/endtime in non-default language not taken into account

In a page the starttime of the default language is set to some time in the future. The “Translation behaviour” of another language of the same page is set to “Custom value” and is empty:

I expect to see the page of the alternative language page in frontend, but a 404 error is displayed instead.

Same for the endtime (which lies in the past) for the default language.

Problem recognized on TYPO3 v12.4.13.

Author Chris Müller
Created 03/21/24, 08:30
Updated 03/21/24, 08:30
Feature
New Orphaned Backend User Interface

#93530 Synchronize date/time fields

In the context of creating some “event”, you often have to deal with some kind of start and end dates (and time).

So your edit form looks like:

Now click the start field to choose a date in 2 months (today is 17.02.2021):

Now move with the date/time picker and choose the date in 2 months.

OK, you now want to define the end date/time 4 hours later than the start… you click the end date and you get the exact same picker, defaulting to today!

I could imagine two UX enhancements (to be enabled in TCA if it makes sense for a use case):

  • Since the end date is empty, clicking/focusing it should default to the start date I just picked instead of “today”
  • More generally, maybe I’d like to get a “synchronize” button next to the end date field.

The button could actually even be totally be omitted as clearing the field would leave us in the context of the end date being undefined and taking the start date as context when we click/focus it again.

Author Xavier Perseguers
Created 02/17/21, 10:28
Updated 03/06/24, 11:02
Bug
Needs Feedback Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#93368 Domain redirects to records not working anymore

Given domain redirects to records when a domain for such a redirect is requested a 404 error is triggered instead of a redirect.

Criteria to trigger this behavior:

  1. The base of all sites must be a full URL like http://example.org/, not simply / (slash).
  2. The incoming domain must not be the base of any site.
  3. The redirect must point to a record URN like t3://record?identifier=<identifier>&uid=<uid>. (There’s an automatic fallback in case of t3://page URNs.)

The incoming domain does not match the base of any site which is why a NullSite is used instead while matching redirects. Due to this TypoScriptFrontendController::getPageAndRootline() (called from RedirectService::bootFrontendController()) triggers an immediate 404 response. This prevents the record URN to be resolved to a valid URL.

As a workaround one can override RedirectService::getTargetUrl() and fall back to any valid site.

Author Mathias Brodala
Created 01/26/21, 11:47
Updated 02/14/24, 11:37
Feature
Author Stefan Bürk
Assigned to Stefan Bürk
Created 02/03/23, 09:14
Updated 11/29/23, 08:48
Feature
New Orphaned Backend User Interface

#102382 Jump to page in tree

I often have the use case that I want to navigate to a page where I only have the slug from the frontend and want to edit the page and siblings of that page. I search the page in the right top corner by the slug and then would like to open the page tree to exactly that page the same way like PhpStorm does it with this icon:

Basically all the parent pages of the currently opened page should be expanded.

Author Simon Schaufelberger
Created 11/16/23, 12:02
Updated 11/29/23, 08:46
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 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
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
Feature
Accepted Orphaned Backend API

#91018 Automatically convert Links with "external" URLs to same site to t3-links (page,file, etc.) in RTE transformation / link wizard / command?

I think it is a common phenomenon, that editors copy URLs out of the site and use it for the links. This may be especially true for large sites where it is tedious to click through the page tree in the link wizard.

The downside is:

  • these links will break if the URL changes. Even if there are redirects, it is not necessary to redirect in this case and it does have an unnecessary performance and load impact.
  • these URLs are more permanent. The page id will not change, the URL may change.
  • will not work for translated pages, e.g. when the content is translated you have to change the links. If these were page links they would automatically already point to the translated page

There is already an extension which does these conversions but it currently does not work for RTE: https://github.com/georgringer/uri2link/

Also, I am wondering, why do this at a later point? Why not do it when the link is created:

  • e.g. in the Link wizard. Either automatically convert the external URL link to page link in the link wizard or via a button. Make this configurable if this should always be done, be done in control of the editor or not at all.
  • or, on RTE -> DB transformation

The conversion should work for RTE field and non-RTE fields.

In any case it would be good to additionally have a wizard or command line tool which does the conversion for old content.

Author Sybille Peters
Created 04/14/20, 10:10
Updated 07/28/23, 04:49
Bug
New Orphaned Workspaces TYPO3 CMS 12

#42109 Shortcuts do not observe in which workspace they were set

Shortcuts do not observe in which workspace they were set.
I try to set a Shotcut wich must only lead to a target in LIVE Workspace.
If i use it in a custom Workspace i get to the Shortcut Target but in the wrong Custum workspace

Maybe its a Solution to give the user within the shortcut edit form an option to set the target to one or all workspace. (such as absolut or ralative path for shortcut)

Author Michael Schramm
Created 10/18/12, 06:59
Updated 07/04/23, 17:02
Feature
Under Review Orphaned Site Handling, Site Sets & Routing

#99995 Add hideTranslation to RecordLinkHandler configuration

Hello,

links to translated records like “news” in RTE fields of translated records (f.e. Content Element) are not working.

To prevent that problem a new option should be added to LinkHandler configuration. Maybe “hideTranslation” as known of the ElementBrowserRecordList.

In nearly every Extbase Extension and maybe all other plugin based Extensions an editor has to link to the record in default language.

Stefan

Author Stefan Froemken
Assigned to Stefan Froemken
Created 02/20/23, 13:50
Updated 04/05/23, 09:54
Feature
New Orphaned felogin

#99904 Process for E-Mail Recovery if an E-Mails is used in more than one fe_user

if an e-mail is used more than one fe_user only the first matching record is fetched:

https://github.com/TYPO3-CMS/felogin/blob/main/Classes/Domain/Repository/FrontendUserRepository.php#L134

and in the recovery mail:

https://github.com/TYPO3-CMS/felogin/blob/main/Classes/Controller/PasswordRecoveryController.php#L62

Only one link is set.

If a mail is used more than ones, the recovery mail shooed have a List with all users matching this mail and a recovery link for each user

Author Timo Poppinga
Created 02/09/23, 14:14
Updated 04/05/23, 09:54
Task
Under Review Orphaned Logging TYPO3 CMS 11

#100074 Make the ErrorHandler log the request url

Like with the ExceptionHandler, as a developer, I would like the ErrorHandler to log the requested url in order to debug easily.

Author Rémy DANIEL
Assigned to Rémy DANIEL
Created 03/03/23, 16:24
Updated 03/03/23, 16:53

Showing results 501 to 525 of 1561