PHPWCMS uses fe_user.php (which is claimed to not work) to login, register and manage a phpwcms_userdetail table. I figured this is / was / will be used for front end user login and registration. This module activates these features with a modified fe_user.php, and extends this with a backend interface to manage all these users/people/employees/members. It allows for adding some detailed information in a set of variable fields, text fields, decimal fileds and such more. Handy you for instance want to have all your employees in your site with some information on when they are in the office, what they do, and what they would like to learn. Most of these fields could also be filled with fileds from the fe_user.php "manage_profile" part. But that would only allow a logged on user to doe this themelves. With this module you can do it as webmaster yourself.
Now what's the cool part?
Well. SInce all these people have their own tags, and detail alias, we can use templates to display these people on different pages, depending on the TAGS gven to that person, and we can have short lists of people, or full detailed information pages on these poeple on your site. Also when using the serach content part, you can include this module in your search. This checks if any of the serach entries comply with the fields :
firstname, lastname, text1, text2 etc.... and comes back with these fields as serach entry return text.
Ok, now probably the question WHY ?
Well, simple, if you can't find a use for it, this module is of no use to you !!!
EXAMPLE OF WHY :
Show the relevant people, to the content of a page using TAGS (WEB 2.0 material !)
Since we are template driven, we can allow for diff
Yes, this module allows frontend users management in the backend. More or less. You can change all values that are used by the phpwcms_userdetail table.
It could also be called Employee Module Based On PHPWCMS Userdetails / Front-End users
What to use it for:
Well, change some user settings for one. I needed it to display different users on different pages that belong to different parts of the website. This module makes strong use of the TAG ability.
Using the frontend part of the module you can tell phpwcms which users you wish to display, or actualy, what users you want tp display using which tags.
Every user has a ALIAS field. WHY? Well since i want to be able to open some detailed pages in different pages of my website. Say the page belonging to the TAG the user is in in that specific case.
I ran around the teaser, news cp parts as well as the shop and glossary module to form this module. It's a BETA release anyway. Will be in production commin march so should be properly finished.
Some code I added to my CSS sheet :
/* Tihs is for the login form only , belongs to personel_module */
Code: Select all
.loginform {
padding : 10px;
}
.fieldset {
width : 180px;
float : left;
margin : 3px;
padding : 10px;
}
.labelpos {
font-size : 12px;
}
.legend {
font-size : 12px;
font-weight : bold;
}
.textfield {
width : 170px;
}
.user_profile {
clear : both;
}
/* End Login form */
/* Start personel / userdetail module css */
/* from the templates */
.detail_list_entry {
padding : 10px;
color : white;
}
.detail_list_entry h3 {
color : white;
}
DOWNLOAD :
http://www.vectrus.nl/download/frontend ... module.rar (version beta3)
Fixes :
beta2
Fixed an alias issue. If the content part has an ALIAS, it will use that as ALIAS, if it doesn't, it will use the users alias. If that doesn't have an alias. The {LINK} wil not work and produce a "Page not found"
beta3
again some issues with backlinks, also found rewite makes a difference Will fix that tomorrow. (24febr)
The only file that should be overwritten is fe_user.php. No real changes some filed values and labels set differently. I also needed to add the image stuff into fe_user.php. It needs to add a field call detail_userimage to a serialized array. Olly Style
Oh Yes and before i forget, it does ADD two fields to the userdetail table. (Sorry O. I realy needed to touch some core this time )
Also included a dutch and a english language file.
Also added search ! Searching also returns possible users that match according to their tags, firstname, lastname, and first 5 textfields. No sense in not beeing able to search for a relevant user.
ALSO I WOULD LIKE TO MAKE A POINT :
This module was created in payed time for a client ! But this client can never stop me from sharing OPEN SOURCE software or modules created specificy for OPEN SOURCE software. Therefor this module is OPEN SOURCE.
Goddamned IT