Jump to content

Daresh

Members
  • Posts

    2,553
  • Joined

  • Last visited

  • Days Won

    21

Everything posted by Daresh

  1. A czy w edycji atrybutu produktu masz poprawnie je ustawione? (Katalog -> Atrybuty -> Rozmiar -> kolumna "Pozycja")
  2. Checkout w Preście jest daleki od ideału, w tej sytuacji jedyne szybkie rozwiązanie, jakie mi się nasuwa to przestawienie go na one-page.
  3. Miałem tak kiedyś, ale to się działo na kopii modułu bankwire, która miała zmienioną nazwę na bankwire2. Tutaj chyba nie zachodzi taka sytuacja? Poniższy kod odpowiada za to sprawdzanie: // Check that this payment option is still available in case the customer changed his address just before the end of the checkout process $authorized = false; foreach (Module::getPaymentModules() as $module) if ($module['name'] == 'bankwire') { $authorized = true; break; } if (!$authorized) die($bankwire->l('This payment method is not available.', 'validation'));
  4. Witam, mamy w ofercie moduł robiący dokładnie to. Można w nim ustawić grupę wyjściową oraz grupę docelową i w momencie zmiany jednej na drugą klient dostaje maila. Zapraszam: [email protected]
  5. Generally you translate the modules via Prestashop translation menu, not the files.
  6. Commenting all that stuff out may not be the best idea to bypass that message. It allows the customer to click the payment method button and proceed with missing data or not accepted rules, This can cause in effect even more confusion and make the customer resign. It would be much better to display the payment methods, but with disabled links, that when clicked will make the customer stay on the checkout page and remind him of the remaining errors. I am working on a small module doing just that, many people complain about this feature causing client's confusion.
  7. Raczej chodziło o to, żeby klient dostawał maila po rejestracji, bo to jest, jak również możliwość wysyłania rabatu. Co do wysyłki - Eolia newsletter jest darmowy i działa ładnie.
  8. A czy w konfiguracji modułu blok newslettera jest włączone przesyłanie do klienta? Musisz też pamiętać o tym, że ten newsletter może wysłać potwierdzenie i rabat, ale nie ma funkcjonalności wysyłania faktycznego newslettera, do tego potrzebne są inne moduły :-)
  9. Warto by było chociażby zobaczyć sklep :-)
  10. Hi, this is not the correct way to approach this. The crossselling module is for displaying cross-sells on the product's information page, not on the add to cart popup. The add to cart popup is generated in the blockcart module. The module has its own crossselling template and adds the crosssels in a different way than the crossselling module. So you would need to replace those crosssells in the blockcart module with accessories. And then, of course, change the 'also bought' translation. I am currently working on a module replacing those crosssells with accessories, if you're interested in purchasing such a simple module, let me know.
  11. Hello, I've got the same problem, have you found the solution?
  12. Hard to tell, maybe the slider includes some js scripts that are in conflict with some other js scripts.
  13. This looks like some error in the slider, maybe you have some slider installed that messes up the js?
  14. Hi! This is a very simple module based on the jQuery CookieBar plugin. The goal was to make it as simple and convenient as possible, so you can set up the message's position (top or bottom), whether to display link to privacy policy page and select the cms page with the policy rules. The messages displayed are configured through the module's translation system (why reinvent the wheel?). The message hooks to the <div id="page"> so it should be compatible with most of the templates. If anyone would need some more options (with regard to the CookieBar plugin), let me know and I will consider extending. gmcookie.zip
  15. As I see it, there is no chance to remind that in he validation email, because the password is encoded in the database.
  16. But the password is encrypted in the database. It is only known and sent to the client when he registers, not whe you validate him.
  17. Zauważyłem bardzo dziwne zachowanie przycisku "Do koszyka" gdy jest on wyłączony dla produktów z atrybutami. Na stronie kategorii działa dobrze, przycisku nie ma: http://krainamotywacji.pl/40-poduszki-dekoracyjne Na stronie wyszukiwania działa dobrze, przycisku nie ma: http://krainamotywacji.pl/szukaj?orderby=position&orderway=desc&search_query=poduszka%20czerwona Na stronie wyszukiwania według tagów działa źle, raz jest, raz nie ma: http://krainamotywacji.pl/szukaj?tag=poduszka+czerwona (Presta 1.6.0.11) Co to może być?
  18. Then I don't know. I wrote it from the air, I would have to test it in the real code to make it work...
  19. Has anyone found a fix for this? Is it fixed in later versions?
  20. I would try something like: $this->context->smarty->assign('telnumber', Configuration::get('blockcontact_telnumber')); in the initContent() function, and then use {telnumber} in template file. Should work (I didn't test it though).
  21. I found the cause. It's the same as in this thread: https://www.prestashop.com/forums/topic/323673-16-backoffice-dashboard-not-displaying-any-sales-data-after-upgrade/ (when invoicing is turned off)
  22. When I go to the customers list on my shop, most of them have zero value in the "Sales" column. This happens for customers who have paid by wire transfer and I accepted the payment manually. For customers who paid with PayPal the value is correct. What can be wrong? PS 1.6.0.9
  23. So that would not be so straightforward as with the Siret. The customer can have many addresses, there is a getAddresses() method in the Customer class, you would need to use it and then go looking for the VAT number. As for the telephone I would rather modify the validate controller to get that configuration value, and then pass it through smarty to the template file.
  24. This is a very interesting module, thanks for sharing :-) Sam, of course it is possible, in the section where the email is sent there is an array with data for the mail template: array('{email}' => $customer->email,'{shopname}' => $this->context->shop->name), Just add fields that you want, like: '{siret}' => $customer->siret And then use it in the e-mail template. (I don't see VAT number field in the Customer class, but maybe it has some other name...) I have one more question regarding the module - is it really necessary to have that additional table in the database? Wouldn't it be just fine to send the email to the customer when his account is activated in the back office?
×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More