Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 01/19/2021 in all areas

  1. 2 points
    Buonasera, ricerchiamo partnership con sviluppatore o azienda che ci segua per assistenza su sito web prestashop e progetto di sviluppo. massima urgenza e attendibilità richiesti. cordialità davide alessio mokaor.shop +393925481925
  2. 1 point
    TNT Pricing module. Module receive shipping info from TNT web-service and shows to customer price and estimated time of delivery. Tested and works on PS 1.7.7.1 and PS 1.6.1.24. You need TNT account credentials. Module use php-CURL extension for communication with TNT web-service. One table in database for caching queries and errors logging. Module support those TNT services: 9:00 Express (09N) 10:00 Express (10N) 12:00 Express (12N) 12:00 Economy Express (412) Express (15N) Economy Express (48N) You must correctly indicate the ISO code of your country, city, postal code. If this module help you, please use the Donate button in the module settings. Now I am collecting errors related to postal codes and working on automatic correction. For example, when a web service requires a code like "LT-02180" and user stored postal code without a prefix "LT-". In this case the module must automatically add prefix, because it is for this country that the web service accepts a request only with a postal code prefix. These and other extensions will be added and upgraded for this module in future. Version 1.0.0 tntpricing.zip
  3. 1 point
    If you edit the first post of the thread you can manually add "[solved]" to the subject line.
  4. 1 point
    No doubt there are better solutions. But one option you could try is the function Prestools to export file lists of a Prestashop installation. That way you can compare them with a similar list from your localhost that is guaranteed safe and see where there are extra files and were there are differences in file size. (shop-rescue -> File list export)
  5. 1 point
    Thanks for the suggestions. I have deliberately moved away from Mailchimp and started using the paid module produced by Crezzur, though not without difficulties I admit. But, it is working. I have already made sales based on yesterday's newsletter, but have to solve the issue of unsubscribing. The newsletter has an inbuilt 'unsubscribe' and that works ... but where I have to do so myself, which is a requirement under GDPR (that anyone can request that I do this), I have no viable route. I've been put off reporting on github for an instance like this. Essentially, I can observe that I have a red X in the customer list, but green subscribed in the account for the customer, and I cannot alter this. There is no error message to report. I've tried to report similar things before, but told I must fill in the correct format of report. Then when I try, I have an email saying there is not enough detail to replicate this and the report is cancelled. This latest seems the same: I can observe a problem, but no error message, so it seems not worth trying to make a report to github. The only solution I have found for changing the newsletter subscription is to change the password, then use the 'login as customer' module and use the password to allow me to save the change. Of course, the customer must now use a password reset but it is better than me potentially breaking the law by sending a newsletter illegally. I'm surprised that the newsletter registration doesn't have a field to change inside the customer record in BO (other than when looking at the big list). I do thank you immensely for your feedback and suggestions. It's very much appreciated, and thank you for your time.
  6. 1 point
  7. 1 point
    To elaborate on Robhur's points: - Prestashop upgrades quite regularly fail. For that reason it is recommended only to upgrade when you have a good reason like a bug that has been fixed in a new version. - Best practice for upgrades: make a good backup before you upgrade and don't rely on the backup that Prestashop makes during the upgrade. Note that module upgrades are usually ok. - In principle minor upgrades (1.7.7.x) shouldn't cause problems for modules and themes. In most cases things will be ok. However, you can never be sure. For that reason it is recommended to keep a copy of your webshop for testing and experimenting purposes. The easiest is to have it on your pc.
  8. 1 point
    Der Wahnsinn! Es hat tatsächlich funktioniert! Ich danke dir vielmals
  9. 1 point
    Sprawdzasz sobie jaką klasę ma dane zdjęcie i nadajesz jej styl .klasa { max-width:100; } to wszystko.
  10. 1 point
    Merci, ça fonctionne, j'avais testé quelque-chose dans ce style, mais qui ne fonctionnait pas avec la version 1.7.7 {assign var='features' value=Product::getFrontFeaturesStatic($cookie->id_lang, $product.id_product)} {if isset($features) && $features} {foreach from=$features item=feature} {if isset($feature.value)} {$feature.value|escape:'htmlall':'UTF-8'}: {$feature.name|escape:'htmlall':'UTF-8'} {/if} {/foreach} {/if} et j'étais du coup parti sur une solution plus fastidieuse que j'avais trouvé ailleurs et qui avait le mérite de fonctionner, mais je vais revenir à votre code plus simple : {if isset($product.features) && !empty($product.features)} {*$product.features|@var_dump*} {foreach from=$product.features item=features} {*$features.id_feature_value|@var_dump*} {if $features.id_feature==3} {assign var=feat value=FeatureValue::getFeatureValueLang($features.id_feature_value)} <!-- parcourir si plusieurs langues --> {if !empty($feat)} {foreach from=$feat item=myfeat} <span class="product-appellation">{$myfeat.value}</span> {/foreach} {/if} {/if} {/foreach} {/if} Merci encore !
  11. 1 point
  12. 1 point
    Gute Idee. SQL ist immer noch ein rotes Tuch für mich und die meisten meiner Abfragen wären ohne dieses Forum nicht zustande gekommen. 1. Bestellhistorie bestimmter Artikel SELECT DISTINCT date(o.date_add) AS Datum, o.id_order AS Bestellung, od.product_quantity AS Anzahl, od.product_reference AS BestellNr, od.product_name AS Artikel, od.total_price_tax_incl AS Summe, c.`id_customer` AS Kundennummer, c.`firstname` AS Vorname, c.`lastname` AS Name FROM `ps_customer` c LEFT JOIN `ps_orders` o ON (c.`id_customer` = o.`id_customer`) LEFT JOIN `ps_order_detail` od ON o.`id_order` = od.`id_order` WHERE od.`product_id` =XXX Die drei XXX am Ende einfach durch die ID des gewünschten Produkts ersetzen. 2. Zum checken bei welchen Kunden die Standardkundengruppe vom Soll abweicht SELECT c.id_customer FROM ps_customer c LEFT JOIN ps_customer_group cg ON (c.id_customer = cg.id_customer) WHERE cg.id_group=3 AND c.id_default_group!=3 Mir ging es dabei um die Kundengruppe 3 "Customer" da die bei Kunden die zuvor "Guest" waren nicht immer automatisch auf "Customer" geändert wurde. 3. Simple Abfrage mit Kundenname, E-Mail und Land des Kunden SELECT a.`firstname`, a.`lastname`, a.`email`, (SELECT c.`date_add` FROM `ps_guest` g LEFT JOIN `ps_connections` c ON c.`id_guest` = g.`id_guest` WHERE g.`id_customer` = a.`id_customer` ORDER BY c.`date_add` DESC LIMIT 1) AS `last_activity`, (SELECT cl.`name` FROM `ps_address` ad LEFT JOIN `ps_country_lang` cl ON cl.`id_country` = ad.`id_country` WHERE ad.`id_customer` = a.`id_customer` ORDER BY ad.`id_address` DESC LIMIT 1) AS `country_name` FROM `ps_customer` a
  13. 1 point
    Recomand. Extrem de operativ si confirm FIX-ul.
  14. 1 point
    Load all your images with the product and reference in the combination file the position of the image (in the Image Position entry) of this combination. FE. prd.csv 12324;"Test product";"image1Red.jpg, image2Red.jpg, imageBlue1.jpg, imageBlue2.jpg" combinations.csv "Product ID";"Atribute Name";"Attribute Value";"Image Position" 12324; "color, size";"Red, S", "1, 2" 12324; "color, size";"Red, M", "1, 2" 12324; "color, size";"Red, L", "1, 2" 12324; "color, size";"Blue, S", "3, 4" 12324; "color, size";"Blue, M", "3, 4" 12324; "color, size";"Blue, L", "3, 4"
  15. 1 point
    Salutare, Modulul de mobilpay inca nu e compatibil cu Prestashop 1.7.7. Cu niste modificari de cod (doar in modul) se poate compatibiliza. Puteti astepta sa faca ei update, sau imi puteti scrie un mesaj in privat si pot rezolva contra-cost in timp util.
  16. 1 point
  17. 1 point
    Hello guys, do you know How can i show weight of the order in shopping cart?? I've set delivery with weight , and i want to show to buyer total price of his cart. Thanks! PS: If there's a way to show weight on product page please help me.
  18. 1 point
    https://mypresta.eu/modules/front-office-features/product-price-range-from-to.html
  19. 1 point
    Wenn sich der Aufwand in Grenzen hält ist das händisch natürlich zu machen, ansonsten schau dir mal das Modul GifCard3 an. Ist ziemlich simple, aber läuft. Das einzige was du beachten musst, egal ob mit Modul oder von Hand ist dass die Warenkorb-Preisregeln nicht auf den Gesamtbetrag anwendbar sind und dadurch die Versandkosten immer noch separat bezahlt werden müssen.
  20. 1 point
    Hi, This is product attributes and combinations. You have by default . But you can some modules like this one to show all options :
  21. 1 point
    Ok, j'ai compris d'où vient le problème. Au moment de greffer le hook sur le module, j'ai mit : return parent::install() && $this->registerHook('hookActionValidateOrder') au lieu de return parent::install() && $this->registerHook('actionValidateOrder') tout fonctionne correctement maintenant.
  22. 1 point
    Bonjour à tous Sur PS 1.7.5.0, impossible de changer l'ordre des moyens de paiements. En changeant l'ordre sur Positions, ça ne change rien sur le FO (thème classic). => les modules de paiements sont affichés dans l'ordre des ID de module. J'ai regardé dans la bdd, la table hook_module a bien enregistré les bonnes positions. Je n'ai pas trouvé à quel endroit dans le code, cet ordre est oublié. Si vous avez une solution, je suis preneur ! Rien vu sur le bug tracker à ce sujet
  23. 1 point
    Ich würde immer das Modul nutzen. Wenn da bereits Fehler passieren ist ein manuelles Upgrade noch gefährlicher. Besser wäre es den Fehlermeldungen vom 1.click modul auf den Grund zu gehen, welche sind denn dies?
  24. 1 point
    Ca se passe sur le site http://connect.mondialrelay.com/ et il faut quelques jours pour que cela soit pris en compte.
  25. 1 point
    C'est le même principe pour boxtal, une fois les transporteurs selectionnés, ton client valide sa commande et son point relais. Tu va sur le site boxtal puis envoi à traiter. Tu importe tes livraisons et comme zekid l'indique, il faut indiqué le poids et les dimensions du colis que tu va utiliser. une fois cela fait, tu valide la commande de ton ou tes bordereaux et tu les recos en PDF. Lorsque je reviens sur mon BO, les commandes concerné sont passés en "préparation en cours" automatiquement. J'avais même activé la création de la facture avec le statut " préparation en cours" comme cela, la facture était généré lorsque l'on édité le bordereau de livraison. Ma femme préfère généré la facture manuellement donc j'ai enlever cette option.
  26. 1 point
    Why not? Distance between key words plays no role in the Prestashop search algorithm. And as all products have the same weight for those keywords the determining factor becomes the way they happen to be stored.
  27. 1 point
    Hi @Pex The index is big because you sue really big images. The entire Index page loads over 16.5 MB This should be below 1.5 MB . to give you an example : The above image has 1.9MB In case you would optimize it, and instead of using a PNG, you would a jpg version (the images doesn't need to be transparent) + you would optimize the JPG image version you can easily end up with an image which would be a fraction of it, like 250-400KB. Once you solved all your issues with the images the site will load way faster. Lazy loading is an option, but I wonder if somebody would build that in into your slider module https://developers.google.com/speed/pagespeed/insights/?hl=en&url=https%3A%2F%2Fthemegamart.in%2F The above is a Google Quality score! Start optimizing your store, a s soon as you can;)
  28. 1 point
    First of all, that "2" in "Mavic 2" won't work. Prestashop has a minimum length of 3 positions. The logical approach would be to increase the search weight of the main product. But of course that will be hard when you have the weight for description, tags, etc set to zero.
  29. 1 point
    Hi, you should enable the debug mode and then add the new category, so the reason for the error 500 to be displayed on the screen, then sand here all the error/exception. Then we can guide you about where the issue is, as most probably some module or override is causing this. Kind regards, Leo
  30. 1 point
    Hola mira que la web trabaje en php 7.3
  31. 1 point
    A fast loading website is the goal of every shop owner, as a slow website can lead to a long list of issues, from disappointed customers who lose patience and abandon their cart, to an overloaded server that stops working, and search engines penalizing your site's ranking due to speed. After helping countless PrestaShop sites optimize and increase their speed, including adding timers around different parts of PrestaShop and analyzing what is taking long and why, we have decided to share our obvious and no-so-obvious findings, and help the entire PrestaShop community. Caching & CCC PrestaShop has several layers of caching, we'll start with the ones on the Performance page * Smarty (Template compilation) Should be set to "Recompile templates if the files have been updated" - This will make sure PrestaShop uses smarty cache at all times, and only recompiles a file if it was changed. * Cache (Caching type) Should be turned on, with File System selected. * CCC (Available on certain PS version) We recommend turning OFF Minify HTML and Compress inline JavaScript in HTML - We noticed PrestaShop was spending a long time (sometimes several seconds) when these features are enabled, which means that any benefit from the compression is more than negated by the slow speed. * Ciphering (Available on certain PS versions) We recommend selecting the "Use the custom BlowFish class" - We found that when the server load was high, saving a cookie on the client side with Mcrypt was taking up to several seconds (due to an issue with randomly encrypting the cookie). Switching to blowfish kept the cookie saving time to a few miliseconds. * Caching (Bottom of the performance page) We recommend turning OFF, as we have seen this feature cause more trouble than offer benefit, with module settings not being updated, and other unexpected behavior. * Install a server side caching system, such as OPCache, you would have to check with your hosting provider to see if it's available, and if they can activate it on your website (You may need to reset the cache after making changes to PHP files, in order for the changes to apply right away. Email * SMTP We highly recommend NOT using a 3rd party SMTP server, we have seen speeds of up to 3-5 seconds sending a single email using a 3rd party SMTP server. * PHP mail() We recommend using this option, however, even with this option selected, we noticed that some versions of PrestaShop had a slow send time (1-2 seconds) due to the Swift version that was installed. If you are using PS 1.5, or even an early version of PS 1.6, you may want to make sure sending emails is not taking a long time (Normal time should be around 0.2 seconds.) Modules / Customizations * Shipping / Tax If you are using any 3rd party modules or services, such as UPS, FedEx, TaxCloud or Avalara, PrestaShop will make API calls whenever a product is added to the cart, and even if they have proper caching in place to avoid making the same API request more than one time, it will still require an API for each new product added, and can take several seconds to do so. Whenever possible, use fixed shipping rates, and if you must use those 3rd party services, we recommend making changes to only calculate taxes and shipping when the customer gets to the checkout page. * Carousel If you are using a product carousel module or customization, or similar upsell / product recommendation that is reading product information to display it, make sure they are using a caching system to avoid doing identical calls to the database that return the same data, and take a long time to run. If you are not sure about their caching, ask the developer, or try to disable the module and compare page speed. Database * Analyze & Repair Databases can get corrupted at times, which will result in queries taking longer. It is recommended to periodically check and repair your database tables, this can be easily done from PHPMyAdmin, by selecting all the tables, and choosing the "Check" option at the bottom. If you see any tables with errors, select them and choose the "Repair" option. * Connections PrestaShop keeps visitor information for statistic purposes in 3 tables, and actively queries ps_connections before writing to it, which can take a long time if the tables gets really big, that in turn can lock up the database, and delay the time it takes for the page to load for all the visitors. We recommend backing up and clearing this table once a year, or sooner for sites with a large number of visitors (Try keeping the table size to less than 500,000 records). ReCaptcha * Google ReCaptcha We noticed a substantial slowdown in the time the front end page finishes loading (sometimes taking 5-7 seconds). We recommend restricting the ReCaptcha code to a specific page (like contact form) rather than enable it for all page loads (in case there's a newsletter signup form in the footer). Miscellaneous * Debug Profiling There could be other things that cause your website to be slow, and the best way to get more information and identify the culprit is by enabling the Debug_Profiling variable in /config/defines.inc.php (Change from "False" to "True". This will generate a report in the front end with exact timing of every part in PrestaShop, including every Database query. You will have to inspect the report and identify any parts that are slow. Keep in mind that this will show up for all visitors, so make sure you only change it for your IP address, unless you are working on a development environment. For the latest updates to the list, see https://www.presto-changeo.com/content/23-tips-on-how-to-speed-up-your-prestashop-website
  32. 1 point
    Gracias, yo llevo poco tiempo desarrollador de PS, aunque todos los desarrolladores dicen lo mismo. lo peor es la documentación de la API, me daría vergüenza ser uno del equipo de PrestaShop y ver la documentación de la competencia
  33. 1 point
    Hi, Try deleting the line 20, which contains the following: use PrestaChamps\MailchimpPro\Formatters\ListMemberFormatter; from the modules/mailchimppro/mailchimppro.php file
  34. 1 point
    Hay algunas tiendas que van conectadas a un ERP, o donde los productos se suben o se modifican a través de aplicaciones externos. En estos casos puede ocurrir que se hagan modificaciones en los productos y no se vean reflejadas inmediatamente en la portada de la tienda debido a la caché de Prestashop. Parecido puede ocurrir con algunos módulos que muestran información de fuentes externas (por ejemplo, desde Facebook, Instagram o un blog externo), que a veces pueden actualizar la información y a pesar de eso que siga apareciendo en portada de la tienda la antigua, debido a que está cacheada. Para todos esos casos se puede utilizar este módulo. Solo hay que instalarle, activarle e indicar cada cuánto tiempo se quiere que se borre la caché (por ejemplo, cada hora). Transcurrido ese periodo de tiempo, se efectuará automáticamente un borrado de la caché. También se puede elegir la activación mediante CRON, proporcionando una URL cuya llamada es posible programar en el CRON del servidor con el intervalo que se quiera para efectuar el borrado de la caché. Versión 2.1.0 disponible para Prestashop 1.6 y 1.7: ftm_cacheclear.zip
  35. 1 point
    I implemented the above solution into 1.7.6 and it did not fully solve the problem, particularly for visitors. I managed to find a decent and simple solution for this after a day of debugging. My solution for 1.7.6 for this problem was to first enable Geolocation, then add a check for the visitor's country in the Carrier class before the default Prestashop country is used. How it works: Geolocation stores the visitor's country iso code in the user's cookie and this is used to select the appropriate carriers and this is properly displayed in the shopping cart. If there are multiple carriers, then the options set in Shipping->preferences will determine what is shown. WARNING: This edit is done directly on a core Prestashop class. Do not do this on a production environment! classes/Carrier.php: line 1505 $id_address = (int) ((null !== $id_address_delivery && $id_address_delivery != 0) ? $id_address_delivery : $cart->id_address_delivery); if ($id_address) { $id_zone = Address::getZoneById($id_address); // Check the country of the address is activated if (!Address::isCountryActiveById($id_address)) { return array(); } // Start of edit // // Check for visitor's country } else if (isset(Context::getContext()->cookie->iso_code_country)){ $country_id = Country::getByIso(Context::getContext()->cookie->iso_code_country); $country = new Country($country_id); $id_zone = $country->id_zone; // End of edit // } else { $country = new Country($ps_country_default); $id_zone = $country->id_zone; } Hope this helps someone else.
  36. 1 point
    The project Core Web Vitals from Google has announced that loading time and performance will have an impact on the website ranking in search results. Google mentions lazy loading in their suggestions. Lazy loading will be available on Classic Theme in version 1.7.8 thanks to Progi1984 and it will definitely improve both user experience and loading time on your site! What is lazy loading ? Lazy loading is a technique that defers loading of non-critical resources at page load time. Instead, these non-critical resources are loaded only when needed. For example, images which are at the bottom of the page are less critical than images at the top of the page and should consequently be loaded later. This feature used to be provided by third party plugins or modules but is now supported natively in all modern browsers. How can I enable native lazy loading on my theme ? Browsers use the loading attribute on the <img> tag to defer loading of images that are off-screen until the user scrolls near them. Consequently on all your <img> tags, you must set a loading attribute with value lazy. And it’s done. What browsers support this feature ? This information can be found on multiple sources, such as “Can I Use”. In 2020, native lazy loading is enabled on 68% of used browsers. And if the feature is not active on the browser, images will be loaded as usual. PrestaShop Classic Theme performance analysis At first, we considered using Lighthouse which is an open-source, automated tool for improving the quality of web pages. But after a few attempts, we encountered an issue in Lighthouse that prevented us to do so. It turns out the detection of lazy loading images is only performed in heavy pages (min 5000px). Core developer Progi1984 chose to use the Google Chrome console and its Network tab in order to show you the performances evolution before and after lazy loading usage. This test is based on the New Products page with 50 products (and so 50 images minimum) per page. The benchmark is performed on develop and lazyloading branches. First scenario is performed against develop branch. Two measures are performed: the first on desktop mode with no throlling the second on emulated device “iPad Pro” mode with Fast 3G throlling Second scenario happens on lazyloading branch. Two measures are performed again: the first on desktop mode with no throlling the second on emulated device “iPad Pro” mode with Fast 3G throlling A gain of 21% to 28% can be observed with lazyloading. You are left to imagine the possible gains for users who browse your websites all around the world, with different connections profiles. Conclusion As a developer or theme provider, implementing this feature is a very good investment. The implementation is easy and the gain is huge is all we have to say. View the full article
  37. 1 point
  38. 1 point
    Hi all, in this post/guide I'd like to show you how to have an independent invoices' numeration for each shop in the multistore feature. Prestashop let's you specify a different prefix for each shop, but the numbers are globally shared among all shops. This is due to the fact that the records in the DB are stored as *id_order --> invoice_number* and Prestashop doesn't care about the shop. The solution consists in *JOINING* the invoice number table with the order table in the *Order* class. file: root/override/classes/Order.php public static function getLastInvoiceNumber() { $id_shop = Context::getContext()->shop->id; $next = Db::getInstance()->getValue(' SELECT MAX(inv.number) FROM `'._DB_PREFIX_.'order_invoice` inv INNER JOIN `'._DB_PREFIX_.'orders` ord ON ord.id_order = inv.id_order WHERE ord.id_shop = ' . (int)$id_shop ); return $next ? $next : 0; } public static function setLastInvoiceNumber($order_invoice_id, $id_shop) { if (!$order_invoice_id) return false; $number = Configuration::get('PS_INVOICE_START_NUMBER', null, null, $id_shop); // If invoice start number has been set, you clean the value of this configuration if ($number) Configuration::updateValue('PS_INVOICE_START_NUMBER', false, false, null, $id_shop); $sql = 'UPDATE `'._DB_PREFIX_.'order_invoice` SET number ='; if ($number) $sql .= (int)$number; else $sql .= '(SELECT new_number FROM (SELECT (MAX(inv.number) + 1) AS new_number FROM `'._DB_PREFIX_.'order_invoice` inv INNER JOIN `'._DB_PREFIX_.'orders` ord ON ord.id_order = inv.id_order WHERE ord.id_shop = ' . (int)$id_shop.') AS result)'; $sql .=' WHERE `id_order_invoice` = '.(int)$order_invoice_id; return Db::getInstance()->execute($sql); } Now you have the desired behavior. Hope you found this useful. If it doesn't work for you, I found a module that claims to do this for you (I am not affiliated with the author neither have used the module) : http://addons.prestashop.com/it/fatturazione-contabilita-moduli-prestashop/17583-different-invoice-numbers-multistore.html
  39. 1 point
    If you disable English it won't appear in the frontoffice but you will be able to set it in your employee profile.
  40. 1 point
    Bonjour, J'ai été confronté au même problème (toujours pas corrigé dans la version 1.7.6.4. ) Pour ceux que ça intéresse, il existe une solution quasi officielle (puisqu'elle a été publiée sur Github) : https://github.com/PrestaShop/PrestaShop/pull/15632 Il faut mettre à jour breadcrumb.tpl : <nav data-depth="{$breadcrumb.count}" class="breadcrumb hidden-sm-down"> <ol itemscope itemtype="http://schema.org/BreadcrumbList"> {block name='breadcrumb'} {foreach from=$breadcrumb.links item=path name=breadcrumb} {block name='breadcrumb_item'} {if not $smarty.foreach.breadcrumb.last} <li itemprop="itemListElement" itemscope itemtype="http://schema.org/ListItem"> <a itemprop="item" href="{$path.url}"><span itemprop="name">{$path.title}</span></a> <meta itemprop="position" content="{$smarty.foreach.breadcrumb.iteration}"> </li> {elseif isset($path.title)} <li> <span>{$path.title}</span> </li> {/if} {/block} {/foreach} {/block} </ol> </nav>
  41. 1 point
    Hi. I was forced to turn on basic stock management so that the PS system would display "out of stock" and "in stock" icons. Now I was wondering if there is a way to prevent the system from deducting inventory quantities after a sale? For example, right now, if I have a product quantity of 10 and a customer orders 1, the stock then is 9. And so forth until it reaches 0 and is "out of stock". My store does not have an inventory. All sales get passed on to a fufillment service, so I would like to DISABLE the -1 that happens after a sale. Right now my work-around is to set quantity for every product to a high number like 9999 which will take a long time to sell out. Then if my fulfillment centre says they ran out of a particular product, I will manually set it to 0 so that it says "Out of Stock". Does this make sense? Does anyone have alternative strategies to share, when using a third party fulfillment service? Is there a setting in PS somewhere that I did not see that will control whether sales deduct stock quantities automatically or not? Thank you! PS 1.6.1.9
  42. 1 point
    You can change it in Advanced Settings -> Products... And if you want to add a sort order, you can edit /modules/ps_facetedsearch/src/product/searchprovider.php and add some code in the getAvailableSortOrders() function... private function getAvailableSortOrders() { $sortPosAsc = new SortOrder('product', 'position', 'asc'); $sortNameAsc = new SortOrder('product', 'name', 'asc'); $sortNameDesc = new SortOrder('product', 'name', 'desc'); $sortPriceAsc = new SortOrder('product', 'price', 'asc'); $sortPriceDesc = new SortOrder('product', 'price', 'desc'); $sortDateAsc = new SortOrder('product', 'date_add', 'asc'); $sortDateDesc = new SortOrder('product', 'date_add', 'desc'); $translator = $this->module->getTranslator(); return [ $sortPosAsc->setLabel( $translator->trans('Relevance', [], 'Modules.Facetedsearch.Shop') ), $sortNameAsc->setLabel( $translator->trans('Name, A to Z', [], 'Shop.Theme.Catalog') ), $sortNameDesc->setLabel( $translator->trans('Name, Z to A', [], 'Shop.Theme.Catalog') ), $sortPriceAsc->setLabel( $translator->trans('Price, low to high', [], 'Shop.Theme.Catalog') ), $sortPriceDesc->setLabel( $translator->trans('Price, high to low', [], 'Shop.Theme.Catalog') ), $sortDateAsc->setLabel( $translator->trans('Data, do mais antigo para o mais recente', [], 'Modules.Facetedsearch.Shop') ), $sortDateDesc->setLabel( $translator->trans('Data, do mais recente para o mais antigo', [], 'Modules.Facetedsearch.Shop') ), ]; } Best Regards
  43. 1 point
    Vale, pues ya está… Ya encontré la solución y sin meterse a las tripas de los ficheros, si bien es cierto que lo publicado anteriormente funcionó solo para el subject, a mi francamente me disgusta modificar los ficheros, por que luego las actualizaciones dan problemas o termino por olvidar que fue lo que cambié, y principalmente por que aún siendo un entusiasta poco entiendo del código y con no poca frecuencia termino haciendo una estupidez. Pero ahí va… No se si derivado de las pruebas iniciales, que en mi caso jugando y probando activé y desactivé la multitienda, o es algún error en esta versión o no se, el asunto es que esta llamando al nombre de la tienda que aparece en nuestra tienda estando habilitada la multitienda, yo en mi caso no ocupo multitienda y no la tenía habilitada, pero ahí es lo que habrá que corregir, por que pasa??? ni idea pero pasa, así que ahí les va... - Parámetros de la tienda>configuración> activar multitienda y guardar. - Ir a Parámetros avanzados>multitienda> en el árbol multitienda seleccionar la nuestra, que en mi caso es la única, y es la que esta dentro del grupo Default, ahí solo habrá que picarle en modificar y cambiarle el nombre a la tienda, de My Shop (el nombre maldito) al nuestro y guardar. Ya entonces regresamos a >Parámetros de la tienda>configuración> desactivamos multitienda, guardamos y zaz! resuelto. Por supuesto regresé el código del fichero Mail.php a como estaba originalmente, eliminando los cambios que hice y que señalé en el anterior post. Saludos!
  44. 1 point
    Bonjour Autre piste, j'avais le même problème, réglé en mettant à jour les modules Bonne journée Pascal h+1 : (bon, j'ai parlé un peu vite car cela ne fonctionne plus) h+2 : J'ai remarqué que sur Internet explorer cela fonctionne un peu mieux.
  45. 1 point
    you will have to: - add new field to ps_order table to store this text for further reference - modify orders admin theme template file to display this field on order details page - modify order controller, where you have to define new field definition in object definition something like: http://www.prestashop.com/forums/topic/285258-solvedhow-to-add-new-text-field-to-a-product-which-will-only-be-available-from-the-bo/ but instead of products controller / template files use files related to orders
  46. 1 point
    hello you can easily modify the core and database, i will show you step by step tutorial below. So we want to create field name: internal name (1) For the first, we need to create new field in ps_product table. so, open phpmyadmin and alter ps_product table. add new VARCHAR(200) field (i think that 200 chars for internal name are enough, am i right? ) field name: internal_name, specification: (2) Now it's time to extend object, open classes/product.php file there is code like: .... read full tutorial here: new field for products in back office
  47. 1 point
    after lots of study i am able to figure out how to do this. It is really difficult for normal customer to find this. The module need to be proper documentation. Here is how you can achieve your goal. 1. want to show 10 product so parameter at the end will be. http://localhost/prestashop/modules/feeder/rss.php?n=10 2. if you want to order your product asc oder http://localhost/prestashop/modules/feeder/rss.php?n=10&orderby=id_product 3. If you want to descending order of the product by there product id than you need to do like . http://localhost/prestashop/modules/feeder/rss.php?n=10&orderby=id_product&orderway=desc So here is the parameter at a glance. 1. n = how many no of product you want to show. 2. orderby how you like to short your rss by product id , name or other supporter parameter for orderby 'id_product', 'price', 'date_add', 'date_upd' supported sorting 'asc', 'desc' Hope any one from now got a better help for feeder tutorial from this post .
  48. 1 point
    Bonjour, Oui ce projet est tout à fait réalisable sous Prestashop, voir http://www.pizzaweb.ch (actuellement en cours de refonte). N'hésitez pas à me contacter en MP. Cordialement
×
×
  • Create New...

Important Information

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