I need a contact database module

[carterbeech]

Hi-

I've been looking around but unable to find this.  I need a module that will act as a repository for consultant information.  We'd like to track name, areas of expertise, contact info, rates, and writing samples to start.  I could set this up using a lot of different modules but I'd like it to be easily searchable so that people can find the consultant their looking for based on name, rate or areas of expertise. 

Any ideas?  Any modules already out there?

Thanks for your help.

[Nullig]

I use the Company Directory module for that sort of thing.

Nullig

[carterbeech]

I'm already using that as a staff contact list.  Any other ideas?

[scooper]

We did something similar a while back using FrontEndUsers and Frontend User Listing.
This has the advantage of letting users update their own information as well. Of course you don't need to let them if you don't want to.

Searching using the Frontend User Listing wasn't great (we cobbled something very simple together) but it looks as if Calguy has been busy and done a new cguserdirectory which would certainly be worth investigating.

s.

[jmcgin51]

I'm already using that as a staff contact list.  Any other ideas?

You can modify CompanyDirectory fairly easily (less than 10 minutes) to make it installable as a completely separate module, so you could have a "CompanyDirectory" and "ContactDirectory" both installed in the same instance of CMSMS.

But I would also recommend CGUserDirectory.

[carterbeech]

Can you tell me how to install the separate instance of company directory?

Thanks.

[jmcgin51]

You will need to download/unzip the CompanyDirectory tarball.  Then rename any php source files (like action.editcompany.php) to reflect your new module name (action.editcontact.php, for example).  Then use a text editor to find/replace all instances of "company" (or any variants) with your desired string (like "contact").  Make sure you get them ALL (case sensitive, and all variants.  This affects your database tables.)  Then upload and install the module.

(Note: Changes to source files make your installation unsupportable, so proceed at your own risk.  I have done this modification and can confirm that it works on my system.  YMMV.)

[carterbeech]

Do I need to change anything else like database fields?

[jmcgin51]

if you follow the instructions in my earlier post, you will be changing the names of the database fields that will be created when you install the module.

[musicscore]

Have you tryed CTLModuleMaker module.
With this module you can create your own database aware module by just clicking some buttons.
It's a great module. It has an advanced search mode (frontend) and a frontend input/edit mode.

Good luck

Musicscore

[Pierre M.]

If you are not a PHP/SQL/Smarty/CMSms coder you should use an existing module (CGUserDirectory, CompanyDirectory...) rather than program your own hack. It is maintained for you and upgradable.

Pierre M.

[musicscore]

CTLModuleMaker is a module for users without any PHP/SQL/SMarty knowledge.
Try it (http://dev.cmsmadesimple.org/projects/ctlmodulemaker) and be amazed how easy the module works.
It is maintained bij Pierre-Luc Germain and if you want to change the module you created .. no problem. The modules are upgradable. I'm not a programmer myself, do not know anything about php and/or mysql and I can use this module. I realy love it because it gives me the possibility to create the module I want.

@carterbeech: Try it, test it. Maybe you like it to.  ;D

Musicscore

[Pierre M.]

I'm not a programmer myself

Hence you don't know what API compatibility is and its consequencies on upgradability.
Non programer CMSms users must care about the distinction between a maintained module and "wild code" generated by a maintained module.

I'm not saying Pierre-Luc's code generator is bad. I'm saying whatever the quality of a generator is it generates code for a given API which may change. The generator's maintainer maintains the generator but will he maintain your generation ?

If we call CMSms "MLE fork" a fork it is because its users may experience problem when migrating to 2.x (or already in 1.x when applying some patches). Regular CMSms users know they have an upgrade path.

Pierre M.