A I mentioned, it's recommended to upgrade for a premium type of membership if you wish to interact with others, to look at their full-sized sex pictures or to access additional advanced features.

Xxxprofiles chat line-29Xxxprofiles chat line-89Xxxprofiles chat line-87

I am currently trying to build a (hopefully fast) Website in Symfony2.

I am using the FOSUser Bundle to manage Users easily.

But that always results in the Error: Service Not Found Exception in Check Exception On Invalid Reference Behavior line 59: The service "security.authentication.manager" has a dependency on a non-existent service "provider.concrete.fos_userbundle".

If I enable both User Providers the Error disappears but the User Manager ist still ignored.

I wrote a custom Cache Manager to store Entities in Redis and to fetch back valid Entities that are managed by Doctrine.

My custom User Manager uses this Service to provide Users Data faster. had to replace the Project Name by 'XXX'): fos_user: db_driver: orm firewall_name: main user_class: XXX\Main Bundle\Entity\User registration: form: type: XXX_user_registration validation_groups: [XXXRegistration] confirmation: enabled: true template: XXXMain Bundle: E-Mail:registration.twig from_email: address: [email protected] will not help much when FOSUser Bundle loads the user by username (because the ORM uses the id as identifier in its SLC, not the username), but this happens only when submitting the login form, or when reading a remember-me cookie if you use this feature.However, it will work for where the user is loaded by primary key (and also in every other place of your project needing to load a user by primary key).Doctrine will also take care of updating the cache when the user is updated so you get valid data (be sure that you don't edit the user without using the ORM though).And if you want to optimize the loading of user by username, you could write your own User Provider which could keep a mapping between usernames and primary keys in Redis and then ask Doctrine for the User object by primary key (which would read it from the ORM cache then), while keeping a refreshing by primary as done in FOSUser Bundle own provider (this is done for security reasons).It returns the User from the Cache but Symfony2 still triggers a DB Query to fetch the User.