This is just a work around because the nodejs module has been refactored I believe there are bugs in the way extensions are loaded

install drupal-node.js
cd drupal-node.js/extensions
copy the drupalchat_nodejs extension to that directory

in the config file for node nodejs add this line
extensions : ['/drupalchat_nodejs.server.extension.js'],

please notice the '/'

start your server

In the old nodejs module, it could just be in the same directory as the config file. that is no longer the case

Comments

SocialNicheGuru created an issue. See original summary.

SocialNicheGuru’s picture

Project: DrupalChat » Node.js integration
Category: Support request » Bug report
Issue tags: +Drupalchat

I think this is an error in the new nodejs module and how it handles extensions

SocialNicheGuru’s picture

Title: Drupalchat_nodejs workaround for drupal nodejs module > 7.x-1.12 » Is there an error in how extensions are added: Drupalchat_nodejs workaround for drupal nodejs module > 7.x-1.12
SocialNicheGuru’s picture

There is a change needed in

**                                                                                                                               
 * Loads extensions.                                                                                                              
 */
configManager.loadExtensions = function () {
  for (var i in this.settings.extensions) {
    try {
      // Load JS files for extensions as modules, and collect the returned                                                        
      // object for each extension.                                                                                               
//sng      this.extensions.push(require(__dirname + '/../extensions' + this.settings.extensions[i]));                             
      this.extensions.push(require(__dirname + '/../extensions/' + this.settings.extensions[i]));  <- 'add /'
};
glekli’s picture

Status: Active » Fixed

That is correct. This has already been fixed in the latest version.

Status: Fixed » Closed (fixed)

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