Thanks for suggestions, but:
In order to remove the need to modify the bb_cookie.php file, could you ship the session changes as bb_session.php
- bb_cookie.php is included in the primary root files, respectively index.php and bb_admin.php. Instead of modifying these files, for keeping easy upgrades possibility, you just should modify bb_cookie.php and do not upgrade it in the future versions. We won't change anything in this case, since it's the best method of implementation for our case. We did a lot of synchronizations, just emulating website's authorization with miniBB functions. It's the best way to fully synchronize miniBB.
and include a new global variable within setup_options.php, such as $auto_using_session=TRUE.
- sessions could be fully emulated modifying bb_cookie.php file.
I suppose you didn't get the idea in full. The idea is not to substitute your own files. That would be difficult, as everybody has its own variables, methods of authorization etc. The idea is to emulate your main website's authorization with miniBB functions (since exactly those functions are used in miniBB to authorize user).
For example, if your website sets a session with the certain variables, there is a script which checks for them some how. The same script is miniBB - you should use its own functions to read your website's session and parse it's variables. All functions are described in the article.