Jump to content


Popular Content

Showing content with the highest reputation since 09/23/2020 in Posts

  1. 2 points
    An open source community is more than just pull requests made by faceless strangers. In order to better understand the people who contribute time and skills to the PrestaShop project, we’re writing a series of interviews with contributors of all ranges. This week, meet Pululu Kinanga André, one of our great developers on GitHub! Hi Pululu! First, could you tell us a bit about yourself? I am Pululu and I come from Angola. I arrived in France in 2013 for my studies, after graduating in electronics and telecommunications. I have a degree in Management Information System (MIS), software development, and design. I am currently assisting the IT department of a digital agency in their migration and automation strategy. I am also interested in systems administrations (Unix), development, software design, and embedded systems. If I had to summarize myself in a few words, I would write that I am “a discreet lazy lazybones who works hard and an Eternal admirer of the complexity of simple things”. When and why did you get involved in contributing to the PrestaShop project? I started to be interested in the open source philosophy in 2014. I found it was an amazing way to be able to help and share my vision with the world! It is now a conviction that we can all help each other and, together, build powerful and sustainable solutions. And a few years later, I started to interact on StackOverflow. I had my first contact with the PrestaShop ecosystem in 2016, I was engaged in a work-study program at Alibabike, in La Rochelle. In 2017, I joined the agency123 as a developer and designer, and I made huge progress very quickly because PrestaShop is their area of expertise and their core business. What motivates you? In my opinion, the decision to migrate Prestashop to Symfony has divided the community. Many members and contributors were disappointed and discouraged. I believe most of them were afraid of not understanding the new system and therefore losing their expertise. As for me, it motivated me to contribute because it was a way of saying: guys, come back… this is no big deal, look, it’s very simple! I also wanted to learn and make progress, discuss with the authors of the solution, be credible, and reassure our +200 customers that I master the solution we offer with the agency. Finally, I think contributing is also a way to thank all of those who have contributed before and to help the software evolve. Do you have any advice for first-time PrestaShop contributors? You are not alone! PrestaShop has a rather large community and, likely, other users have already encountered the same problems as you. By contributing, you are helping to improve the solution, and this is an opportunity to share directly with the PrestaShop team. What’s the number one thing you’ve learnt by contributing to Open Source projects? I was not alone and there are many ways to look at it! Thank you Pululu, we hope to see more from you as PrestaShop evolves! :) View the full article
  2. 1 point
    This module allows BO administrators to login FO as a customer by clicking a simple button at AdminCustomer page. Adds a simple login button to customer pages at BO. The module never needs to change password of customer or any information of a customer. It is also quick and safe due to using own encryiption keys. Can be used for: Create orders on behalf of your customers (customers who requested help to ordering just like in live chat, or by phone) Redirecting customer by browsing same pagea step by step Check for errors or feedbacks froms customer quickly Update: Please follow https://github.com/rowanfuchs/PrestaShop-login-as-a-customer download up to date files. Thanks to @Rowan - 999 Games PrestaShop-login-as-a-customer-master.zip
  3. 1 point
    Hola, podéis enviar un correo a soporte@digitaldot.es para que os lo envíen necesitan generar la licencia con vuestro email para informar en caso de actualizaciones. Un saludo
  4. 1 point
    ./classes/Mail.php find: change to:
  5. 1 point
    Looks like it is part of your theme. Either look in the template file or ask your theme provider.
  6. 1 point
    Tak mám hotový modul zdarma pro skrytí / zobrazení standardních sloupců 😉
  7. 1 point
    Ještě potřebuješ "počet kusů" v seznamu produktů ? ./themes/classic/templates/catalog/_partials/miniatures/product.tpl změnit: <div class="product-description"> na: <div class="product-description" style="height: auto !important;"> pod: {block name='product_reviews'} {hook h='displayProductListReviews' product=$product} {/block} vložit: <span class="product-title" style="display:block;">{l s='Quantity' d='Shop.Theme.Actions'}: {$product.quantity}</span> výsledek:
  8. 1 point
  9. 1 point
    La forma más fácil de ocultarlo es poniendo este código en el archivo custom.css de tu tema actual: .post_meta { display: none !important; } Ten en cuenta que esto solo lo oculta de la página, pero si alguien mirara el código fuente lo podría encontrar. Si necesitas borrarlo completamente avísame por aquí y buscaré otra forma. Un saludo, Rafa
  10. 1 point
    First time with PrestaShop, so I'm not sure I'm doing it right. I have registrated a new custom hook in the theme.yml file like this: - name: displayMyCustomHook title: displayMyCustomHook description: Display my custom hook Inside that hook I want to display the search bar. So the header.tpl have this code: {block name='header_search'} <div class="header_search"> {hook h='displayMyCustomHook'} </div> {/block} But, when going to Design > Positions in the backend, my custom hook is not displayed in the dropdown menu "Transplant to". What am I doing wrong? Is this possible? /Magnus
  11. 1 point
    Hola, No me acuerdo porque hace mucho de esto, pero creo que lo que hice es quitar el modulo de los mas vendidos.
  12. 1 point
  13. 1 point
    Bonjour, j' ai eu ça ce matin avec une erreur 400, j' ai supprimer le module via le ftp, supprimer les cookies de votre navigateur, vider le cash et j' ai réinstaller le module en le téléchargeant le module directement sur le site de PrestaShop et tout est rentré dans l' ordre
  14. 1 point
    Hello all, Just like Prestan0ob I would like to enrich the WYSIWYG but unfortunately the process given above doesn't work for me either on PS: Would anyone have a solution for this version ? Many thanks,
  15. 1 point
    Indem du eine vorhandene Mailvorlage im Template-Ordner mails/de kopierst, entsprechend benennst und veränderst. Normalerweise nutzt man einen eigenen Versanddienst, ich habe das ja hierzulande ziemlich überflüssige mitgelieferte Scheck-Modul entsprechend angepaßt. In der E-Mail wird dem Kunden dann halt nicht mitgeteilt, wohin der den Scheck schicken soll, sondern wo und wann er die Ware abholen kann oder daß er eine Mitteilung erhält, wenn die Ware abholbereit ist, dafür kannst du dann einen eigenen Status mit der dafür erstellten Mailvorlage erstellen.
  16. 1 point
    Thank you PCQUATRO. You save my life. Now looks OK. The best banner module for my need. Ricardo.
  17. 1 point
    I made some further optimizations. The main problem is now likely in product-proc that takes too long. As the main time consumer there is indexation you could try to skip indexation by checking that option. I will look whether some optimizations there are possible. product-edit6.txt
  18. 1 point
    Możesz podać link do sklepu, inaczej ciężko będzie Ci pomóc - ewentualnie, jeżeli nie chcesz publicznie podawać daj na PW.
  19. 1 point
  20. 1 point
  21. 1 point
    Hi guys, I'm trying to modify the new_order template for the module Mail Alerts. I've found the two file, new_order.html and new_order.txt, in /modules/mailalerts/mails/it folder, I changed them adding a simple "email: {email}", cleared the cache (both ftp and db cache) and...changes don't display. If I read the two files in the browser windows (http://site.it/modules/mailalerts/mails/it/new_order.html) I see the new files with correct data, but in the mailbox I receive the same old template. What's wrong?
  22. 1 point
    I had to fix the syntax a little to ALTER TABLE `ps_layered_price_index` ADD `id_country` int(11) DEFAULT 8 ; but that worked perfectly. Thanks very much for your help. All good now. JR
  23. 1 point
    @joseantgv On the Prestashop DevDocs (https://devdocs.prestashop.com/1.7/basics/installation/system-requirements/) " You can use our system requirements tool to easily check if your environment fulfills PrestaShop’s requirements." When running the system requirement tool, it recommends 7.3:
  24. 1 point
    is your store located after the file "htdocs' ? check this page here: http://blog.mdsohelrana.com/2011/11/01/how-to-change-the-document-root-in-xampp-on-windows/
  25. 1 point
    Si vous êtes sur Prestashop 1.7 ça ne m'étonne pas vu qu'ils ont fichu un bazar monstre dans les règles paniers... Vu que le transporteur est calculé avant l'application des règles vous ne vous en sortirez pas comme ça. Il faudrait remonter votre bug sur Github.
  26. 1 point
  27. 1 point
    Hello, Thank you for using our Live Chat free module. I'm really sorry about the problem you encountered while using our module Regarding one of our users, please try to replace strtotime('now') to strtotime(time, now) in the main PHP file of module. Save your change and check if the offline problem has been solved. My best regard.
  28. 1 point
    Vous ne pouvez pas car ce paramètre "par défaut" n'existe pas^^ Prestashop vous ramène les adresses actives dans l'ordre où elles ont été créées dans la base de données. Vous devez donc récupérer la 1ère du tableau renvoyé ou, si vous êtes dans le contexte de commande, récupérer l'id_address_delivery du panier en cours si elle existe.
  29. 1 point
    Siguiendo la misma línea de trabajo del módulo de trinkinho para PS 1.5 y 1.6, he adaptado el módulo original que trae PS ps_wirepayment (v2.0.4) y le he copiado el código de trinkinho (bankwire_discount) para que ofrezca también descuentos en 1.7.1 y 1.7.2 como ps_wirepaymentdiscount. La única modificación a su código que he hecho es aplicar el descuento en la validación SOLO a los artículos ANTES de aplicarle los impuestos. Es decir, en vez de aplicar el descuento al total del carro de la compra (Cart::BOTH) lo he aplicado sólo a los artículos sin impuestos ni gastos de envío y/o manipulación (Cart::ONLY_PRODUCTS). Adjunto el módulo. Si te gusta, dame un Like ps_wirepaymentdiscount.zip
  30. 1 point
    Bonjour, Je suis vendeur sur addons. j'ai un client qui me demande de l'aide, mais je ne peux pas car il est marqué comme "Pas de commande". il m'envoi la facture sauf que la date et le numéro de commande n'existe pas dans mon interface vendeur de addons. c'est normal et que faire. c'est la première fois que j'ai ce problème. merci d'avance
  31. 1 point
    I could kiss you for this. I have just had the same problem, and getting in to the admin panel (which was awkward to find as I didn't realise it was admin92n93hc or whatever - I was expecting it to be /admin or /administration and /login didn't work) and changing the SSL settings fixed it. However when I loaded the admin panel, the Onboarding "menu" in the bottom right was in the way of the preferences settings. The continue and dismiss buttons would not work. Thankfully, I remembered I can delete stuff with Inspect Element. So I inspected the box and deleted it, and could reveal the hidden two configuration options. I could the change the setting. The front end immediately began working, and clicking both buttons on the bottom left onboarding "menu" also functioned normally. However it begs the question, why is this not more intitive? I've used a LOT of scripts in my time. Forum scripts, content management, ecommerce, contact form creation, among others, and not a single one has caused problems like this, with practically all working regardless of http or https, and most are able to detect when I installed the very script using a https:// installation link. I am surprised this process was not automatic, and was not a selectable option on installation. I have tried CS Cart and Open Cart alongside this script and neither of those had problems either.
  32. 1 point
    Don`t worry. ))) I not have access to your files. I just looked in browser as developer.
  33. 1 point
    Miałem to samo, w modułach znajdź "Customer Reassurance" - to jest to tylko nieprzetłumaczone
  34. 1 point
    Bonjour, voici un module permettant de récupérer vos données via requetes SQL assez facilement. Le module contient quelques requetes SQL par défaut, vous pouvez les modifier, les supprimer, en ajouter sans limites. Les requêtes SQL peuvent utiliser ps_ (préfixe par défaut des tables, exemple ps_cart), ou _DB_PREFIX_ (conseillé, si vous souhaitez réutiliser les requetes SQL sur d'autres boutiques, _DB_PREFIX_cart donnera ps_cart par exemple), ou encore _PREFIX_ (si vous voulez faire plus court, _PREFIX_cart donnera ps_cart par exemple). Voici le rendu des tables SQL : Pour chaque requêtes vous pouvez sauvegarder une description afin de mieux vous y retrouver, les actions possibles sont : voir, sauvegarder, supprimer, voir le résultat sous forme sérialisée (voir l'image plus bas), voir le fichier CSV avec Excel. Résultats que vous pouvez avoir sous différentes formes : Version 1.1.0 : Et pour finir le zip : v.1.0.0 : bigdata.zip Première version, testée sous 1.5 et 1.6. avec quelques requêtes SQL provenant de https://www.prestashop.com/forums/topic/155423-astuce-generer-automatiquement-vos-fichiers-csv-via-requete-sql/page-6?do=findComment&comment=2236793 et une que j'ai rajoutée permettant d'avoir les données complètes sur les commandes sur les 3 derniers mois V.1.0.1 : v.1.0.1.bigdata.zip ajout des traductions en Espagnol (par masqueunaweb.com), ajout d'une nouvelle requête permettant d'avoir la liste des stocks des produits et déclinaisons, j'ai changé _PREFIX_ dans les requêtes par _DB_PREFIX_ pour éviter les confusions, mais vous pouvez toujours utiliser _PREFIX_ V.1.1.0 : v.1.1.0.bigdata.zip apparemment serialize peut quelque fois "bugguer", pour éviter tout problème je rajoute base64_encode, donc pour récupérer les données sérialisée il faudra rajouter base64_decode. le tableau de résultat possède de nouvelles fonctionnalités : tri (en cliquant les les en-têtes de colonnes), recherche, pagination (si vous avez beaucoup de résultats) v 1.1.1 : v.1.1.1.bigdata.zip fixe un bug qui empêchait d'enregistrer plusieurs nouvelles requêtes à la suite (ceci obligeait à rafraîchir la page) v 1.1.2 : v.1.1.2.bigdata.zip petite modification v 1.1.3 : v.1.1.3.bigdata.zip compatible 1.6 & 1.7
  35. 1 point
    pues la respuesta es más sencilla aun, se puede instalar el modulo gratuito email alerts donde se configuran estos parámetros
  36. 1 point
    bonjour Yoan, je n'avais pas vu votre message au cas où je fais un retour quand même sur la résolution du probleme. Une personne a rencontré le même soucis et m'a transmis le fichier joint . Rencontre du problème en particulier sur des anciennes versions de chrome et derniere version de firefox Le fichier joint à remplacer dans ...(votre thème)/templates/checkout/_partials/steps Probleme corrigé personal-information.tpl
  37. 1 point
    I found that for Mac using terminal: zip -d your-file.zip *__MACOSX/\* zip -d your-file.zip *DS_Store* I hope that be useful.
  38. 1 point
    Since I joined this forum in June 2017 I've asked four questions. Never had an answer/reply to any of them So today I answer my own question. I was able to achieve the desired cart summary total by commenting out the tax exclusive arguments in shopping-cart.tpl <tr class="cart_total_price"> <td colspan="{$col_span_subtotal}" class="total_price_container text-right"> <span>{l s='Total'}</span> <div class="hookDisplayProductPriceBlock-price" id="HOOK_DISPLAY_PRODUCT_PRICE_BLOCK"> {hook h="displayCartTotalPriceLabel"} </div> </td> {* {if $use_taxes} {if $priceDisplay} <td colspan="2" class="price" id="total_price_container"> <span id="total_price_without_tax">{displayPrice price=$total_price_without_tax}</span> </td> {else} *} <td colspan="2" class="price" id="total_price_container"> <span id="total_price">{displayPrice price=$total_price}</span> </td> {* {/if} {else} <td colspan="2" class="price" id="total_price_container"> <span id="total_price_without_tax">{displayPrice price=$total_price_without_tax}</span> </td> {/if} *} </tr>
  39. 1 point
    Hi , I have developed a custom module and i want to publish it on Prestashop marketplace can someone guide me on the procedure/steps to follow to publish my module on Prestashop Any related suggestion is much appretiated... Thanks
  40. 1 point
    Salut, Certains n'ont pas ce module dans leur version 1.7, je partage avec vous le module pour supprimer le contenu d'origine ( Démo ) Prestashop 1.7..x pscleaner ps 1.7.zip
  41. 1 point
    you can add there condition to check what cms page is viewed based on Daresh suggestion, you can use something like: if ($('body').hasClass('cms-3')) { } each cms page has own unique class in <body> tag. 3 in the example above is an ID of terms of conditions page. you can change it to work only on selected page, just replace "3" with ID of target cms page.
  42. 1 point
    Cambiar Prestashop 1.7 de dominio y cambio de clave Para resumir todo el proceso de cambio de servidor, dominio y si fuera necesario el cambio de clave del panel de administración (me he ayudado principalmente del usuario ide41): Copiar todos los archivos al nuevo servidor (mediante SSH o FTP o como desees) Hacer un clonado de la base de datos, mediante exportar e importar del phpMyAdmin) Poner los nuevos datos de la base de datos en el archivo /app/config/parameters.php En la base de datos en la tabla ps_configuration, cambiar los valores de los campos PS_SHOP_DOMANIN y PS_SHOP_DOMAIN:SSL. Tienes que poner tu dominio. En la tabla ps_shop_url tienes que cambiar los campos DOMAIN, DOMAIN_SSL Y PHYSICAL_URI. (en physical URI debe de poner "/"). Solo si quieres cambiar la contraseña de acceso: Cambiar la cookie key de la tabla PS_EMPLOYEE:Tienes que abrir el archivo /app/config/parameters.php de la instalación remota y copiar el texto que sale en "cookie key". Vas a la página http://www.md5.fr/ y pegas el contenido de cookie key, y a continuación (sin espacios ni nada) la nueva contraseña que quieres poner. Le das al botón convertir MD5 y te dará como resultado una nueva contraseña transformada en MD5. Luego vas a la tabla ps_employee, y cambias directamente en la tabla, la columna password por el resultado que te ha dado en MD5 anterior. Con eso se cambia la contraseña antigua por la nueva, y transformado en MD5. Desactivar URL amigables y borrar contenido de las carpetas/cache/smarty/compile y /cache/smarty/cache (sin eliminar los archivos index.php de cada una de ellas) Activar de nuevo las URL amigables. Parámetros avanzados > Rendimiento > Clear Cache
  43. 1 point
    Generally this happens when you inserts script outside literal tag. To identify your issue, turn on error reporting by following below steps: Edit following file. /config/define_inc.php Replace define('_PS_MODE_DEV_', false); with define('_PS_MODE_DEV_', true);
  44. 1 point
    Thank you to anyone who has looked at my problem, its taken much more learning but I've completed the script by adding the upload query and its fully working! I also descovered I had to update price impact in 2 tables and its just 'price' not 'unit_price_impact' that needed updating. Thank you to everyone who took time to read this topic.
  45. 1 point
    Подскажите с таким вопросом. Начал переводить шаблон (Локализация - Переводы - Перевести магазин) на русский язык. Но при сохранение перевода выкидывает на страницу сайта с ошибкой 404. Что делать, подскажите. Может какого-то файла не хватает?
  46. 1 point
    bunu panelde vergiler bölümünden yapabilirsiniz
  47. 1 point
    ¿Por que no utilizas este modulo: http://www.prestashop.com/forums/topic/210495-free-module-homecategoryplus-display-your-categories-and-subcategories-on-the-home/ para mostrar las categorias en la home?
  48. 1 point
    Un placer ayudarte y servirte! Un saludo y recuerda que estaremos en el foro, para guiarte por este mundo oscuro y tenebroso. PD: La magia de Prestashop. (Es mentira, la magia no existe.. )
  49. 1 point
    Para cambiar el fondo general de todos los encabezados de los modulos, fichero: /themes/tu-plantilla/css/global.css Busca esto: .block .title_block, .block h4 { padding: 6px 11px; font-size: 12px; color: #fff; text-shadow: 0 1px 0 #000; text-transform: uppercase; background: #383838; text-align: left; font-weight: bold; } Y cambia el: background: #383838; es decir esto: #383838; por el nuevo codigo de color de fondo que quieras establezcar.
  • Create New...

Important Information

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