make:user

Hey odds,

Yep, that's the reserved word in SQL, it may work though with ticks, i.e. SELECT * FROM `user` , but better to avoid it, i.e. rename, though not the DB but the user table, e.g. to something like app_user, etc.

Cheers!

Hey @discipolat

Usually inheritance is not a good idea because it makes the code base more complex. I recommend using composition or PHP treats to share some common code among your user type classes. Also, applying inheritance to Doctrine is not always easy. So, unless you got a strong reason to use inheritance I suggest avoiding it

Cheers!

Are you going to use the same login form and route for everyone? You'll need to write a custom authenticator and perhaps an extra field to determine what type of user is logging in
https://symfony.com/doc/current/security/custom_authenticator.html

Hey @t5810 ,

When you call that bin/console make:registration-form - it will ask you "Enter the User class that you want to create during registration". So, I suppose you would need to specify the corrrect entity there instead of the default App\Entity\User, i.e. specify there namespace of those Company/Freelancer entities and that should work I suppose :)

Cheers!

HI Victor

Thanks for the prompt replay. When I type symfony console make:registration-form console reply with:

Creating a registration form for App\Entity\User

 Do you want to add a #[UniqueEntity] validation attribute to your User class to make sure duplicate accounts aren't created? (yes/no) [yes]:

So, I have no way to change the entity for which the registration form will be made.

The only option that I have is: to commit all my changes, and then to proceed with making the changes for the user, and then manually to make the same changes for the Companies and Freelancers, and to revert the changes for the Users.

However, I am trying to learn best practices of using Symfony, and I am not sure if this approach may be considered as such.

Any suggestion will be deeply appreciated.

Regards

Hey @t5810 ,

Hm, probably you're not on the latest version of Maker bundle. Try to update Maker bundle to the latest version first and try again :)

Otherwise, you can generate it for the User entity but then manually tweak the generated code replacing User with other entity you need - also a valid way because the generated code is just a boilerplate that is suppose to be changed for you specific needs :)

Cheers!

Hi Victor

I upgrade the symfony/maker-bundle to the latest version 1.50.0, same command:

symfony console make:registration-form

Same reply:

Creating a registration form for App\Entity\User

 Do you want to add a #[UniqueEntity] validation attribute to your User class to make sure duplicate accounts aren't created? (yes/no) [yes]:

By the way, I have send you an invitation to the repository, to avoid making this thread too long if that can help somehow to resolve the issue.
Regards

Hey @t5810 ,

Hm, I'm also on the latest v1.50.0, but in the very beginning the command asks me:

Enter the User class that you want to create during registration (e.g. App\Entity\User) [App\Entity\User]:

Probably try to go further, it might be the next (2nd) question for you... because I do have that UniqueEntity and that's why probably it does not ask me :)

Unfortunately, we do not have the bandwidth to look at personal project issues. Anyway, as I said, you can generate a boilerplate code with this command and then change the entity to whatever you want in it.

Cheers!

Hi Victor

Thanks for your advice. I will create the code for the user and then manually create the code for the rest of the entities that I need.

Thanks.

Hey @t5810 ,

Yeah, sounds like a good strategy. Maker bundle is meant to be a helper that will generate some boilerplate code for you anyway, but you would need to tweak it eventually.

Cheers!

Hey @reflex!

Hmmm. Is the failing migration fully creating the new user table? Or does it somehow exist and you're altering it? If I'm reading this correctly, the error indicates that there is already a user table... and this user table already has rows in it. So, when the email column is added (which does not allow null), it doesn't know what value to put for those.

If I'm correct, the fix for this is to either:

A) If you don't have anything deployed to production yet, this isn't a real problem as you won't have this situation on production where you already have rows in your user table. Just drop your database entirely and restart:

symfony console doctrine:database:drop --force
symfony console doctrine:database:create
symfony console doctrine:migrations:migrate

B) If your user table IS already on production, you'll need to be a little fancier:

1) Modify the migration to allow email to be null
2) Add a new line after this in the migration that assigns every existing user some value for their email column (no idea how you would do this - it depends on your business logic).
3) Run the migration
4) Ron make:migration again: it will generate a final migration that will simply change the email column to no allow null.

Let me know if this helps :)

Cheers!

thanks a lot,
I am not sure about the real root cause, but I tried this fix multiple times until it worked,
after executing

symfony console doctrine:database:drop --force
symfony console doctrine:database:create
symfony console doctrine:migrations:migrate

I had some different error messages like An exception occurred while executing a query: SQLSTATE[42704]: Undefined object: 7 ERROR: index "uniq_8d93d6495e23 <br /> 7e06" does not exist and An exception occurred in the driver: SQLSTATE[08006] [7] FATAL: database "app" does not exist similar to this one :
https://stackoverflow.com/questions/27915200/cannot-create-postgres-database-with-doctrine

so I just reverted the repo to the state before installing doctrine and security bundle, and retried going step by step again, things seem to work fine now, thanks for the suggestion and sorry for the late reply!!

Woohoo! Sometimes there are just weird gremlins in the code - good thinking to back up :).

Hey Rufnex,

My apologies, but I didn't understand your question. Do you mean how to define a custom table/field name?

Cheers!

i still don't understand how the security logic works exactly. if you use it, a user table is created. But if I already have a table with user data that has a different name and the password field is different. how would I have to adjust the classes?

You can re-use your existing user's table, you only need to specify the name of it

#[ORM\Table(name: 'your_table_name')]
class User
{
    #[ORM\Column(name: 'field_name')]
    private string $password;
}

Does it answer your question?

Sounds easy ..

To rename the entire class to e.g. MyUserClass is not a good idea?

I will try it. Thank you!

you can name whatever you want to your user class as long as it implements the UserInterface

Cheers!

After i playe arround the whole day, no i'm clear with auth ;o) Thank you.

Hey The_nuts,

Yeah, as soon as you implemented that new getUserIdentifier() - you definitely may keep that getUsername() method as well. The new system will use the getUserIdentifier(), but in your custom code you may continue using getUsername() of course. Actually, I think the deprecation should gone right after that method gone from the interface where it's deprecated.

Unfortunately, no the exact guide about how to migrate from old system to the new one, but we covered it partially in this course, so you basically should port your current system into one we shows in this course.

I hope this helps!

Cheers!

Hey Franck,

I think the first option should be better IMO, and it also will lead to less entities in your project, but really it may depends on your specific case, i.e. how different data should be for those different account types, how many data you will store there, etc. The best would be to implement both cases and profile with a special tool like Blackfire.io that will give you some numbers and you will see what fits better for you. We have a separate course about this tool btw: https://symfonycasts.com/sc...

Cheers!

Hey vespino_rojo!

The Docker + Symfony web server integration is kind of... "half Docker". It uses Docker to launch any services you have - e.g. database, Elasticsearch, etc - but you still have php installed locally and Node if you want to build the web assets. We're thinking of providing some Docker configuration to the code downloads to make life easier for users that want to use full Docker, but we don't have that yet.

Oh, but about the JS assets. You do not need to build the JS in this tutorial. Because this tutorial is all about security (and not JS stuff), we shipped the pre-built JS & CSS files you need in the public/build directory. So once you launch your web server, those files will simply be there: there is no need to run Webpack/Encore or anything else. We list this as an "optional" step in the README... and it really is optional - you an skip it entirely.

Let me know if that helps!

Cheers!

Hey Gustavo D. !

Yup - one more tomorrow - then we'll start again next week. We usually do one per day - we MAY go faster on this tutorial, but I'm not sure yet. I know, it sucks when the tutorial first comes out and things are slow - apologies!

Cheers!

Hi! Can you record a video that will show how to show a list of everyone I invited via a referral link on the site?

Hey @Работа На дому Интернет работа!

That, unfortunately, will not make it into this video :). But here is how I would implement that. A referral link is fairly simple. First, on your User class, you would probably have something like a referralCode property that stores some random, unique string. This is used to build the referral link. The route for that page would look something like /refer/{referralCode}. In the controller, I would store the referral code in the session and redirect to the registration page. Then, in the registration controller - right after success, but before redirecting - I would check to see if there is a referral code in the session. If there is, I would find which User that referral code belongs to and update something in the database to track this. For example, on the User class, you could add a referredBy ManyToOne to User. So, on the NEW User record, you would call $newUser->setReferredBy($referralUser) where $referralUser is the User that the referralCode belongs to.

Good luck!