FoodAssets

We are still hoping for someone to offer some real solutions to this problem. So far, nobody has weighed in on anything that works. That download link from goldies is disabled, and for the wrong version, so we can't even look at it for some ideas. We attempted to hire a company to helps solve this issue, but they too remain clueless on what to do, so even that attempt went nowhere. Needless to say, we are very unimpressed with Prestashop support, module developers and so on. This reinforces our opinion that this is actually a horrible platform to build your business around. Our company is being literally pummeled with orders now (we sell food) due to the coronavirus pandemic, and yet Google is ranking us very, very, VERY badly. You'd think the opposite would be true, since we have more business then we've ever seen now. But apparently, Google is punishing us for the 700+ Errors it's throwing on the Products. We can think of no other explanation for the poor ranking vs heavy site traffic we're now getting. This is undoubtedly costing us thousands of customers during the current crisis. If ANYBODY has some ideas for version 1.6.1.2 please let us know ASAP.

That's definitely not going to work for us. Module developers rarely get things right in our experience, nor do they bother answering detailed questions (as explained in my post). They're more interested in just taking money versus providing well-coded modules. Prestashop is plagued with serious issues out of the box, and there seems to be a "module fix" for each of them (by design in our opinion). It's great way for them to take money - no thanks. You're "almost cleared all the errors" comment is a great example of how crappy module developers are in our experience and seem to be in the business of releasing poor quality "solutions". We're just not interested in supporting this kind of shady business activity. We tested your product page in Google's Structured Data Testing Tool (https://www.erenovation.com.au/in-wall-cistern-wall-hung-toilets/reno-302-rt-cistern-wall-hung-toilet#/59-button_option_rt-g3004109_square_chrome_12500/63-toilet_pan_color_option-gloss_white_toilet_pan) and it reports 4 warnings which I'm sure you know about. There is a difference we've noted in the Testing Tool warnings and errors, and what Google Tools shows (increased severity). They are not giving out the same errors and warnings in all cases, some warnings are now "Errors", which are more severe. We also suspect Google will (and has) changed its mind about how important these warnings and errors are. This is a code problem with the core files in Prestashop in our opinion and it needs to be fixed.

Our efforts to unravel the "instructions" above in this thread and fix our Google Search Console errors have failed (and broke our site). The problem for us is the instructions do not actually contain sufficient step-by-step information. We are running Prestashop 1.6.1.2 with modified product.tpl (no child themes). Google Search Console is producing over 700 errors: Error "Either "offers", "review", or "aggregateRating" should be specified There are also warnings on every product: Warning Missing field "brand" Warning No global identifier provided (e.g., gtin, mpn, isbn) Warning Missing field "priceValidUntil" Warning Missing field "url" Warning Missing field "aggregateRating" Warning Missing field "review" Warning Missing field "availability" Warning Missing field "sku" Warning Missing field "description" We are using Customer Ratings and Reviews Pro + Google Rich Snippets v4.1.6 - by Business Tech - which was a massive mistake in our opinion, this module has never worked properly for us, nor could we ever get it to update. It's also incredibly slow to load, or to perform any administrative functions (such as approve reviews), taking nearly 5 minutes to display the admin screens. We've contacted Biz Tech about these Search Console errors and they refused to help (their answer was buy the newer version). They refused to answer our specific questions regarding if they've actually solved each of these errors in their updated version of this module (we provided them with the entire list of errors asking if they fixed these - they chose not to respond to those questions). Why would we buy this crappy module again on a gamble like that? Needless to say, we're extremely frustrated with this company, but it has been our experience that Prestashop module support is among the worst in the world, so par for the course in our opinion. We have tried turning this module off, but that hasn't actually solved the Search Console errors either. Clearly, we need code corrections. Has anyone here resolved these Search Console errors in Prestashop 1.6x? If so, exactly what steps did you take, and which files were modified?

attribute_impact appears to be for storing the range of price or weight changes, it does not store the actual price or weight - it stores the value of how much it is supposed to change - as far as I can tell, but I'm no expert on this. We did some testing - there is no way to update the attribute_impact price after it has first been created. This cannot be done in back office or in Shop Manager. We used Shop Manager to create the groups, the attributes and the combination generator. This created a record in the attribute_impact table with the range of prices, but we were completely unable to update those prices in Shop Manager - or the back office - making this table utterly useless if you cannot change the values it holds. What we need is to have the select drop-down list show the attributes and the actual price of the attribute. Code samples in this thread do not do this for v1.6.1.2

Does not work for 1.6.1.2. This version of prestashop does not store the attribute prices in the attribute_impact table, there are no price values in there at all. Those appear to be stored in the product_attribute table. I've fiddled around with changing the sql query, but it's clear that several other changes are required to the classes, controllers and tpl. And that's where I got lost. This is a hugely critical function if anyone wants to use attributes that have different prices - and appears to be a deliberate by the developers so that you are forced to buy a module to handle this. Who would write code that does NOT show the prices in the selection when a customer is selecting an attribute? It's absolutely nuts.

I've searched the forums for this and have not found out how to do this. We want to display the selected product attribute on the product.tpl page. Right now, it just shows the product reference, but what I need to do is show the selected attribute also. We use v1.6.1.2. https://foodassets.com/apples/van-drunen-farms-apple-dices-freeze-dried.html This is the code that needs to be updated in product.tpl <p id="product_reference"{if empty($product->reference) || !$product->reference} style="display: none;"{/if}> <label>{l s='Item #:'} </label> <span class="editable" itemprop="sku"{if !empty($product->reference) && $product->reference} content="{$product->reference}"{/if}>{if !isset($groups)}{$product->reference|escape:'html':'UTF-8'}{/if}</span> </p> I can't figure out what the proper variable is called. Shopping-cart.tpl uses {$product.id_product_attribute} but that doesn't seem to work. What is the actual name of the variable that stores the selected attribute name?

We need to change our product attributes to display by price (lowest first). Product attributes do not have sort order positions assigned. We want to change product.php instead to handle this. We need a two-part sort - sort by attribute name first (descending), then by product price (ascending). Example of attributes: Select Product 30 lb box 12 oz, #2.5 can 12 oz, (6) #2.5 cans 46 oz, #10 can 46 oz, (6) #10 cans Select Product Rumford 30 oz, #2.5 can Select Product is always the first attribute we want displayed. All the other attributes can be found in any order (how they were loaded into the database). Since we have almost a thousand attributes, we don't want to have to assign a sort order to each group. We want the REST of the attributes to sort by price (lowest to highest). In product.php - $sql = 'SELECT pa.*, product_attribute_shop.*, ag.`id_attribute_group`, ag.`is_color_group`, agl.`name` AS group_name, al.`name` AS attribute_name, a.`id_attribute` FROM `'._DB_PREFIX_.'product_attribute` pa '.Shop::addSqlAssociation('product_attribute', 'pa').' LEFT JOIN `'._DB_PREFIX_.'product_attribute_combination` pac ON pac.`id_product_attribute` = pa.`id_product_attribute` LEFT JOIN `'._DB_PREFIX_.'attribute` a ON a.`id_attribute` = pac.`id_attribute` LEFT JOIN `'._DB_PREFIX_.'attribute_group` ag ON ag.`id_attribute_group` = a.`id_attribute_group` LEFT JOIN `'._DB_PREFIX_.'attribute_lang` al ON (a.`id_attribute` = al.`id_attribute` AND al.`id_lang` = '.(int)$id_lang.') LEFT JOIN `'._DB_PREFIX_.'attribute_group_lang` agl ON (ag.`id_attribute_group` = agl.`id_attribute_group` AND agl.`id_lang` = '.(int)$id_lang.') WHERE pa.`id_product` = '.(int)$this->id.' GROUP BY pa.`id_product_attribute`, ag.`id_attribute_group` ORDER BY pa.`id_product_attribute`'; Changing ORDER BY to something like - pa.'name' desc, pa.'price' asc; should work, but it doesn't. We're probably missing something else. Any suggestions would be much appreciated.

We are interested in the the following module and would like some feedback on it: http://addons.prestashop.com/en/6144-customer-ratings-and-reviews-pro-google-rich-snippets.html What we'd like to know is: 1) does it work? 2) Have you experienced any improvements after using it? Please be specific, was your improvements ranking, traffic, or? We have tried a lot of Prestashop modules and found a lot of them to be buggy and unsupported. Before we jump into another one, we'd like to see some honest reviews from end users. Using Prestashop ver. 1.6.1.2 Thank you for your time ~

I've had several very bad experiences with Prestashop module developers. In several years of use, only 1 developer has been worth doing business with, 3 others have been worse then useless and have often left my site broken and unworking after paying out thousands of dollars in total fees for lousy 'support'. So I do not know from experience that community members are any better (not true in my experience). This latest fiasco with Prestashop has definitely left me unhappy once again. Prestashop has a terrible reputation imo and is only suitable for coders who are current with the development and repairs required. A gigantic (global) business opportunity certainly exist for a competent team of developers and support personnel to offer properly designed and documented modules and technical support. The one I tried was horrible, but from many other posts I've seen on this board, thousands of people need this kind of assistance.

Multiple efforts have been made to contact the 'developer' with dismal results (no reply, no resolution) even after providing FTP and login credentials to resolve the problems. Notice that a PayPal dispute would be filed also went unanswered. A complaint (and then a claim) with PayPal has been filed requesting full refund. I do not recommend this software module to anyone. There is no support. The module does not work as advertised. Documentation is appallingly terrible.

I've tried all three instances. None of them work.

Hello, Using PrestaShop Version 1.6.1.2. I recently purchased Abandoned Cart Reminder Pro module. I have configured the discounts field and email templates correctly to the best of my knowledge and per the instructions. However, the discount text field will not show up in any test emails sent from the module. Where the discount text should be listed in the email, it shows up like this: %DISCOUNT_TEXT% This means to me that the module is failing to parse the variable and replace with the specified values. We have used this as the discount (borrowed from the modules 'suggestion'): One thing that I have noticed is that the "discount text" tag is referenced 3 different ways within the instructions and menus and PDF documentation of the module, which is very confusing and sloppy on the part of the developers: %DISCOUNT_TEXT% %DISCOUNT_TXT% %DISCOUNT_TEXT Which is correct syntax? This is our test email template that we are using: The %DISCOUNT_TEXT% fails to show up in the email. A few other questions: 1) When sending a test email, does the discount text field show up for test emails? The module documentation does not mention this. Or does the discount only activate on live carts with live customers? I have the module's "Reminder Frequencies" set up to send an email after 1 hour. I have tried creating numerous live carts as a 'customer' and abandoning them on our end - no emails are being sent to the email address used. No reminders show in the modules Statistics list. Prestashop does not immediately record these as "Abandoned Carts" either. I'm guessing that it only toggles a cart as abandoned after a set period of time (24 hours?) By the way, I have tried contacting the module developers with these questions. Support to date has been non-existent...

Because that is EXACTLY what Prestashop developers want Prestashop users to do - to achieve such a high level of frustration that they will be forced to hire a developer to fix the inherent problems and buy support or a module. I have a MAJOR problem with this scam because that is exactly what this is. It's a SCAM orchestrated on the entire Prestashop community. Why should I buy into this scheme? That makes me as complicit as the idiots that wrote this crap. And I won't do that. Since posting this thread, I've had other Prestashop problems and have to fire two developers for more crap coding, leaving my site more broken then before. I wound up fixing all of it myself. So 'hiring a developer' is very iffy. Even the "good ones" will leave you hanging. Never again. And no, PayPal module has NEVER worked. I found a work around - trash the PayPal module altogether and NEVER use it. Simply show the order totals on the checkout page and provide the link for the customer to login to PayPal themselves and send the money to the store. Works every time. No "developer" or paid module needed. No need to worry about whether you hired a competent developer or not. No need to EVER worry about upgrading either, or a module becoming non-supported because you're never going to use it and never going to need it. Prestashop is NOT "free" nor without many headaches (and not recommended except for those that like lots of pain). The "open source solution" simply isn't. Merchants need to get PAID - not PAY to have CRAP fixed on software that is simply unready for the real world of business.

Yes, deleted the files in the img folder. This didn't help, as PS continued to assign the survival-acres to the image name when logo image was re-uploaded through the back office. I found a fix and will share. I've not re-uploaded the logo image to test this fix below to see if PS still appends the survival-acres string to the image name (it might, just don't know yet), just fixed the stored reference data to the image in the ps_xxx tables. Since I discovered a lot of bad references in the steps below, I'm assuming re-uploading the image will NOT try to insert survival-acres to the image name like it was doing before. In MySql, select all the tables in the database and search for all the strings (one by one) that aren't supposed to be there if you've moved your site to a new domain. You could also do this to search for anything else that should or should not be in your tables. I searched for all of these: survivalacres, survival acres, survival-acres, /shop, etc. The search found hundreds of references in about a dozen tables that were still incorrect (this is where we had problems with the clown we hired). Even the ps_shop table still had 'survivalacres' in it, the ps_configuration also had a bad reference in it. Most of the ps_lang_xx tables did too. In other words, they left our site broken for months. Edit the ps_xxx table that has the errors. You can issue a SQL command (back up your table first!) to update the column values if needed, this will change all rows in the table all at once (so be careful). I only wanted to change the substring, not the entire thing, so this is what I used: Example: UPDATE `ps_product_lang` SET `description` = REPLACE( `description` , 'https://survivalacres.com/shop', 'http://foodassets.com' ); Some tables should be left alone. I updated the ps_lang tables mostly.

Hi all, Using PrestaShop Version 1.6.1.2 Strange issue here with trying to change the header image (logo) on my website. Sometime last year we had changed domain names from 'http://survivalacres.com' to 'http://foodassets.com'. The site was transitioned over from an older version of Presta 1.5 to 1.6 by DesignHaus, but left badly broken and required a great deal of intervention to fix. So far most of the bugs have been worked out... ... except the following issue: 1) The name of the logo image I am trying to upload is: food_assets_logo.png. 2) Uploading the image is successful through preferences>themes>logo (it will appear on the website). 3) However, clicking the image properties in a browser window (or view source code) shows this image has been renamed to: 'http://foodassets.com/img/survival-acres-logo-1457027282.jpg' I have tried several things now: 1) Physically deleting the 'renamed' image through FTP. 2) Clearing the cache on both browser and Prestashop. 3) Verified that this isn't an issue with the browser I am using (it does this on Chrome, Firefox, Safari, Opera, IE.) 4) Renaming the image in FTP (this breaks the image on the site). Subsequently, uploading the logo again works, but it gets 'renamed' by Prestashop to 'http://foodassets.com/img/survival-acres-logo-1457027282.jpg'. It's also renaming the images for email and invoices headers too in the same fashion, always inserting "survival-acres-logo" into the image names. We suspect there is some sort of configuration setting, or even hard-coded value somewhere that is causing this. We really need some help on where to look for this and how these images are having this "survival-acres-logo" inserted into their names.