[TYPO3-core] FYI24 Bug #11585: Faulty usage of t3lib_matchCondition in backend template

[Oliver Hader]

Hi everybody,

Ingo Renner schrieb:
> Hi Olly,
> 
> in an attempt to streamline class naming I'd like to commit the attached
> follow up. Please let me now whether that'd be ok with you.
> 
> BTW, I also started ripping appart t3lib_div into t3lib_utility_Array
> _String and _Http, let's see how this goes...

Since we don't have a section in the CGL how many uppercase characters a
 class name might have, I don't really care whether it's an uppercase or
lowercase character.

We have a similar scheme with the caching framework. However, we had
this all before with t3lib_TCEmain for example.

As far as I understood the discussion, the file name stays the same, in
lowercase. So Ingo, I'd ask you to update the hook definition in your
patch - there's "t3lib/div/class.t3lib_utility_Client.php" using the
uppercase character.

PHP does not care whether it's t3lib_utility_client or
t3lib_utility_Client - there's no difference.

+1 to change it to uppercase

olly
-- 
Oliver Hader
TYPO3 Release Manager 4.3