Problems setting up WolfAuth (with solutions!)

[sevenpointsix]

I'm just experimenting with WolfAuth, and I had to make the following changes to get the downloadable code working locally. I just thought this might be useful for someone!

• I had to switch auth_check() for $this->auth->auth_check() in the __construct() function of the Testauth controller
• I had to add a semi colon after return FALSE at the very end of Auth_simpleauth.php
• I had to add a "public $has_one = array('role');" definition to the Permission model, as this seemed to be missing

Also, the default password in the SQL provided doesn't appear to be "password". I'm not sure what it is, but if the default salt "ZroJKXzM" is used, then the password hash should be "f06180a8d403e3e60a1f589b2198b9fd51a57cc9". The username "admin" and the password "password" should then log the user in correctly.

[sevenpointsix]

Also, when I was using CI 2.0, I had to add $this->auth-> to all function calls in the Testauth controller (for example, $this->auth->login()). However, using CI 2.1, this doesn't seem to be necessary -- although it is needed in __construct(), as above.

[Vheissu]

Thanks for that sevenpointsix. I've been so busy with work work that I haven't had time to give Wolf the attention it deserves. I'll be taking a look at the aforementioned feedback and issues.

[jamesarnold]

In addition to the above issues, I am getting a 'Call to protected method CI_DB_active_record::_reset_select() from context 'DataMapper' error.

Do you have any ideas how I can resolve this please?

[Vheissu]

Sit tight James, I'm in the midst of moving Wolf away from DataMapper. Might require a tiny bit of tweaking but if you can wait a couple of days or so, version 2 should be ready and less complex to the point issues like this shouldn't arise so frequently. The issue with DataMapper is that if there is a new CI version and the current DM doesn't work with it, you have a broken auth library.

The new version uses the defacto CI ActiveRecord library and models. I've made everything modular and split up, and Wolf of course still uses driver functionality to allow for other drivers to be written.

[jamesarnold]

That's great, thanks; I am not due to start the project that I want to use it on for a week so that should work out nicely.

[jamesarnold]

Sorry to hassle, but do you have an estimate of when you will be releasing this?

[Vheissu]

Hey you're right mate not a hassle. Planning on releasing a beta in about 2 days. You can access the code by switching to the develop branch, a lot of the stuff hasn't been tested yet. The goal is to launch with stripped back functionality and then add in more functionality via drivers.