Rutas, controladores y respuestas

Hi AlejandroVillafane!

Hmm, that is super weird! So, no, you should not need to do anything like what's described in the StackOverflow post: it should work out-of-the-box. But let me explain, so we can maybe find the problem :).

When you start a new project (e.g. with symfony new my_new_project), one of the files that you should immediately have is config/routes.yaml, which looks like this:

controllers:
    resource:
        path: ../src/Controller/
        namespace: App\Controller
    type: attribute

THAT is what will load the "attributes" routes from your src/Controller directory. It looks slightly different than what's in the SO post, but it's effectively the same. So that poster IS right that you DO need a file like this... but it should be there without you doing anything :).

Do you have this config/routes.yaml file in your app? If so, what does it look like?

Cheers!

Thanks weaverryan
Yes, the file config/routes.yml exists.
But the content is different:

#index:
#    path: /
#    controller: App\Controller\DefaultController::index

That's the file content given with the project, without being modified.

Hi Alejandro!

Hmm, super weird. Are you starting a new Symfony 5.4 project? Basically, since Symfony 6.0, if you're starting a new app, your file should look like mine. But for 5.4 and earlier, the file would look like your version.

Cheers!

Hey @Michael-Kost

I'm guessing your routes are not being loaded for some reason, perhaps because you forgot to update the config/routes.yaml file. If you execute php symfony console debug:router what do you see? It should print all of your routes

Cheers!

I ran the following command

symfony console debug:router

and i got the following message:

Name Method Scheme Host Path

_preview_error ANY ANY ANY /_error/{code}.{_format}

yea, it means your routes are not being loaded. Double-check your config/routes.yaml file. If you're using PHP attributes you need to set the type key to attribute

When i open the config/routes.yaml file, i get the following

#index:
path: /
#controller: App\Controller\DefaultController::index

Ok, since you're in Symfony 5.4 you'll need to install doctrine/annotations and, of course use annotations on your routes (unless you're on PHP 8). You can find more info here: https://symfony.com/doc/5.4/routing.html

Cheers!

Hey Andromeda,

We're sorry to hear you have trouble with following this course! Could you share more information about your problem? Do you have problems with annotations? Do you see any errors? What errors exactly? Please, give us a bit more context and our support team will help you to fix it and move forward. Also important to know, did you download the course code and run the project from the start/ dir? Did you follow all the instructions in the README.md file? Did you ever run composer update command in your project?

About this specific course, we do have automated CI on it that tests course code on PHP 8.0 and 8.2 and it does not show any problems in this course. So your problem might be an edge case problem that isn't covered by our CI or it might depend on your specific setup. We definitely would like to know about it so we could make the course code even better.

Unfortunately, project maintenance is a required non-stop process. Along with framework development devs should upgrade their projects as well at least to support new PHP versions as you said.

Cheers!

No errors it just dosn't work there is some issue with symfony that is making the annotation routing not work I tried installing it with composer even and nothing it just doesn't work I suppose I could have fought it harder and more but I choose to give up it is way easier to program php than someone elses interpreation of what php should be. I then know what is going on and don't have to weave through miles of spaggettie and extreme bloatwear to find out what the issue is.

Hey @Andromeda,

The issue is that Symfony doesn't include annotation reader BTW it wasn't a part of symfony at all, it was part of Doctrine library so the easiest way to get annotations back is install doctrine/annotations package but with version constraint
use:

composer require doctrine/annotations:^1.14

also there might be required one more package: sensio/framework-extra-bundle

I hope we got the correct understanding of the issue you have, also I'd like to know why do you need the support of annotations? From my point of view it's not a perfect solution for metadata it also requires some additional code to work, I mean it's not the part of PHP itself so it may have performance downsides so that's why I'm asking!

Cheers!

Hey Benoit,

Did you have Symfony plugin installed? Please, make sure you have it installed and configured, but first - try to upgrade your PhpStorm to the latest version. Then, after all installs and upgrades - make sure to restart the PhpStorm IDE. Then it should work I think :)

Cheers!

Hey there,

My apologies for any inconvenience you may have experienced, but just to corroborate, is this the tutorial you got problems with? I'm asking because this tutorial was built with Symfony 6 and PHP 8

Hey Matthew,

Yes, but only if you're defining your routes with PHP annotations, but in a modern Symfony app, you'd be using PHP attributes

Cheers!

Hey Ariful,

Good question! But the legacy workaround is simple ;) You just need to change the order of your controllers, i.e. make that "photographer.index" controller going first, it will do the trick. Or, switch to yaml config instead of PHP Attributes for that exact controllers and place them in the correct order there.

Also, since Symfony 5.1 you can set the "priority" for routes, see the blog post with example: https://symfony.com/blog/ne... - so if you're on a newer version of Symfony - this will be the best option for you.

Cheers!

Hey jlchafardet

Could you double check your entities relationship? It seems to me that you have a OneToMany instead of a having a ManyToOne or OneToOne. If that's not the case I'd have to see your entitie's metadata and possible the form as well.

Cheers!

it is ManyToOne :S

<blockquote>
Entity
<br />#[ORM\ManyToOne(targetEntity: WalletProvider::class, inversedBy: 'coins')]<br />#[ORM\JoinColumn(nullable: false)]<br />private $walletProvider;<br />
FormType
`
$builder

->add('name')
->add('abreviation')
->add('coingecko_url')
->add('walletProvider', null, [
    'required' => false,
    'multiple' => true,
]);

<br />Controller<br />
#[Route('/new', name: 'app_coin_new', methods: ['GET', 'POST'])]
public function new(Request $request, CoinRepository $coinRepository): Response
{

$coin = new Coin();
$form = $this->createForm(CoinType::class, $coin);
$form->handleRequest($request);

if ($form->isSubmitted() && $form->isValid()) {

    $coinRepository->add($coin);
    return $this->redirectToRoute('app_coin_index', [], Response::HTTP_SEE_OTHER);
}

return $this->renderForm('coin/new.html.twig', [
    'coin' => $coin,
    'form' => $form,
]);

}
`
</blockquote>

Ok, try this in your form type

$builder
->add('walletProvider', EntityType::class, [
'class' => WallerProvider::class,
'required' => false,
'multiple' => false, # attention to this
]);

with multiple => false works, but that goes against everything I'm interested in having... I need it to allow me to select multiple providers.

I see.. then, you need to rethink the relationship of your entities. What you need is to have multiple WalletProvider objects inside your other entity (I believe its Coin). Or, you can create an intermediate entity that will hold the collection of WalletProvider per Coin record

The key here is that your Coin entity is holding a single reference of a WalletProvider object, but what you actually want is to hold a collection of them (OneToMany relationship)

so in this case, what I should do is "start" the relationship of "OneToMany" from walletProvider, or straight up go "ManyToMany" as many wallet providers can hold many coins??

Let me see if I can explain it better.

There are many coins, just as there are more than 1 WalletProviders(at least 2 at this time but could be more in the future)

there are also "Wallets", so each Wallet can hold many coins, but 1 wallet can only belong to 1 WalletProvider.

does that makes more sense?

and to complicate it more, the app manages "users"
so each user can have 1 or more wallet, and each coin can have an "amount" that is tied to both the wallet and the user.

user 1, wallet-from-walletProvider-1,
accepts: coin1 and coin2
coin 1 balance: 22
coin 2 balance: 5

Hey jlchafardet

Ok so, you'll need a ManyToMany relationship on your Coin - WalletProvider entities
Then, the Wallet entity will have a OneToMany to the Coin entity, and a OneToOne (or ManyToOne) to the WalletProvider entity

I hope it helps. Cheers!

will do my best :D hopefully works the way I want it to work.

I'll let you guys know.

Great! For your User relationship it's not that easy to tell because I don't know the use-cases of your application but just keep in mind that you can add an intermediate entity that work like thin wrapper between your relationships, it's quite useful for storing extra fields and for adding behavior to the entities.

The relationships are in theory fairly simple.

Wallet Provider (Binance, KuCoin for example, they offer exchance services for cryptocurrencies[it is not really that important as the app does nothing nor has anything to do with trades, trading or the likes, we want them just because we want to know who provides the eWallet for the users.) its just there for us to know who provides the eWallet service. Each Wallet Provider can have many wallets, and support many coins.

Wallet: the eWallet itself, where the User will receive their coins, each wallet can hold many coins. but belong to a single user, and each user can only register 1 wallet.

Coin: the cryptocurrency our app will manage (we have 2, but might add more in the future), Users earn Coins for doing stuff, sometimes is Coin 1, sometimes is Coin 2, and in the future we might add Coin X.

User: the user itself, email, name, last name, favorite food, name of pet, foot size...... you get the gist of it. Each user can have ONLY 1 wallet, but can receive more than 1 coin to their Wallet.

this is the "MVP" aspect of the app.

I also have a role in user, that is not in use yet, but in a future iteration I want to be able to assign "regular users" to "staff users" to manage. example, we have 100 regular users and 3 staff users, Staff user 1, manages user 1 to 33, Staff user 2 manages user 34 to 67, and staff user 3 manages users 68 to 100.

in that iteration I will want to display in those "staff user" dashboard, a list of their "managed accounts". so they can only see what they should see. but we can get to that later :D.

did this get you a little better picture of what I want to do with the relationships? (another thing important to note is, the app itself does nothing more than parse a bunch of logs that cli tools output, and displays them on screen)

Hey Michel,

Oh, this sounds like permissions error on Windows OS. You might need to double-check the permissions for that folder, but if you say that "rm -rf var/cache/" helps only until you edit a file and then the problem returns - most probably it won't help. I'd suggest you to put your project somewhere in a public dir, I see Symfony dir it's located in the root of disk C. Try to create a project somewhere in the user directory and try again, otherwise try to google this problem, most probably some Windows users may give you some hints over the internet.

Also, it might depends on how you run the PHP. If you're using a separate server like XAMPP, I'd recommend you to try to run it without admin permissions, or the reverse if you run it without admin permissions - it might help. Or probably better to install PHP natively in your system and use it directly with Symfony CLI built-in web server.

If no luck, I'd recommend you to take a look at Docker or other virtualization tools. Or probably better take a look at Windows WSL - Windows guys say that it's the best way lately if you're on Windows OS.

I hope this helps!

Cheers!

It seems that the Acronis anti-ransomware app is the cause of this issue
Thanks.

Hey Michel,

Ah, yes, some antiviruses might cause such errors too, good catch!

Cheers!