Frontend User Manager
Frontend user management normally is a core functionality of the typo3 backend. But more than often it’s also a functionality requested in a separate protected space of a dedicated frontend. In particular for each web application frontend user management is an additional elementary core functionality.
Having had the necessary more than twice, MotoGo developed a frontend user management which encompasses full featured
- frontend user data maintenance,
- frontend group data maintenance and in addition
- frontend E-Mail client
opportunities.
Beside the fields of the typical typo3 frontend user or group data record at least additional application specific fields are necessary to represent requested application concerns. For example, any accounting app needs at least one frontend user balance field. Or any sport application very likely needs a set of additional sport attributes.
To be as flexible as possible in individual frontend user and group attribution a core feature of the MotoGo Lib is the easy attribute definition and configuration feasibility which mainly is done per “AttributeDefinition”-Array alias an own configuration “language”. Furthermore, full (OO) inheritance opportunities can be used to reuse a kind of “base AttributeDefinition” in difference frontend user contexts. In short, individual attribution of any application can be be realized quickly.
Note, in case listed features aren't enough, it’s simple to add own contact fields, verifications or different checks for unwanted robot requests. Also it’s simple to extend the base functionality with own actions alias functionalities. The simplicity of the MotoGo Lib ensures that it’s a matter of few configuration changes or additional lines of code.
Moreover for all frontend output pure CSS, jquery mobile as well as bootstrap layout can be used. Whereby it poses no problem to use two layouts in one solution if necessary. Thus, the frontend user account request form can be part of a bootstrap page, even though the frontend user management is performed in a separate jquery mobile environment.
User Mgr.
User Mgr.
The plugin in the base implementation provides in a “hidden” frontend area
- … a frontend user form having standard mandatory or optional fields with validation. This can be provided in different styles to the user itself for self-editing purposes or to nominated user admins for general administration purposes.
- … the list of all registered frontend users. This list provides all functionalities needed for dedicated frontend user management.
- In particular search and sort opportunities provide a good overview over all frontend users.
- Each frontend user can be contacted per internal E-Mail functionality directly or per circular- or newsletter.
- (Filtered) frontend user data can be exported in an EXCEL list.
Moreover, in a “free” frontend area
- … a request form for requesting a frontend user access is still available. Of course, this form can have standard mandatory or optional fields with validation feasibilities too.
- … frontend user data or frontend user lists are showable for e.g. representatives.
A job schedule enables scheduled maintenance actions in the background for
- … deletion of not any longer necessary frontend user data according the data protection law.
- … sending yearly data update request or happy birthday wishes to frontend users.
- etc.
Group Mgr.
Group Mgr.
The plugin in the base implementation provides in a “hidden” frontend area
- … a frontend group form having standard mandatory or optional fields with validation. Also group recursions are editable.
- … the list of all created frontend groups. This list provides all functionalities needed for dedicated frontend group management.
- In particular search and sort opportunities provide a good overview over all frontend groups.
- Each frontend group can be contacted per internal E-Mail functionality directly or per circular- or newsletter.
- (Filtered) frontend group data can be exported in an EXCEL list.
Moreover, in a “free” frontend area
- … frontend group incl. assigned frontend user data are showable.
E-Mail Mgr.
E-Mail Mgr.
The plugin in the base implementation provides in a “hidden” frontend area
- … a frontend E-Mail form having standard mandatory or optional fields with validation and the opportunity to attach documents. Select selectable frontend users, groups or enter individual E-Mail addresses as receiver.
- … the list of all send E-Mails. This list provides all functionalities needed for dedicated E-Mail management.
- In particular search and sort opportunities provide a good overview over all send E-Mails.
- A test E-Mails can be sent to ensure that e.g. a newsletter is in a good shape before it's sent to all receivers.
- Nice looking E-Mail templates can be used.
- In case of circular- or newsletters, individual frontend data can be inserted per E-Mail. In case of unintentional interruption, sent can be restarted at interruption point. So it’s ensured that receivers will never get two E-Mails only because an interruption occurred.
- Each E-Mail has status information. Due to this beside the E-Mail itself it provides an info e.g. if sent was successful or not.
It’s notable that the E-Mail client is everywhere accessible. Each other (MotoGo) typo3 plugin can use it to send own E-Mails automatically or interactively.