Project

General

Profile

Actions
Copy link

Bug #19648

closed

BE module configuration does not properly consider TYPO3_MODE

Added by Marcus Krause almost 16 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2008-11-26
Due date:
% Done:

0%

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

Description

Common way to register XCLASSes is something like
$TYPO3_CONF_VARS[TYPO3_MODE]['XCLASS']['ext/felogin/pi1/class.tx_felogin_pi1.php'] = *

This is valid for FE and BE.

If I'd like to review the configuration I would expect to see the XCLASS for FE and BE in this example. But as configuration module is in BE, I only see the XCLASS for BE.

Fix: Either provide a way to simulate TYPO3_MODEs or replace TYPO3_MODE on the fly by 'BE' and 'FE' to get configuration values for all modes.

(issue imported from #M9847)

Actions
Copy link
 #1

Updated by Steffen Kamper almost 16 years ago

this is not possible as TYPO3_MODE is replaced by 'BE' at the begin of the script and can't be changed later.

Actions
Copy link
 #2

Updated by Marcus Krause almost 16 years ago

I guess, issue can then be set to resolved.

Actions
Copy link
 #3

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF