bcolflesh

Thanks metacreo!

Downloaded archive will come from https://download.prestashop.com/download/releases/prestashop_1.6.1.20.zip MD5 hash will be checked against 39d2eb1adb541d8da28f8f7aabcf8f70 downloading from https://download.prestashop.com/download/releases/prestashop_1.6.1.20.zip file will be saved in /mypath/autoupgrade/download/prestashop.zip download directory has been emptied Download complete but MD5 sum does not match (e67b119d6bf80ee556f89db9f8e0d2ac).

Fix works for me as well - thanks.

Dashtrends module got an update today, but it has no effect (cleared cache, etc) at all on this issue.

I have the same issue with the 1.6.1.1 upgrade as well, everything was fine before that.

I can confirm this same issue - sales records are there and validated, but the dashboard->Sales (sum of revenue) reports 0.00 for any range.

PrestaVOD support replied to my email: "This is a bug introduced with new PrestaShop version. It's realy not important (a simple warning because PrestaShop does not check content before calling it). We made a little patch, and we have to release a new version of PrestaVOD module soon. Keep in touch through PrestaVOD.com."

This was noticed after the 16.1.0 upgrade, but it could have existed before - on an iPad in horizontal mode, the scroll bar overlaps the content approximately an inch and a half from the right side, like it is keeping the absolute position from portrait mode, This is a vanilla install, with no default theme or CSS changes. Anyone have a fix?

Notice: Undefined index: quick_access_current_link_name in /home/pcnweb/public/pcnstore.com/public/cache/smarty/compile/96/d1/d8/96d1d8257e2f374960c2a9e082663a3958f6b01f.file.header.tpl.php on line 376 Notice: Trying to get property of non-object in /home/pcnweb/public/pcnstore.com/public/cache/smarty/compile/96/d1/d8/96d1d8257e2f374960c2a9e082663a3958f6b01f.file.header.tpl.php on line 376 What is the easiest way to fix this and not hose anything? I tried clearing the cache.

We didn't have many products, I had someone go page by page and disable, then go one by one until they found the offender.

Note: everything is working for me now after updating to 1.6.0.11 this morning - thanks PrestaShop!

Nope, no good - something is fundamentally broken in the stock 1.6.0.9 version of the Friendly URL functionality. If someone needs logs or debugging info I will try to provide.

PS 1.6.0.9 with existing inventory, mod-rewrite enabled and working on AWS, turn on friendly URLs, regenerate thumbnails, clear cache - images missing from front page, links 404. Tried disabling friendly URLs, manually deleting .htaccess file in root directory, enable friendly URLs, regen, clear, etc - no dice. Anyone ever get this working in this scenario?

Same here on 1.6.0.9 - any ideas?

This definitely works, but it requires everything to be done - folks with the errors are missing steps: https://console.developers.google.com - create Project > APIs >> add Analytics API (you can remove the other default ones that are "on" > Credentials >> Redirect URIs ex: http://www.yourstore.com/modules/gapi/oauth2callback.phphttps://www.yourstore.com/modules/gapi/oauth2callback.php https://yourstore.com/modules/gapi/oauth2callback.php https://yourstore.com/modules/gapi/oauth2callback.php >> JavaScript Origins ex: http://www.yourstore.com http://yourstore.com https://www.yourstore.com https://yourstore.com >> Consent Screen (important - will not work without this!) Fill out all non-optional information in the form and save. ---------------------------------- Prestashop Back Office Modules > - Filter by Installed & Not Installed and Enabled & Disbaled - search for google - Install Google Analytics 1.x by Prestashop and configure - add your user agent from Google Analytics website, ex : UA-1234567-1 - it's visible on the Home tab and several sub menus - check Universal box and hit save/update Modules > - now do the Google Analytics API module config with the previous data _______________________ You will always get an error about the data, as it takes a variable amount of time for it start pushing out via the API calls - all Google Analytics tie-ins are subject to this. You can make sure you are collecting data by going to the Google Analytics site and drilling down to Real Time > Overview, which will show live traffic to your site.