TYPO3 Core

Hey.

First: Thanks for a good how-to-reproduce and a boiled down test extension! It took me just a couple of minutes to look at this and it would have taken much longer otherwise. Thanks!

However, I'm currently unable to reproduce (details below). We've had an important cache related fix with #101177 in this area, which has been released with 12.4.3, and is in 12.4.4 as well, of course. Is there any chance you mis-measured your 12.4.3 result?

• new core dev-main (v13) installation, v12 is identical in this regard, I would be very baffled if v12<->main behaves differently here.

• Create two top level pages "Example1" and "Example2", site records are created automatically

• Create a sys_template record for both, both have (db wise) root=1, clear=3, include_static="EXT:fluid_styled_content/Configuration/TypoScript/" and config:
  

  " 
  # Default PAGE object:
  page = PAGE
  page.typeNum = 0
  page.10 < styles.content.get
  " 
  

• Note the detail content of sys_template records are important, this influences caching: Same sys_template records can share things in cache - that's one of the new ts parser features. To be sure, here is my output on mariadb lowlevel (two "content identical" rows, just tstamp and crdate are different, which are not used in cache-identifier-hashes):
  

  MariaDB [coreinstall]> select * from sys_template;
  +-----+-----+------------+------------+---------+--------+-----------+---------+---------+-------------+------------+----------+------+-------+----------------------------------------------------+-----------+---------------------------------------------------------------------------------------+---------+---------------------------+------------------+-------------------+
  | uid | pid | tstamp     | crdate     | deleted | hidden | starttime | endtime | sorting | description | t3_origuid | title    | root | clear | include_static_file                                | constants | config                                                                                | basedOn | includeStaticAfterBasedOn | static_file_mode | tx_impexp_origuid |
  +-----+-----+------------+------------+---------+--------+-----------+---------+---------+-------------+------------+----------+------+-------+----------------------------------------------------+-----------+---------------------------------------------------------------------------------------+---------+---------------------------+------------------+-------------------+
  |   1 |   1 | 1690559581 | 1690558132 |       0 |      0 |         0 |       0 |     256 | NULL        |          0 | NEW SITE |    1 |     3 | EXT:fluid_styled_content/Configuration/TypoScript/ | NULL      | # Default PAGE object:
  page = PAGE
  page.typeNum = 0
  page.10 < styles.content.get
   |         |                         0 |                0 |                 0 |
  |   2 |   2 | 1690559588 | 1690558664 |       0 |      0 |         0 |       0 |     256 | NULL        |          0 | NEW SITE |    1 |     3 | EXT:fluid_styled_content/Configuration/TypoScript/ | NULL      | # Default PAGE object:
  page = PAGE
  page.typeNum = 0
  page.10 < styles.content.get
   |         |                         0 |                0 |                 0 |
  +-----+-----+------------+------------+---------+--------+-----------+---------+---------+-------------+------------+----------+------+-------+----------------------------------------------------+-----------+---------------------------------------------------------------------------------------+---------+---------------------------+------------------+-------------------+
  2 rows in set (0,000 sec)
  
  

• Now create the two plugin content elements on the two root pages.

• Start an "icognito" browser session to call the frontend (to not have a BE user logged in).

• Call autogenerated-1: "Correct Template"
• Call autogenerated-1 again: "Correct Template"
• Call autogenerated-2: "Correct Template"
• Call autogenerated-2 again: "Correct Template"

From reading the code, I think 12.4.3 fixed the "different site" related cache issue already. Could you please re-check and tell me what I may be missing on my side to reproduce the issue in case you are still able to reproduce this?

I think it's fine, but of course we still may have missed something. It would be great if you could have just another look at this to verify if this is still an issue after the 12.4.3 fix in this area. Please point me into the right direction if this is the case.

Confirmed. Thanks for looking at this some further!

Found issue. Patch incoming.

Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80240

Patch set 1 for branch 12.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/80220