Showing results 1301 to 1325 of 1561

Task
New Orphaned Localization TYPO3 CMS 12

#103525 Sorting of translated content elements after copy&paste and with no page translation

  • Have a page in default language without any translation. Copy&Paste a content element having a translation to that page.
  • Now there is a non-visible translated content element on that page (fine).
  • Create a page translation. You see the translated content element now.
  • Use the “translate” button to translate all content elements from default language.

I expect to see the translated element at the position that it has in the default language.

I see the translated element at the top position (wrong).

Author Christoph Lehmann
Created 04/03/24, 08:20
Updated 04/03/24, 08:22
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
Feature
Needs Feedback Orphaned Backend User Interface

#93344 Translate button disappear

If the base language has no content elements the translate button disappear. So you even can not translated from one translate language to another translated language. If you add one dummy element to base the translate button appre and it works fine even the translating language to another translated.

Author Timo Poppinga
Created 01/22/21, 08:23
Updated 04/01/24, 17:42
Bug
New Orphaned Backend User Interface TYPO3 CMS 11

#101411 Message that there are references which point to this record is not always displayed when trying to delete a record

Usually, we get an alert, sometime like this:

> Are you sure you want to delete the record ‘textmedia1 [tt_content:54]’? There are 1 reference(s) to this record!

or

> Are you sure you want to delete ‘textmedia with shortcuts to this ce’? (There are 1 reference(s) to this record!)

when trying to delete a record (e.g. [textmedia]) which has references pointing to it (e.g. “Insert Records” [shortcut]”).

But sometimes we get a generic message which does not point out there are references, such as:

> Are you sure you want to delete this record?

It looks like the behaviour improved between v11 => v13 but is not fully resolved.

(language label: labels.referencesToRecord)

Problems / Inconsistencies

in v13

  • list module: if using checkboxes to select several records then deleting, we get:

> Delete marked
> Are you sure you want to delete all marked records from the table ‘Page Content’?
> Close Delete

(no hint that there are references)

  • (minor): in FormEngine the “Delete record” button does not have an “(!)”, in the other cases it does

in v11 , sames as v13, but also

  • in page layout: using inline delete button, we get generic message (not warning about references):

> Delete this record?
> Delete this record?
> Cancel | OK

  • some more minor inconsistencies in how the delete button is named etc.

Screenshots

v13

Full report

see delete_record_with_references.txt

Author Sybille Peters
Created 07/22/23, 12:42
Updated 03/29/24, 06:45
Feature
New Orphaned Site Handling, Site Sets & Routing

#103486 Configurability of the PageRouter

Hello,

I wanted to extend the PageRouter for a project but there seems to be no way without XClass.

Searching through the core I found the getRouter function in the class TYPO3\CMS\Core\Site\Entity\Site, which was commented with:
??Returns the applicable router for this site. This might be configurable in the future.??

Would this be something to be still implementable as a patch for v12 or only for v13?
(I would think adding a registration for an own class would’nt be a breaking change)

I don’t know if someone already had thoughts on this so I hope it’s okay to open this issue for the topic.

Author Daniel Dorndorf
Assigned to Stefan Bürk
Created 03/26/24, 13:06
Updated 03/26/24, 13:28
Bug
New Orphaned Link Handling & Redirect Handling TYPO3 CMS 11

#103467 Redirect module: Problems with redirects with regexp

Hello everybody,

I have some problems with the redirect module of TYPO3.

I use a redirect with regex “#^/newpage/(.*)$#” to redirect all incoming URL’s of a certain page. This works well, so far no problem.
But now I also have cases where the old URL looks like this: “www.domain.tld/newpage/index.aspx?id=123” and here the redirect no longer works because my TYPO3 has problems with the “id=123”. It does not redirect, but tries to display the TYPO3 page with the id “123”, which cannot be resolved (because this page does not exist in this case) and (in this case also correctly) leads to my 404 page.

It seems that if I have a regex-redirect with an id inside my URL, the redirect does not work.

The TYPO3 is 11.5.36, “is_regexp” is set to true.

Author Manuel Csikos
Assigned to Stefan Bürk
Created 03/22/24, 10:33
Updated 03/22/24, 10:42
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
Bug
Accepted Orphaned Fluid TYPO3 CMS 12

#100758 Viewhelpers and other things do not work outside of extbase context

Using f:form* or f:*.action viewhelpers does not work anymore outside of extbase context. For instance within StandaloneView or FLUIDTEMPLATE.

StandaloneView is regularily used for rendering e-mail and there of course links should be generated.

It should be checked if this still works:

  • f:form viewhelper do correctly prefix the fieldnames. E.g. having an non-extbase plugin using StandaloneView the prefix should be like `tx_myext_pi1[name]` for a name input field

——

Collection of notes from other forge issues:

f:form – Exception:
(1/1) #1639821904 RuntimeException
ViewHelper f:form can be used only in extbase context and needs a request implementing extbase RequestInterface.
/vendor/typo3/cms-fluid/Classes/ViewHelpers/FormViewHelper.php line 148

f:link.action – Exception
(1/1) #1639818540 RuntimeException
ViewHelper f:link.action can be used only in extbase context and needs a request implementing extbase RequestInterface.
/vendor/typo3/cms-fluid/Classes/ViewHelpers/Link/ActionViewHelper.php line 81

In both cases the “TYPO3\CMS\Core\Http\ServerRequest object” is in the $request instead the RequestInterface.

Author Markus Klein
Created 04/26/23, 10:06
Updated 03/07/24, 10:08
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
Feature
New Orphaned Form Framework

#103267 EXT:form Improvement: Field identifier should be editable

The identifier of fields created through the EXT:form backend GUI are generated automatically (text-1, text-2, text-3, etc.) and cannot be edited. Since these identifiers are used in locallang XLF files to find labels, it would be nice if we could change them.

Of course, we have to make sure, that identifiers are unique.

Author Daniel Goerz
Created 03/04/24, 13:17
Updated 03/04/24, 13:17
Feature
New Orphaned Form Framework

#103266 EXT:form Improvement: Introduce Possibility for Validators at form level

Currently, EXT:form only allows validation on a per-field level.

However, it would be helpful to be able to register validators for the whole form like we can do with arguments of extbase actions.

Author Daniel Goerz
Created 03/04/24, 13:13
Updated 03/04/24, 13:13
Bug
New Orphaned Backend User Interface TYPO3 CMS 11

#97317 Duplicates when pages are copied

Creating a copy with the clipboard tends to create undesired additional copies.
One reason I remarked is when the site is reloaded, that might be the case even without user-action by the browser.
Further things like large page-trees could be possible reasons too.

I never verified how the task to create the copies are temporally saved, at least it’s not sufficient.
The copies have to be filtered / deleted manually to remove undesired ones.

Author David Bruchmann
Created 04/06/22, 10:38
Updated 02/29/24, 11:18
Bug
New Orphaned Workspaces TYPO3 CMS 11

#103173 Workspaces: starttime will not respected after pulishing a news into the live-workspace

I checked two procedures in a local TYPO3 system (ddev, TYPO3 11.5.35 & News 10.0.3):

behavior expected:
1. I create a news in the live system and define the `starttime` for the news-record. I surf the frontendpage of the news page before the starttime and don’t see the news. I am wainting. I reload the page after the starttime and see the news. (No need to clear cache in between.)

unexpected behavior:
2. I create a news in my workspace and define the `starttime` for the news-record. I publish the message. I surf the frontendpage of the news page before the starttime and don’t see the news. (expected) I am wainting. I reload the page after the starttime and DON’T see the news. (UNexpected) I clear the System-cache or Frontend-cache. I reload the page once more. I see the news.

The second approach seems to be a bug to me. But I’m not sure whether the error is in the news extension or in the workspace extension. I have ask that question in the slack-channel for the news extension. But the answers did not help me.

Author Dieter Dr. Porth
Created 02/21/24, 14:20
Updated 02/21/24, 15:33
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
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
New Orphaned DataHandler aka TCEmain

#103062 Missing l10n_mode option to not copy the field

Some fields should remain empty when creating a new translation, instead of copying the original value. This is the case for optional SEO fields, that would fallback to the title of the page/record when empty. Copying the original languages value in those fields makes it very likely to display original language on translated pages whenever editors forget to edit them to the target language.

The l10n_mode behaves differently between pages and records (see https://forge.typo3.org/issues/97526), making it it technically possible to prevent translating a field in pages by removing its l10n_mode attribute (although this is not documented).

_.l10n_mode _.Pages _.Other records
(unset) field will not be copied field will be copied (without a prepending string)
“” field will be copied (without a prepending string) field will be copied (without a prepending string)

It would be useful to have a clearly defined and documented l10n_mode that prevents fields from being copied, in both pages and other records.

Right now, our workaround was to create a hook for processDatamap_postProcessFieldArray that runs only for translation operations ($status === 'new' and the transOrigPointerField has a value), loops over all $GLOBALS['TCA'][$table]['columns'] and unsets all $fieldArray keys for which the l10n_mode is noCopy.
It’s working fine, but it would probably make sense to offer such an option directly in the native DataHandler, and ensure a consistent behaviour between pages and other records.

Author Yann Weyer
Created 02/06/24, 13:40
Updated 02/06/24, 13:45
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 Extbase TYPO3 CMS 10

#90949 persistence.storagePid ignores startingpoint (pages), when it is a stdWrap

Consider following situation:

TypoScript setup:

plugin.tx_myext.persistence {
    storagePid.ifEmpty.data = TSFE:id
}

ContentObject:

Array (
    [data] => Array (
        [CType] => list
        [list_type] => myext_myplugin
        [pages] => 123
    )
)

Now, one could expect, that the definitive storagePid would be 123, but it is the value of TSFE:id. This is because ArrayUtility::mergeRecursiveWithOverrule() does not override the storagePid FrontendConfigurationManager::overrideStoragePidIfStartingPointIsSet(), when the storagePid is an array. Which is true, when a config like the one above is used. This leads to the situation, where the value argument passed to stdWrap() would always be the one from TypoScript.

Affected TYPO3 versions: 9.5 and master.

I’ll submit a patch in a moment.

Author Christian Futterlieb
Created 04/04/20, 16:36
Updated 02/05/24, 07:20
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
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
Bug
Accepted Orphaned Link Handling & Redirect Handling TYPO3 CMS 10

#89326 Prevent duplicate redirects in auto redirects

Case Auto redirect (>= v10.1)
An editor changes the slug of a page several times back and forth. A redirect is always created, no matter if it already exists.

Possible solution:
Optimal would be a hash value which is created from all 8 values.

Author Guido Schmechel
Assigned to Frank Nägler
Created 10/01/19, 21:04
Updated 11/09/23, 13:26
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

Showing results 1301 to 1325 of 1561