savedario

I am developing a custom theme for a client and stumbled upon the issue that the additional styles I added are being ignored because, owing to the use of Vue, the styles of the elements managed by blockwishlist are being blasted inline into the element thus overriding whatever other styles one defines elsewhere. Has anyone encountered this issue ? Is there another option other than cloning the whole module and change 2 lines of stylesheet ?

I tried the approach above but in Prestashop 1.7.8.0 things a different and I cannot generate .map files. Has anyone solved it for the recent version ?

I'm having the same issue with Prestashop 1.6.1.6 and, so far, only on Google Chrome. I searched the source code, and there's no mention of the non-unique ids anywhere, except for those button elements. I removed them and got no errors so far, except Chrome shows no warning anymore. Still, the behavior is very different between Firefox and Chrome. On Chrome, I can only update a product the first time. After that, whether I use "Save and Stay" or just "Save", the changes are not saved and "Save" does not go back to the product list.

Thanks for pointing me in the right direction. I have 1.6.1.6 installed and I implemented your idea by adding the override file: override/classes/Media.php with the following content: class Media extends MediaCore { public static function getCSSPath($css_uri, $css_media_type = 'all', $need_rtl = true) { $css = parent::getCSSPath($css_uri, $css_media_type, $need_rtl); if (is_array($css)) { $url = key($css); $media = $css[$url]; if (file_exists($_SERVER['DOCUMENT_ROOT'] . $url)) { $ver = filemtime($_SERVER['DOCUMENT_ROOT'] . $url); } else { $ver = '1'; } $css = array($url .'?v='.$ver => $media); } return $css; } }

Thanks mdekker for the answer. Is there an alternative to that module?

We are running Prestashop 1.6.1.6, but I tested this with a vanilla 1.6.1.9. The configured minimum order amount is not checked when using the advancedeucompliance module feature named 'Advanced Checkout'. Is this a design/implementation choice or just something that got missed ?

On Prestashop 1.6.1.6 I've managed with: $myModule = Module::getInstanceByName('mymodule');

@razaro, Thanks for your suggestion. I was hoping to find a way for the theme to add it's own styles to be compressed. Unfortunately all the files in the autoload folder are added before all the modules, which is a bit strange, because the theme "should" have the last say on the way things look... so it would logically go after all the other styles. I will have to keep the override...

Old thread, but it comes at the top of the search so... I tried the suggested solution, but it did not work for me because setMedia() is called before all the modules have a chance to add their stylesheets and my theme needs the extra css added as the last one. It was originally added "manually" in the the header.tpl, but that does not work either when compressing the css because, for some reason, the smarty variable $media contains 'print' and the HTML: <link rel="stylesheet" href="{$css_dir}style.css" type="text/css" media="{$media|escape:'html':'UTF-8'}" /> was basically ignored for screens. My solution was to override FrontController as suggested but to do this instead: class FrontController extends FrontControllerCore { public function display() { $this->addCSS(_THEME_CSS_DIR_.'style.css','all'); parent::display(); } } Using Prestashop 1.6.1.6. Hoping this helps someone...

It's end of 2016 and this is still an error. The Backoffice has: Customers > Send a newsletter and there's no AdminNewsletterController.php Using Prestashop 1.6.1.6 Did anyone solve this ?

I know it's a rather old question but... I am struggling to import into PS products that have attributes with commas in their names (e.g. "fish, red"), which works fine if entered in the backend, but causes troubles when importing. I think the issue here is that the import treats certain columns (e.g. Categories and Attribute / Value) as multi-value, where each value is separated with a comma from the other. E.g.: 123;red,blue;Pants describes the product Pants, with ID 123 and that belongs to the categories red AND blue. Edit: And of course the solution (duh) in PS 1.6.1.6 is to choose a different multi-value delimiter, possibly a character that is not in the attribute names (e.g. |)...

It's now 2016 and the issue seems to be still there. If someone is still have problems, read further... For some reason a new product defaults to using the tax group with ID = 1. I was able to import my products with tax-included prices by doing the following: - Disable all tax rules - Select "Price (Tax excluded)" for the import. The logic seems a bit counter-intuitive, but this way the price being imported is used and the product price without taxes, since there are no tax rules, the same value ends up in the retail price with tax. Edit because of post #4: Yes, but only during the import.