Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aauth v3.0.0-alpha1 is done! #191

Open
6 of 25 tasks
REJack opened this issue Feb 5, 2017 · 13 comments
Open
6 of 25 tasks

Aauth v3.0.0-alpha1 is done! #191

REJack opened this issue Feb 5, 2017 · 13 comments
Labels
Milestone

Comments

@REJack
Copy link
Collaborator

REJack commented Feb 5, 2017

Hey Guys,
based on the news (#189) last week, i've pushed v3.0.0-alpha1 (i named my commit to v3.0.0-rc1 😅)

Now all models donw incl. PHPunit tests over Travis-CI and code-coverage over CodeCov

I hope you like how i created the models.

Next steps are:

  • create whole library without any new suggestion (use model functions in library)
  • change language lines to use sprintf
  • add composer decencies
  • Unspecific session variable names for user

The CodeIgnitier-Aauth v3.0.0 Plans are:

  • write from scratch in MVC
    • db actions into models
    • use model functions in library
    • enhance language lines with sprintf
    • whole code in one code style (CI3 PHP Style Guide)
  • PHPUnit tests over Travis-CI.org & Code-Coverage over CodeCov.
    • Add other databases to test (postgre, odbc, etc.)
  • Aauth Init Class
    • it allows to remove the SQL files
    • creates automatic all database
    • easy database updates in further releases
    • should works flawless with other databases (postgre, odbc, etc.)
  • add .editorconfig EditorConfig helps to define and maintain consistent coding styles between different editors and IDEs,
  • a proper documentation on GitBook
    • replace config explanation with a docs link
  • add composer decencies instead of the reCAPTCHA & TOTP helpers
    • (on release push) travis would creates 2 zips & upload it to the release
      • 1 with vendor-folder, downloaded/integrated composer
        (there some website hosts they not give a ability for a SSH access)
      • 1 without vendor-folder, not integrated composer decencies
  • add CI's Form Validation support
  • add foreign key to database tables (working dbforge solution for Aauth Init Class usage)
  • Single Login mode (allow only one session per user) (Single Login #187)
  • remove * from select on list_users (list_users select * from db  #184)
  • Unspecific session variable names for user (Unspecific session variable names for user #177)
  • Login with email and username (idk main behavior or config option)
  • basic ui (login/register, user-, group-, perm-management, pm center, etc.)
  • extenison-able (plugins):
    • social sign-in (google, github, facebok, etc.)
    • Private Message System
    • maybe system variables
  • easy Migration from v2.X
  • change licence to MIT (Change licence? #88)
  • change email to use a view with passed parameters, instead of plain text

overall Aauth would need PHP 5.5 or higher

If anyone has some suggestions, feel free to answer on this issue 😃.

@REJack REJack mentioned this issue Feb 5, 2017
@REJack REJack added this to the Aauth v3.0.0 milestone Feb 5, 2017
@REJack REJack added the news label Feb 5, 2017
@perenstrom
Copy link
Contributor

Nice work! But doesn't rc mean release candidate, that is feature complete and ready for final bug testing? And not alpha? :P

@REJack
Copy link
Collaborator Author

REJack commented Feb 14, 2017

@perenstrom I named some commit with rc but it was a mistake by me 😅 It's definitely a alpha 😄

@hersag
Copy link

hersag commented Mar 13, 2017

thank you for such a great stuff. appreciate the efforts for V3!

will there be any updates on V3 anytime soon? or should we stick to V2 for new projects?

@REJack
Copy link
Collaborator Author

REJack commented Mar 13, 2017

@hersag You can stick with V2 but with BCrypt (use_password_hash on true), if V3 is ready i'll create a detailed documentation for easy upgrade.

I have at the moment much work with my job 😞, i hope that i can find some time at the next weekend.

@hersag
Copy link

hersag commented Mar 14, 2017

that's great, thank you!

@andacata
Copy link

Great work!

It would be nice to be able to customize transactional emails. May be a customizable view and pass the parameters?

@REJack
Copy link
Collaborator Author

REJack commented Apr 14, 2017

@andacata how you mean this?

@andacata
Copy link

andacata commented Apr 15, 2017

Example in v2, function remind_password:
$this->CI->email->message($this->CI->lang->line('aauth_email_reset_text') . site_url() . $this->config_vars['reset_password_link'] . $ver_code );
My proposal:
$this->CI->email->message($this->CI->load->view('aauth_email_reset', array('url' => site_url($this->config_vars['reset_password_link']), 'ver_code' => $ver_code), TRUE));

@tswagger
Copy link
Contributor

tswagger commented Apr 16, 2017 via email

@REJack
Copy link
Collaborator Author

REJack commented Apr 16, 2017

@andacata & @tswagger i agree on this too, its a nice idea 😄 I'll add this to the list later.

@lyarinet
Copy link

where is source aauth 3.0

@korllan
Copy link
Contributor

korllan commented May 10, 2018

@asifagaria Branch: v3-dev

@lyarinet
Copy link

Thanks For Source But Documents Not Work

please make easy guide whit view

thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants