TYPO3 Core

userFunc is currently disabled in BE
This could be extended to use t3lib_div::callUserFunction (also for FE) - thus it's not required anymore (but allowed) to have the user function globally.

userFunc was enabled again, but not with t3lib_div::callUserFunction - there are some more changes needed (if it makes sense at all) and would go to a new feature request.

I had a bug in t3lib_matchCondition::getPageId and fixed it with the new file 0005613_v4.patch.

• PIDupinRootline didn't work when creating a new page and the parent page was the one set in PIDupinRootline
• disabled caching of TSconfig if conditions were found

• on saving a new page record during the TCEmain phase the PIDupinRootline was processed wrong if the parent page of the new one was set there (thanks to Carsten Lausen for pointing this out)

• if a new page is created after another one (uid negative, e.g. "-333") this wasn't resolved correctly

This patch is not in the core yet!

Somebody needs to submit it to the core list, I haven't seen it in my latest trunk.

Oh, it is already in the Core List. Bernhard just used a misleading subject:
"RFC: Hook request for t3lib_befunc + t3lib_userauthgroup" (2007-11-16)

I added a patch agains current revison 3600 (4_2 branch)

It works for my so far, but I could not resolv the remaining issues Olly mentioned in core List:

--------------
1) t3lib_TSparser_TSconfig
Why are you looking for $TSFE->sys_page? The hash-string stays the same
if deliverd to t3lib_pageSelect ($TSFE->sys_page) or to t3lib_BEfunc.
IMO we could replace the stuff in t3lib_TSparser_TSconfig::getHash() by:
if (TYPO3_MODE=='BE' || isset($GLOBALS['TSFE']) &&
is_object($GLOBALS['TSFE']) && $GLOBALS['TSFE']->beUserLogin) {
return t3lib_BEfunc::getHash($hash, $expTime);
}
Can't we?

2) We have to encapsulate the new functions (private, protected, ...)

3) In t3lib_matchCondition::evalPageId() I found a bug:
'new': the id delivered might be negative (new record after existing)

In t3lib_matchCondition::evalConditionStr(), case 'treeLevel':
This should be extended for the case a new page is generated which would
increment the treeLevel by 1.
--------------

Perhaps someone can do this and update the patch. This will be a great feature for 4.3

Benni, thanks for adding an updated version of the patch! :)

Sure, however, I don't like adding this new "hybrid" class. I would much rather have a new class named "t3lib_febefunc" class that includes a lot of common functions used for FE and BE, "hybrid" just doesn't tell what's in the class. "febefunc" I don't like so much either, better ideas?

Attached a "work-in-progress" version as v13 - it's not finished...

Split up matchCondition to a backend and frontend class.
Updated patch to apply with Trunk again.

More to come...

• integration of follow-up for #19601
• integration of refactoring #19601

Committed to SVN Trunk (rev. 6188)
Committed tests to SVN Trunk (rev. 6189)