Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No route for details of order #401

Closed
ghost opened this issue Oct 13, 2013 · 10 comments · Fixed by #404
Closed

No route for details of order #401

ghost opened this issue Oct 13, 2013 · 10 comments · Fixed by #404
Labels
Potential Bug Potential bugs or bugfixes, that needs to be reproduced.

Comments

@ghost
Copy link

ghost commented Oct 13, 2013

Hi everyone,

I usera fresh Sylius installation.
Almost everything works fine.

But I have an annoying problem.
I just create an account, everything looks good, I'm automatically connected with it, I do some orders, but when I try to see the details of an order, I have a no route found error :

No route found for "GET /account/order/"
404 Not Found - NotFoundHttpException
1 linked Exception: ResourceNotFoundException »

What is going on ?

Thanks ;)

@ghost
Copy link
Author

ghost commented Oct 13, 2013

@stloyd : So actually, it's impossible to see the details of any order ?

@ghost
Copy link
Author

ghost commented Oct 13, 2013

I just see the HTML code of the account/orders page, you could see the problem : there is no ID for the order... :

                                <tr class="order" id="order-">
                    <td>October 12, 2013 22:24</td>
                    <td></td>
                    <td>82,46 €</td>
                    <td>
                            Ready since October 12, 2013 22:25
                        </td>
                    <td>
                                                        -
                                                </td>
                    <td>


<a class="btn  btn-default " id="order--details" href="/sylius/web/app.php/account/order/">
        <i class="icon-book"></i>
    details
                    </td>
                </tr>

@Richtermeister
Copy link
Contributor

@jujusous3 The issue is that order numbers were not generated during the checkout, so viewing order details fails (needs order number in url). There are 1-2 tickets being worked on right now that are going to fix this. Hang in there :)

@ghost
Copy link
Author

ghost commented Oct 14, 2013

OK thanks ;)
I just need an info, I have a Sylius project installed, how I could update it with the last bug fix ?
If I just do a "composer update" it's ok ?

Also, I don't really understand how it's works here.
When someone commit a bug fix, the correction is not online immediately ?

Thanks for your help ;)

@Richtermeister
Copy link
Contributor

@jujusous3 Complicated subject. The development of the main project takes place at Sylius/Sylius (here), so if your project is a clone of this repo, you can pull updates from here immediately when they appear.

However, this repo is really intended for development, not to base your project on. For that you want to use Sylius/Sylius-Standard (https://github.com/Sylius/Sylius-Standard), which pulls all bundles as vendors via composer. In that case, yes, you pull updates via composer update, but those externals only update every few hours (they are subtree splits from the main repo).

Have I confused you sufficiently? :)

@ghost
Copy link
Author

ghost commented Oct 15, 2013

@Richtermeister
Thanks for the quick reply !
If I understand, to contribute to the project, I could get Sylius/Sylius, and to create a new project and use all bundles as vendors, I need to install Sylius/sylius-standard ?

If I'm right, anything works, could you help me a little please ? :)
I create a ticket here : Sylius/Sylius-Standard#3

@Richtermeister
Copy link
Contributor

@jujusous3 Yes, that is right, and yes, Sylius-Standard is probably a bit buddy right now (fast development going on right now). But, I will help out get it working. I have a need for it as well..

@ghost
Copy link
Author

ghost commented Oct 16, 2013

Ok, I'm a little confused...
Sylius seems quite new, and in development, but reading some news about it, like on : http://sylius.org/get-started , it's not clear. I thought it was possible to use Sylius, but apparently there is no way to build a project with Syrius just now :/
But so how the website in the "ShowCase" did ?

I need quickly to begin the development of a new website, is there anyway to use Sylius properly without using standard edition ? I understand the developers are busy, I just want to have some informations to try to do that by me own ;)

Thanks ;)

@Richtermeister
Copy link
Contributor

@jujusous3 The other developers did it with a fair amount of custom work I assume :) But not as much work as they would have needed if they had started from scratch..

If you quickly need something fairly solid up & running, you can just fork the Sylius/Sylius project and work in there. You can pull in updates via git to keep up with development.

What I did for now is create a bundle for MY project, and I have it extend the SyliusWebBundle. That way I can override everything I need customized.

Eventually I will drop my bundle into the Sylius/Standard-Edition, and with some minor config tweaks the migration should be pretty easy.

Does that help?

@jjanvier
Copy link
Contributor

@jujusous3 For the projects of the showcase, most developers used the Sylius' bundles (and not the whole app) as far as I know. That's what I did too. For a custom project, Sylius Standard Edition is the way to go, even if it's very young. This should evolve quite quickly in the next weeks.But if you know Symfony you should be able to build your project with Sylius Standard. And this will be even easier when the documentation will be up to date.

pamil pushed a commit to pamil/Sylius that referenced this issue Mar 21, 2016
…ce-documentation

Mention requirement to implement ResourceInterface
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Potential Bug Potential bugs or bugfixes, that needs to be reproduced.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants