Showing results 376 to 400 of 1561

Bug
New Orphaned File Abstraction Layer (FAL) TYPO3 CMS 9

#89141 Filelist renaming a folder does not update related fields from TCA configs with new name

Renaming a folder in the FAL list (Filelist) does not update related fields from TCA config with the new folder name. Old folder names are retained and lead to exceptions in the output in the frontend.

There are two possibilities to define folder links with the TCA config.

'config' => [
                'type' => 'input',
                'renderType' => 'inputLink',
                'size' => 50,
                'max' => 1024,
                'eval' => 'trim',
                'fieldControl' => [
                    'linkPopup' => [
                        'options' => [
                            'blindLinkFields' => 'class,target,title',
                            'blindLinkOptions' => 'mail,url,page,file'
                        ],
                    ],
                ],
                'softref' => 'typolink'
            ]
 'config' => [
                'type' => 'group',
                'internal_type' => 'folder',
                'size' => 1,
                'maxItems' => 1,
                'softref' => 'typolink'
            ]

*Expected behavior:*
If a folder in the FAL filelist is renamed, moved or deleted, all related TCA config fields getting involved in the changes.

Author Joerg Boesche
Created 09/11/19, 08:38
Updated 09/11/19, 08:38
Bug
Accepted Orphaned Extbase TYPO3 CMS 9

#88464 LazyLoadingProxy does not resolve into \SplObjectStorage, resulting in infinite loop (same for `@var array`)

This report is about \TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper::mapResultToPropertyValue() and the magic (__call() etc) and \Iterator interface methods of \TYPO3\CMS\Extbase\Persistence\Generic\LazyLoadingProxy:

Preface

\SplObjectStorage used to be buggy, which is why the Extbase ObjectStorage was created. In currently supported PHP versions \SplObjectStorage is no longer buggy and it would be time to shed the non-standard Extbase ObjectStorage.

The Problem

Code indicates that \SplObjectStorage is supported. However, LazyLoadingProxy fails to map fetched related objects onto an \SplObjectStorage:

it checks the following:

if (in_array($propertyMetaData['type'], ['array', 'ArrayObject', 'SplObjectStorage', Persistence\ObjectStorage::class], true)) {
    ...
}

(Note that array is supported as well, which will lead to the same infinite loop when iterating through the results!)

The method fetches the objects into an array $objects[]. For a target var@ type ArrayObject or Extbase Persistence ObjectStorage, the objects array is boxed into the respective container.
There is no handling for \SplObjectStorage though, which causes a plain array to be set as the $parentObject’s resolved formerly-lazy property.

When iterating through the \Iterator, e.g. with a for(... as ...) loop, the LazyLoadingProxy calls \TYPO3\CMS\Extbase\Persistence\Generic\LazyLoadingProxy::_loadRealInstance(), to then call current(), next() or reset() on the result.

This works well for object containers, but not for arrays, because PHP returns arrays by value, not by reference .

On each call to $this->_loadRealInstance(), a new copy of the fetched related objects is made, stored in $realInstance and current(), next() or reset() called on the copy. These calls do not at all influence the actual real instance.

Solution steps:

1) Reference assignments

In the LazyLoadingProxy magic methods (__call() etc) and \Iterator interface methods, use reference (“@&@”) assignments:

$realInstance = &$this->_loadRealInstance();

This step will fix the redirect loop for \var array@, but we still need to fulfill the var \SplObjectStorage<vendor>@ annotation</vendor>

2) Handling \SplObjectStorage property mapping targets

In \TYPO3\CMS\Extbase\Persistence\Generic\Mapper\DataMapper::mapResultToPropertyValue(), implement a section for \SplObjectStorage:

                } elseif ($propertyMetaData['type'] === \SplObjectStorage::class) {
                    $propertyValue = new \SplObjectStorage();
                    foreach ($objects as $object) {
                        $propertyValue->attach($object);
                    }
                    $propertyValue->_memorizeCleanState();
                }

This section should probably share code – except for the constructor – with the Extbase Persistence ObjectStorage section.

Note:
Long ago it was tried to base ObjectStorage on SplObjectStorage (https://forge.typo3.org/issues/63989), but that was abandoned: https://review.typo3.org/c/Packages/TYPO3.CMS/+/35585

I believe it is time to decide:

1)
Drop ObjectStorage and switch Extbase to the native SplObjectStorage

2)
Or: Drop support for SplObjectStorage and only support ObjectStorage (then what about ArrayObject and array?)

3)
Or: Properly support SplObjectStorage and array like ObjectStorage and ArrayObject are supported. (solution indicated above)

Author Leonie Philine
Created 05/30/19, 16:15
Updated 06/09/19, 19:39
Feature
New Orphaned Form Framework

#84566 Add FormProtection API to form framework

Is there a possibility to combine the FormProtection API within the Form framework?

The reason for this request is that a security scan of a self-developed web page has a CSRF problem found.
Among other things, I use the database finisher, so this issue is security-relevant.

I couldn’t find any option in the documentation of Form framework!
If there is already a solution to the problem, then I would be very pleased for the addition in the documentation.

Author Erik Krühne
Created 03/30/18, 12:25
Updated 04/04/19, 18:33
Bug
New Orphaned Import/Export (T3D) TYPO3 CMS 8

#73443 Backend-layouts not properly mapped upon import

When doing an import/export of pages and backend layout records get included in the T3D file the relations to those backend-layouts will not get properly updated upon import.

Rather the fields “backend_layout” and “backend_layout_next_level” of the pages table will point to the same UID the backend layout records had on the export site.

To counteract this a “softref” field should get configured for the backend_layout fields of the pages table and a soft reference parser (or the default softref parser) should handle those fields.

Author Bernhard Kraft
Created 02/15/16, 18:06
Updated 03/11/19, 13:48
Feature
New Orphaned Localization

#85177 Store localization state in database

In order to streamline the localization mode behavior (free / connected mode), the Core must be aware of that state. The state must be stored in the database, to have it available in any context of the application.

In its current state, the used localization mode is calculated on runtime in the page module.

The following things are required:
- Field in the database
- Setting the field using the localization wizard
- Upgrade wizard
- DataHandler changes

Author Andreas Kienast
Created 06/07/18, 19:29
Updated 03/08/19, 16:09
Bug
New Orphaned Install Tool TYPO3 CMS 9

#87370 If Install tool session expires, all ajax requests fail

To reproduce:

  • Open “Maintenance” module
  • Go drinking a coffee and return after an hour
  • Click “flush caches”

Expectation:

Install tool session lasts as long as backend session

Actual result:

Install tool session is limited to 60 minutes, even if backend session is configured to be longer and maintenance module is called from backend session

Considerations:

Currently, when accessing the install tool from the backend, a session for standalone install tool is created as well,
thus install tool can be opened in standalone context. It also means that install tool is unlocked and accessible for other requests as well.

Suggestion:

When accessing the install tool from the backend, the install tool session should be shared with the backend session and be independent from a standalone session

Author Helmut Hummel
Created 01/08/19, 17:23
Updated 01/27/19, 11:32
Feature
New Orphaned Backend User Interface

#87526 LinksController - Override with default on LinkHandler switch

If i want to create an link in lets say TextMedia, i mark the Text and create an link. In this Pop-Up where i can set title, path and target i get my default values in the first tab, sites. If i now switch the tab to external links, there are still the default values from the sites link. In the core there is an if witch checks if there is already an value in title an if, then it doesn’t overrides them. Just if the title is empty it sets the default values wich i defined in typoscript for the ck-editor.
Could you build in the option to make this query editable, so that there are two options:
1. on tab switch it doesn’t overrides the values and fills the default just if the value is empty (current).
2. on tab switch all values will be reset to blank and then filled with the default values from the ck-editor/typoscript (like in the older Typo3-Versions like 4.5).

Author Daniel Kary
Created 01/23/19, 12:01
Updated 01/23/19, 12:01
Epic
Accepted Orphaned

#95690 Performance issues when hosting a large amount of websites, and optimizations propositions

Context

My company uses Typo3 to provide a website to each of our clients, meaning that we host around 3500 websites (i.e. around 120.000 pages) on a single Typo3 installation.

We’re now using Typo3 10.4. This installation is built with composer, uses php7.4 and mariadb 10.3, and is hosted on a dedicated apache server.

The general behaviour is really satisfying, but hosting that many websites and pages also presents some difficulties.
The main challenges we faced were about perfs.

First of all, the website configuration system introduced with Typo3 9 and implying one yaml file per website caused a huge performance loss. The time needed to parse 3500 files is really long, and opening the “Sites” backend module can last something like 30sec.

We also had to rise the php limit about the max number of files that it can maintain open at the same time.
The website and page resolution were also problematics. In their primitive form, they triggered one or two db query per site, meaning that each page displayed made around 7000 db queries each time! Not only the loading time was near to 6secs, but our hosting machine had some bad times…

We fixed these issues by:

  • rebuilding an inbase website configuration (we’ve got a ‘website’ table hosting those informations). The ‘pages’ table got a new foreign key linking it to this new table.
  • overriding the \TYPO3\CMS\Frontend\Middleware\PageResolver middleware to resolve the website first with one db query on this ‘website’ table, then
    a second query in the ‘pages’ table to find the suited page. From 7000 queries, we’re now to only 2.
  • also, xclassing the now named TYPO3\CMS\Core\Routing\PageSlugCandidateProvider class, precisely the getPagesFromDatabaseForCandidates method. the way this method is designed makes the while loop to call getSiteByPageId once for each page matching the given ‘slug’. But with 3500 websites, we’ve also got 3500 pages with the ‘/’ slug..

The last problems we could’nt solve at this time are related to the backend when accessed by the super-admin.
Because this admin can see all of the pages, sites, files, or users, the backend performances are really overstretched.

Reproducing and optimizing

I created a docker container reproducing the problem, and an extension that assemble the patches we made.
You can find it there: https://github.com/Opentalent/Typo3MultisitesOptim

The docker is based on the martinhelmich/typo3:10.4 container.

An extension (populate) provides CLI command to populate the DB with as many dummy websites as requested:

php /var/www/html/typo3/sysext/core/bin/typo3 ot:populate 3000

For those who possess a blackfire licence, it also ship a blackfire docker, allowing to profile the typo3 docker, with or without the optimization measures.

Last but not least, I ran two blackfire tests against this container on my machine. These tests were run with 3510 of thoses basic websites (=108810 pages), and all caches flushed before each test :

Author Olivier Massot
Created 10/18/21, 14:40
Updated 10/19/21, 06:22
Task
New Orphaned Security TYPO3 CMS 10

#95559 Make authentication warnings configurable

Following TYPO3_CONF_VARS should be configurable:

  • ['BE']['warning_email_addr'] (possible already)
  • ['BE']['warning_period'] (new, time in seconds >= 0, 0 means always)
  • ['BE']['warning_max'] (new, integer >= 0, 0 means always)
Author Oliver Hader
Assigned to Oliver Hader
Created 10/11/21, 10:42
Updated 10/11/21, 10:42
Task
New Orphaned Backend API TYPO3 CMS 10

#95621 Initial sorting of added assets

There is inconsistency in behaviour when adding assets, two buttons next to each other, if editor choose Add media file (from server) images are sorted ascending, but if editor choose Select & upload files images are sorted randomly.

This is non breaking as for now you never know in what order images will be added.

https://app.slack.com/client/T024TUMLZ/D01CZBWMHV1

Author Zeljko Debeljuh
Created 10/13/21, 08:11
Updated 10/13/21, 08:11
Feature
New Orphaned Pagetree

#94080 Pagetree ShowNavTitle and selectTree

Hello,

in the User-Config with

options.pageTree.showNavTitle = 1
I can use the nav title instead of the page title for the rendering. When using a selectTree (https://docs.typo3.org/m/typo3/reference-tca/master/en-us/ColumnsConfig/Type/Select/Tree/Index.html) the page title is rendered and not the nav title. The selectTree should also consider this option.
Best would be to make this more flexible and

But i think if the option is set for the user globale the selectTree should also consider this setting.

Thanks and kind regards,
Harald

Author varioous OG
Created 05/06/21, 14:29
Updated 10/14/21, 07:08
Bug
New Orphaned DataHandler aka TCEmain TYPO3 CMS 8

#81102 BackendUtility::setUpdateSignal not always triggered instantly

  1. Problem

Triggering setUpdateSignal from a DataHandlerCmdHook does not always execute the triggered Signals in the Frontend of the Backend.

  1. Steps to reproduce:
  • Register a DataHandler Hook
  • Create a page via D&D
  • Change Title of page in pagetree (by double clicking)
  1. what i expected
  • execution of update signals directly after ajax operation
  1. what happened
  • execution of signal was triggered with next loaded module
Author Kay Strobach
Created 05/02/17, 10:08
Updated 06/26/18, 22:45
Bug
New Orphaned Extension Manager TYPO3 CMS 8

#83913 Extension Manager installs extension although a warning is shown that dependencies could not be resolved

When using the extension manager to install a lower version of an extension, which is not compatible with the current TYPO3 version, a warning is shown that dependencies could not be resolved. The user gets prompted to either cancel the installation or to proceed. In the background the lower version of the extension gets already installed, when cancelling the process the lower version is installed without the user knowing.

How to reproduce:
  • install compatible extension (e.g. gridelements 7.2.0) through extension manager
  • open extension manager, go to “Get Extensions” and choose to install an incompatible version of the extension (e.g. gridelements 3.4.0)
  • Cancel the “dependencies could not be resolved” warning
  • check the installed version of the extension in the extension manager

Tested on:
TYPO3 7.6.24
TYPO3 8.7.10

When installing an incompatible extension for the first time, cancelling actually cancels the process and the extension is not installed. This would be the expected behaviour when cancelling the installtion of a lower version as well.

Author Dirk Müller
Created 02/15/18, 10:48
Updated 02/20/18, 18:37
Bug
New Orphaned Extbase TYPO3 CMS 6.2

#59822 Same action called on property mapping errors with view.pluginNamespace

With plugin.tx_<myext>.view.pluginNamespace one can have all plugins of an extension share the same prefix for form data, e.g. for having multiple plugins affect the same object.

However, if property mapping errors occur in this setup, all plugins show the same output (of the last plugin).

This error occurs due to the internal argument __referrer having the same prefix for all plugins, thus the last one prevails and all actions are redirected to this referring request.

Author Mathias Brodala
Created 06/23/14, 17:17
Updated 10/28/15, 12:42
Feature
New Orphaned Backend User Interface

#52114 Expand "do not search" to subpages

The do not search function in page settings is a quite useful thing. Especially if you want to hide pages from search and googlesitemap xml rendering.

But there´s one thing that makes it quite unhandy on large pagetrees. You cannot expand it to child pages. You can go with the list module, but even this is much efford if you want to hide 200 pages.

An equivalent usage to the access function would be a great benefit from an editors POV.

Cheers

David

Author d.ros no-lastname-given
Assigned to Mathias Schreiber
Created 09/18/13, 15:41
Updated 06/16/15, 09:49
Feature
New Orphaned File Abstraction Layer (FAL)

#65397 Make available metadata edition when uploading file

After uploading files in filelist module, I have to refresh page to be able to edit metadata (same for other actions). It will be nice to have access to these actions without page refreshing.

Author David Lemaitre
Created 02/27/15, 15:10
Updated 06/12/15, 17:18
Feature
New Orphaned File Abstraction Layer (FAL)

#65797 TCA: Allow context-based filtering by File Storage in FAL IRRE relations

Currently, when configuring the TCA for a FAL relation, you can specify which file types are allowed and available in the element browser when selecting the file. It would be awesome to be able to also scope a particular TCA context to a subset of all available FAL storages.

FYI: References below are from TYPO3 6.2.11 release

For example, in the helper method

\TYPO3\CMS\Core\Utility\ExtensionManagementUtility::getFileFieldTCAConfig

we currently have parameters for

$allowedFileExtensions
Would it be possible to add something like these?:
$allowedFileStorages
and
$disallowedFileStorages

I spent a little time on this, and it appears filtering on the DataHandler / saving side can be relatively straightforward, by adding a new filtering class in $config[‘filter’].

The trickier part is dealing with the element browser. The configuration interface available in $config[‘foreign_selector_fieldTcaOverride’] (typo3/sysext/core/Classes/Utility/ExtensionManagementUtility.php:508) appears designed to support filtering only by the single facet (‘elementBrowserAllowed’ => [list of file extensions]). The config interface problem can be worked around, perhaps, but I ran into really mucky territory when looking at ways to leverage the filtering information to limit tree scope when rendering the element browser in TYPO3\CMS\Recordlist\Browser\ElementBrowser::main_file (sysext/recordlist/Classes/Browser/ElementBrowser.php:1376).

Anyone have any ideas? This would be a great feature, and it seems unusual that it’s not in place already.

Author Gabe Blair
Created 03/18/15, 02:14
Updated 03/18/15, 02:14
Feature
Accepted Orphaned Backend JavaScript

#70923 TCA: Show proper error message if validation is failing

in TCA you can define validation rules for example the range. More here:

In case of an error, don’t just frame the field with a red border but also say, what is the error.

Author Simon Schaufelberger
Created 10/21/15, 19:04
Updated 12/06/17, 13:21
Bug
New Orphaned Localization TYPO3 CMS 6.2

#62727 Allow MM reference translation on non inline fields for bidirectional MM relations

Consider the following Example:

Categories <— m:m —> Products

TCA:

tx_heimspiel_domain_model_category.php

'products' => array(
    'config' => array(
        'type' => 'select',
        'foreign_table' => 'tx_heimspiel_domain_model_product',
        'MM' => 'tx_heimspiel_product_category_mm',
        'MM_opposite_field' => 'categories',
    )
)

tx_heimspiel_domain_model_product.php

'categories' => array(
    'config' => array(
        'type' => 'select',
        'foreign_table' => 'tx_heimspiel_domain_model_category',
        'MM' => 'tx_heimspiel_product_category_mm',
    )
),

You have a category C1 and a localized version C1Localized and a product P1 that is associated with C1 through the MM table.

If you now localize P1 to P1Localized the expected result is that P1Localized is associated with C1Localized through the MM table, but what happens is that P1Localized gets associated to C1 through the MM table.

I propose allowing localizeReferencesAtParentLocalization to be used in conjunction with MM tables, which would allow for the expected behavior.

Attached is a 1 line diff to make that happen.

Author Danilo Bürger
Created 11/05/14, 21:41
Updated 02/03/18, 22:44
Bug
Under Review Fresh Link Handling & Redirect Handling TYPO3 CMS 14

#110179 RuntimeException on page translation with different doktype than default language

Visiting a translated page whose doktype differs from its default-language page throws an uncaught RuntimeException (“This class may only be used with pages of doktype ‘Link’ (3), doktype X is not supported”) when the default-language page has doktype = 3 (Link).

Steps to reproduce

  1. Create a page with doktype = 3 (Link) in the default language (e.g. link = ‘#’).
  2. Create a free-mode translation of that page (l10n_parent = 0) with a different doktype, e.g. doktype = 4 (Shortcut) pointing elsewhere. Only tested in free mode; connected mode (l10n_parent = source page uid) not verified.
  3. Visit the translation’s own slug in the frontend.
  4. RuntimeException (code 1762776917) in PageTypeLinkResolver::resolveTypolinkParts().

Analysis

In PageInformationFactory::setPageAndRootline(), $pageDoktype is read from the page record before settingLanguage() overlays it into the requested language. The branch condition (if ($pageDoktype === DOKTYPE_LINK)) still uses this stale pre-overlay value, but the record passed to PageTypeLinkResolver::resolveTypolinkParts() is the post-overlay (translated) record. That resolver strictly checks the translated record’s actual doktype:

if ((int)($pageRecord['doktype'] ?? 0) !== PageRepository::DOKTYPE_LINK) { throw new \RuntimeException(...); }

If the translation’s doktype differs, this throws. The same stale-variable pattern likely affects the DOKTYPE_SHORTCUT
branch further down (unconfirmed crash there — resolved silently to the wrong result in testing instead).

Impact

Any multi-language site using per-translation doktype overrides on the same page (e.g. default = inert doktype=3 placeholder, one translation = doktype=4 shortcut) gets a hard 500 on that translation. So far only confirmed for free-mode translations; unknown whether connected-mode translations are equally affected.

Author Martina Kratky
Created 07/09/26, 11:55
Updated 11/19/26, 10:57
Task
Under Review Fresh Dashboard TYPO3 CMS 13

#108206 Dashboard Widget: space between scrollable text and cta missing

Adding more space between text and button adds a more friendly look and feel

!clipboard-202511200547-2tymf.png!

Author Josef Glatz
Created 11/20/25, 04:48
Updated 11/19/26, 14:44
Task
Under Review Fresh Backend JavaScript TYPO3 CMS 14

#111509 Make most of the backend null-safe

The JavaScript of the backend reads values that can be missing at runtime without a check. Most of it follows the shape the other extensions showed: lookups of elements the module renders itself are declared as if they always succeed, dataset attributes are used as strings although a missing one yields undefined, and indices are built from values that may not be there.

Some declarations are untrue as well. Parameters with a null default declare a type that does not admit null, so every caller has to work around them. The TypoScript stream parser models its scratch state, its variable chain and its context chain as always present, although all three start as null and are walked until null. Its combinators are pushed on a stack and invoked generically, yet the stack claims to know their arguments. The module menu reads the top level TYPO3 object through an optional chain and then treats the result as always set.

These places should get a guard or a fallback where the value can really be missing, and a correct declaration where it was wrong. What the backend still reports afterwards is a long tail without a shared shape and is left to a follow-up.

Author Benjamin Kott
Created 11/19/26, 14:43
Updated 11/19/26, 14:43
Epic
Under Review Fresh Backend User Interface

#103033 New Record Creation Workflow / Process

Currently, it is very unintuitive to create a new page. The most common and selected way is done via the pagetree (using drag+drop and the chosen page type to select a position), there is also the way of doing this via the list module, where a “Page Creation Wizard” is showing up.

For the content elements, there is wizard, where you also first have to select a page AND the position, in order to select the type, and the continue further,

For other records, this is done in a basic way to just simply show the FormEngine.

There is always the click menu to create new records as well.

Proposal

I strongly urge to unify this process, by providing a sane dialog which is the same for all, but then can also be customized and extended. Let’s first look at “new” empty pages / records of any kind.

A dialog / modal should open where the position should be selectable (for pages, it is the pagetree), also the breadcrumb to the location should be shown.

Then, when the type is selected (CType, doktype, news_type, be_users.admin, see TCA ctrl “typeColumn”), only relevant fields for new records should be shown.

For pages of type “Standard” this should be title, slug, and maybe some additional fields like disabled, starttime, for pages of type “external URL” this should actually be the target URL (which is a required field anyways, and not considered).

This concept should then also apply to content elements, where also the column where it is placed should be shown.

This concept should also apply to regular news elements as well.

In order to configure the fields to be shown, I recommend
a) always show the required fields of the subtype (do not use FormEngine’s tab logic as it is, we could use FormEngine but a different rendering for the tabs)
b) allow custom fields either through TCA and overrides via PageTsConfig.

We also need to consider this for translations (thus, selecting a language might be an option).

Once this has been solved, we need to consider creating new records from “presets”, that might be records that we have in the bookmarks or something along the lines. Like “cloning” a page (incl. records on it), or a “content element” from an existing “preset” record which has been marked like this before.

Author Benni Mack
Created 02/04/24, 13:21
Updated 11/19/26, 15:34
Task
Under Review Fresh Form Framework TYPO3 CMS 15

#109860 Remove frontend class properties from Form framework configuration

This change removes all CSS class property definitions from the YAML configuration files of the EXT:form framework’s form elements, as well as the fieldProperties and formNavigation rendering options from the root Form.yaml. The corresponding Fluid frontend templates are updated to use hardcoded CSS class names instead of dynamically reading them from YAML properties.

Intention

Previously, CSS classes applied by the frontend templates (e.g. form-control, is-invalid, form-label, form-text, etc.) were stored as configurable properties in the YAML definitions of each form element and in the global renderingOptions of the form. The Fluid templates dynamically resolved these class names at render time via property lookups like {element.properties.elementClassAttribute} or {element.rootForm.renderingOptions.fieldProperties.errorClassAttribute}.
This relationship created an indirect coupling between the YAML configuration layer and the frontend rendering layer, making it harder to understand how HTML output is produced and which configuration actually influences the DOM.

Benefits

  • Improved clarity: Frontend templates are now self-contained and readable without needing to cross-reference YAML files to understand which CSS classes are applied.
  • Reduced configuration complexity
  • Cleaner separation of concerns: The YAML layer defines form behaviour and structure; the Fluid layer owns the rendering output including CSS classes.
  • Easier customisation: Integrators who want to change frontend styling are now clearly directed to override Fluid templates rather than patching YAML class attributes scattered across dozens of files.
Author Josua Vogel
Assigned to Josua Vogel
Created 05/21/26, 20:17
Updated 11/19/26, 11:40
Feature
Under Review Fresh

#110661 Live search: rank results by relevance across all providers

Problem

The backend live search asks every search provider in turn and
concatenates the results in provider order. Within a provider, records
come back ordered by uid, and the user interface then groups them by
record type.

Nothing in that chain looks at how well a record actually matches the
query. A page titled exactly like the search term ranks behind an
unrelated record that happens to carry a higher uid, and as soon as
there are more than a handful of hits, the best match can end up on the
last page.

Proposal

Rank results by relevance across all providers, so the records matching
a query best are on the first page regardless of which provider supplied
them.

  • Score a match in tiers: exact label match, label prefix, match at a
    word boundary, label substring, and a match in any other searchable
    field.
  • Let providers score and paginate at the data source, so only the
    records of the requested page are read in full. For the database
    providers that means an SQL expression, sorted and limited by the
    database.
  • Keep providers that do not opt in working. They are scored in PHP from
    the values they declare.
  • Replace the provider dropdown of the search form with filter tabs
    above the result list, one per provider plus “All”, each carrying its
    result count. Since ranking is global, the type headlines in the
    result list are no longer needed.

Impact

Editors get the best match first instead of paging through results
ordered by uid. Extension authors keep their existing providers
working, and can opt into database-side scoring and pagination.

Author Benjamin Kott
Created 09/09/26, 09:00
Updated 11/19/26, 12:38

Showing results 376 to 400 of 1561