Showing results 1526 to 1550 of 1561

Feature
New Orphaned Backend User Interface

#55949 IRRE: Copy / Paste / Duplicate Records inline

It seems to me that this feature is not present at the moment. As far as I can see.

Situation:
Imagine you create a survey with inline records as answers. A definition of an answer can be quite time consuming and complex. Now you need the next answer with the same record settings and nearly the same answer. In this case it would be really cool if you could duplicate the former record inline as this saves a lot of time.

At the moment you can only create, move, hide, show information inline. The duplicate functionality is missing although it has a high potential usage in case of creating surverys and other recurring records in inidvidual extensions.

Author d.ros no-lastname-given
Created 02/13/14, 04:12
Updated 09/03/19, 11:12
Feature
New Orphaned Extbase

#88734 Extbase: M:N Relation – Sorting of Child Model Records by $defaultOrderings

In an M:N relation, the $defaultOrderings as defined in the model repositories should be taken into account – at least in case the parent_child_mm.sorting property is set to 0.

*Explanation/Example:*
I have an extension with two models that are m:n related. You can edit the relations from both sides by use of a selectCheckBox list of records. The child model is always supposed to be sorted by a date field in ORDER_DESCENDING, as defined in the model’s repository:

protected $defaultOrderings = ['date_open' => \TYPO3\CMS\Extbase\Persistence\QueryInterface::ORDER_DESCENDING];

The frontend detail view of the parent model shows the related records of the child model. The sorting is correct when I select the relation from the parent model record as T3 stores the sorting in parent_child_mm.sorting. This sorting order is defined by the TCA setting of the selectCheckBox, thus the order of the checkboxes in the backend form.

But if I only select the relation in the child model records (and thus parent_child_mm.sorting=0), the sorting in the frontend detail view is random: in my local development version it’s correct, in the production version it’s not (I reckon, it’s being sorted by uid::ASC).

I’ve been searching for ways to determine the sorting in the frontend. Some suggested the <v:iterator.for> viewhelper – but I think it should not be set in the view but in the controller or repository. And besides I don’t want to have the additional dependency on ext_vhs. Others suggested to create a specific repository method in the child model – but they referred to old T3 versions and I couldn’t make those ideas work in T3v9.

I think the $defaultOrdering should be taken into account – after all, it’s what the property name DEFAULT ORDERING suggests.

Author Hagen Gebauer
Created 07/12/19, 10:21
Updated 08/21/19, 18:57
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
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 9

#87079 TCA: readOnly renders as 'disabled' element instead of 'readonly'. 'passthrough' type renders nothing (not even a hidden field). No way to pass default IRRE child 'type' values.

Please read here:
https://forge.typo3.org/issues/32412#note-6

It would have been a good idea to continue at that old ticket, since the issue is still the same. But I guess nobody is reading that ticket, because it had already been marked as rejected and probably won’t show up in the usual “list all fresh unresolved tickets” dashboards.
Now there’s apparently a regression – so please check out https://forge.typo3.org/issues/32412#note-6 and re-open that ticket (or continue here).

Author Leonie Philine
Created 12/04/18, 21:38
Updated 04/26/19, 21:26
Bug
New Orphaned FormEngine aka TCEforms TYPO3 CMS 8

#84012 Toggle all function at TCA control selectCheckBox ignores 'onChange' => 'reload'

The TCA control selectCheckBox has a “Toggle all” / “Revert selection” feature, which selects or unckecks all items in the list.

This “Toggle all” function does not trigger a form reload, if ‘onChange’ => ‘reload’ is set in TCA.

TCA example:

‘fam_fa_thisismycustomfield’ => [
‘displayCond’ => ‘USER:Motor\\Myext\\Utility\\TcaUtility->topicsDisplayCondition:topics:fam_fa’,
‘onChange’ => ‘reload’,
‘exclude’ => true,
‘label’ => ‘LLL:EXT:myext/Resources/Private/Language/locallang_tx_ext_lang.xlf:fam_fa_thisismycustomfield,
‘config’ => [
‘type’ => ‘select’,
‘renderType’ => ‘selectCheckBox’,
// TODO https://forge.typo3.org/issues/83457
‘minitems’ => ‘1’,
‘items’ => [
[‘LLL:EXT:myext/Resources/Private/Language/locallang_tx_ext_lang.xlf:fam_fa_thisismycustomfield.access’, ‘access’],
[‘LLL:EXT:myext/Resources/Private/Language/locallang_tx_ext_lang.xlf:fam_fa_thisismycustomfield.benefits’, ‘benefits’],
[‘LLL:EXT:myext/Resources/Private/Language/locallang_tx_ext_lang.xlf:fam_fa_thisismycustomfield.cash-benefits’, ‘cash-benefits’],
[‘LLL:EXT:myext/Resources/Private/Language/locallang_tx_ext_lang.xlf:fam_fa_thisismycustomfield.tax-benefits’, ‘tax-benefits’],
[‘others’, ‘others’]
]
],
],
Author Jan-Henrik Hempel
Created 02/22/18, 11:23
Updated 04/17/19, 23:41
Bug
Accepted Orphaned DataHandler aka TCEmain TYPO3 CMS 8

#80875 Multiple problems with relation handler if too many records exist on a page

I’ve multiple problems with the relation handler if i modify (edit, delete) a record that is stored on a page where many records of that type exist.

Steps to reproduce:

  1. Install tt_address (should also work with any other record that uses categories)
  2. Create a sys_category record
  3. Create a Page of type folder
  4. Store 70.000 Records of type tt_address in that folder and put all records into the same sys_category

Steps that fail:

  1. Open one of the records and try to save the record
PHP Fatal error:  Allowed memory size of 1073741824 bytes exhausted (tried to allocate 294912 bytes) in /xxx/vendor/typo3/cms/typo3/sysext/core/Classes/Database/ReferenceIndex.php on line 226
  1. Try to delet a record
Core: Exception handler (WEB): Uncaught TYPO3 Exception: An exception occurred while executing 'SELECT `uid`, `t3ver_oid`, `t3ver_state` FROM `tt_address` WHERE (`pid` = ?) AND (`t3ver_oid` IN (?, ?, ?, ?, ### HERE ARE AROUND 70.000 PLACEHOLDERS!### , ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)) AND (`t3ver_wsid` <> ?) ORDER BY `t3ver_state` DESC' with params [-1, 6877, ... ###HERE ARE AROUND 70.000 IDS!###, 0]:

Prepared statement contains too many placeholders | Doctrine\DBAL\Exception\DriverException thrown in file /xxx/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php in line 115. Requested URL: https://xxx/typo3/index.php?route=%2Frecord%2Fcommit&token=b7ea833b34189d38b4fd1100f4a55766c16b0613&redirect=%2Ftypo3%2Findex.php%3FM%3Dweb_list%26moduleToken%3D114051d1fe77316e97e2afd42f8034d93a647a7d%26id%3D1316%26table%3D%26imagemode%3D1%26search_field%3Da%26table%3Dtt_address&cmd[tt_address][1300][delete]=1&prErr=1

There a multiple probelms but all of them are related to the realtion handling.
The relation handler does fetch all ids and puts them into a prepared statement. That fails as prepared statements to only allow 65.536 placeholders.
So this should be solved by a subquery and not by fetching all ids.
The other problem is, that all records are fetched and this ends up in a excessive memory usage.

It looks like all actions are executed as expected (records are deleted and saved) but the state of the databse is or can be inconsistent as the save process fails somewhere in the middle.

Author Sascha Egerer
Assigned to Sascha Egerer
Created 04/18/17, 13:02
Updated 04/17/19, 23:41
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
Accepted Orphaned Backend User Interface TYPO3 CMS 7

#73630 flexform data is not deleted when changing plugin

Changing the selected plugin in a content element, where the former plugin had a flexform configuration, but the new plugin does not have one must remove the existing configuration, otherwise the old configuration is still applied to the new plugin.

Another option would be to simply ignore the existing flexform data if the current plugin does not require them.

Author Markus Klein
Created 02/23/16, 18:00
Updated 03/13/19, 14:44
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 FormEngine aka TCEforms TYPO3 CMS 7

#71239 FAL relation + flexform config: Use full setting path as name

Multiple FAL relations in a single flexform do not work if the fields have the same name, but different path (through nesting).

This leads to bugs like
- fluidpages #285: Page configuration: <flux:field> value duplicated for subpage config</flux:field>
- flux #759: inline.fal in a form.container

@NamelessCoder described the problem as follows:

> The situation is that the FAL relation field types were initially created for purely record relations, and the support for using the same field in a FlexForm context is more of an afterthought; an adaptation that allows the field to store at least basic relations when used in a FlexForm.

> Technically, the issue is that when you save a record that has a FlexForm with a FAL field, the FAL relation is stored using the field name without considering the nesting which means that all your relations have the field name image after they’re saved. Of course, when you reload the form, the methods that pre-fill the FAL relation fields are then detecting the same relation in all fields.

> The solution would be to parse the nesting structure of the FlexForm when determining which field name to use when the relation is stored in the database. This would allow TYPO3 to store a field name like settings.foreground.image in your case, rather than simply image. If the method that renders the field is then also capable of determining the same (I believe this needs to be added) the puzzle should be solved, allowing any combination of nested FAL/IRRE fields inside and outside FlexForms in the same way.

Author Christian Weiske
Created 11/02/15, 09:48
Updated 03/06/19, 21:28
Feature
New Orphaned File Abstraction Layer (FAL)

#87013 Add editMetaData a permission for users, storages, filemounts

To be more flexible with permissions to edit meta data of files, we need to add it
to the permission list, so that it can be configured per user, storage and file mount.

To proceed, fix for #65636 needs to be merged first

Author Helmut Hummel
Assigned to Helmut Hummel
Created 11/27/18, 11:35
Updated 03/06/19, 11:43
Feature
Accepted Orphaned Backend User Interface

#40255 Simplify the creation of referenced content elements

In Templavoila it’s easy to create a reference to a content element: the editor must click the “Create reference” button in the content element.

Page Module should have the same easiness. Maybe a “Paste reference after” near the “Paste after” menu item.

P.S.: Please, read this well written post about referenced content elements: http://www.jochen-froehlich.de/en/typo3-best-practice/references.html

Author Christian Toffolo
Assigned to Jo Hasenau
Created 08/27/12, 12:01
Updated 03/01/19, 18:35
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
Bug
New Orphaned Extbase TYPO3 CMS 7

#72600 Singleton ConfigurationManager creates problems with nested extbase plugins

This bug is a bit complicated to describe.

Currently the extbase ConfigurationManager is a singleton which has a state, for example AbstractConfigurationManager::$extensionName

When one extbase plugin calls cObjGetSingle on typoscript which also contains an extbase plugin, the configuration manager will hold incorrect values for the first plugin after the call.

This happens for example in the powermail extension, which allows fields to render a TypoScript object path. After rendering the typoscript, all calls to configurationManager->getConfiguration will return the configuration of the other plugin.

Another shortened example:

# TypoScript
page = PAGE
page.10  = USER
page.10 {
    userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
    extensionName = Plugin1
    pluginName = plugin1
    vendorName = Plugin1
}

lib.plugin2  = USER
lib.plugin2 {
    userFunc = TYPO3\CMS\Extbase\Core\Bootstrap->run
    extensionName = Plugin2
    pluginName = plugin2
    vendorName = Plugin2
}

# Plugin1Controller.php
class Plugin1Controller extends \TYPO3\CMS\Extbase\Mvc\Controller\ActionController {
    public function plugin1Action() {
        $correct = $this->configurationManager->getConfiguration(ConfigurationManagerInterface::CONFIGURATION_TYPE_FRAMEWORK);
        $string = $this->configurationManager->getContentObject()->cObjGetSingle('USER', $GLOBALS['TSFE']->tmpl->setup['lib.']['plugin2.']);
        $incorrect = $this->configurationManager->getConfiguration(ConfigurationManagerInterface::CONFIGURATION_TYPE_FRAMEWORK);
    }
}

Plugin1 renders TypoScript which contains Plugin2. Afterwards Plugin1 cannot get it’s own configuration.

Author Robert Vock
Created 01/08/16, 14:45
Updated 12/18/18, 16:08
Task
New Orphaned Site Handling, Site Sets & Routing TYPO3 CMS 9

#86887 Enable urls like `https://example.com/` and `https://example.com/path/to/site.html`, so only `.html` suffix for page type 0 if there is a path.

We just discussed how to configure the new URL handling within 9.5.x.

Our goal: Have urls like https://example.com/ and https://example.com/path/to/site.html, so only .html suffix for page type 0 if there is a path.

    PageTypeSuffix:
        default: .html
        index: ''
        map:
            .html: 0
        type: PageType

I know this doesn’t fit the current idea of the enhancer. The index is by default set to index, resulting in https://example.com/index.html which I can fully understand.

Most websites still were configured to support the above version. I can understand that this will not work, as you can have .xml: 10 and .json: 15 for example. So TYPO3 does need this to be consistent. But is there a chance to add something like disableSuffixForDefault: true:

    PageTypeSuffix:
        default: .html
        index: ''
        disableSuffixForDefault: true
        map:
            .html: 0
        type: PageType

So TYPO3 will check that the default mapping will be applied, with the index and prevent adding anything?

That should solve the issue and should, hopefully, not be a big deal. If so, I’ll open an issue in forge.
Maybe there are other solutions, but I didn’t find anything else that still fits the streamlined approach.
Or did I oversee some approach? As there is no issue right now, we might be alone with this issue?
Corresponding stackoverflow entry: https://stackoverflow.com/questions/52903641/real-urls-in-typo3-9-5-0

Author Daniel Siepmann
Created 11/08/18, 14:29
Updated 12/04/18, 13:53
Feature
New Orphaned File Abstraction Layer (FAL)

#62091 Add conflict handling to FAL create methods

When adding files to a FAL file storage with addFile() the $conflictMode parameter allows to handle file name conflicts easily (cancel, replace or renameNewFile). It would be nice if that conflict handling could be provided for create methods as well. In my case I want to add files from remote servers to a file storage, but with their original file name:

$url = 'http://example.com/file.ext';
$filename = basename($url);
$content = GeneralUtility::getUrl($url);

$storage = $storageRepository->findByUid(1);
$folder = $storage->getFolder('1:myFolder');

$folder->createFile($filename)->setContents($content);

Currently there seems to be no proper way to rename a new name automatically if another file with the same name already exists. With the proposed change the last line could look like this:

$folder->createFile($filename, 'renameNewFile')->setContents($content);

I think that this would be helpful for folders as well (createFolder()).

Author Simon Praetorius
Created 10/07/14, 22:18
Updated 10/02/18, 13:09
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 Workspaces TYPO3 CMS 4.0

#52070 'eval' => 'unique' and Versioning don't work as expected

“SWAP with current” in modul “Versioning” and “Publish” and/or “Swap” in modul “Workspace Manager” don’t work. The results of the actions are very confused.

(issue imported from #M3744)

Author Toralf Lenz
Created 09/17/13, 12:19
Updated 06/10/18, 12:55
Feature
New Orphaned FormEngine aka TCEforms

#84582 formEngine Evaluation "required" for SysFile Reference / sysFile Metadata properties with checkbox for "upper" evaluation

Problem/Description

Scenario:

  • tt_Content CType “Downloadbox”
  • and you want to require the title property of the IRRE item
  • but an already set title from sys_metadata should also be taken into account by eval => 'required'
                    'columnsOverrides' => [
                        'media' => [
                            'config' => [
                                'overrideChildTca' => [
                                    'columns' => [
                                        'title' => [
                                            'config' => [
                                                'eval' => 'required',
                                            ],
                                        ],
                                    ],
                                ],
                            ],
                        ],
                    ],

Usecase scenario

  • Make sure that an editor fills out the title field of sys_file_reference to force a “nice” download link in the frontend for that FAL-reference if the title field in sys_file_metadata is also empty.

Acceptance Criteria

  • The evaluation “required” (or another named) should only throw a note (mark red) if there is no (e.g.) title set in sys_file_reference and sys_file_metadata
Author Josef Glatz
Created 04/03/18, 14:17
Updated 04/03/18, 14:53
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
Feature
New Orphaned Backend User Interface

#79873 After closing/saving a record in the listview the viewport must scroll to last edited content element

Its the same as #70074 but for the listview and therefore for any record type.
A editor told me this was working with 6.2 and that it´s a important feature to her.

Author Benjamin no-lastname-given
Created 02/17/17, 11:57
Updated 02/17/18, 23:29
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
Feature
New Orphaned Localization

#64902 Translation tools

Hey guys,

first of all: if there are already solutions for my problems i am sorry, did not find much.

I want to suggest a set of features to make translation handling in typo3 much easier:

Extend backend module

It would be a nice feature to make it possible to override all registered labels in a backend module, the additional information would be saved in a database table and when creating the cache it overrides the xliff values. Also it should be possible for admins to manage xliff from that module, so you could merge a translation into your xliff file.

You should also be able to see all labels inserted via TCA/Future Extbase Meta Tag that has no translation. So if you write TCA and use path/to/file/locallang.xlf:some.value and that file does not contain the specific translation (always default file, no translations checked here) you can check it in the module and add it to the file automatically.

Loading suggestions for non-translated labels (example: you have configured french as language but one package does not provide french translations) could also be integrated in that module.

auto-generate xliff translations

It would also be very nice to run a task (via command line) to generate labels automatically from all registered fluid template paths. So you could create the basic translation by writing the view. Every <f:translate key="some.key" extensionname="SomePackage">fallbackvalue</f:translate> would be inserted in the packages locallang.xlf, that is found in Resources/Private/Language. Only labels having the extensionName Attribute would be respected.

Background:

I don’t think its necessary to write my reasons for this request :)

Please let me know what you think of those requests, maybe i might be able to contribute.

Author Philipp Wrann
Created 02/06/15, 11:24
Updated 01/28/18, 14:28

Showing results 1526 to 1550 of 1561