Excellent module!

We are doing a migration from static HTML to Drupal and ParaChat is in the mix.

Is there a way to keep existing settings as far as ParaChat and test the Drupal integration as the Drupal version of the site is not live yet? I would think possibly skipping the "The next thing to do is set the ParaChat applet to make a request to your Drupal site to verify the user is valid." step would accomplish this? Do I suspect correctly?

From the sample screen looks very intriguing!

Thanks!

Comments

mdlueck’s picture

mdlueck commented

BTW: Currently the static HTML site relies on directory level security, and the pages interfacing with ParaChat are all in that protected directory. ParaChat itself has no authentication, users merely pick a screen name to be known by in the ParaChat system.

mdlueck’s picture

mdlueck commented

Having gotten no response, I went ahead and tested. Seems to work very well - enough for testing the Drupal version of the site. Thanks for developing this module!

vm’s picture

vm commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.