vegaskev

yes....the link to the site is here. Thanks in advance for your assistance.

BUMP Please

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.

For future reference, there was an issue with the cart block on mobile. PrestaShop has released a temporary patch for this, which you can view using the link below and they are also working on a permanent resolution to implement in a future release of PrestaShop core. You can stay updated on this issue by visiting this forge thread: http://forge.prestashop.com/browse/PSCSX-3243

I have your solution for you right here http://www.prestashop.com/forums/topic/349695-paypal-payments-not-showing-in-bo/?p=1799751 since nobody seems to have noticed your post.

I had a similar issue. Though I found no solution here on PS forums, a drupal user figured out the issue to be that the cart time out timeframe (the time before an order is determined to be 'abandoned') does not allow for the time it can take paypal to actually send the signal back to the cart that the payment was authorized and completed. According to another individual's IPN logs, the paypal signalled the order nearly 21 hours after the order was actually placed...by then his cms (and PS) will have already clocked the order as abandoned (especially if the buyer has closed their browser). Not sure if PS core can do something to maybe delay carts being dropped into the abandoned class, or not, but that's what I would look at. Rumor has it that PayPal Pro doesn't have this issue and I know from experience that most other merchant processors (authorize.net, etc.) do not have this issue. Just my two cents.

Nemo, Thanks for the tip, Unfortunately, I don't have that function in my product.js. In fact, I don't have any such function referencing #layer_cart at all inside my product.js. I also checked the layered cart module inside my theme and looked in blocklayered.js and no such reference to that div# in there either. Any other ideas Nemo? Thanks in advance.

PS 1.6.0.6 > Default-Bootstrap > Product Page > 'Add to Cart' Popup > 'Continue Shopping' href So when you click 'add to cart' on a product page the modal box pops up with your newly added product and an option to 'Continue Shopping' or 'Proceed to Checkout'. I changed the tpl file to include a link to the home page (per client's request) for the 'Continue Shopping' button, and when you hover over the 'Continue Shopping' button, the browser does display the hyperlink accordingly, however, when you actually click the button, the modal box simply closes and stays on the existing page. What did I miss? Thanks in advance.

In various versions of PS 1.6.... I noticed that in PrestaShop 1.6 the left column Cart Block ajax isn't as dialed in as in previous versions. In previous versions of PS cart block, if you added a product and then clicked the browser's back button, once the previous page was loaded, the ajax in the cart block would kick in and reset the products displayed in the cart block to show the most recent combination of products, whereas in PS 1.6, nothing happens to the cart block when you hit the back button. Since most people hit the back button when they demo their new sites, they are asking why the cart block doesn't function like it did in their older version of prestashop. Was this an oversight, or was this a change in direction for the cart block? Thanks in advance.

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

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.

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.

Would you happen to have a copy of crontab for PS 1.5 you can share? I can't seem to find it anywhere. It's been pulled from the marketplace and I could really use it on this 1.5 site I have. Thanks in advance.

Sorry....it's 1.6.0.6. I'm using the default-bootstrap theme. Does prestashop cache product meta? And if so, how would I go about clearing said cache? Thanks in advance.

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?