Feature #36669
closed
Add Hook to manipulate BE login form
Added by Sebastian Michaelsen over 12 years ago.
Updated almost 7 years ago.
Category:
Backend User Interface
Description
With TYPO3 4.7 the old deprecated way of defining Login News ($TYPO3_CONF_VARS['BE']['loginNews']) was removed and the sys_news database table is the only source for login news now.
But you may want to add items from another source (e.g. RSS-Feed).
This is why I want to implement a hook to manipulate the Login News Records.
Yes, I will (probably today). But I have to add the issue here first, right?
- Status changed from New to Needs Feedback
It would be very easy to add items from that other source to the sys_news records (I've already made an extension which imports RSS data into sys_news).
What is the use case for a hook here?
I remember Sebastian tried/tries to "abuse" the login news for his oneclicklogin extension http://typo3.org/extensions/repository/view/oneclicklogin ... If this is the real purpose for this request, why not ask for it instead of trying to sneak something in? As Jigal said, providing news coming from an RSS source would be ease by creating a scheduler task that imports a feed into sys_news.
Jigal van Hemert wrote:
What is the use case for a hook here?
I'd be happy to see a hook that let's one post-process the generated login-news output. In our case I'd throw it away and instead show some other stuff that we're showing on the login page of our customer's installations (e.g. some news about us, recent projects, ...). Of course I could import them into the database - but then I'd have to trick around to get it displayed as we have it right now (two columns).
well, then import it into the regular backend news records o_0
Ingo Renner wrote:
well, then import it into the regular backend news records o_0
That would be a solution, if I'd like to show just one list of things that could be represented with the now used mechanism. But that's not what I'd need.
The point is that we have a working solution in place, that now doesn't run with 4.7 (which is not the problem so far), but there is no hook available so that we could go on using what we had in place.
From the reactions I see that the request is actually not a hook to manipulate the specific BE news items, but a way to modify the BE login form.
The template can already be modified by setting $GLOBALS['TBE_STYLES']['htmlTemplates']['templates/login.html'] (it even supports EXT: prefix, etc.)
If we add a signal/slot mechanism in SC_index::wrapLoginForm() which can modify the $markers array it would be fairly easy to add/modify/remove stuff from the BE login form.
IIRC there were plans to change the BE login a bit, so I'll start a thread in the core list to discuss this and the plans for a modified BE login form.
- Subject changed from Add Hook to manipulate the Login News Records to Add Hook to manipulate BE login form
- Category set to Backend User Interface
- Status changed from Needs Feedback to Accepted
- Assignee set to Jigal van Hemert
- Status changed from Accepted to Under Review
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF