Create migration & models

[schmunk42]

Use migrations instead of an SQL dump.

We can use the configured table prefix, like the advanced app now does: https://github.com/yiisoft/yii2/blob/master/apps/advanced/console/migrations/m130524_201442_init.php#L14

Just as a note: Usually migrations must not be changed after they've been pushed to the repo. There may be exceptions to this rule for initial development, but when we've released a first version, this is a very important convention.

[kartik-v]

Use migrations instead of an SQL dump.

Yes... we should. But for that we need to confirm the db structure. Are we ok on the db design?

Possible DB Design Areas to Close:

• RBAC/Roles related: We need some idea for the role part for Simple RBAC. @schmunk42 and others where should we do this (in user table or a separate db table or as PHP config)? Also IMO, we may need to keep the module open for any other rbac module to plugin easily.
• Image upload integration: Opening it for third party image upload plugins (not sure there is any impact on db)... but let know
• Any other changes: For Email and Social Integration.

If you note, I had done some slight enhancements to the db design:

• Cleaned up and rearranged some columns.
• User table has a last_login_ip in addition to last_login_on
• 3 keys maintained now in user table:
  • auth_key: for rememberMe cookie
  • activation_key: for activating user after registration
  • reset_key: for resetting the user password
• A column called ban_log (a text field) added to adm_user_profile. This will be used to store the ban_history for every instance an user was banned (will concatenate and maintain the ban_reason, login_ip, and time). Ideally there should be a ban_log detail table for this... so let know.

[robregonm]

Latest changes looks great.
Regarding the image upload integration. It may not impact, since we can use is_readable function, which executes fast, for that purpose.

[robregonm]

Btw, in the migrations file we must include the indices code, since there are some DBMS that don't create indices for foreign keys automatically (e.g. PostgreSQL).

[kartik-v]

@robregonm can you take a stab at doing the IdentityInterface or you need some help?

[kartik-v]

I have incorporated quite a few additions.

Have updated the module, models, and added controllers. Check the latest committed code stack.

• Look at all the constants setup in Module - these will be used across the module.
• Module configuration parameters enhanced - look at all config options. The setConfig method will generate the default configuration.
• Models User and LoginForm updated with quite a few methods/functions and all scenarios.
• Controllers added with a BaseController. Thought is to have these controllers
  • AccountController : Will control all user account actions. Currently login, logout, and registration actions have been updated. But it will include few more actions like recovery, reset.
  • SocialController: Social authentication actions. Probably can be merged with the AccountController in case there are not too many actions in here.
  • ProfileController: Will help user to manage user profile.
  • AdminController: Will be used to manage all admin actions.

The names above will also help generate friendly url's.

We must soon have the db migration finalized.

[evercode1]

nice addition to data structure: User table has a last_login_ip in addition to last_login_on. Shaping up to be a very robust data structure for user.

I noticed the timestamp data type for created_on and updated_on fields. In order for me to get that working properly in my Yii2 project, I had to specify the data type in behaviors by adding:

'value' => new Expression('NOW()'),

to behaviors method and use yii\db\Expression; So you might want to add that to behaviors in the BaseModel. Otherwise it might record the wrong data type or fail entirely.

[robregonm]

Working on IdentityInterface, hopefully I will push tomorrow.

[kartik-v]

@evercode1 for handling timestamps it depends on the DB type (mysql, sqllite, postgres, nosql etc.) which developers will be using and the Expression may not work for some DB types. Hence, I have now included a module level setting now with the latest commit. All timestamps will use this setting to generate current time. This is a Closure anonymous function and for this module it defaults to:

'now' => function() {
    return date('Y-m-d H:i:s');
}

The above function will return value similar to Expression('NOW()') and this can be changed by the developer based on his/her need.

[kartik-v]

Working on IdentityInterface, hopefully I will push tomorrow.

@robregonm - great... also check if we need to have a modified User component based on your experience.

[kartik-v]

@robregonm please pull the latest code first ... before pushing (as there are updates across)... or can submit a PR.

[philippfrenzel]

BTW Migrations are really cool and can u pls make them "ongoing" and not changing the "first" one only?

[schmunk42]

RBAC/Roles related: We need some idea for the role part for Simple RBAC. @schmunk42 and others where should we do this (in user table or a separate db table or as PHP config)? Also IMO, we may need to keep the module open for any other rbac module to plugin easily.

Sure, atm I'd we just use the RBAC API Yii provides, so it doesn't matter which RBAC module you've plugged into your app. There's already a PHP and DB version available.

Image upload integration: Opening it for third party image upload plugins (not sure there is any impact on db)... but let know

That would be really nice, see also schmunk42/yii2-extension-requests#9
I used this approach in Yii 1 several times, the imagemanger should provide an input widget with select and upload functionality. IMHO we should do this in a separate extension.

[kartik-v]

Migrations added and models updated with commit 06f9a68.

Couple of tables and models added:

1. UserBanLog
2. MailQueue

[robregonm]

Cool, looks nice so far, however, IMHO the table names should be customizable, so, they shouldn't be constants.
Take a look at this and this
That way, the user will not be forced to use a certain table name, or (in my case, which I want to use this extension within a current ongoing development, that initially developed using yii2-auth) if you have already some table and you just want to migrate to this extension, then the dev only needs to change some field names.