Project

General

Profile

Actions

Bug #25063

closed

Flagnames aren't stored with file-Extension in sys_language

Added by Mischa Heissmann almost 14 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Category:
-
Target version:
-
Start date:
2011-02-17
Due date:
% Done:

0%

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

Description

in t3skin the ext_tables.php creates the flagnames for the sys_language table (line 109 ff). These names must contain the file-ext (.gif) otherwise the flags won't be shown in backend - even after update or new install.

(issue imported from #M17624)

Actions #1

Updated by Steffen Ritter almost 14 years ago

Hello Mischa,
the thing you explained is not a Bug, flags are used as Sprites upon now.
Therefore only the ISO2 Code will be stored.
An UpdateWizard even modifies this for you if you are updating.

To exchange the flag-set you nowadays have to use the normal sprite Api to overwrite or exchange sprites (see Skinning manual).

So if flags are not shown in Backend, you either have a xclassed version of the form, which therefore is not capable of the new way or you are using iso-codes not within the sprite, for which you would have to register your icons anyways.

Could you please give us an insight?

Actions #2

Updated by Mischa Heissmann almost 14 years ago

Alternatively you can change line 137 to

$TCA['sys_language']['columns']['flag']['config']['items'][] = array($flagName, $flagName.'.gif', 'EXT:t3skin/images/flags/'. $flagName . '.png');
Actions #3

Updated by Mischa Heissmann almost 14 years ago

I recognized a problem with some ext, that use the filename in the table sys_language (e.g. templaVoila). While the file-ext is missing, the unknown.gif - Flag is shown.
That makes 4.5 a bit incopatible with older extentions.

But alternatively I can post a reference to this "bug" on the tv-Bugtracker.

Actions #4

Updated by Steffen Ritter almost 14 years ago

I already moved your second report about the same problem, too the bugtracker.

This is indeed a breaking change to Extensions - there never has been a clean API to resolve flags.

So this one can be closed as for core, there is no bug.

Actions #5

Updated by Steffen Ritter almost 14 years ago

I already moved your second report about the same problem, too the bugtracker.

This is indeed a breaking change to Extensions - there never has been a clean API to resolve flags.

So this one can be closed as for core, there is no bug, it has to be filed for extensions.

Actions #6

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF