Jump to content

Cloned Products Showing Original Reference #


Recommended Posts

I'm using PrestaShop 1.6

 

For some reason, when I clone a product and change the product info (title, description, reference #, etc.) PrestaShop back office accepts and displays the new reference#, though on the front end on the product page and quick view, it is displaying the cloned product's original reference #.

 

I have even deleted the reference # completely in the clones and the front end product pages still display the cloned reference #.

 

I have cache disabled and I have force compilation selected in advanced > performance.  So I don't think it's a caching issue, though I haven't been working with PrestaShop long enough to be sure.

 

Any thoughts, guidance, etc. would be greatly appreciated.  Thanks in advance.

Link to comment
Share on other sites

rather than clearing ps cache, compile etc.

 

try clearing your browser cache...

 

fingers crossed :)

 

lol....yeah I tried that.

 

I actually wasn't the one that cloned the products.  Client did that.  He showed me the issue after he got his products uploaded into his storefront.

 

Any other thoughts?

Link to comment
Share on other sites

can you check using phpmyadmin ps_product, find the product(s), the reference is a field, here example from demo

 

max_input_vars

 

09.08.2014-16.52.png
http://screencast.com/t/enDy7mLFAfJU

 

can you tell us, bo-->preferences-->seo & urls

 

what is in the 'route to products' field?

 

for example: {category:/}{id}-{rewrite}{-:ean13}.html

 

is  standard...sorry I really don't know much about this...so we learn together (and I could not find a 1.6 issue like this reported)

Link to comment
Share on other sites

What often happens is that people clone a product and change its data. And then they switch to another language and find that all the unchanged data are still there - changing goes one language at a time. 

 

thanks musicmaster (the more help the better)

 

I did quick test, ref/ean-13/upc etc, do not have  translations

Link to comment
Share on other sites

can you check using phpmyadmin ps_product, find the product(s), the reference is a field, here example from demo

 

I checked the ps_product table and the reference key field values are the valid values.  Thanks for the head's up on what table, I hadn't had time yet to jump back in this and figure it out for myself.  Much appreciated.

 

max_input_vars

 

09.08.2014-16.52.png

http://screencast.com/t/enDy7mLFAfJU

 

can you tell us, bo-->preferences-->seo & urls

 

what is in the 'route to products' field?

 

for example: {category:/}{id}-{rewrite}{-:ean13}.html

 

is  standard...sorry I really don't know much about this...so we learn together (and I could not find a 1.6 issue like this reported)

 

I have ...

{category:/}{id}-{rewrite}{-:ean13}.html

Also, here's a screenshot of that entire section in BO > Preferences > SEO & URLs    => Screenshot

 

That being said, I apologize for my delayed, I got slammed with urgent tasks for the last couple of days.  I appreciate everyone chiming in and lending a hand on this baffling oddity.

Link to comment
Share on other sites

What often happens is that people clone a product and change its data. And then they switch to another language and find that all the unchanged data are still there - changing goes one language at a time. 

That's good to know musicmaster.  I wonder if I would've thought of that automatically if I was in that situation.  In my scenario, everything started out in English and has stayed in English, so unfortunately the solution to my issue won't be as easy to solve as it would in those cases.  But I appreciate the offer up of knowledge.

Link to comment
Share on other sites

El Patron,

 

I have submitted a Bug Report as requested.  For those that run into this issue in the future, please follow and participate in the forge thread I've linked in this reply.  When this issue has been solved I will come back here and mark this post solved so that visitors will know a resolution has been made.

 

http://forge.prestashop.com/browse/PSCSX-3335

Link to comment
Share on other sites

Quick Update: 

 

Apparently the combinations retain the cloned product's reference#.  I was unaware there was a reference# in the combinations area tbh as I'm a developer, rather than a shop admin.   Basically what is happening (for those that run into the same issue), when all product 'combinations' have one reference number, that reference number overrides the main product reference number, since every possible purchased combination is actually a different reference number.  Not sure if this is best practice for PS Core, however, that's the issue. 

 

So, in short, if you change a product reference number, you must also go into your product > combinations and update the reference numbers for those as well.  I know, I know, this is 1+1 for people who've managed their store for awhile, but for noobs, I figure I'd share the solution if they run into this situation as well.

Link to comment
Share on other sites

Quick Update: 

 

Apparently the combinations retain the cloned product's reference#.  I was unaware there was a reference# in the combinations area tbh as I'm a developer, rather than a shop admin.   Basically what is happening (for those that run into the same issue), when all product 'combinations' have one reference number, that reference number overrides the main product reference number, since every possible purchased combination is actually a different reference number.  Not sure if this is best practice for PS Core, however, that's the issue. 

 

So, in short, if you change a product reference number, you must also go into your product > combinations and update the reference numbers for those as well.  I know, I know, this is 1+1 for people who've managed their store for awhile, but for noobs, I figure I'd share the solution if they run into this situation as well.

 

 

thanks for the update...

 

Hi, I have exactly the same - version of PrestaShop 1.6.0.9

 

please see response from vegaskev

 

this appears to be native behavior

Link to comment
Share on other sites

×
×
  • Create New...