endriudb

No one facing this issue? No help?

Hi to all, I have a very strange problem on a shop. When people buy using different delivery address and invoice address, in some case, I have this situation: Order object/db record: id_address_delivery: x id_address_invoice: y Cart object/db record: id_address_delivery: y id_address_invoice: y the result is that the customer pays wrong shipping costs, calculated on y instead of x. I've tried to reproduce this issue in every way I could imagine, but everything worked as expected. Have you ever encountered a problem like this? ---------------------- I'm using Prestashop 1.6.1.10 (updated, not installed with this version) with a bought theme (leo_shoesworld)

Salve a tutti, Halloween ormai è passato, ma un paio di settimane fa ho dovuto affrontare un problema con delle regole carrello che volevo far applicare "a cascata", e non ne sono venuto a capo Un carrello di esempio potrebbe essere questo: In quell'esempio potete vedere un prodotto con 2 codici sconto applicati: SHIPPING DISCOUNT PROMO => sconto di 5€ sull'importo del carrello HALLOWEEN 2105 => sconto del 10% sull'importo del carrello Le priorità che ho settato per queste 2 regole sono le seguenti: SHIPPING DISCOUNT PROMO => priorità 2 HALLOWEEN 2105 => priorità 10 Nel pannello admin di prestashop c'è scritto che le regole con priorità più bassa verranno processate prima di quelle con una priorità più alta. Quindi mi aspetterei un comportamento del genere: Valore del prodotto: 155€ Viene applicata la regola "SHIPPING DISCOUNT PROMO": 155€ - 5€ = 150€ Viene applicata la regola "HALLOWEEN 2105": 150€ - 10% = 135€ Vengono aggiunte le spese di spedizione, quindi: 135€ + 14.60€ = 149.60€ Il problema è che, quando viene applicata la regola "HALLOWEEN 2015", lo sconto del 10% viene calcolato sul prezzo originario del prodotto, quindi senza considerare le eventuali regole/sconti applicati prima. Ho provato anche a scambiare le priorità ma non è cambiato nulla, tutto viene calcolato sempre sul prezzo del prodotto non scontato. Qualcuno si è imbattuto in questo tipo di problematica? Idee per risolvere? Grazie a tutti

Any Prestashop expert can help with this?

No one having this issue or a possible solution? It's kind of urgent..

HI all! I have a problem with cart rules that I would apply "on cascade". My example cart is like this: You can see there is a product with two discount codes applied: SHIPPING DISCOUNT PROMO => discount -5€ on cart's value HALLOWEEN 2105 => discount -10% on cart's value You can see the priorities set for these 2 rules: SHIPPING DISCOUNT PROMO => priority 2 HALLOWEEN 2105 => piority 10 In the prestashop's backoffice it tells that rules with lower priority will be processed before rules with higher priority. So I expect that the cart will be: Product's value: 155€ Rule "SHIPPING DISCOUNT PROMO" applied, so: 155€ - 5€ = 150€ Rule "HALLOWEEN 2105" applied, so: 150€ - 10% = 135€ Shipping cost added, so: 135€ + 14.60€ = 149.60€ But when the "HALLOWEEN 2105" rule is applied, the 10% discount is calculated on the original item's price (without other rules applied before) How can I fix this? Priorities seem to be ignored by Prestashop. Thank you all for every help you'll provide!

Anyone? It's very critical, and urgent enough..

Hello, I have a very critical problem on the pagination links in blocklayered module in a shop based on PS 1.6.0.6. The pagination links seem to work well until I set a filter on the layered navigation module; if I do that, the pagination links become broken, and clicking on one of them, prestashop presents a "page not found" error. I think it's due to the fact that the links are not "friendly", because if I append "&p=2" (for example, to go to page #2) to the url I have after filtering, it comes interpreted well. I tried to: update the module uninstall, replace all the module with the one that comes with Prestashop 1.6.1.0 and reinstall replace the blocklayered.js file with the one I've found on GitHub - shared by someone on the bugtracker in relation to other pagination problems replace the Link.php class from the one that comes with Prestashop 1.6.1.0 and nothing solved the problem. If you want to see the issue, you can go to: http://floppypipe.it/71-pipe-originali and test pagination, that's working well. Then, make a filter (all's right with that) and try to go to another page (page #2 instead of page #1, for example).. the link is broken! Any help or suggest would be really appreciated, because after hours spent trying fixing this I have no more ideas

Hi all! I just fixed the same problem on Prestashop 1.6.0.6 The shop's owner called us because the voucher block didn't appear on Mac platform (latest O.S. version) with Chrome browser. I've verified that also on my Firefox (latest version) on Windows 7 the block didn't appear, so I found this topic and solved changing the ID of the block like amerigeau described. Is it possible that after 2 years (the first post has been written in 2013) this problem continues to affect the PayPal module? Why is there a line that removes the voucher block's content? I can't figure it out Maybe someone of the Prestashop Gurus can help to understand this? Thanks anyway for providing me solution P.S.: updating the PayPal module didn't help at all, the problem continues to be there.

Yep, I know. I've read both those guides and I appreciate them so much. But there are not so many examples and they explain how to realize a very simple module. So when I face new errors I search in the forum, then through internet with Google, and the informations that can be found are precious but at the same time confusional, fragmented, and not always compatible with the version I'm using or I wanna fix. Many times, I've found different people facing the same problem in different ways, and I really don't know the best practices I should follow. I'm not saying "I don't wanna study, you have to tell me what I have to do to make a brilliant module!"... I'm only saying that there's not a great documentation about all the aspects a developer have to face to make advanced modules I'm not new to developing in Prestashop, and I'm not even new to PHP, OOP and MVC. But sometime I find difficult to find solutions because I'm not one of Prestashop's creators, and it would be great to have a scheme saying: * for 1.6 version you should be doin' this and NOT that * to assure compatibility with 1.4 you should add this method and so on.. these are example, ok? Guidelines, only and simple guidelines

Well, my topic is not about a blank page I can't figure out. At all. It's about receiving guidelines to handle modules' compatibility through the various Prestashop's versions. Because (correct me if I'm wrong) there should be - imho - a section in the developer's guide about this argument, but there isn't. It's a suggestion, a sort of "Hei, why don't we do it?" A free opinion, something to help developers to make quality modules; if the community wants to grow, it has to help other people to know the platform, and how to handle these problems. A clear, rich, well-done documentation is the key. P.S.: my suggestions are about development, so I chose this section to make my topic. If it's wrong, feel free to move it to another section

Yes, I tried to reinstall several times but nothing changed..

No one interested about this??

Sorry for being late in answering, I returned in the office today No, there are no errors and yes, the hook appears and it seems to be connected with my module. Here is the code I use: Constructor of the class public function __construct() { $this->name = 'roundview'; $this->tab = 'front_office_features'; $this->version = '1.7.5'; $this->author = 'NORZ SRL'; $this->need_instance = 0; $this->ps_versions_compliancy = array('min' => '1.5', 'max' => '1.6'); $this->bootstrap = true; $this->roundview_img_upload_path = _PS_IMG_DIR_.'roundview'; parent::__construct(); $this->displayName = $this->l('Roundview'); $this->description = $this->l('Give your products a wonderful 360 view!'); $this->confirmUninstall = $this->l('Are you sure you want to uninstall? The folder with all your -360 view- images will be deleted! Be sure to have a backup before proceeding.'); } Registering the hook in the install method public function install() { if (Shop::isFeatureActive()) Shop::setContext(Shop::CONTEXT_ALL); if (!parent::install() || !$this->registerHook('displayAdminProductsExtra') || !$this->registerHook('displayRightColumnProduct') || !$this->registerHook('displayHeader') || !$this->registerHook('displayBackOfficeHeader') || ) return false; return true; } The hook's method public function hookDisplayAdminProductsExtra($params) { $id_product = (int)Tools::getValue('id_product'); if (Validate::isLoadedObject($product = new Product($id_product))) { $images = Db::getInstance()->ExecuteS('SELECT .....'); $active = Db::getInstance()->ExecuteS('SELECT .....'); $this->context->smarty->assign(array( 'id_product' => $id_product, 'roundview_images' => $images, 'active' => (!empty($active[0]) ? $active[0]['active'] : false), 'base_dir' => _PS_BASE_URL_.__PS_BASE_URI__ )); return $this->display(__FILE__, 'views/templates/admin/RoundviewForm.tpl'); } } All the other code is to uninstall the module or to handle other various hooks. Is there something that doesn't work with the 1.5.0.1 PS version?

Hi all! These days I'm starting so many topics 'cause developing a module makes me reflecting about different aspects about Prestashop platform Btw, I tried to install the module I'm developing on the 1.4.9.0 version (of Prestashop, of course) and the installation fails at all. It gives me a blank page with no errors and no alert messages, so I can't figure out what's wrong. I could study how the modules for 1.4.x version are installed to find differences in the process and maybe fix the problem, but the question I've in my mind is more generic: How do we (the developers) have to manage the modules' compatibility? If I develop (as I'm doin') a module starting on the 1.6.x PS version (the newer one), how can I assure and manage the compatibility for the older PS versions? How I change and structure my code? Are there guide lines for doin' this? And if not, maybe someone from the PS staff could write a guide all about compatiblity. I've read the developer's guide but I can't remember anything about it. What do you think about? I'd love to do it myself (I love to write documentation, yes... maybe I'm crazy), but I've not enough experience in PS development