Showing results 1351 to 1375 of 1561

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
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
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 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
New Orphaned Backend API

#23633 regex in TCA eval function

Would be nice to use regex in eval to check values of input fields.

With the attached patch you can use
’eval’ => ‘trim,lower,/[a-z0-9 _-]*/‘
in your TCA configuration.

http://typo3.org/documentation/document-library/core-documentation/doc_core_api/4.3.0/view/4/2/#id2520906

(issue imported from #M15836)

Author Robert Heel
Created 09/28/10, 19:04
Updated 07/04/23, 13:13
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
Bug
Accepted Orphaned Backend User Interface TYPO3 CMS 7

#75338 Replacing a youtube/vimeo video in filelist not possible

It isn’t possible to replace an uploaded youtube video in the filelist. If I want to do this, I always get the file upload dialogue – like when replacing an image – which doesn’t make sense in that case. The youtube/vimeo form should be displayed there.

Author Tobias Wollender
Created 03/31/16, 16:23
Updated 06/06/23, 13: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
Task
New Orphaned Backend API TYPO3 CMS 11

#94325 Naming conventions for extensions for extending Page TSconfig

What namespace should extensions use for naming the TSconfig settings (e.g. “tx_myext”, “mod.tx_myext”, “user.tx_myext” …).

Should core and extension settings be separated?

How the namespace is also affects how they are displayed in “Info > Page TSconfig” (the order and if they can be selected in the select field”

Also, ideally the core settings should be unified in using uppercase / lowercase in the top-level “objects”, currently we have a mix of all uppercase and all lowercase. There may be some deeper meaning or reason I am not aware of, but from what I wrote in #94321:

> For basic coredev installation it looks like this:
> * TCEFORM
> * TCEMAIN
> * mod
> … I think it would be better to (long term) unify the naming so that the top-level items are all lowercase.
> In TypoScript, by convention the type of the “objects” are uppercase (e.g. PAGE) and the “objects” themselves are lowercase. So I think TCEFORM, TCEMAIN etc. should be changed to lowercase. (This sometimes mixing of type and “object” and inconsistent usage of terms is something which was not just noticed and pointed out by me, we already make some changes in the “TypoScript Reference” to address this).

Requirements

1. Make it possible to easily find the settings in the filter options in “Info > Page TSconfig”.
2. All extension TSconfig should be grouped together, not found in various places
3. They should be grouped logically
4. use an intuitive convention that is easy to remember

The difficulty is finding a good namespace. In mod, you have the namespaces per module, e.g mod.web_info, but you might rather want to group by extension key or group by third party extensions in general.

Examples for existing TSconfig:

Examples for extension TSconfig and how they are displayed.

  • news: tx_news: only appears in “all” (this is what news uses)
  • linkvalidator: mod.linkvalidator: appears in “all” and in “mod”
  • direct_mail: mod.web_modules.dmail : appears in “Module: Web>Modules”
Author Sybille Peters
Created 06/12/21, 10:30
Updated 06/03/23, 05:27
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
New Orphaned Localization TYPO3 CMS 10

#89448 Translation Wizard can get stuck

The translation wizard can get stuck when no elements are available for translation from a given language.

Steps to reproduce
  1. Have at least two languages besides “default” (language 1 and language 2)
  2. Create an new page and translate to both languages
  3. Create content element1 in default.
  4. Translate element1 to language 1 with translation wizard
  5. Translate element1 to language 2 with translation wizard but chose language 1 as source
  6. Create content element2 in default.
  7. Translate element2 to language 2 with translation wizard

As element1 was translated from language 1 and element2 does not exist in language 1 yet, the translation wizard tries to translate element2 fro language 1 again, cant submit any elements and therefore triggers a bad request (400) response which causes the wizard to die, blocking the UI without any option to close it again.

Author Daniel Goerz
Created 10/18/19, 12:13
Updated 05/06/23, 15:21
Feature
New Orphaned Extbase

#100808 Out of the box Domain Model extendibility

The majority of modern Frameworks, PHP or not, that use the MVC concept, are using out of the box extendibility. Either with events or other methods. Extending a domain model and having the changes/extends directly there without having to do anything else, could come in handy, specially when multiple extensions, extend one extension and the domain model has to be extended multiple times and have all the extends available.

Here is an example: https://extensions.typo3.org/extension/extender

We should start making the extendibility of other extensions easier and finally get rid of the XClasses.

Author Aristeidis Karavas
Created 05/04/23, 10:54
Updated 05/04/23, 10:54
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
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
Feature
Under Review Orphaned Backend User Interface

#99378 Hide edit/delete buttons for site configuration

For our projects site configuration is added to git and we don’t want anyone to edit or delete them through the backend. We can of course set the file/directory permissions to read only, but in the backend the edit/delete buttons are still there. It would be great if there’s a check to see if the file can be edited/deleted and the buttons are not shown if they can’t be.

Author Rudy Gnodde
Created 12/15/22, 11:14
Updated 04/05/23, 09:54
Feature
New Orphaned Form Framework

#97518 Duplicate form elements

As an editor I want to duplicate a form element in form editor. This should be possible for all elements.
When duplicating a container element (e.g. grid row and fieldset), all sub elements will be also duplicated.

There should be a new button (or new context menu) on the form element on stage to duplicate en element quickly by just one click.

The copy is technically (YAML) completely the same except for the identifier.

Author Andreas Steiger
Created 04/29/22, 12:25
Updated 04/05/23, 09:54
Feature
Author Ralf Zimmermann
Created 02/06/21, 11:18
Updated 04/05/23, 09:54
Task
Accepted Orphaned Backend JavaScript TYPO3 CMS 12

#97393 Validate password policy on the fly in FormEngine

- Create and implement JavaScript module and API to validate password in TCA type=password fields.
- Add ExcludeFromLiveCheck Interface

Author Torben Hansen
Created 04/15/22, 05:57
Updated 03/26/23, 10:45
Bug
New Orphaned RTE (rtehtmlarea + ckeditor) TYPO3 CMS 10

#88690 Translated content elements are not available in linkbrowser of the ckeditor in free mode

If you want to set an intern anchor for a translated content element on a free mode translated page in TYPO3 9 then you can’t choose the translated content elements via linkbrowser in ckeditor, you can only select content elements in the default language.

In TYPO3 8 all content elements were listed, translated and non translated, but this have changed with TYPO3 9.

Author Ronny Hauptvogel
Created 07/05/19, 11:01
Updated 03/05/23, 17:47
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
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
Bug
Needs Feedback Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 10

#98073 Can not add 2 properties of same inline type in the SiteConfiguration because the GUI overrides form values

I wanted to add an additional property to the SiteConfiguration record of type site. My plan was to add multiple domains, that will be requested via ajax to share some cookie-value across multiple domains. I wanted to re-use the site_base_variant record type because its not possible to add own record types and it fits my needs perfectly.

Adding values by editing the yaml file works fine, but using the GUI does not. TYPO3 will start to mix up values, so the values from the baseVariants will be set as values in the fields of my new property. The problem is the data structure, the fields are simply named data[site_base_variant]0[base] and there is no reference to the field-name they relate to.

So i cant use the GUI for my feature for the moment.

There are 2 potential issues/solutions related to this problem:

1) TYPO3 should allow custom records for SiteConfiguration
2) TYPO3 should render the values like they are stored later on: data[site][baseVariant]0[base] and data[site][customProperty]0[base] for example

Both points are valid recommendations

What are your plans in the long run anyway?

Will there be the possibility of adding custom record types to SiteConfiguration? To be honest – at the moment the whole frontend configuration situation is some kind of a mess!
Because some configuration is stored in the SiteConfiguration, other things are configured in typoscript and others again have to be configured via TCA (pages for example) because the SiteConfiguration is restricted to (very) limited features.

Author Philipp Wrann
Created 08/04/22, 08:13
Updated 01/24/23, 17:33
Task
New Orphaned Performance TYPO3 CMS 12

#99700 Language menu: Fetch all translations with a single query

Instead of fetching each page translation individually and possibly fetch translations twice (due to fallbacks), better fetch them in a single query and match them against the LanguageAspect.

Author Christoph Lehmann
Assigned to Christoph Lehmann
Created 01/24/23, 13:19
Updated 01/24/23, 13:19

Showing results 1351 to 1375 of 1561