Developer forum

Hi Adrian

Can you maybe send me a link to your solution?

The data in EcomShopLanguageRelation is handled on the shop settings:

Hi Nicolai,

Here you go: https://ascom.ignite.commergent.ro/
I don;t see the Workflow section at all:

Moreover, I have tried for a few hours already to make the setup display the Product list based on GroupID and product detail page, but with no luck. The group links are not evaluating the GroupID: https://ascom.ignite.commergent.ro/nl/products?GroupID=GROUP1 and Product details return 404.
I have compared my setup with the standard Swift but I could not spot any relevant differences.
It would be a huge relief if you managed to find out what is wrong.
Thank you,

Adrian

Hi Nicolai, 

Any news for me?

Thank you,
Adrian

Hi Adrian,

could you share credentials for an user has administrator rights on the solution above to have a look, I do not have angel access.

BR, Oleg QA

Hi Oleg,

I don't think that I have your email address. Can you please share it?

Thank you,
Adrian

you can see my email address as tooltip when over the name under my photo.

Oleg 

Cool! I did not know that :)

I have sent you an email with all the details.

Thank you,

Adrian

Hi,

1. regarding EcomShopLanguageRelation table, it's matter not used in DW10 and related to languages can be managed on shop edit page in DW9 only. Existing data can be found inside if related to an old db restored.

2. regarding absent of data in shop edit on your solution, it's fixed by reinstalled trial license.

3. regarding 404 on https://ascom.ignite.commergent.ro/nl/products?GroupID=GROUP1, since you want to use name of site in URL, so it fixed by setting the options as follows: you website was renamed as "NL", option "Do not include URL in subpage URLs" was disabled in the site settings, option "Use website name" was enabled in Settings-WEB & http-Frendly URLs. Please, check the link.   

4. regarding 404 on product details. It seems to be related to not valid scheme of import activity you used, the mapping seems not to be follow some required conditions. I've tried to import product via file like yours but via "Import" feature on new created product group. The mapping had simple matching like product name, number and short\long descriptin (note parent group is mapped by default in UI). I've updated price+stock and rebuild index. You can sure that it's OK via link. So, you have to check an product added via your activity and my one in db to find a mismatching (I don't have access to yuor db to edit etc.). Besides, I've asked DW guy - integration expert to have a look at your activity as well.

BR, Oleg QA 

Hi Oleg,

Thank you very much for the detailed response.

I will start investigating your actions and I will get back to you with questions if any.

Thank you,
Adrian

Hi Oleg,

I believe I understand everything you did on points #1-#3.
I am still confused about the 404 on products.

I have checked the database and compared your products with mine (I already did the same thing comparing a product added through the interface and an imported product).
I have compared the records in EcomProducts and EcomGroupProductRelation, and there is nothing obvious between your products and mine.
Is there any other table I should check for comparison?

Thank you,

Adrian

Hi Adrian,

Let's wait to replay of DW integration expert who can comment the issue fully I suppose and knows which table(s) and fields should be mandatory in the product import.

Oleg QA

Hi Adrian,

I checked the issue 4 but did not yet have any answer about cause. I've added new products via new integration activity is copy of yours as well as via general UI or copy of an failed one on my test group. Them are shown in product details page correctly, try details in the list (e.g. details) but I see 404 on product mentioned via link above added and rendered correctly yesterday...WTF. Besides I see error exception on deleting an added product and related to permissions not shown evidently. I cannot reproduce the issues on Swift2 solution based on last DW10 admin, so I'm confused. Try to use last admin version and submit case to support if still reproduced and relevan.

Oleg 

Hi Oleg,

Is there any way of checking the friendly URLs?

I am guessing some index is updated with wrong data.

With solutions starting from standard Swift, I never had an issue. But the manual setup should work just as well considering that will be situations where a new Swift2 instance should be added to an existing project.

How should I proceed further in identifying the issue?

Thank you,

Adrian
 

Hi,

as I've said above, try to use last DW10 admin to exclude an URL builder issues could already be fixed by now. See hints and tooltips on options at Settins-Web & HTTP-Friendly URLs allow to understand applying of it when enabled\disabled on DW10. Refer to manual describes the feature in DW9.  

Oleg

Hi Oleg,

What do you mean by "last DW admin"?
I am running on DW 10.16.5. I have other test solutions running on the same version with Swift2 without any issues when importing products.
 

Adrian

Hi Adrian

I am also looking into this - and I cannot figure it out.

It is not a URL issue - I checked that - it will also give 404 for a product not using the friendly urls.

On this page I added a new product - using the UI:

https://ascom.ignite.commergent.ro/nl/products/mobility/handsets/smartphones

It is just called "d" and I can access that: https://ascom.ignite.commergent.ro/nl/products/mobility/handsets/smartphones/d

Then I rebuilt the assortments - and I could not see it.

Now I have added an anonymous assortment with all products, and I can see all of the products.

So it seems like there is a bug related to "Enable assortments" setting - that it does not take affect for product detail pages.

BR Nicolai

Bug # 24917

Hi Nicolai,

Thank you for confirming it, I was going insane debugging this.

I believe I have also mentioned a potentially similar bug in DW 9.19 a while ago. If you have assortments defined, even if they are not activated, the assortment check will still kick in.

Maybe it is the same issue.

Thank you

Adrian