when revised the code.. you have a fairly abstract vision, which makes it difficult to collaborate if you don't have good programming skills specially when dont have good OOP skills ... that makes it difficult for any person to collaborate in your application

this issue is not only the usage of a new class as https://www.kavoir.com/2012/04/php-class-for-handling-htpasswd-and-htgroup-member-login-user-management.html ( that class provides a htpasswd with group support! )

but also the management of the gui ones.. at includes/user_table.php (that list only user and mail, will now must list group also) and model/meta_model.php (that abstract for OOP the user object from .htpasswd and .meta files now must hable a group array and now only a grou item)

i request for this cos the main clases index.php it calls itselft to manage all the things.. by the usage of the rest of clasess. too abstrac and great .. but complicated for me! thanks` in advance.

hi i liked your app.. revised the code.. You have a fairly abstract vision, which makes it difficult to collaborate if you don't have good programming skills specially when dont have good OOP skills ... that makes it difficult for any person to collaborate in your application

currently the htpasswd class ( at tools/htpasswd.php) only handles a single file and assumes a single path , so it retrieves the path from the protected directory, that's fine only for shitty apache like noob admins..

in best practice deploys those files are far away from that dir,, so i guess i better to change it on the ini file in that way:

1. make a new key item named secure_file or htpasswd file
2. in constructor of htpasswd class ( at tools/htpasswd.php) add the supprot of independient paths
3. make a first string extract with $fch = substr($htpasswdfile, 0, 1);
4. compared if start with / suing strcmp($fch, '/') if TRUE then use absolute paths,
5. make a second string extract with $fch = substr($htpasswdfile, 0, 3);
6. compared if start with ../ suing strcmp($fch, '../') if TRUE use directory app path as reference
7. if both fails.. use the protected directory

thanks in advance, i suggest another more advanced option.. by usage the more advanced htpasswd class that support groups

• https://www.kavoir.com/2012/04/php-class-for-handling-htpasswd-and-htgroup-member-login-user-management.html

that class provides a htpasswd with group support!