Project

General

Profile

Actions

Bug #72758

closed

Bug #72735: Missing anchors in TYPO3 7.6

EXT:felogin - anchor is missing when using FSC

Added by Björn Jacob over 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
felogin
Target version:
-
Start date:
2016-01-16
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The typoscript for core extensions "form" and "felogin" defines the plugins like CSC (css_styled_content). When using FSC (fluid_styled_content), the wrapped container setting the uid of the cObj as id is missing. Therefore the anchor does not work any more for this cObjs.

For both extensions there should exist different static typoscript templates for both rendering engines.

But "felogin" has only a typoscript preset in EXT:felogin/ext_typoscript_setup.txt. Changing this by replacing this with two extension templates will result in having a breaking change. The only solution would be to define an additional static extension template for FSC which will replace and override the default template. Not nice, but for me the only solution to prevent breaking the old behaviour.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #49127: Felogin deprecated ext_typoscript_setup.txtRejected2013-06-14

Actions
Actions #1

Updated by Björn Jacob over 8 years ago

Maybe it's time to discuss #49127 again since using ext_typoscript_setup.txt is very old school IMHO and does magic new integrators don't understand. Furthermore it's diffcult to override such settings relying on default configuration of TYPO3.

Actions #2

Updated by Riccardo De Contardi about 7 years ago

this has been solved in version 8.7 AFAIK Can you confirm?

Actions #3

Updated by Riccardo De Contardi over 6 years ago

  • Status changed from New to Closed

I guess that it is safe to close this one for now: as far as I know it happens with fluid_styled_content only in version 7.6 and it will not be fixed for that version (it is in priority bugfix mode).

If you think that this is the wrong decision or there is still work to be done, please reopen it or open a new issue with a reference to this one

Actions

Also available in: Atom PDF