playground/user

Module managing user

Friday, June 29, 2018
by gregorybesson
Repository
1 Watchers
1 Stars
6,770 Installations

PHP
8 Dependents
0 Suggesters
8 Forks
1 Open issues
76 Versions
5 % Grown

The README.md

PlaygroundUser

, _(*1)

Introduction

Ce module étend LmcUser qui permet de nombreuses fonctionnalités liées à la gestion d'un compte client., _(*2)

Le fonctionnalités apportées par PgUser sont : * Gestion des autorisations via BjyAuthorize * Mot de passe oublié * Activation de compte par mail * Remember me * Gestion d'un avatar * Authentification Facebook (basée sur HybridAuth) * Login via Ajax * Gestion de son profil par lutilisateur * Gestion des comptes en back-office * Blocage de son compte (== soft delete), _(*3)

Installation

Utilisation de Doctrine

Se positionner via shell dans le répertoire vendor/doctrine/doctrine-module/bin., _(*4)

La commande php doctrine-module.php orm:schema-tool:create permet d'installer les tables de ce module dans la base de données, _(*5)

La commande php doctrine-module.php data-fixture:import --append permet d'installer les rôles 'user' et 'admin' ainsi que l'utilisateur 'admin@test.com' (mot de passe 'admin') avec les droits d'administration., _(*6)

Extending PgUser

Use your own User entity

If you want to use your own entity :, _(*7)

Change the value of 'user_entity_class' in the lmcuser.global.php file., _(*8)
```
'user_entity_class' => 'MyUser\Entity\User',
```

Put your doctrine definition in your module.config.php Module (the one extending the user entity), _(*9)

'doctrine' => array(
'driver' => array(
    'lmcuser_entity' => array(
        'class' => 'Doctrine\ORM\Mapping\Driver\AnnotationDriver',
        'cache' => 'array',
        'paths' => __DIR__ . '/../src/MyUser/Entity'
    ),

    'orm_default' => array(
        'drivers' => array(
            'MyUser\Entity'  => 'lmcuser_entity'
        )
    )
)
),

Create your entity (using the doctrine annotation) in your Module. You'll have to implement the interface PgUser\Entity\UserInterface (see below for the explanation), _(*10)
```
class User implements \PgUser\Entity\UserInterface, ProviderInterface, InputFilterAwareInterface
```
The entities of other Adfab modules which need to link PgUser entity base the relationship on an interface : PgUser\Entity\UserInterface. So that, in case you extend the User entity, you can replace this relationship easily. To be able to do that, your user entity needs to implement PgUser\Entity\UserInterface. And in your Module.php onBootstrap method, You have then to use the doctrine listener feature to replace the interface with the correct class, _(*11)
```
public function onBootstrap($e)
{
$sm = $e->getApplication()->getServiceManager();
$doctrine = $sm->get('application_doctrine_em');
$evm = $doctrine->getEventManager();

$listener = new  \Doctrine\ORM\Tools\ResolveTargetEntityListener();
$listener->addResolveTargetEntity(
    'PgUser\Entity\UserInterface',
    'MyUser\Entity\User',
    array()
);
$evm->addEventListener(\Doctrine\ORM\Events::loadClassMetadata, $listener);
}
```

BEWARE : Your Module extending the entity must be placed after the other modules that have a link to the entity extended in application.config.php, _(*12)

Use your own Form

If you want to change the ChangeInfo Form for example (ie. you want to add a 'children' select list to persist in your user database table). First extend the entity as explained previously. Then :, _(*13)

Create the Form class in your Module, which extends the PgUser Form, _(*14)

class ChangeInfo extends \PgUser\Form\ChangeInfo

If you want to use the default fields of the PgUser Form, you can do this by using the parent constructor, _(*15)

 parent::__construct($name, $createOptions, $translator);

And then you add the Form elements you want, _(*16)

$this->add(array(
    'type' => 'Laminas\Form\Element\Select',
    'name' => 'children',
    'attributes' =>  array(
        'id' => 'children',
        'options' => array(
            '0' => 0,
            '1' => 1,
            '2' => 2,
            '3' => 3,
        ),
    ),
    'options' => array(
        'empty_option' => $translator->translate('Select', 'pguser'),
        'label' => $translator->translate('Children', 'pguser'),
    ),
));

Declare your Form in your Module.php factories definition by reusing the same form name used in PgUser (as your module is loaded after PgUser, your definition will be taken instead of the PgUser definition), _(*17)

public function getServiceConfig()
{
return array(
    'factories' => array(
        'pguser_change_info_form' => function($sm) {
            $translator = $sm->get('MvcTranslator');
            $options = $sm->get('pguser_module_options');
            $form = new Form\ChangeInfo(null, $options, $translator);
            return $form;
        },
    )
);
}

Use your own User controller

If you want to add an action or modify an existing one., _(*18)

Create the controller in your Module (extend the PgUser one if you want to use its methods), _(*19)

class UserController extends \PgUser\Controller\Frontend\UserController
{
    public function profileAction ()
    {
        ...
    }
}

Define your controller and associate the route with your controller in your module.config.php file. Don't forget to define the view name and adjust the core layout definition if you need to, _(*20)

'core_layout' => array(
'MyUser' => array(
    'default_layout' => 'layout/2columns-left',
    'children_views' => array(
    'col_left'  => 'adfab-user/layout/col-user.phtml',
),
),
),
'controllers' => array(
'invokables' => array(
    'myuser_user'    => 'MyUser\Controller\UserController',
),
),
'router' => array(
'routes' => array(
    'lmcuser' => array(
        'child_routes' => array(
            'profile' => array(
                'type' => 'Laminas\Router\Http\Literal',
                'options' => array(
                    'route' => '/mes-coordonnees',
                    'defaults' => array(
                        'controller' => 'myuser_user',
                        'action'     => 'profile',
                    ),
                ),
            ),
        ),
    ),
),
),
'view_manager' => array(
'template_path_stack' => array(
    'pguser' => __DIR__ . '/../view',
),
'template_map' => array(
    'adfab-user/header/login.phtml' => __DIR__ . '/../view/adfab-user/frontend/header/login.phtml',
    'my-user/user/profile'       => __DIR__ . '/../view/adfab-user/frontend/account/profile.phtml',
),
),

You'll have to declare this new controller to bjyauthorize.global.php, _(*21)

'guards' => array(
    'BjyAuthorize\Guard\Controller' => array(
        //Front Area
        array('controller' => 'myuser_user', 'roles' => array('guest', 'user')),

The Versions

29/06 2018

dev-master

9999999-dev https://github.com/gregorybesson/PlaygroundUser

Module managing user

library user

Module managing user

playground/user

The README.md

PlaygroundUser

Introduction

Installation

Utilisation de Doctrine

Extending PgUser

Use your own User entity

Use your own Form

Use your own User controller

The Versions

dev-master

The Requires

The Development Requires

by Greg Besson

4.1.4

The Requires

The Development Requires

by Greg Besson

dev-develop

The Requires

The Development Requires

by Greg Besson

4.1.3

The Requires

The Development Requires

by Greg Besson

4.1.2

The Requires

The Development Requires

by Greg Besson

4.1.1

The Requires

The Development Requires

by Greg Besson

4.1.0

The Requires

The Development Requires

by Greg Besson

4.0.5

The Requires

The Development Requires

by Greg Besson

4.0.4

The Requires

The Development Requires

by Greg Besson

4.0.3

The Requires

The Development Requires

by Greg Besson

4.0.2

The Requires

The Development Requires

by Greg Besson

4.0.1

The Requires

The Development Requires

by Greg Besson

4.0.0

The Requires

The Development Requires

by Greg Besson

3.1.0

The Requires

The Development Requires

by Greg Besson

3.0.8

The Requires

The Development Requires

by Greg Besson

3.0.7

The Requires

The Development Requires

by Greg Besson

3.0.6

The Requires

The Development Requires