Alphaloc

Yes, I realized and corrected my mistake before you clicked reply. Reason I didn't check the original post again is that I use Shop::getContextShopID() all the time, without issue. Just checked it again and it works fine, giving the correct shop id depending on the shop selected, at least for 1.6.1.x

please ignore :-)

You basically want all the carts from the ps_cart table that do not have a corresponding record in the ps_orders table (carts without a linked order is an abandoned cart) The query below will give you those rows. SELECT c.* FROM ps_cart c LEFT JOIN ps_orders o ON ( c.id_cart = o.id_cart ) WHERE o.id_order IS NULL ORDER BY c.id_cart ASC

Great post and work! Thanks for sharing

There might be a number of reasons why 1 shop or platform performs better than another. Get as much data on both as possible, preferably in a package like universal analytics or comparable and try to find out why you're getting less traffic, what channels (organic search, paid search, social, ...) produce less traffic, and so on. Like mdekker said: when you change platforms most of your URLs will be different. Those old spotify URLs were indexed, have backlinks, ... and the new prestashop ones start from scratch. That's why it's important to 301 redirect every old URL to the matching new one, so you let search engines know that the page has moved to this new URL. (and you'll keep most of your ranking signals and thus your position in the search engines) That way you don't loose the time and all the hard work you did on the old shop. Then check if the reduction in traffic matches the reduction in orders. If it matches, the reduction in orders *might* just be a direct consequence of the reduction in traffic. If it doesn't, check your checkout pages and find the essential differences between those and the spotify checkout pages and see how you can improve your prestashop checkout process.

Preferences > SEO & URLs This will show you a list of all built-in / template pages. If you click "edit" next to the index page, you'll be able to adjust the meta tags of the index (home) page. Note that you should only work with meta title and meta description tags. Meta keywords aren't used anymore by search engines (and might even have a negative effect)

Hi yog_sothoth, Preferences -> SEO & URLs -> Set Shop URL Shop domain and SSL domain should be set to: www.mywebsite.com Base URI should be set to: /catalogo/some-text-here/

I would probably just ignore it, assuming that that empty image tag is updated by javascript at some point. The tester you use probably doesn't recognize that and sees it as a problem... I would just skip that one and follow-up on the others. Good luck

You have an empty img tag: <div class="click-desk-tool-tip1" style="padding-left:75px!important;"> <a class="cd-eye-catcher" onclick="return false;" style="margin: 0px auto; width: auto; height: auto; top: 0px; padding-top: 7px; line-height: 0em !important; position: relative !important; text-align: center !important; display: none; background: none !important;"> <img src=""> <span id="clickdesk_close_eye_catcher_image" onclick="CLICKDESK_CHAT_WINDOW_UI.hide_eye_catcher(event);return false;">x</span> </a> </div>

I have to agree as well... There seems to be a constant drive to add more features while the current feature set is far from bug-free (quite the opposite unfortunately), to add major versions when the current version is far from perfect. Befitting an open-source project, people do their best to report these issues on the forge and get largely ignored, those who can make pull requests for fixes and... get largely ignored. I understand that it's much sexier to add things than fix them but this is getting quite frustrating. My (and your) customers need a working, stable and secure e-commerce system with preferably as many options and features as possible. But number of features should not take priority over quality and for a long time now I have the feeling that this is the case. When 1.7 gets released (early 2016 at best?) it 'll be at least months, but probably closer to a year before it's really stable and production-ready (based on past experience). By that time, we'll have a system that's as reliable as 1.6 is now and work on 1.8 will probably start... In the meantime, we're stuck with 1.6 where so little is getting fixed while so much is available. If the low-hanging fruit would be hanging even lower, it would basically be lying on the ground. It's these choices and priorities that make it so difficult to keep recommending PrestaShop as the e-commerce solution of choice. (done ranting now...)

Then you want both pages (with or without the tag=1) to have the same canonical page and thus the same rel=canonical link <link rel="canonical" href="http://mysite.com/product.html" /> The whole idea behind the canonical tag is that when you have multiple URLs for (nearly) the same page with the same content, to tell the search engines which URL (variant) is the authoritative (canonical) one. That way only the canonical variant will be indexed by the search engines and that canonical URL will combine all the "power" (ranking signals) of the different versions. In addition, the different versions won't be considered as duplicate content. More info on rel=canonical on google's support page.

No, you probably want to have the same canonical variant for both pages, unless the tag=1 makes it a completely different page.

Yes, you will lose rank if you just add a language. You can compensate (and keep most but not all of your rank) if you let search engines know that the page has moved permanently (301 Redirect). There are 2 ways to do that. Set your shop's default language to French (should be the case already since it's your only language) and In Preferences -> SEO & URLs set "Redirect to the canonical URL" to "301 - Permanently moved". That way, whenever someone tries to reach yourshop.fr/category_x/product_y they will be canonically redirected to yourshop.fr/fr/category_x/product_y. Since it's a 301 redirect, you will keep most of your ranking. (mind you, 302 redirects don't do this) Problem with his method is that it's based on a prestashop bug (at least in my opinion) because language redirects should actually happen with a 302 redirect, no matter what. So maybe the better way is to manually configure server redirects on your server that will redirect all pages that have no language set (where the 'xx/' is missing in yourshop.fr/xx/...) to yourshop.fr/fr/... Best to consult your server documentation to see how you best take care of that.

Some ideas, not complete and not saying you should do all of them ;-) do email the brands you're selling to be listed as a "retailer/dealer/distributor" on their website (if they have such a section) create a youtube channel with videos on the products you sell, link the channel to your website (youtube is the 2nd biggest search engine, after google itself) pick 1 or a few (not all) social media sites that fit your purposes/products best and be active on them. Best to have 1 really good really active social media account instead of 10 passive ones make sure you have a google mybusiness page (as well as analytics and adwords, but that takes us out of the SEO realm) get listed on google shopping (merchant center) and any other (local) relevant aggregators find out what the authoritative sites are for your products/style/location/niche and see if they mention webshops/other sites in their articles and why they get mentioned. Can you get mentioned as well? backlink check on your main competitors, find out what's working for them and do that as well (preferably better) invest in photo's/pictures, make sure your product pictures are high resolution and that you have even higher resolution versions of them. Not only makes this your webshop much more attractive and gives it more opportunity on google images, it'll also allow you to respond to image requests from content/news sites and print media (closely linked with on-page SEO of course) become a certified shop in your country if the certification is meaningful / recognizable analyze what current off-site seo traffic is working for you, try to expand on it (use analytics, moz.com pro, ...) don't buy links/mentions, participate in link schemes, cross-linking, ... guest blog

I also had a 0 byte archive problem, seems it was due to filesystem permissions of the theme directory I was trying to export. Changing ownership of the theme directory to the user prestashop/webserver runs as fixed it. chown -R <webserver_user>:<webserver_user> <path_to_theme_to_export>