Kanenas

I have the 'program' but the same problem without the solution with 1.6.1.1 Did you find a solution?

Same problem here! Prestashop is a pain in the a[spam-filter] everything is buggy and you have to buy solutions that mess up more stuff and then you can't upgrade... changing state and country is buggy on mobile but no one has any answer why. When will the official prestahop be released since every version seems beta?

Me too! Identical problem - any solution anyone? I think it may have been caused after removing an awful add on called supercheckout which made a total mess of the checkout fields and caused a lot of problems with shipping etc. Seeing your post Blaz1988 I am curious if you ever used supercheckout, and if you found a solution to this problem?

Can anyone please tell me if there is a solution found here that addresses the issue of gsitemap indexing only 1 (the cover) image of every product and how to add all the product images to the sitemap?

Similar problem here but the problem occurs on google sitemap. I just realized I have been wasting 10s of hours writing descriptive alts in the back end and they're not even in the sitemap. Actually I am getting the image alt I want from the backend 'legend' section but there is STILL a problem in the sitemap as the sitemap generates the 'title' of the image as the product name. The sitemap generated from gsitemap.php - and the line with the problem seems to be 'title_img' => htmlspecialchars(strip_tags($product->name)), As the product title is already mentioned in the sitemap, and there is no image alt field in the sitemap, only image title, I am assuming that this should be the 'legend' which I have so carfully included on every photo in the back-end in vain. As I know nothing about databases, can someone please tell me what I should change my php to (this line) to point to the alt/legend image title field? ALSO How the hell get gsitemap to display not just the cover photo of each product but all the images? I see there's a module on this but I can't go to the hassle of intalling a module (risk of patchy disaster from my experience) just for a few lines of code in gsitemaps... HELP anyone?

Thanks guys but after spending the entire day I have managed to fix by disabling the mod_sec on cpanel. Not sure how safe this is in the long run, but its a way to upload large images. Other posts on this forum suggested disabling mod security on PS back-end, but that made no difference at all to me. The guys at inmotion hosting are also pretty dull so I spent the entire day trying everything possible to reach this solution. If anyone could suggest a work-around for security (wehn I disable mod_sec) that would be great!

I finally resolved this but it was tricky. Firstly - disabling mod_security in Ps back - end didn't help. I had to do it in cpanel. Secondly - ini_set('memory_limit','256M'); in config.inc.php is actually helpful Looks like I might postpone going to shopify after all.

Fixed thanks.. in combination with disabling mod_sec from cpanel!!!

I am having the same problem and the idea of migrating to shopify is becoming very enticing... that or to marry a prestashop developer

I am having the same problem exactly over 130 kb product images in 1.6 Have checked all the ini.php stuff and settings. I know that this is a while back but did you ever manage to find a solution on this?

Same issue here. 130 kb is all I can upload. I have checked php.ini and admin>pref>image size and no joy. Very annoying. This kind of rubbish makes you want to go to shopify which is probably cheaper considering you need to marry a developer to get through prestashop. Please let me know if you have found a solution.

Looking for a pro with advanced knowledge of Webmaster tools, and competent with .htaccess, sitemaps and robots.txt to work around a google caching and indexing problem. Looking for someone with a professional attitude that wants work.. (I say this because from my brief experience in the forum, there is a tendency to show off in the forums and get little work done outside). Please contact me if you're interested in helping me on a paid basis. Thanks

OMG! Its fixed!!! I just submitted /index.php to be fetched through google webmaster tools instead of raw domain and google refreshed it instantly !!!!!! The problem remains that I need a module to lock currency to country. I have tried a couple, and when these seem to not allow google to fetch content when they are on. Any ideas? Has anyone tested a module like this that allows a full googlebot fetch through Webmastertools?

By the way, the website is adult oriented and NSFW so if anyone has an objection, please do not open link.

The problem is that a bad popup geo module on homepage disallowed Google to crawl for too long. Now google has not got homepage cache and is showing 'this site may be hacked' This has been going on for months and has cost me thousands to build a NEW site on a NEW server to get rid of this message. After all this, message is still there! Furthermore there's no message in Webmaster tools - so there's no way to fix it. Even though I have made many FETCH attempts in WMT, and it is crawled ok but not re-indexed. have also checked robots.txt and htaccess.. and nothing. Site is http://tiny.cc/udxszx (minified) I have reported it here over the last few months but nothing.. https://www.google.com/safebrowsing/report_error/ Furthermore Google's own tool shows the site is super-clean in past 90 days - see for yourself at http://www.google.com/safebrowsing/diagnostic?site=REPLACE WITH MY URL and I have also used 3rd part checks!! I am under the suspicion that a smarty/cache compilation error in prestashop first triggered this (geo popup).. but I have replaced the website completely to an upgraded version and google's classification REMAINS 'hacked' Not even the description metadata is being replaced! It might be rolling back to older identical messages - this isn't helping. I am now thinking if I can change htaccess to make a temporary redirect to another page, it might unblock google and force it to get new cache.. any ideas? Any help will be grandly appreciated. (The fact that this is all damage may all be caused by a certified Prestashop agency is outrageous)