Integrating the member systems of WSN scripts just consists of picking one script to integrate the others into. You can also integrate templates so that template customizations in one script will apply to the others.

Integrating Members, PMs, IMs, Online Users, Stylesheets and Images

First, select one script installation (where you have the most members currently) and declare that the parent installation, which the child installations will connect to.

Go to Admin Panel -> Members -> Integration in each child installation, and select to integrate with the parent script. Use the pre-supplied options for the WSN scripts in the dropdown menu. This will automatically integrate members (including avatars), PMs, IMs and online users. More details in the member integration article.

When the script you're integrating with is another WSN script, please be aware that all the scripts should be on the same series -- if you have Classifieds 5.1, use Links 5.1 too, or there could be errors in spots. You don't have to have the exact same version, just series.

When integrated with another WSN script, it will use the other WSN Script's template set name and language name. In most cases this isn't an issue, because most people leave the default language and template names and only have one language and one template set. If you have a variety of language, style and template options that differ by script, however, you can make a new field to handle those settings for your integration: add $newtemplate = 'template_2'; $newlanguage = 'language_2';

Note that stylesheets and images are automatically shared when integrating. The stylesheet of the script you integrate into is automatically put into use, along with its associated images directory, so you don't have to redo your design.

Integrating Toplist Data

You can do a toplist of items from one WSN script from the template of a different WSN script. See the cross-script toplists article for the details.

Integrating Templates

Many templates are by default the same across all the WSN scripts. If you want to be able to customize in just one place and have it apply to all, you can specify template integration in your integration file (the member integration file created in your /integration/ directory during member system integration). Add these lines:

Replace /blah/blah/otherscript/ with the full file path to the script you're integrating with (the base directory, thus the same as your config.php's $uploadpath with the 'attachments/' chopped off). The $templatesharing list of templates to share has been filled here with the list of non-admin templates which are the same across all the WSN scripts.

Since the 5.1 series, the stylesheets and images are auto-shared.

To share the entire templates directory, use
$templatesharing = 'all';
Please remember that sharing the entire directory only works if it's another install of the same WSN script -- with different WSN scripts, you'll want to share only specific templates.

You can edit the template from any of the scripts and it'll save to the host script appropriately. Note that shared templates must be chmoded since the non-host script won't be able to do FTP chmoding automatically.

It's also possible to share your wrapper template. Add wrapper.tpl to the $templatesharing list. Then use conditionals which detect {DIRURL}, {SITETITLE} or some other distinctive setting in order to serve up any desired slightly different wrapper content depending on the script its being used from. If your forum is at forum.yourdomain.com for example you could use <IF {DIRURL} contains forum.yourdomain.com>forum-only stuff here</IF>

Of course, template sharing is optional and unnecessary.