-
Notifications
You must be signed in to change notification settings - Fork 332
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
Just nothing works... #3
Comments
The order number generation problem has been fixed. Sorry for the trouble, this standard edition is quite new, I'll make sure it works properly and move the fixture images to the bundle, which seems to be the cause of problems. |
Thanks for the quick reply ;) But I have some difficulties to understand, if I want to use Sylius and develop some specifc things, I really have to use this Sylius/sylius-standard ? Thanks |
I add the image folder for fixtures, the installation work great.
Edit : After a composer update, I now have this error when I finalize :
Catchable Fatal Error: Argument 1 passed to Sylius\Bundle\InventoryBundle\Operator\BackordersHandler::processBackorders() must be of the type array,
object given, called in /Users/Juju/Sites/sylius-standard/vendor/sylius/inventory-bundle/Sylius/Bundle/InventoryBundle/Operator/InventoryOperator.php on line 86
and defined in /Users/Juju/Sites/sylius-standard/vendor/sylius/inventory-bundle/Sylius/Bundle/InventoryBundle/Operator/BackordersHandler.php line 45
|
@jujusous3 A bit strange error, in next few moments I'll update the SE accordingly so it works nicely. |
@pjedrzejewski Thanks for the reply. In fact, it's not so weird, the InventoryBundle seems to be not the good version. |
I fixed the inventory error, the reason was simple, packagist did not update |
Thanks for your help ;) |
Always got the error :
A new entity was found through the relationship 'Sylius\Bundle\CoreBundle\Model\Order#user'
that was not configured to cascade persist operations for entity: xxxx@gmail.com.
To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or
configure cascade persist this association in the mapping for example @ManyToOne(..,cascade={"persist"}).
Anyone has an idea of why ? I tried to change the version of the different bundle, but nothing works... :/ Thanks ;) |
Not an issue anymore. |
Hi !
I want to build a new project using Sylius.
It seems really awesome, but it's been an entire week I'm facing to installation errors, bugs in the application...etc
If I understand, for a new project, I have to use sylius/sylius-standard.
So I do :
composer create-project -s dev sylius/sylius-standard
(on the http://sylius.org/get-started, the "-s dev" is not present, but without it it doesn't work).
Next, I do :
cd sylius/sylius-standard
php app/console sylius:install
Everything begins good, but at the end I have an error :
[InvalidArgumentException]
The "/Users/Juju/Sites/sylius-standard/app/../web/fixtures" directory does
not exist.
So, I create this folder manually, next I do :
php app/console doctrine:fixtures:load
But now I have this error :
[Symfony\Component\Debug\Exception\ContextErrorException]
Notice: Undefined index: Sylius.Image.sticker in /Users/Juju/Sites/sylius-s
tandard/vendor/doctrine/data-fixtures/lib/Doctrine/Common/DataFixtures/Refe
renceRepository.php line 145
So, even if I have this error, I try to go to the website.
It seems work, I place an order, but when I finalize the order (checkout/finalize/forward), I have this error :
A new entity was found through the relationship 'Sylius\Bundle\CoreBundle\Model\Order#user' that was not configured to cascade persist operations for entity: sylius@example.com. To solve this issue: Either explicitly call EntityManager#persist() on this unknown entity or configure cascade persist this association in the mapping for example @manytoone(..,cascade={"persist"}).
So, is there anyway to make Sylius works ?
Before that, I used Sylius/sylius, all works good, but there was a big bug (no number generated for orders) so customers can't simply see there orders...
Any help ? I'm desperate ...
Thanks a lot ;)
The text was updated successfully, but these errors were encountered: