search

craftcms / commerce

Fully integrated ecommerce for Craft CMS.
https://craftcms.com/commerce
Other
226 stars 170 forks source link

Can't have urls for my products #369

Closed echantigny closed 6 years ago

echantigny commented 6 years ago

Database driver & version: MySQL 5.7.21 Craft CMS: Craft Solo 3.0.10.2 Craft Commerce: 2.0.0-beta.5 Redactor: 2.1.0

For some reason, it seems that I can't have urls for my products. The checkbox for it doesn't even exist in the Product Type section. Is this an issue or I'm missing something? I've been looking at this page to confirm my thought: https://github.com/craftcms/commerce-docs/blob/v2/en/product-types.md

2018-06-07 10_29_43-clothing - great boardgames

echantigny commented 6 years ago

Oaky, this is not an actual bug, but it was confusing. A product doesn't have a url if you only have the title field in there. Adding a description field made the url active.

The documentation is also false now though, and it also makes the demo products a bit confusing.

lukeholder commented 6 years ago

You shouldn't need a custom field like 'description' to get URLs for products to work.

See http://jmp.sh/25IHPfJ

Can you explain further what you are experiencing? Could it be that you didn't have a template set up for the product URL to resolve to?

echantigny commented 6 years ago

Hi @lukeholder ,

From what I remember, it was a clean install:

1- Install Craft 3 2- Install Craft Commerce 2 3- Look at the site (all default products and templates at this point)

When I got to the products listing, nothing was clickable. I added a field (description wysiwyg) and then all the products became clickable. All this with the basic templates that comes with the plugin.

If needed, I can definitely try a new install and see if I can replicate that. I played around a lot with it since then.

mediabeastnz commented 6 years ago

This is still happening in 2.0.0-beta.11. As @echantigny said, adding one field triggers the ability to view a product.

lukeholder commented 6 years ago

This has now been fixed for the next release.