Jump to content

Malemi

Members
  • Posts

    47
  • Joined

  • Last visited

Posts posted by Malemi

  1. Hello,

     

    1. Create a new product combination.
    2. Get back and try to edit a single combination of the same product.
    3. Cannot add or remove, or simply change any attribute value on a combination being edited. We do not have this option as on PS 1.6

     

    Result: Once created a set of product combinations, we cannot change/add/remove any attribute value on a single combination basis.

     

    Expected Result: As on PrestaShop 1.6, we need to be able to edit attribute values on a single combination basis.

     

    That is big issue, each time we need to change a value of a single combination we would need to generate the whole set of combinations!

     

    A poor workaround is deleting the targeted single product variant and set up a new one !

     

    That means spending much more hours to update products.

     

    That works great on PS 1.6, just editing and switching any single attribute value on a specific combination. No need to delete the whole combination and create it again.

     

    Thank you
    BR

  2. Hello, me using PS 1.7.2.1

     

    This seems to me so unbelievable that me cannot believe it being real (maybe me doing something wrong):

     

    1. Create a new product combinations set.

    2. Get back and try to edit a single combination of the same product.

    3. Cannot add or remove, or simply change any attribute value on a single combination being edited. We do not have this option.

     

    Result: Once created a set of product combinations, we cannot change/add/remove any attribute value on a single combination basis.

     

    Expected Result: As on PrestaShop 1.6, we need to be able to edit attribute values on a single combination.

     

    That is  big issue, each time we need to change a value of a single combination we would need to generate the whole set of combinations!

     

    A poor workaround is deleting the targeted single product variant and set up a new one !

     

    That means spending much more hours to update products.

     

    Taht works great on PS 1.6, just editing and switching any attribute value on a specific combination in a set of combinations. No need to delete the whole combination and create it again.

     

    Am I wrong, am I doing something wrong as using PS 1.7 product variants ?

     

    Any help appreciate.

     

    Thank you

     

    BR

     

     

    I thought PS 1.7 would reduce products time editing, that was a declareted objective.

     

    In fact it is not, worst than PS 1.6

  3. You'll have to change it manually in database : ps_configuration : "PS_ROUTE_product_rule".

    Then go to category page, your links are now with ?variant=...

    But if you look at the product page and select a combination, it doesn't work (product refresh).

    Some work (in controllers) have to be done to get it working.

    The # part is useless in ps 1.7 because Prestashop get the id_product_attribute in url before # part.

    This was not the case in ps 1.6, some javascript read it and refresh product.

     

     

    Hi _tech

     

    Thanks for helping us!

     

    Me, I am not able to get this working, do not know how to modify controllers and BD.

     

    Any help is appreciated

     

    Anyway a big thanks to you, _tech !

     

    Let me please stress our requirements to PrestaShop team in order to fix product URLs for PS 1.7 as soon as possible.

     

    Guys, please go deep in this, uniques URLs is a must, users play with URLs, sharing, linking, talking around there, etc.

     

    The more URLs are clean, the better are getting around !

     

    Thank you

  4. Hello,

     

    It is possible to do like spotify but with Prestashop : http://examplemyshop.com/category/[id-product]-rewrite.html?variant=[id_product_attribute]

    (a rule like that : {category:/}{id}-{rewrite}{-:ean13}.html?variant={id_product_attribute} )

     

     

    Thank you _tech 

     

     

    have been trying yours out:

     

    {category:/}{id}-{rewrite}{-:ean13}.html?variant={id_product_attribute} 

     

    Getting the following error:

     

    :(

     

    The route {category:/}{id}-{rewrite}{-:ean13}.html?variant={id_product_attribute} is not valid

     

    Same as using "#" instead "of" ? (as on PS .6):

     

    The route {category:/}{id}-{rewrite}{-:ean13}.html#{id_product_attribute} is not valid

     

    :(

  5. Please, let me share with you how Shopify works product variants:

     

    https://www.allbirds.com/products/mens-wool-runners

     

    /products/mens-wool-runners

     

    /products/mens-wool-runners?variant=40210878599

     

    /products/mens-wool-runners?variant=22238446727

     

    Base URL is not being changed because of product variants, they just add "?" followed by IDs

     

    That is how PS 1.6 works: attributes following a "#".

     

    Please have a look at attached pics: Shopify does use "canonical" tag BUT internal links are clean, those inetrnal links to product do not show any combinations (as per PS 1.7)

     

    Please, go on this page and hover on menu internal links to any products: URLs are clean https://www.allbirds.com/

     

    Do the same on PS 1.7, inernal links to products depend on default combination ( look at pics attached in this bug report http://forge.prestashop.com/browse/BOOM-2804 ) This is another big issue on PrestaShop 1.7 !

     

    I think internal links to products should be to the canonical URL, not to default combination one ( please, look at attached pic showing PS 1.7 internal links to products).

     

    Thank you

    Greetings

    post-915280-0-72976000-1494319704_thumb.jpg

    post-915280-0-27426400-1494319705_thumb.jpg

    post-915280-0-36762000-1494319713_thumb.jpg

  6. And in my opinion it is not necessary. Read about canonical urls, prestashop uses this kind of feature to avoid DC.

     

    Thank you vekia.

     

    Canonical is fine, we all know about it.

     

    Canonical is for search engines (not all) not for web users! What about social links, web page links, etc ?

     

    We need a unique URL for the same product because web users interacts with it, they are used to sharing as well as websites sharing, links, pingbacks, etc.

     

    What do you think about a product variant being sold out? Any link to is going to be lost > big drop in web trafic because of link changes > bad SEO because of traffic and reputation lost.

     

    What about switching among default combinations? URL is being changed and not redirected > big drop in web trafic because of link changes  > bad SEO because of traffic and reputation lost.

     

    What about Default combination being showed in internal links? Please have a look at those pics http://forge.prestashop.com/browse/BOOM-2804

     

    Canonical is just a way to talk with search engines.

     

    vekia: you know, efficient SEO is not just about "canonicalization" and put "canonical" tag in head, SEO is much more nowadays.

     

    Users is our real world, they are "our clients", our best SEO !

     

    Why does WooCommerce, Magento and Shopify, why do they not change base-URLs behaviour?

     

    Why does PrestaShop 1.6 behaves correctly?

     

    For those reasons we need URLs to keep immutable even if we change product attributes.

    • Like 4
  7. It seems PrestaShop 1.7 is absolutely bad for SEO

     

    That is because each product variant generates a product URL !

     

    Same product = tons of URLs !!

     

    https://www.prestashop.com/forums/topic/554789-how-to-remove-id-product-attribute-from-product-links/

     

    http://forge.prestashop.com/browse/BOOM-2804

     

    In PS team opinion that is not a bug: http://forge.prestashop.com/browse/BOOM-2737

     

    Cannot believe this being real

  8. Hello, 

     

    Please, follow this link to check-out a Magento 2 demo and look how product combinations works:

     

    http://magento2-demo.nexcess.net/hero-hoodie.html

     

    Not any URL change as a client switches among product combinations.

     

    That is far better for SEO !!

     

    Why does PrestaShop 1.7 modify URLs as a client switches among combinations ?

     

    Might someone give us a logical explanation ?

     

    Thank you

     

    Best regards

  9. Hi vekia,

    Thank you for clear this up: confirmed, those red numbers are IDs of combination.
     

    As i already mentioned this is id of selected combination so-called id-product-attribute (technical nomenclature). Product pages will not work properly without this id.



    Question 1 is: why does PrestaShop 1.6 not use IDs of combination?
    Question 2: is PrestaShop team aware of URLs duplication due to this issue ?

     

    this is not an issue This is a part of core features, this is how prestashop 1.7 is developed

     

    vekia: do you really think this is not a SEO issue ?

    I mean, we are not talking this being a PrestaShop issue, obviously it is not a bug.

    It is a SEO deep, very deep problem because of URLs duplication.

    vekia: might you please give your point of view as far as this SEO problem ?

    Thank you

  10. Hello vekia,

     

    You had the opportunity to work out PS 1.7 in order to build up your addon, might you please tell us what exactly those red numbers are ?

     

    They are not product ID, nor attribute ID, what are they?

     

    Product ID is "2" number, blue colored in the following example.

    Attribute ID are green number.

    What exactly is red number on those URLs?

     

    /en/blouses/2-7-blouse.html
    /en/blouses/2-8-blouse.html
    /en/blouses/2-8-blouse.html#/1-size-s/11-color-negro

     

     

    prestashop product pages requires this param to properly identify the product's attributes change.

     

    The only one way to remove the id of product / id of attribute or both of them is a module that removes id numbers from urls. 

  11. Hello vekia,

     

    Issue is not exactly id_product_attribute

     

    Please have a look at URLs, we are talking about "7" number

     

    We do not know what exactly is "7" number in URLs, I guess it is the combination_id

     

    /en/blouses/2-7-blouse.html

    /en/blouses/2-7-blouse.html#1-size-s/11-color-black

     

    Green part is not a problem, as it works like on PS 1.6

    Red is our issue

     

    At the beginning of this thread we all believe issue is because of id_product_attribute.

     

    Not exactly!

     

    What is 7 number in combination URL ?

     

    I guess is id of product combination.

     

    combination_id, that is probably our issue!

     

    Cannot believe nobody here is able to deeply look at something like this  :(  and give us a definitve answer.

     

    Thank you

    • Like 1
  12. Anyone interested, just posted a reply on Forge:

     

    Please, give your point of view.

     

    Thank you

     

     

    Thank you Vincent, Marcos for following this up.

    URLs positioning is so worrying, that makes this issue so urgent in my opinion.

    As Marcos wrote: "The urls must be immutable even if we change characteristics of the product"

    I have a client requiring me to switch to another ecommerce because of SEO reasons affecting PS 1.7, others client staying on PS 1.6 watching out.

    Vincent, this seems a big problem, please be aware ot it!

    Not only because of SEO, I also think about URLs sharing links on social network: what about me switching between default product combinations > URL is being changed and not redirected > big drop in web trafic because of link changes.

    Also think about sitemap, lots of product duplication.

    URl should probably keep immutable, product attributes should go following the URL "hash tag":

    eg:

    /en/blouses/2-blouse.html#1-size-s/11-color-black

    instead of:

    /en/blouses/2-7-blouse.html#1-size-s/11-color-black

    What is exactly "7" number in the URL? It is not the id of product attribute. It is the combination id, isn't it?

    Detailed explanations at forum PS thread https://www.prestashop.com/forums/topic/554789-how-to-remove-id-product-attribute-from-product-links/

    Thank you!

    PS: this issue is closely related with http://forge.prestashop.com/browse/BOOM-2737

     

  13. Just opened a new bug report on Forge:

     

    http://forge.prestashop.com/browse/BOOM-2804

     

     

    Hello,

    Please, hover on any product link, e.g. PS 1.7. website homepage or any category page, you may see as products URLs links show "default combination" in product URLs, please look at pic attached.

    On the contrary PS 1.6 does show clear URL: please look at pic attached > each combination is being added using a hash tag following the URL and not any combination is being showed in page links.

    This is bad for SEO not only because of multiple product URLs but also because we might switch among product default combinations depending on stock or sales.. etc. this resulting in a different product URL for SEO positioning once we set a new default combination for the same product.

    I would say URLs should be unique, does not matter default combination or extra combinations for each products.

    Might you please explain which reasons lead you to set this behaviour for products combinations links and URLs?

    Thank you

     

  14. That is a really bad news.
     
    That pushes me reconsidering whether using PrestaShop or not.
     
    No any client of me is going to accept bad SEO, hundreds of URLs ...
     
    Any help is appreciated to fix this.
     
     

    We won't work on that specific point on the core of Prestashop, but this is something that can be improved with this module : 
    https://addons.prestashop.com/fr/seo-referencement-naturel/25758-seo-performance-url-cleaner.html
    Thanks for your report


    http://forge.prestashop.com/browse/BOOM-2737

×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More