Geo Burlibasa

Salut, Se poate testa in demo-ul de aici: https://addons.prestashop.com/en/shipping-carriers/46400-romanian-carriers-fan-courier.html Nu incetineste magazinul atat timp cat e folosit pe modul de calcul local. Modulul original incetineste magazinul pentru ca face apeluri API pentru preluarea costului de transport la fiecare incarcare de pagina. Nu e cazul modulului meu.

Salutare, Problema din printscreen-uri este total diferita de problema descrisa in topic. Problema din printscreen poate fi rezolvata cu modulul asta: https://addons.prestashop.com/en/seo-natural-search-engine-optimization/47867-google-breadcrumb-schema.html Cat despre preturile cu TVA, cam orice programator te-ar putea ajuta cu depanarea si rezolvarea problemei, e cam imposibil de depanat pe forum, e nevoie de date.

Ca sa vinzi la preturi diferite acelasi produs in acelasi cos si in aceeasi comanda s-ar putea sa ai de rescris mii de linii de cod. S-ar putea sa nu fie cea mai buna varianta dpdv tehnic. Trebuie sa te pui la masa cu un dezvoltator cu experienta si sa stabiliti concret cum sa functioneze. Sunt foarte multe scenarii de discutat si orice mica variatie de la implicit poate aduce batai foarte mari de cap. Trebuie discutat tot cap-coada.

Am mai facut marketplace-uri, dar sa ai acelasi produs (acelasi obiect) la mai multi selleri pare sa incurce putin treaba. Daca seller-ul 1 are 1 buc. pe stoc, seller-ul 2 are tot 1 buc., iar clientul vrea 2buc, dar sunt la pret diferit, cum gestionezi?

There is no recommended behaviour on this manner, you can not do this without user intervention or without automatically altering the TPL files (which can lead to issues if not done correctly, or if the theme has big differences from the default one). What I mean by both is you can let the user choose which of the methods to use, in the configuration form of your module: 1. If he knows how, let him modify the tpl file manually; 2. If he does not know how, use the javascript method but inform him about the consequences.

Hello, Why not both? Let the user choose the method desired.

Hello leadi, You could just hide the password field via CSS rules (if you have technical knowledge) if you are using Prestashop 1.7. If the password is left blank, then the customer will be a guest. As for disabling the account creation process outside of the checkout feature, you could just hide the module that displays the Customer widget in frontoffice, usually in the upper right corner. The module name depends on your theme, in the default theme it's "ps_customersignin".

Just comment the {block} using {* CODE HERE *}. Creating a child theme can sometimes be problematic if the theme/modules are already configured, it's usually recommended to be done exactly after installing the theme, and not after.

Are you using a module for Checkout? Like Supercheckout, The Checkout, etc.?

You may want to provide us some more info: 1. Will you enable only guest-checkout? Or the ability to checkout will also be disabled (it can't work without an account)? 2. Before checkout it should be available?

Use this: https://github.com/hyperized/benchmark or this: http://php-benchmark-script.com/

You might want to try to use a cache module, it will not fix the actual issue but it will reduce the stress on the database which will surely help. To fix the actual issue you would need to talk to a developer to check the loading time of the algorithms. In my experience, carrier modules which calculate the shipping cost based on API calls can slow your frontoffice a lot, you might want to check that.

You can not add or modify products in Prestashop if the Delivery has already been made. Changing the status to an already delivered order will not help either. Order delivered = The order has been at least once in a status which has "Delivery" set to "true", as in the above example.

Check if there is any available update for the module, it might be.

Cred ca ai toate motivele sa apelezi la un dezvoltator, nu par a fi probleme ce le vei putea rezolva cu ajutor de aici. Sunt multe de depanat.