Showing results 1101 to 1125 of 1561

Feature
Needs Feedback Orphaned Backend User Interface

#99423 Let editors remove/unlink content from colpos with an action button in the contents "more actions" button list

Hello,

We want the editors stop hidding useless contents instead of deleting them, and cluttering their own working area.

This improvement is splitted in smaller, and if possible, independant patches.

link to the full video (publically accessible): https://drive.google.com/file/d/1cxHaU7JHPiDE1_4hFsfDiM1m2YxfHoLz/view?usp=share_link

This tasks relates to the time 1.13min of the video

Rachel

Author Rachel Foucard
Created 12/23/22, 16:28
Updated 04/19/25, 08:27
Feature
Accepted Orphaned Backend User Interface

#90478 Better UX for the backend user module - managing be user groups, rights assignment

Hi,

I would like to make a suggestion for a more userfriendly backend user groups modul.

When you have multiple backend users and backend usergroups, it’s really complicated to keep track of the rights assignment.
You have the users and you can assign groups to the user but you don’t know which particular rights the user has. You have to go into each be usergroup to find out which checkmarks are set. Comparing 3 or 4 different groups, almost impossible. Sure, you can name the be groups to make the purpose clear and split them for functionality/roles (ACL Group, Database mount group, page groups etc.) We already use this approach and have a lot of groups because some groups inherit from each other.

Lets say someone sets a right in the wrong group…you have to check every group which is assigned to the user to find out what is wrong.

My suggestion:

Add a new tab “user rights” to the be user properties where you can see all options and usergroups in a 2-dimensional overview (see the attached screenshot). Vertically you see all the ACL, DM, PG options and horizontally you see all usergroups. With this view you can easily see all the groups and rights which the user has. You can easily check if you have assigned the same right to multiple groups, you can change and edit the groups right, maybe create new groups aswell. That way you don’t have to switch the usergroups to check the rights assignment – which can be very time consuming.

Maybe you have other suggestions or want to add something. I think there is much potential to optimize the rights assignment workflow. Maybe not for the upcoming LTS10, but maybe for LTS11…

Author David Menzel
Created 02/21/20, 22:41
Updated 04/18/25, 09:24
Task
New Orphaned Backend User Interface TYPO3 CMS 9

#81238 Streamline severity and message of delete modal

Story:

As an user I would like to know if a record or a file is moved to trash or deleted from database or file system.

Reference behavior:

Delete a tt_content record:
  • modal serverity warning (yellow).
Switch to the recycler module and delete the record there:
  • modal severity danger (red).
So as an user I expect the following relation:
  • warning → moved to trash
  • danger → delete

Overview:

case expected behavior current behavior example
TCA record with ctrl – delete and deleted = 0 warning warning tt_content
TCA record with ctrl – delete and deleted = 1 danger danger tt_content
TCA record without ctrl – delete danger warning sys_domain
Record without TCA danger warning scheduler task
File with recycler available and not in recycler warning warning file
File in recycler danger warning file
File without recycler danger warning file
Author Daniel Windloff
Created 05/17/17, 08:55
Updated 04/18/25, 07:56
Feature
Accepted Orphaned Backend User Interface

#43134 Allow Drag'n'drop of records in list-module

Now that drag’n‘drop for content elements in page-module is set, it would be great to replace the arrows (up & down) in list-module with a similar system.

Each record from each list could be drag’n‘drop up or down.

Thanks a lot!

Author Eric Chavaillaz
Created 11/20/12, 09:44
Updated 04/15/25, 19:35
Bug
Accepted Orphaned Backend JavaScript TYPO3 CMS 13

#106567 Backend login broken when applying recommended strict-dynamic CSP mutation

TYPO3 12 introduces a GoogleMapsHelper PHP class that provides recommendations for configuring the Content Security Policy (CSP) when violations are detected in the backend module “Content Security Policy”.

Among the suggestions, the following mutation is recommended by TYPO3 to address issues related to Google Maps:

new Mutation(
    MutationMode::Extend,
    Directive::ScriptSrcElem,
    SourceKeyword::strictDynamic, // requires(!) Nonce everywhere
    SourceScheme::https, // thx Google!
    SourceKeyword::unsafeEval, // thx Google!
    SourceScheme::blob, // thx Google!
),

However, when applying this recommended mutation in TYPO3 13.4.9, the backend login becomes inaccessible. The browser (tested in Google Chrome) blocks required JavaScript files due to the presence of ‘strict-dynamic’ in the script-src-elem directive.

Here are excerpts of the error messages from the browser console:

Refused to load the script 'https://typo313.ddev.site/_assets/1ee1d3e909b58d32e30dcea666dd3224/JavaScript/Contrib/bootstrap.js?bust=1744616604' because it violates the following Content Security Policy directive: "script-src-elem 'self' 'nonce-aui6eSHIzC2VbdLGkCYA__eI24tsAGFdRv528lUt1VDu_OkIf_9YUQ' 'strict-dynamic' https: 'unsafe-eval' blob: 'report-sample'". Note that 'strict-dynamic' is present, so host-based allowlisting is disabled.
Understand this error

login:1 Refused to load the script 'https://typo313.ddev.site/_assets/081fa96a07de1dccb64a8a83e1567439/JavaScript/login.js?bust=1744616604' because it violates the following Content Security Policy directive: "script-src-elem 'self' 'nonce-aui6eSHIzC2VbdLGkCYA__eI24tsAGFdRv528lUt1VDu_OkIf_9YUQ' 'strict-dynamic' https: 'unsafe-eval' blob: 'report-sample'". Note that 'strict-dynamic' is present, so host-based allowlisting is disabled.
Understand this error

login:1 Refused to load the script 'https://typo313.ddev.site/_assets/081fa96a07de1dccb64a8a83e1567439/JavaScript/user-pass-login.js?bust=1744616604' because it violates the following Content Security Policy directive: "script-src-elem 'self' 'nonce-aui6eSHIzC2VbdLGkCYA__eI24tsAGFdRv528lUt1VDu_OkIf_9YUQ' 'strict-dynamic' https: 'unsafe-eval' blob: 'report-sample'". Note that 'strict-dynamic' is present, so host-based allowlisting is disabled.
Author Stefan Froemken
Assigned to Benjamin Franzke
Created 04/14/25, 08:51
Updated 04/14/25, 16:32
Bug
Needs Feedback Orphaned Frontend TYPO3 CMS 13

#97037 Shortcut in menu to root page is always active

In version 11.5.6 and 11.5.7 the shortcut in the menu to the root page is always marked as active. (I use the MenuProcessor).

Also testet with a fresh installation of 11.5.7 with the Introduction Package. See my screenshot:
Customize is the real current page, and Home is marked as active too.

Author extremo74 no-lastname-given
Created 02/25/22, 10:21
Updated 04/13/25, 13:19
Task
Accepted Orphaned File Abstraction Layer (FAL) TYPO3 CMS 6.2

#77988 Moving folders between local file storages does not work

Trying to move one folder to another storage leads to an flash error message in the backend file module >Directory … was not moved to “/”. Write permission problem?<

Source and target storage are using both the local filesystem driver and are writable, readable, accessible and online.

I tried to debug this issue and tracked it down so far to $this->absoluteBasePath = null in the LocalDriver class. I have not figured out why this is null at this point, but it leads to an error while checking permissions on an malformed file path, due to $this->absoluteBasePath = null.

Thank you

Author Steffen Wargalla
Created 09/18/16, 23:40
Updated 04/12/25, 20:03
Task
Accepted Orphaned Extension Manager TYPO3 CMS 12

#104116 Version not compatible with current TYPO3 version shown as default in Extension Manager and not intuitive how to select other version

Reproduce

Tested this with extension pagetreefilter in v11 non-Composer installation.

pagetreefilter has versions >= 2.0.0 with support for v12, but not v11.

When trying to install the extension in the EM,

1. Go to extension manager
2. Select “Get Extensions” in Menu
3. Click “Update now“
4. Search for “pagetreefilter”

  • the (not compatible) version 2.1.0 is selected by default
  • only when you click on the version you get the information “Not compatible with your version”
  • in the list “Show all versions of pagetreefilter” you get the information that the selected version 2.1.0 is not compatible with current version, and you see the list but do not see which are compatible with current version

Possible improvements

  • by default, select highest version which is compatible with currently installed TYPO3 version
  • in list of versions, show which are compatible
  • in list of versions, ideally mark highest compatible version

Screenshots

Author Sybille Peters
Created 06/15/24, 08:41
Updated 04/12/25, 14:53
Task
New Orphaned Install Tool TYPO3 CMS 9

#89252 Enhance usability of Install Tool presets

  • in Install Tool
  • all settings for instance allow to make use of dropdowns (using allowedValues)
  • this rendering possibility is not available in presets which makes it hard to select proper values
  • besides that, not description is rendered in presets

This way, using presets and having to fill in settings is actually harder than doing that among all settings.

Author Oliver Hader
Created 09/24/19, 18:29
Updated 04/12/25, 14:35
Epic
New Orphaned Localization

#101557 Translation Handling Findings

This is a collection of issues related to any kind of translation handling features, tasks or bugs.

It will be structured by stories for the time being but is supposed to be restructured and rewritten as soon as the translation handling initative picks up working on those issues.

Author Jo Hasenau
Created 08/03/23, 19:32
Updated 04/12/25, 14:12
Feature
Under Review Orphaned FormEngine aka TCEforms

#99997 Support disabling of flexform section object fields via PageTS TCEFORM

It is currently possible to disable flexform fields via PageTS TCEFORM:
https://docs.typo3.org/m/typo3/reference-tsconfig/main/en-us/PageTsconfig/TceForm.html#disabled

This only works on the first level of flexform for the fields inside of sheets.

I suggest that this is extended to also be able to disable fields inside the structure of flexform.
When using the type “array” and section is set to “1” it is possible to add new items like with the “inline” field type.

My suggestion would be that it is possible to define the following PageTS config:

TCEFORM.tt_content.pi_flexform.my_ext_pi1.sDEF.myField.section.disabled = 1
TCEFORM.tt_content.pi_flexform.my_ext_pi1.sDEF.myField.section.sectionField.disabled = 1

I will add a patch with my proposed changes and new test cases.

Author Justus Moroni
Created 02/20/23, 17:40
Updated 04/12/25, 12:25
Epic
New Orphaned Extbase

#102682 Make Extbase plugin registration and configuration more comfortable

This epic is about how to make extension developers life more comfortable when creating Extbase plugins.

Author Torben Hansen
Created 12/16/23, 11:55
Updated 04/11/25, 11:32
Bug
New Orphaned Localization TYPO3 CMS 8

#89498 FSC menu_categorized_content doesn't return content of non default language

Envireonment:
A site with multible languages and categorised content elements.

On a overview page we use the fsc ctype menu_categorized_content to display all ces related to a branch (category).
On the page with the default language menu_categorized_content returns all ces related to the category. Perfect!
On the translated page menu_categorized_content doesn’t return any ce.

After checking the sql query there are two problems.

Query in default language:

SELECT tt_content.* FROM `tt_content` INNER JOIN `sys_category_record_mm` ON uid = sys_category_record_mm.uid_foreign AND sys_category_record_mm.uid_local IN(18) WHERE (`tt_content`.`pid` IN (1, 2, 3, 4, 5, 6, 7, 8, 9)) AND (tablenames='tt_content' and fieldname='categories') AND (`tt_content`.`sys_language_uid` IN (0, -1)) AND ((`tt_content`.`deleted` = 0) AND (`tt_content`.`t3ver_state` <= 0) AND (`tt_content`.`pid` <> -1) AND (`tt_content`.`hidden` = 0) AND (`tt_content`.`starttime` <= 1571910180) AND ((`tt_content`.`endtime` = 0) OR (`tt_content`.`endtime` > 1571910180)) AND (((`tt_content`.`fe_group` = '') OR (`tt_content`.`fe_group` IS NULL) OR (`tt_content`.`fe_group` = '0') OR (FIND_IN_SET('0', `tt_content`.`fe_group`)) OR (FIND_IN_SET('-2', `tt_content`.`fe_group`)) OR (FIND_IN_SET('13', `tt_content`.`fe_group`))))) GROUP BY `uid` ORDER BY `tt_content`.`header` ASC

Query in lang 1:

SELECT tt_content.* FROM `tt_content` INNER JOIN `sys_category_record_mm` ON uid = sys_category_record_mm.uid_foreign AND sys_category_record_mm.uid_local IN(18) WHERE (`tt_content`.`pid` IN (1, 2, 3, 4, 5, 6, 7, 8, 9)) AND (tablenames='tt_content' and fieldname='0') AND (`tt_content`.`sys_language_uid` IN (0, -1)) AND ((`tt_content`.`deleted` = 0) AND (`tt_content`.`t3ver_state` <= 0) AND (`tt_content`.`pid` <> -1) AND (`tt_content`.`hidden` = 0) AND (`tt_content`.`starttime` <= 1571909640) AND ((`tt_content`.`endtime` = 0) OR (`tt_content`.`endtime` > 1571909640)) AND (((`tt_content`.`fe_group` = '') OR (`tt_content`.`fe_group` IS NULL) OR (`tt_content`.`fe_group` = '0') OR (FIND_IN_SET('0', `tt_content`.`fe_group`)) OR (FIND_IN_SET('-2', `tt_content`.`fe_group`)) OR (FIND_IN_SET('13', `tt_content`.`fe_group`))))) GROUP BY `uid` ORDER BY `tt_content`.`header` ASC

Problems in the query:

1:

(tablenames='tt_content' and fieldname='0')

Seems like “data = field:category_field” returns 0 in non default lannguage.
https://github.com/TYPO3/TYPO3.CMS/blob/v8.7.28/typo3/sysext/fluid_styled_content/Configuration/TypoScript/ContentElement/MenuCategorizedContent.txt#L19

2:

(`tt_content`.`sys_language_uid` IN (0, -1)

It just queries default and all language records instead of the current language.

The first I have workedaround with fixing the fieldname

tt_content.menu_categorized_content.dataProcessing.10.where >
tt_content.menu_categorized_content.dataProcessing.10.where = {#tablenames}='tt_content' and {#fieldname}='categories'

For problem 2 I haven’t a workaround yet.

Author Jan Kiesewetter
Created 10/24/19, 12:21
Updated 04/11/25, 07:55
Feature
Accepted Orphaned Mailer API

#102362 FluidEmail should render (rte) links as absolute by default

Relative links in email make no sense in general. Any links within a `FluidEmail` content should be rendered as absolute links per default. Or else there should be any `TypoScript` configuration option (or mailer class property) be introduced.

Current use case: When using `FluidEmail` with any RTE content, `lib.parseFunc_RTE` need to be modified (or copied) and passed to `f:format.html()` like `{myCustomEmailBody -> f:format.html(parseFuncTSPath: ‘lib.parseFunc_RTE_EMAIL’)}`. This should be simplified and made more developer friendly.

Author Jan Kornblum
Created 11/10/23, 17:33
Updated 04/10/25, 22:14
Feature
New Orphaned Backend User Interface

#105381 Make translate button in sys_file_reference IRRE element more prominent

I think the main problem here are:

  • the button “Localize” (e.g. in sys_file_reference relation in “textmedia” field “assets) does not look active the way it is displayed currently
  • and it is not visible this is the relation from the original language. Usually if content from original language is displayed, it is displayed with the flag icon.

Reproduce

1. Create a textmedia element
2. Translate it (connected)
3. Now add image in tab “media” field “assets” in element with original language

Now, in the translated element go to tab media and see the greyed out relation from the original language.

The buttons “Display information” and “Localize” also look greyed out.

Suggestion

  • make the buttons look active and clickable
  • possibly make the button “localize” marked as primary button (e.g. with class=“btn btn-primary”)
  • show a flag symbol for the reference from the default language

Screenshot

Versions

  • v11 … v14 (main)
Author Sybille Peters
Created 10/21/24, 15:34
Updated 04/10/25, 19:43
Feature
New Orphaned Backend User Interface

#103414 Add a date restriction/filter to backend search

As an editor, I want to use date fields in the backend search to limit long search hit lists to the selection that is relevant to me.

Background: My editors often have to search for specific records and the general search offers an unusable number of results for larger instances. A useful restriction would often be to be able to select a time period for a specific date field.

Examples:

  • Search for »Apple« in the demo instance (see screenshot)

Use Cases:

  • All content elements created after 01.01.2024 (crdate)
  • All content elements that were created before 28.02.2024 (crdate)
  • All pages that were last edited before 01.01.2020 (tstamp)
  • All news with a publication date between 01.01.2022 and 31.12.2023 (datetime)
  • All events with a start date after 01.02.2024 and before 01.03.2024 (startdate)
Author Dan Kleine (Untenzu)
Created 03/18/24, 09:58
Updated 04/10/25, 09:49
Feature
New Orphaned Backend User Interface

#77580 List module: Make the selection of single record mode, multi-selection mode and the selection of the record type available via module menus

To make the features of the list module (EXT:recordlist) easy to find, add the main (currently implicit) selections to the module menu.
Remove the “activated clipboard” dependency from the selection mode.

Example 1:
The user wants to edit or remove multiple records.

Current situation:
The user has to scroll down, active the clipboard, scroll down and click to the multi selection mode (e.g. Clipboard 1).
The action itself (edit, remove) has no relation to clipboard features (move, copy, paste).

Proposed behaviour:
Select the single record mode or the multi-selection mode via module menu (in case of a deactivated clipboard). Select the clipboard via module menu in case of an activated clipboard.

Example 2:
The user wants to select an additional column (download a csv…).

Current situation:
Scroll to the table of the record type and click to the table title. If there are many record types and records, the link will be hard to find.

Proposed behaviour:
Select record type in the module menu.

Author Daniel Windloff
Created 08/22/16, 14:35
Updated 04/10/25, 08:04
Feature
New Orphaned Backend User Interface

#40689 Filter for list-view

In the list-view you can select to see only a certain record-type. But it’s not possible to filter that view. It might help go go throw and check/edit records if you could select records to display in the list by applying certain criteria (all news-records which appear in a certain category, all non-hidden elements, …). Maybe we should have some kind of filter-dialog for that like phpmyadmin has (list of fields, smaller/larger/equals/…, value – and that depending on field-type)?

Please note that we have several field-types, for example a multi-select. Dependent on type interface (and filter-query) would need to adjust.

Please also note that moving records up/down in the list-view needs to be taken into account as well. You can’t just move an entry “up by one” like normal because when filtered users would expect to move that record by one row in the filtered table (there might be hidden rows inbetween). Another possibility might for the moment be to disable moving when a filtered view is used (and create a follow-up issue to fix that later).

Author Stefan Neufeind
Created 09/07/12, 04:42
Updated 04/10/25, 07:43
Bug
New Orphaned Localization TYPO3 CMS 9

#88966 Backend translation of contents should show warnings related to defined fallbackType from Site Configuration

There are currently 3 types for Frontend: strict, fallback and free.

In Backend there are two modes: connected (translate) and free (copy), (and mixed if you count that).

Problem is that they are independent and very misleading to editors in certain setups. For example: if we define the fallbackType: free, backend still shows red warings if we mix both modes in backen – what is totally fine for the frontend.
Or we define fallbackType: fallback and create only free translated contents in backen – no warning, but in frontend no translation is shown but the default contents.

I think the warnings in Backend should be related to the fallbackType set.

Author Anonymous
Created 08/16/19, 09:48
Updated 04/03/25, 13:35
Feature
New Orphaned felogin

#97838 Frontend Login & MFA

Since TYPO3 11.5 has MFA available for the backend login it would make sense to also enable this for frontend login. I’m actually surprised that it wasn’t included in the first place.

Author Emile Blume
Created 07/01/22, 07:32
Updated 04/03/25, 13:09
Feature
New Orphaned Security

#87300 Limit amount of concurrent user sessions for same user

TYPO3 allows to use multiple sessions per user which is a feature on the one hand, but could also be a security risk on the other. In order to enhance the scenario it should be possible to limit the amount of concurrent user sessions per user (or disable concurrent logins at all).

Behavior either can be configured for the whole system or (optionally) per user.

Author Oliver Hader
Created 12/27/18, 13:53
Updated 04/03/25, 12:23
Feature
New Orphaned Site Handling, Site Sets & Routing

#106490 it should be possible to define static routes differently depending on application context

In a site configuration it should be possible to define static routes differently depending on the application context. While it is possible to define different base variants, it should likewise be possible to define different static routes. The following example shall illustrate the benefits.

base: /
baseVariants:
  -
    base: 'https://example.com'
    condition: 'applicationContext == "Production"'
  -
    base: 'https://staging.example.com'
    condition: 'applicationContext == "Staging"'
  -
    base: 'http://localhost:8000'
    condition: 'applicationContext == "Development"'
[...]
routes:
  -
    route: robots.txt
    condition: 'applicationContext == "Production"'
    type: staticText
    content: "User-agent: *\r\nDisallow: /typo3/\r\nDisallow: /typo3_src/\r\nAllow: /typo3/sysext/frontend/Resources/Public/*\r\nSitemap: path/to/sitemap.xml"
  -
    route: robots.txt
    condition: 'applicationContext == "Staging"'
    type: staticText
    content: "User-agent: *\r\nDisallow: /"
websiteTitle: My Website

I hope I did not overlook any duplicate issues and/or any explanations in the docs as to why this is designed the way it is. Also, I would love to know how others use this feature and how they deal with different requirements in different contexts (especially for robots.txt).

Author Thilo Ratnaweera
Created 04/02/25, 10:23
Updated 04/02/25, 20:02
Feature
Accepted Orphaned FormEngine aka TCEforms

#61110 Support for timezones in all date fields in TYPO3 BE

Johannes Feustel:
> As an editor and as a dev
> i want a documentation about how datetime filed acutally behave in typo3
> so that i understand what values (TZ) to enter and how to test
>
> AC
> there should be a document/wiki page listing all relevant datetime fields like
> * access stop start of content and pages and records
> * admin panel
> * scheduler task
> * publish date for workspaces
>
> Define meaningful use cases covering each of those like:
> beeing in a specific timezone like CEST while server is in PST, entering a datetime into start field of a page
> what will be save to the db? local time? server time?
> when will it go live acutally?
> How to test? what do i need to emter into the mock date filed of the admin panel (server time?)?
>
>
> Description
>
> All time fields in TYPO3 should be easy understandable (format) and lead to reliable result.
> Format should ideally be based on a user setting and for all the places below TYPO3 should display the timezone
>
> Following cases should be covered
>
> * admin panel
> * schedule for content desired for display in different timezone compared to server time
> * date time of a workspace to auto publish
> * parse datetime string possible like “today”, “MM:HH DD-MM-YYYY”, ISO 8601: “YYYY-MM-DD HH:MM”, “Tue, 24 Nov 09 16:00:00 -0500” in the client?
> * make it possible for the editor to change format of datetime fields in user settings?
>
> See also
> * http://forge.typo3.org/issues/27919 Preview in Admin Panel does not handle Timezone correctly
> * http://forge.typo3.org/issues/32081 document timezone handling / eval datetime
> * http://forge.typo3.org/issues/20088 In BE time and datetime fields GMT-0 will be shown by ja

Author Nikola Stojiljković
Created 08/21/14, 10:36
Updated 04/02/25, 06:05
Feature
New Orphaned Categorization API

#66155 Backend display of localized records

If you translate a category the translated cat is not shown in the category list of another language.
If you translate aacat, in the database table you see a new category – but not a translated one.
So it is not possible to assign categories whith / or to translations.

IMHO a big problem.

I found similar issues like #61923 and #64417

Author Andrea Herzog-Kienast
Created 03/30/15, 18:09
Updated 04/01/25, 13:34
Feature
New Orphaned Pagetree

#89582 Introduce translated page tree

*Motivation*
Currently there is being some work for improving the accessibility of page tree done.
See e.g.: https://forge.typo3.org/issues/86818. This is therefore a great opportunity to jump on this train and continue this process.

There are already several issues in the board, which partially are almost six or more years old.
All these issues describe more or less the possibility to have a translated page tree.

This issue aims to summarize this requests and bundles them to have a good basis for further discussions and considerations.

All this requests are based on several drawbacks, the page tree is facing currently:
  • A TYPO3 editor isn’t always fluent in the default language which is used for the page tree and therefore the page tree is just useless for him.
    Expect the general page structure.
  • The page tree live search only considers the default page records (this applies for either searching for title and also for uid).
    So it’s currently not possible to filter for localized page records.
  • To get the position of a localized page record in the page tree, one has to find it through the top bar navigation,
    switch to the default record in e.g. the edit view, copy the uid and afterwards search in the page tree search for the default one.
    Only after these steps he is able to edit the localized page record.

Site note: To improve the readability I’ll always use the term „language“. But keep in mind that it can actually also be a localization,
because one can add `sys_language` for DE_CH as well as DE_AT.

*Solution (general)*
Introduction of a selection (select box) at the top of the page tree (next to the search / filter) buttons to enable each backend user to select his preferred language.
Obviously in which he is fluent.

This selection should certainly be saved to backend users UC settings. He shouldn’t need to select it again after each login.

The select box will only be displayed if there is at least one `sys_language` record defined.
Furthermore only languages the backend user has proper access rights are displayed in the select box.

Additional
  • Really obvious but it needs to be defined: Default will be always the default language till a backend user adjusts it by selecting another one.
    Or another default is set via UserTSConfig.
  • The context menu in the page tree refers to the page record in the selected language.
    This means, if a backend user has selected “German” and afterwards hides the page record in the context menu, the “German” record gets hidden.
  • Searching / Filtering the page tree will always consider the currently selected language + default records which are not yet translated (See „necessary consideration“ for the reasons).
  • Changing the page tree language while searching / filtering is active, the page tree will reload with the „new“ page tree in the selected language and after that also applies the filtering to it.
  • A UserTSConfig option will be introduced which allows disabling the language selector for user (groups).
  • A UserTSConfig option will be introduced which allows setting a default page tree language for user (groups).

*Necessary considerations*
What happens if the page is not fully translated/localized in the selected language?

More specific: What happens when just a parent page is not translated/localized but the child pages are?

A possible solution would be to show the default ones in this case. Furthermore the page title should be in brackets
to give the backend user directly information about this record is yet not translated.
By editing the page title (returning the default title including the brackets) a new localized record will be created.
This possibility should be made public to the backend user via e.g. a tooltip by hovering over the default record.

*Step 2 features (TBD)*
If the page tree language was switched, hovering over a record should display a tooltip containing the uid and title of the default record.

Author Oliver Bartsch
Created 11/05/19, 08:52
Updated 04/01/25, 13:31

Showing results 1101 to 1125 of 1561