CoreCommunity ExtensionsIncubatorDistributionsTYPO3 4.5 ProjectsTYPO3 4.7 ProjectsTYPO3 6.0 ProjectsTYPO3 6.1 ProjectsTYPO3 6.2 Projects (+)

Bug #6134

Set backend configuration properly

Added by Gernot Leitgab over 3 years ago. Updated over 2 years ago.

Status:Closed Start date:2010-01-20
Priority:Must have Due date:
Assignee:- % Done:

100%

Category:-
Target version:-
Votes: 0

Description

You have to set backend configuration in ext_tables.php properly, otherwise (if configuration differs from default) be users cannot authenticate any more. Patch is attached.

ext_tables.php.diff (339 Bytes) Gernot Leitgab, 2010-01-20 17:38

History

Updated by Reinhard Führicht over 3 years ago

Please explain how Formhandler could affect the login status of a backend user.
I don't get it.

Updated by Gernot Leitgab over 3 years ago

If configuration of backend is changed in localconf.php (e.g. $TYPO3_CONF_VARS['BE']['lockIP']) this problem occurs. Because you authenticate via TYPO3 routine with those information set (have a look at /typo3/init.php) and in your ext_tables.php those information are currently not set. So information from session (set with other IP-mask) does not match current authentication information and be user is logged out and it's not possible to re-login any more because this happens at every login.

Updated by Reinhard Führicht over 3 years ago

Ok, I get it now, sorry.

The funny thing is, that I actually don't know why this code is even in there.
As far as I can see, it makes no sense to create a new backend user object, if TYPO3_MODE is 'BE'.

Updated by Gernot Leitgab over 3 years ago

I guess with these lines of code you offer the opportunity to override standard flexform configuration per user.
You set standard flexform with
$file = 'FILE:EXT:' . $_EXTKEY . '/Resources/XML/flexform_ds.xml';
afterwards you try to get configuration from $tsConfig

Updated by Reinhard Führicht over 3 years ago

That's right, but if TYPO3_MODE is BE there has to be a backend user object anyway. Maybe there isn't, if you run some automated tasks, but Formhandler shouldn't have to care about that.
Am I missing something?

Updated by Gernot Leitgab over 3 years ago

I think at this point the be-user is not set, because you can also add own be-user authentication methods in ext_tables.php, so it would make no sense if the be-user is authenticated already.

Updated by Reinhard Führicht over 3 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Removing the creation of the backend user object, resulted in a fatal error, so you are right, there actually is no backend user object at this point.

I committed your changes to trunk.

Also available in: Atom PDF