Project

General

Profile

Actions

Bug #102608

closed

"Show in all view" leads to not found image.

Added by arde roma 8 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
File Abstraction Layer (FAL)
Target version:
-
Start date:
2023-12-05
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
11
PHP Version:
8.1
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

Hi

Frontend is throwing "No file reference (sys_file_reference) was found for given UID: "***"" on translations of a record with a disabled/hidden image when is set as "Show in all views" or "Show only in list view".

Steps to replicate:
- Create a record of an extension that has an image field like georgringer/news or derhansen/sf_event_mgt, and add a featured image to it.
- Localize the record so each image gets localized too.
- Edit one of the localized records, and set one of the images as "Show in all views" or "Show only in list view".
- Go the the default language and disable/hide that image you just set as "Show in all views" in the previous step.
- Go to the frontend and check the localized frontend version of the record and the error will be thrown.

I have tested it in a new clean installation of Typo3 11 in multiple extensions (sf_event_mgt, news and others from my own) they all throw this error.
I tried with php 8.1 and 7.4 and got the same result.

Actions #1

Updated by Riccardo De Contardi 3 months ago

I tested with both TYPO3 11.5.35 and 12.4.14 and ext:news 11.4.1

  • I used "show in all views"
  • the news plugin in the frontend has been configured as "News article list (incl.detail view)"

and these are the results:

TYPO3 11.5.35

The issue is still present

TYPO3 12.4.14

There is no exception

  • on the default language version of the news, the hidden image remains hidden on both list and detail view
  • on the localized version of the news, the hidden image is visible on both list and detail view

So the behavior seems correct now

Actions #2

Updated by Benni Mack about 1 month ago

  • Status changed from New to Closed

Hey all,

I will close this issue now. The main issue is that the localization part had too many problems that were "fundamentally wrong" and we had to do breaking changes in v12 (in Extbase localization) to achieve this result. v12 now has proper tests for such functionatlity now.

Actions

Also available in: Atom PDF