ongr-io/support

Simonas Šerlinskas

@saimaz

can you try with different name than _id?

and for the variant it should be used property

not id annotation

Jan

@funkdoobiest

i will try

renamed it to „product_id“ and it’s working, thanks :)

Simonas Šerlinskas

@saimaz

thats good to hear I could help

but actually it has to work with id

could you please create an issue about it and paste the elasticsearch structure

Jan

@funkdoobiest

sure

Simonas Šerlinskas

@saimaz

I will take a look later why _id or id isn’t working

Jan

@funkdoobiest

sorry, did not have time to dig deeper in this problem

but have an other question. how to map an array in elasticsearch document? is there an @ES\Property for this?

it’s just an array of image urls

so no need for a nested object

Mantas Marcinkevičius

@einorler

You can just provide a property type string, it can hold a single or an array of strings

Jan

@funkdoobiest

i see, thanks

Mantas Marcinkevičius

@einorler

No problem

Jan

@funkdoobiest

Hey

I want to generate a url in twig template for a product variant

but I am getting: Route 'The route object is fit for parsing to generate() method' not found")

I’ve used „SeoAwareTrait"

for the variant class

any idea?

in twig i am using: „path(variant)“. for a product it’s working

Jan

@funkdoobiest

fixed it

was my fault

Jan

@funkdoobiest

hm no, not fixed.

it’s working for product but not vor variant :(

Mantas Marcinkevičius

@einorler

whats your data structure? How do you implement variants?

Jan

@funkdoobiest

<?php

namespace AppBundle\Document;

use ONGR\ElasticsearchBundle\Annotation as ES;
use ONGR\RouterBundle\Document\SeoAwareTrait;
use ONGR\RouterBundle\Document\SeoAwareInterface;


/**
 * @ES\Nested
 */
class ProductVariant implements SeoAwareInterface
{
    use SeoAwareTrait;
}

Mantas Marcinkevičius

@einorler

hmm...

Jan

@funkdoobiest

'Route 'The route object is fit for parsing to generate() method' not found': Document is not correct or route cannot be generated.

Mantas Marcinkevičius

@einorler

i would suggest simply using a link to a product with a correct id of a variant in the requst query and let the twig handle the correct variant to display

Jan

@funkdoobiest

we need real urls for SEO

Mantas Marcinkevičius

@einorler

that way you wouldnt need to use the trait in the variant at all

it is a real url to a product

Jan

@funkdoobiest

yes, but not the same as before

and I need this specific urls for seo

Mantas Marcinkevičius

@einorler

difficult to say whats wrong in your situation, but it may be that if you insist on having the urls generated for variants and the problem is deeper, it may be that you will need to create a custom router

the shrot description on how to do it is in the docs right now, a lot more in depth one will be accessible in the docs shortly

you coud try to debug the generate method in ONGR\RouterBundle\Routing to see whats going wrong

Mantas Marcinkevičius

@einorler

i ment ONGR\RouterBundle\Routing\DocumentUrlGenerator :)

Mantas Marcinkevičius

@einorler

I've just taken a quick look at the ONGR url generator

you should check if its so, but it seems, that it will not return a correct type because the variant is not a ES document, but a nested object

look at the line here: https://github.com/ongr-io/RouterBundle/blob/73b64e2291f2a68e063960d32b5ac294358a6119/Routing/DocumentUrlGenerator.php#L77

this may be the problem in your case

Mantas Marcinkevičius

@einorler

This message was deleted

Jan

@funkdoobiest

thanks, I will have a look

Jan

@funkdoobiest

problem is routing is just for „Document“ type not for „nested"

Where communities thrive

People

Repo info

Activity