Posted by ssm2017 Binder on December 16, 2008 at 7:11am
i m trying to port the components i have made for Joomla! to be used with drupal.
the first one is called slcontact.
i will not release them in one time and i will proceed by steps because im learning how to dev for Drupal on the same time.
i project to release a module that will depend on this framework and will allow :
- to register on the site from in-world
- to receive messages from the website ( like the contact form )
the message system is already working and i will need then to see how to register on the site ( and learn cvs...:( i prefear svn :) ).
i plan to release this during january ( maybe :) )
Comments
news...
i have finished on today my module
i have requested a cvs account that is always refused because of bugs
i hope that i will be able to debug everything and get this account to provide this module
this module allows :
- registration on the website from secondlife / opensim
- use a "pay to access" system ( people pay in sl to have an acces to the website )
- add some friends from sl to the website
- send an im message to friends
- people can send a message to the user if this one allows it
if my account is enabled, i will be able to build some secondlife/opensim modules like one to log in the website using secondlife authentication parameters and automatically get real friends list etc...
what do you think about it ?
question
this module is a complete all in one integration but maybe this can be better to separate tasks into different modules.
if yes, ist it better to store user infos in the user table and the "data" serialized field or is it better to use a separated table ?
im asking this question there : http://drupal.org/node/351876
what do you think about that ?
Separate table for sure
It is much better to have it in a separate table, like most contributed module do.
You should not change the schema for core tables, since it creates upgrade issues in the future. The data field is not queryable in SQL, and hence access to it is only sequential which is very inefficient.
So, in summary: add your own table, using uid as a key into the users table.
Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.
Drupal performance tuning, development, customization and consulting: 2bits.com, Inc..
Personal blog: Baheyeldin.com.
cvs account granted :)
my cvs account request was granted on today
im very happy and i plan to rewrite my module to be able to use others modules and maybe i will release a new version during january
the first step will be :
- sl user and drupal user mapping
the other tasks will be others modules
here are my projects
hello
im very happy to annouce the release of my 2 first drupal's projects.
http://drupal.org/project/slcontact_xt
is the full all in one solution to :
register users from inworld
manage time limited registration from paying inworld
manage a friends list
send message from the website to inworld to friends
receive messages from the website
http://drupal.org/project/sluser
this version is a just simple one that will use different modules to be able to make more customised choices.
this will be able in the future to use points module and friends module and more maybe...
the future will tell us