Hello.
I did a fresh new installation of MRBS 1.4.8: it's working and i already tested the standalone auth system.
I followed the Readme instruction to set up it in drupal, with your module, but here comes the problems.
When i change the config.inc.php with $auth["session"] = "drupal"; $auth["type"] = "drupal"; and replace it in the webserver, i can't see anymore the MRBS.
The screen goes just blank when i try to open it.
Of course also the auth_drupal.inc and session_drupal.inc are well placed, and the config.inc.php is clean as possible, with only the "drupal" auths mentioned above and the lines relative for the database connection.
Also, after i installed the module into my Website and activated it in the modules page, i still can't see the relative permission tabs!So i can't assign any permission to people to use or not the MRBS 1.4.8.
I suppose the 2 problems are strictly related.
I used the module for the 6.* version a year ago and worked like a charm, i hope we'll fix this problem asap .
Thank you and keep up the good work.
Later i will post my config.inc.php and directory trees if needed.
Comments
Comment #1
giosko commentedUpdate:
I upgraded from my previous version of mrbs to the new module for drupal 7 and mrbs 1.4.8.
Upgrading the version and db worked well, but when i modify the config.php.inc with the
$auth["session"] = "drupal";
$auth["type"] = "drupal";
it still give me back blank screen and i still can't see the permission tab relative to mrbs in drupal.
Also i can't still login in mrbs with my drupal credentials.
Here is my config.php.inc, for further information
And here it is my directory tree
Comment #2
giosko commentedComment #3
giosko commentedKnock knock?
Problem is persisting :(
Comment #4
giosko commentedI managed to log in with drupal accounts into MRBs.But i still not see the permission Tab of the module in my website.
The new permission tab for mrbs does not work out of the box, as soon as installed into the /sites/all/modules/ directory and activated it in the module page?
Am i missing something?
Comment #5
isak_manresa commentedHi giosko,
At the beginig I've made the migration using roles to control the access to MRBS.
You make me reflect with your questions, and I think that module permission control is better to control the access to MRBS to certain roles.
In the last release I've changed the role control access to module permission control access.
In another way, I've tried to use a single Session but have problems with MRBS includes. Then the file session_drupal.inc makes the integration better, but still use a independent session for both, mrbs and drupal. Read new readme.txt for more information.
Regards!
Isak
Comment #6
isak_manresa commented