Thank you Mamba. please add this module to the SVN under XoopsModules branch.
As i wrote in the news, I dont name it Alpha because of stability. I call it Alpha because im not sure about anything in this module like the structures and features. nothing is final in this module. once we finalize all my doubts about this module we can release a final version soon.
I wrote this module because i find it a big missing part in XOOPS. this module was far from my abilities
but i release the first alpha version anyway to have something in hand to show the community what is missing in XOOPS.
I also had this intention to develop it as a real community driven project.
In the coding part:
unfortunately now in xoops we have less than 10 active free developers so we should work together to reach to the best outcome. Now there is an unwritten rule in xoops that one developer write a module as an close project then release it and in sometimes the developer leave xoops and the module get orphaned. i really want to break it and do a real teamwork
so i invite all developers to come here and read this topic, review this module codes (I will explain all codes in the module help), advise me, share better codes with us and commit to the SVN.
I want to invite Mage, Trabis, Mamba, timgno, zyspec, red, voltan, mojtaba, peekey, black_beard, alfred and all other developers that i cannot remember there names to come here and share in developments. please lets make it a community project.
In non coding part:
please report me any feature you think we should add to a log module.
Now please focus on feature rather than reporting bugs. bugs can wait for beta versions. focus on structure and let me know your ideas. i will explain more in module help and document parts.
ok lets back to the module.
I think this module is vital for any CMS. here is my proposal that force me to write this module.
1- a log system. we simply need to know what is happening in our websites. if your site make bigger your problems will be bigger too. eg: you will be in more trouble finding issues come from all admins have some permissions.
2- a view/read/unread/new nodes system. Now all modules have a counter to count views. but today this counter is useless. it just count every views without telling us about who is viewing and when the item is viewed
we really need this feature in xoops. i introduce it in this module but it is really basic now and needs your attentions.
3- a login history: im not sure about it. i just want to log the login and logouts. now this module is doing it. but i want to now what you want to see for example in a login history block.
it doesn't run on PHP 5.4.
this module should work in 5.4 what is the issue?
- we need to change the module logo to our standard XOOPS "Blue Move" logo. If you need help, let me know
yes i need all your helps.
Did you measure how his module impacts overall performance on a busy site (like what you have)?
I did my best for it. Im sure it will not cause more trouble than protector but i dont test it in real environments.
- add "Purge" tab, to be able to delete selected entries manually (with option to delete, or export and then delete). Right now you can only set it in Preferences
- add "Export" tab, to export as CSV or Excel files for selected entries (like selected users or selected dates)
- and for release 2.0 or 3.0, it would be interesting to link Userlog to entries in Protector, to for example, select a suspicious activity in Protector, and then see all entries for the same IP from the Userlog. Or the opposite - select IP or User in Userlog, and see if there were any entries in the Protector.
yes i also think about them. there is an automatic purge in the module now. i wanted to release it as soon as possible but i will add purge, export and other things.
the file logging is incomplete now i will complete it soon.
also we really need to integrate this module with logger and protector in 2.6
thank you i just add that config in hurry. but once you add a setting and start to log some users the folder will be created automatically.
I will solve that.
thank you for your suggestions.
From In the middle of nowhere
Community Coordinator (temporary)