Bug #62127
FAL image in translation of Record not working
| Status: | Rejected | Start date: | 2014-10-09 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | File Abstraction Layer (FAL) | Spent time: | - | |
| Target version: | - | |||
| TYPO3 Version: | 6.2 | Is Regression: | No | |
| PHP Version: | 5.4 | Sprint Focus: | ||
| Complexity: |
Description
We experience problems with FAL and translated records used in extbase/fluid.
Usecase 1:- An extbase extension brings it's own records. These records contain a FAL image.
- A plugin uses Extbase and Fluid to display the record data.
- Such a record is created, an image assigned.
- This record gets translated.
Should:
In the frontend the Image should appear in the default language and the image should appear in the translation.
Current state:
The image does not show up in the translated frontend even though it's visible in the backend.
- An extbase extension brings it's own records. These records contain a FAL image.
- A plugin uses Extbase and Fluid to display the record data.
- Such a record is created, an image assigned.
- This record gets translated.
- The image in the translation gets replaced by another picture.
Should:
In the frontend the Image of the translation should appear in the translation, the original image should show up at the default language.
Current state:
The image does not show up in the translated frontend (mode strict) or falls back to the one of the default language even though it's visible in the backend.
You can use the attached example extension to reproduce the behaviour.
A root level template and languages 0 and 1 are assumed.
Related issues
History
#1 Updated by Andreas Wolf 4 months ago
- Status changed from New to Rejected
This is actually a duplicate of #57272.
@Rüdiger: can you check if the patch attached there fixes your problem? If not, we have to further investigate this issue. I’ll reopen then.