[Typo3-dev] One usertable in TYPO3?

[Christian Jul Jensen]

Kasper Skårhøj <kasper2005 at typo3.com> writes:

> I think someone has already made an extension that keeps the two tables
> in sync and also creates a session for both logins when a login is made
> in either frontend or backend. This approach seems to solve the issue
> right away, doesn't it?

I don't think anybody made full solution for this, But there are
attempts to link fe-logins to be-logins which works ok, but are still
not "the thing"

> Another way to go could be to consider if eg. a backend login should be
> allowed to work in the frontend as well (so the frontend user tables are
> disabled). Alternatively frontend users could work in the backend (which
> is much more complex and probably not the solution).

I think this is definetly the cleaner way to go, right away I see three pretty
simple issues:

We need a FE login for BE users, I will probably be making such an
extension for a project soon.

We need to restrict pages based on BE access, this can be done by 'BE
user section', but the menu's don't follow that which is a problem. I
made an extension that solves the latter, but not in the best way.

The BEuser object are unset in the frontend if the page is not
FE-editable by the user, this complicates writing extensions that uses
BEuser. If this could be changed so an object always exist if a BEuser
is logged in, it would be great. But I'm not sure what side-effects
that might have.

And then there's one big issue:

All the extensions that provide functionality for FEusers can't be
used in this case.


What about merging the two tables on DBAL-level? Ie. simply mapping
the FE-table to the BE-table?

--
-julle