Jump to content

Leaderboard

  1. Eolia

    Eolia

    Members


    • Points

      527

    • Content Count

      14,251


  2. doekia

    doekia

    Members


    • Points

      328

    • Content Count

      9,725


  3. Mediacom87

    Mediacom87

    Global Moderators


    • Points

      191

    • Content Count

      8,254


  4. ttoine

    ttoine

    PrestaShop Team


    • Points

      147

    • Content Count

      425



Popular Content

Showing content with the highest reputation since 06/25/2018 in all areas

  1. 10 points
    Depuis que je connais Prestashop, il y eu une seule mise à jour concernant un problème de sécurité et c'était sur une version 1.4. Oui Prestashop est un cms très particulier. Par son code et la stratégie actuelle. Leur gros problème ce sont les tests, ils nous disent qu'ils en font, ok mais ils les font juste sur leur boutique de test avec John Doe comme seul client, 4 robes et 10 pauvres modules installés. Leur réponse est toujours la même: "On ne peut pas tester toutes les configurations". Et c'est là que le bas blesse, perso à chaque mise à jour, je commence par faire un diff avant de cliquer sur ce bouton sans réfléchir, parce que rien que le changelog c'est minimaliste et ça ne reflète pas les réels changements effectués. Correction d'un bug ? Ok, je vais voir ce qu'ils ont fait et si le bug est vraiment résolu. Ajout d'une feature ? Alors là, attention parce que généralement ça veut dire nouveaux bugs ou pas géré suivant tous les cas de figure. Ensuite, mes boutiques de test on des bases de 2 à 8000 clients en moyenne, des tas de règles paniers et prix spécifique, des configurations multi-langues et des catalogues de + de 10 000 produits. A ça on peut ajouter entre 2 et 300 modules installés. Là je considère que les tests commencent à être représentatifs. Oui Prestashop est responsable en annonçant comme fiable une version qui ne l'est pas Oui Prestashop est responsable en ne mettant en avant que cette version 1.7 et en dissimulant bien les autres (Pour info, la dernière maj de la 1.6 (1.6.1.20) date de moins de 15 jours, alors parler d'ancienne version me fait doucement rigoler) Oui Prestashop depuis 2 ans ne mise plus que sur l'aspect RENTABLE et FINANCIER de sa solution. Exit le côté communautaire, exit la fiabilité, exit les remontées utilisateurs. ils sont les meilleurs et n'écoutent plus leurs clients. Si vous voulez leur parler, ils sont planqués là: - http://build.prestashop.com/ - https://gitter.im/PrestaShop/General - http://forge.prestashop.com/ Bien sûr, vous devez écrire en anglais, sinon passez votre chemin... Symfony, on l'avait réclamé en 2011/2012 et on nous avait répondu à l'époque que le code maison de Presta était très bien comme il était et que ce n'était pas à l'ordre du jour. Smarty fonctionne bien nativement, le problème c'est que Prestashop en a tellement trituré le code que c'est devenu n'importe quoi au niveau de la gestion du cache et que les serveurs passent plus de temps à l'effacer / ré-écrire plutôt qu'à l'utiliser. (Je ne parle même pas de l'option débile d'écrire ce cache en bdd qui plante le moindre mutu...) Suite à la pression des investisseurs et de certains devs, Prestashop a décidé de passer sous Symfony pour plusieurs raisons: - Le code devenait difficile à maintenir (Ben oui, les employés actuels sont tous là depuis peu et maîtrisent très mal les 300 000 lignes de code maison) donc en passant par un framework relativement connu ce sera plus simple. - Ils espèrent faire revenir les développeurs externes vers Prestashop (modules, thèmes et GitHub) - Prestashop donne l'impression d'être à jour et dans la course Mais là encore, on fait ça à la sauce Prestashop, c'est à dire par morceaux tenus par du scotch pour que ça pète pas trop. Passer à Symfony c'est une bonne idée, oui mais leurs modules et thèmes vendus sur Addons ne sont pas compatibles (écrits pour Smarty) et ils n'ont pas le temps ni le personnel pour les mettre à jour, donc s'ils veulent continuer à les vendre, il faut conserver Smarty en parallèle. Et voilà comment on commence les conneries... La 1.7 c'est une 1.6.0.10 à la base qui utilise 2 moteurs de templates (un inédit dans le monde du CMS quand même !) et à laquelle on a supprimé tout ce qui ne marchait pas (on verra au fur et à mesure pour les remettre ou pas, mais l'objectif actuel semble plutôt se tourner vers le remplacement de ces fonctionnalités par des modules payants) Mais plutôt de ré-écrire Prestashop pour être conforme avec Symfony, ils ont rajouté une couche de compatibilité ce qui alourdit encore plus le code et crée une véritable usine à gaz. Et j'ai lu dernièrement qu'ils allaient encore en rajouter une couche pour que nous puissions continuer à écrire le code comme pour les 1.6 (Vu qu'ils peinent à donner envie aux devs externes d'utiliser leur 1.7 bancale). Alors oui, je suis désolé pour vos mésaventures, mais je ne peux pas vous encourager à continuer avec cette version uniquement parce que le nouveau principe de templates est sympa. C'est l'arbre qui cache la forêt et c'est le jour où vous allez vouloir utiliser Prestashop dans ses fonctions avancées que vous aller commencer à galérer sévère (Taxes, prix spécifiques, déclinaisons, transporteurs, stocks avancés, etc...) La 1.7 soit-disante "stable" c'est une version hybride dont les tests sont effectués sur votre dos et sans aucune assistance, et ça, c'est juste une honte.
  2. 8 points
    Here is a free module to let you export your products to the Google Merchant Center, and make them available on the Google Shopping market place. It's an evolution to the GoogleShopping module made by Jordi and accessible on the spanish forum. The tool had already been modified by other users. This module lets you associate your shop categories to the Google Merchant Center ones. It exports price with and without reduction. You can also set a minimum price to filter products to export. You can associate some features value with categories (condition, availability, gender, age group). It offers the attributes combinations management. You can choose to export only one product or one product for each attributes combination. Last addition to the module is that you can now select the currency (among the available ones) to export in the feed for each available language. It has been tested on PS 1.5 and PS 1.6, and should also work on PS 1.7. Please report using problems you may encounter as an issue on GIthub or in this thread. This is how the module works : - if your products already have a "condition" attribute set in prestashop, then you can indicate it in the module main page, by the way products are exported with your native product's condition value. - if your products have not any "condition" attribute, and Google asks for it, then you can set the value for this attribute in the module category's configuration form, then each product in this category is exported with this value. - if your product have no condition attribute, and its module category has no 'condition' value set, then product is exported with the condition value set for its parent category, and so on till the root category. If all of your shop products belong to the same Google Shopping category, you can just set it for your root/home category, no need to set it for all of your categories. Children categories automatically get the same parameter. The module works the same way for the condition attribute, availability, gender and age_group attributes. "Default" value means: "Use the product's attribute. If product have no condition attribute set, then use the category attribute value. And if it's not set, then use the first parent category's filled setting." ... Not really clear but should be helpful ? In other words, If Google Merchant Center doesn't accept your products because the "condition" attribute is missing, then just set the value "new" to the condition attribute while editing your root category in the module configuration page. By the way all of your shop products are exported with the condition attribute set to "new". No need to change the "Default" value for each products category. In the latest releases (v1.5.6 -> 1.6), the color/material/pattern/size attributes can be mapped to the products attributes OR to the products features, according to your choice. Products features are mapped in the module main configuration page, and products attributes can be mapped separately for each category. Enjoy! (feedback is welcome ) PS: if you choose to use this module, please uninstall before the existing GoogleShopping module from your prestashop, if any. Last updates: - automatically export shipping prices ( Thanks to GuillaumeGBzh ) - all reported errors corrected (16 Feb 2016) - added currency selection for each available language - added filters and improvements on products selection SQL query (optimization) - rounded sale prices adjusted (06 Feb 2016) - Prestashop' rules compliant source code (by Elitius) - added products combinations names in exported products names (13 Apr. 2015) - combinations management improved (01/05/2015) : combinations pictures and links corrected - ability to attach different products attributes (or attributes groups) to each category - ability to export product features as well as product attributes - ability to manually specify the shop's product type (optionnal) - automatically export prices with or without tax included, following the shop's visitors group setting Todo: - add an option to normalise product name Last dev. version on GitHub (v 1.7.x): https://github.com/dim00z/gshoppingflux/ How to use this module? - download and install the package on your Prestashop server. - at first, configure the default products category of your shop in the main module configuration page - then set the parameters you need to activate - link shop features in the main module configuration page (if needed) - edit the main category (root or home) of your shop by clicking on it in the list - link products attributes in the main category edit page - then select the needed currencies to export with each available language - test the feed import in Google Merchant Center - if ok, configure a cron task to automatically update the feed Download gshoppingflux-1.7.2.zip
  3. 7 points
    El problema de Prestashop estos años, es que hicieron en su momento una mala planificación en la salida de la versión 1.7 (no será ni la primera ni la última empresa que tenga este tipo de problemas), pero la idea del cambio a symfony no es mala (no está completa todavía). Desde la salida "oficial" de la 1.7 (finales de 2016) a este año, se han corregido bastante problemas, además de ir migrando poco a poco a symfony (recuerdo que la migración sigue sin ser completa todavía), y se seguirán corrigiendo, porque todavía falta un trecho. Pero estoy seguro que el resultado final que veremos, sera un salto de calidad importante en comparación con versiones anteriores. En definitiva, ¿Ha cometido un error Prestashop? Como mínimo: Sí, sacar prematuramente la versión 1.7 en su momento. Anunciar que el soporte de la 1.6 se acababa en octubre de 2018, cuando al final lo han terminado ampliando hasta finales de junio de 2019. No decir toda la verdad (estos años), sobre el uso de la 1.7 en una tienda en producción (sobre si es recomendado u no). Personas que estamos metidas en el mundillo, sabíamos la realidad, pero el usuario que entraba en la web no estaba al tanto, a excepción de que buscara información por Google. Eso sí, Prestashop decía que todo era una maravilla. Por otro lado, y es mi opinión personal, falta involucrarse más en la comunidad (por parte de la empresa). Entiendo que el objetivo de una empresa es obtener el máximo beneficio económico, pero algunos hemos ayudado a mejorar la herramienta (de forma altruista), bien sea por el foro dando soporte, otros ayudando en los repositorios de código, otros en las traducciones, etc. Sobre la decisión de webempresa, no opino, ni negativamente, ni positivamente, cada empresa decide su estrategia comercial. Y cuando ellos han decidido no seguir con Prestashop, imagino que lo han estudiado detalladamente, y no ha sido una decisión en caliente. Podemos hacer especulaciones, en base al comunicado de webempresa, pero nada más. Sin más dilación, Un saludo de @nadie
  4. 7 points
    Ok, c'est Prestashop addons qui mouline et ne répond pas. Désactivez l'appel à addons, dans /classes/tools.php vers la ligne 3352, remplacez protected static $is_addons_up = true; Par: protected static $is_addons_up = false; Une fois cela fait, si vous aviez des alertes en rouge concernant les fichiers xml, supprimez tous les fichiers xxxxxx.xml du répertoire /config/xml/ Et supprimez le module gamification du ftp: /modules/gamification
  5. 6 points
    Display Add To Cart button in product list pages PrestaShop 1.7.x View Demo hiaddtocartbutton_v1.0.6.zip
  6. 6 points
    Duplicate content is something that search engine robots don't like. To avoid it, it's recommended to add canonical links in the header of your shop. It's also good to: direct robots to other language versions of your shop with hreflang links help them navigate through paginated content with prev and next links prevent them from indexing unnecessary parts of the shop with noindex tag To achieve all this, we combined some of the common solutions into one handy free module. You can download the module directly here: gmseofields.zip or from this location (module is for prestashop version 1.6, newer version has canonical tags already partially implemented, so maybe other are coming soon)
  7. 6 points
    Custom popup notification by PrestaCraft Current module version: 2.0.2 PrestaShop compatible: 1.6 , 1.7 http://prestacraft.com/custom-popup-notification/ This module displays a popup with Your content on chosen pages. Note: If you run more than one language in Your store, fill the popup content for all languages to save it correctly. Features Cookie system - Module remembers if user has closed the popup. If You don't want to show it again, You can set cookie duration. User will see the popup again after that amount of time. Display options (colors, size, etc.) Popup content for each available language in Your shop Delay option: define how many seconds must pass to show the popup Display your popup wherever you want to – just select any hook(s) Friendly User Interface Screenshots Changelog v2.0.2 - Removed error "Uncaught ReferenceError: id_lang is not defined at HTMLDocument.<anonymous> (blocksearch.js:56)" which was causing the home slider plugin failure. v2.0.1 - Fixed GitHub issue: https://github.com/PrestaCraft/custompopup/issues/1 v2.0.0 - Multistore support - Pure JavaScript popup – “tingle” – no jQuery - Much better BackOffice look and navigation - Hooking option – now you can select where do you want to display the popup - Popup footer – optional feature where you can insert your text, buttons or both. Fully customizable. v1.2.0 - Fixed bug of always appearing popup, even with cookie set - Changed "jquery cookie" to "js cookie" library, because previous one was broken - Added "version checker" tab where you can check now if your module version is current one - Added info under content area about requirement of filling this field for each language v1.1.0 - Compatibility with PS 1.7 - Code formatting matches PSR-2 standards and PS validation - Delay option: define how many seconds must pass to show the popup - Images inside popup are resized properly to the browser width Download - Current version custompopup_2.0.2.zip IF YOU LIKE THIS MODULE, PLEASE DONATE AND SHARE ❤️
  8. 5 points
    An application that directly posts your Whatsapp number when you talk and click through Whatsapp. Button click open whatsapp your number New Added Features Attached to the desired Hook added Fixed mobile errors Shared with product name brought on product page Product Share Page DEMO 17-whatsapp-live-chat.zip
  9. 5 points
    Free product reviews module for new PrestaShop 1.7.x this addon is a modification of old 'productcomments' module that we have by default in each installation of prestashop 1.6.x / 1.5.x. Now it fully supports new releases of PS 1.7.x. Module has exactly the same features as previous versions with improved design. Features: - module creates "reviews" form on product pages where customers can add review about products - reviews can be moderated before publication - you can create as much reviews criterions as you want - products can have own unique criterions - customers can send reports about comments so you will be able to moderate them - customers can mark reviews as helpful / not helpful what's new? New hook available right after someone will: - add review to product - send report - mark post as helpful / not helpful - multistore support - feedback page where module show (with pagination) all added reviews - support of GDPR rules DOWNLOAD v9.3.4 productcomments.zip
  10. 5 points
    The debug mode is widely used to see the errors on your shop and when: you get blank pages; you get 500 Internal Server Error; you have strage issues with your shop and don't know where to start; To turn on the Debug mode on PrestaShop 1.7 is more simple comparing it to the previous versions of Prestashop. You can do this from your PrestaShop Dashboard > Advanced Parameters > Performance > DEBUG MODE PANEL > Set it to YES If you can't acces you dashboard you can also enable it through FTP by accessing config/defines.inc.php and usually @line 29 you will find : define('_PS_MODE_DEV_', false); change it to: define('_PS_MODE_DEV_', true); Turning on the Debug Mode on other versions of Prestashop For PrestaShop 1.5.3 to 1.6 the procedure is the same: Open config/defines.inc.php and usually @line 29 you will find : define('_PS_MODE_DEV_', false); change it to: define('_PS_MODE_DEV_', true); For PrestaShop below 1.5.3 you have to edit the config/defines.inc.php file and make the following changes: Change this line: @ini_set('display_errors', 'off'); to this: @ini_set('display_errors', 'on'); !!! Be careful, turn the Debug Mode off when finished debugging, hackers may get advatage of it and may harm your website and besides of that any visible error is not good for visitors.
  11. 5 points
    Ideal for catalogues made in PrestaShop where sale or small ecommerce is not enabled. The module inserts information on the customer's user management page to request access to personal data to be corrected and deleted. The Official GDPR Compliance Module by PrestaShop for version 1.6 is by payment, so we have created a simple module that can be used where requests for access to personal data and deletion are rare, and where the deletion of data does not require special attention like demo versions and catalogues made in prestashop. New version 1.0.4 (18/05/2018) - addition consent request to user registration and guest orders Dowload free module: artfreegdpr1.0.4.zip Dowbload ver. 1.0.7 (22/05/2018): artfreegdpr1.0.7.zip Ability to disable the consent to the privacy policy for the guest account (Guest Checkout); Possibility of disabling the consent to the privacy policy for orders and user registration; Possibility to activate consent for the contact form;
  12. 5 points
    Hola, Ha salido la versión 1 - Click upgrade versión 4.2.0 estable . EDITO este post el 17 de septiembre de 2018 para poner bien la versión estable voy a poner los pasos efectuados para poder actualizar desde la versión que tengas 1.7 a la 1.7.4.2 Hay que seguir estos pasos y lo voy a poner fácil y detallado todos los pasos. Vamos al detalle 1 - Ante todo copia de seguridad de los archivos y de la base de datos, de tu tienda en producción por si algo va mal ( este paso es obligatorio) 2 - Bajarse el 1 - Click Upgrade version 4.2.0 estable https://github.com/PrestaShop/autoupgrade/archive/v4.2.0.zip https://github.com/PrestaShop/autoupgrade/releases 3 - Entrar en el Back Office o el admin de la tienda 4 - Una vez dentro , ver la versión que tienes intalada, y así estar seguro para proceder a actualizar 5 - Asegurarte que no tienes el modulo 1 - click instalado en tu web y si lo tienes lo desactivas y lo desintalas 6 - Ahora subes el módulo que bajaste en el paso nº 2 de 1 - Click Upgrade versión 4.2.0 estable 7 - Te aseguras de que pone la versión que tienes y la que te va a actualizar 8 - Pones la tienda en mantenimiento y luego le das al botón de comprobar actualización ( esto es obligatorio) , si no lo haces te puede fallar lo demás 9 - Ahora ya viene lo bueno , Click al botón de actualizar a prestashop pone 1.7.4.2 y se actualizara a 1.7.4.2 , ya lo verás 10 - No te asustes, si sale error , espera hasta que termine 11 - Ahora ya esta todo instalado, ( Atención con los siguientes pasos son importantes) 12 - Ir a Módulos , para desinstalar el 1- Click Upgrade 4.0.0 beta 5 , verás que te deslogueas y pierdes los estilos ( no asustarse, es normal) en el siguiente paso se arregla 13 - Ahora esta sin estilos , entra en el admin , y una vez dentro (Saldrá el menu en color azul y feo ) lo arreglamos dando click a Modo mantenimiento y activando la tienda 14 - Ir a Módulos , para desinstalar el 1- Click Upgrade 4.0.0 beta 5 , Desactivar y luego desinstalar ( paso obligatorio ) 15 - Cerrar sesión y volver a entrar , ahora el back office la pantalla del login del admin ya sale correcta. 16 - Una vez dentro , debería salirte bien, pero si te sale azul el menu lateral, refrescas el navegador con las teclas Ctrl + F5 y ahora ya sale bien 17 - Borra el caché de la tienda , en Parámetros Avanzados / Rendimiento arriba botón Borrar caché 18 - Prueba la tienda que todo te funciona bien y correctamente la version 1.7.4.2 que acabas de actualizar 18 - Recuerda la copia que hizo el modulo 1 - click upgrade 4.2.0 estable , parece que ahora sirve 19 - Si te falla, debes volver con las copias de seguridad tuyas, ¿Recuerdas? las que hiciste en el paso 1 , y eran obligatorias VER IMAGENES: 4 - Una vez dentro , ver la versión que tienes intalada, y así estar seguro para proceder a actualizar 6 - Ahora subes el módulo que bajaste en el paso nº 2 de 1 - Click Upgrade vesión 4.0.0 beta 5 7 - Te aseguras de que pone la versión que tienes y la que te va a actualizar 8 - Pones la tienda en mantenimiento y luego le das al botón de comprobar actualización ( esto es obligatorio) , si no lo haces te puede fallar lo demás 9 - Ahora ya biene lo bueno , Click al botón de actualizar a prestashop pone 1.7.4.2 y se actualizara a 1.7.4.2 , ya lo verás 11 - Ahora ya esta todo instalado, ( Atención con los siguientes pasos son importantes) 14 - Ir a Módulos , para desinstalar el 1- Click Upgrade 4.0.0 beta 5 , Desactivar y luego desintalar ( paso obligatorio ) 18 - Prueba la tienda que todo te funciona bien y correctamente la version 1.7.4.2 que acabas de actualizar Saludos
  13. 5 points
    I've checked the "incognito" mode, I've also cleaned cahe and cookies in my browser - still access denied. I've made some kind of an experiment. I've kept my dev stores filesystem on server, but I've cleared DB and restore it with the one from clean Presta. Now I can get to Order and see first example orders from John Doe... I believe this means that the issue reason is in DB. Have you got any idea where to look for it? EDIT: Problem Solved! I've restored 'my' DB, removed 'ps_access' table, and restored 'ps_access' from 'clean' DB. Now it all works fine Thank you guys for help! In attachement there is 'ps_access' table from clean DB - in the case if someone would need it in the future ps_access.sql.gz
  14. 5 points
  15. 5 points
    As a developer, since the 1.7 version was launched, I often found myself in the need of a list with Prestashop 1.7 Smarty Global Variables and I know many others were in this situation. Same as you maybe, reading this article, you may also looking for a similar list. So here it is, use it wisely ("with great power comes great responsibility"). The most used arrays: {$urls|@var_dump} -> Contains Prestashop urls; {$shop|@var_dump} -> Contains shop variables (shop name, email, phone, etc...); {$page|@var_dump} -> Contains current page variables; {$currency|@var_dump} -> Currency variables; {$language|@var_dump} -> Language variables; {$customer|@var_dump} -> Customer variables; {$configuration|@var_dump} -> Configuration variables; {$link|@var_dump} -> Link variables; {$breadcrumb|@var_dump} -> Breadcrumb variables; And here are some ready-tu-use variables: {$currency.name} -> Name of the active currency. {$currency.iso_code} -> ISO language code enabled. {$currency.sign} -> Symbol of the active currency {$currency.iso_code_num} -> Active Currency ISO Code {$shop.name} -> Store name in Prestashop 1.7 {$shop.email} -> Store Email in Prestashop 1.7 {$shop.logo} -> Image routing store logo in Prestashop 1.7 {$shop.favicon} -> Route favicon image of the store in Prestashop 1.7 {$shop.address.address1} -> Store address 1 in Prestashop 1.7 {$shop.address.address2} -> Store address 2 in Prestashop 1.7 {$shop.address.postcode} -> Store Zip Code in Prestashop 1.7 {$shop.address.city} -> Store City in Prestashop 1.7 {$shop.address.state} -> Province of the store in Prestashop 1.7 {$shop..address.country} -> Shop Country in Prestashop 1.7 {$shop.phone} -> Store phone in Prestashop 1.7 {$shop.fax} -> Store Fax in Prestashop 1.7 {$language.name} -> Language name enabled {$language.iso_code} -> ISO language code enabled {$language.language_code} -> Language code enabled (for Spanish, fr for French, tc ..) {$language.is_rtl} -> (1 -> On / 0 Off (for when language is written from right to left) {$language.format_lite} and {$ language.format_full} -> Simulated date format and full date format {$language.id} -> Language ID enabled {$customer.lastname} -> Customer Last Name in Prestashop 1.7 {$customer.firstname} -> Client Name Prestashop 1.7 {$customer.email} -> Prestashop Customer Email 1.7 {$customer.birthday} -> Prestashop client birthday 1.7 {$customer.newsletter} -> Subscribed to the newsletter in Prestashop 1.7 (1 subscribed / 0 unsubscribed) {$customer.newsletter_date_add} -> Newsletter subscription date {$customer.ip_registration_newsletter} -> IP Registration Customers newsletter {$customer.optin} -> Subscribed to offers from our partners in Prestashop 1.7 {$customer.date_add} -> Client creation date in Prestashop 1.7 {$customer.date_upd} -> Last updated client update in Prestashop 1.7 {$customer.id} -> Customer ID in Prestashop 1.7 {$customer.id_default_group} -> Default group to which the client is associated in Prestashop 1.7 {$customer.is_logged} -> Check if the client is "logged in" in Prestashop 1.7 {$customer.gender.name [$ customer.gender.id]} -> Client Gender (Mr / Ms) {$customer.addresses [Address ID] .city} -> Client city of address 'X' that has partner. (Address ID, because a client can theoretically have multiple addresses) {$customer.addresses [Address ID] .alias} -> Address alias {$customer.addresses [Address ID] .firstname} -> Addressholder last name {$customer.addresses [Address ID] .lastname} -> Name of address holder {$customer.addresses [Address ID] .company} -> Company name of address holder {$customer.addresses [Address ID] .address1} -> Address 1 {$customer.addresses [Address ID] .address2} -> Address 2 {$customer.addresses [Address ID] .postcode} -> Mailing address {$customer.addresses [Address ID] .id_state} -> Address Province ID {$customer.addresses [Address ID] .state} -> Province address {$customer.addresses [Address ID] .state_iso} -> ISO address province code {$customer.addresses [Address ID] .id_country} -> Country address ID {$customer.addresses [Address ID] .country} -> Country of address {$customer.addresses [Address ID] .country_iso} -> ISO country address code {$customer.addresses [Address ID] .phone} -> Address phone {$customer.addresses [Address ID] .phone_mobile} -> Mobile phone address {$customer.addresses [iD Address] .dni} -> Address ID {$customer.addresses [Address ID] .vat_number} -> Customer VAT number {$customer.addresses [Address ID] .formatted} -> Client formatted address {$urls.base_url} -> Store address {$urls.current_url} -> Current address (url) where we are {$urls.shop_domain_url} -> Store domain {$urls.img_ps_url} -> Image root directory url {$urls.img_cat_url} -> Url directory of images of the categories {$urls.img_lang_url} -> Url of the language images directory {$urls.img_prod_url} -> Url of the product images directory {$urls.img_manu_url} -> Url directory of manufacturers images {$urls.img_sup_url} -> Url of the providers directory {$urls.img_ship_url} -> Url directory of images of carriers {$urls.img_store_url} -> Store url {$urls.img_url} -> Url of the image directory of the template {$urls.css_url} -> Template URL directory url {$urls.js_url} -> Template JS directory url {$urls.pic_url} -> Url file directory uploaded {$urls.pages.address} -> Url from the "My Address" section {$urls.pages.addresses} -> Url from the "My addresses" section {$urls.pages.authentication} -> Url section of the authentication page {$urls.pages.cart} -> Cart section url (order summary) {$urls.pages.category} -> Url section of categories {$urls.pages.cms} -> Url of the content section {$urls.pages.contact} - > Url section of the contact form {$urls.pages.discount} -> Url of the discount voucher section {$urls.pages.guest_tracking} -> Tracking url for unregistered clients {$urls.pages.history} -> Url from the order history section {$urls.pages.identity} -> Url of the section "Personal data" {$urls.pages.index} -> Page url {$urls.pages.my_account} -> Url section of my account {$urls.pages.order_confirmation} -> Url section of the order confirmation page. {$urls.pages.order_follow} - > Url in the "Order Tracking" {$urls.pages.order} -> Url of the order page {$urls.pages.order_return} -> Url of the order return page {$urls.pages.order_slip} -> Url of the order slip page {$urls.pages.pagenotfound} -> Url of section "404 (Page not found)" {$urls.pages.password} -> Url of the section "Recover Password" {$urls.pages.pdf_invoice} -> Pdf invoice page url {$urls.pages.pdf_order_return} -> Pdf order return page url {$urls.pages.pdf_order_slip} -> Pdf order slip url page {$urls.pages.prices_drop} -> Url section we lowered prices / products discount / discounts {$urls.pages.product} -> Product tab url {$urls.pages.search} -> Url of the searcher section {$urls.pages.sitemap} -> Site Map section url {$urls.pages.stores} -> Url of the section "Shops / Our stores" {$urls.pages.supplier} -> Url from the providers section {$urls.pages.register} -> Url log page {$urls.pages.order_login} -> Order login page url {$urls.theme_assets} -> Url of the "assets" directory of the template / themes / template / assets / {$urls.actions.logout} -> Url to close section in the store
  16. 5 points
    Sorry for bringing up this old thread - but I just had to comment. You say "thousand of time"? That's the overstatement of the decade. I search for "delete order" and got 72 hits - and four of them was directly related to my search. If only people who know where to find information replyed, the web would be faster. If you don't have anything useful to say - don't say it! The challenge with forums like this is that there are people from all over the world using it. The spoken languages are many, and not all understand or writes english (or french for that matter) that well - me included! A little help and understanding is all that is needed for people to smile. And this software is all about smiling, because it's GREAT!
  17. 4 points
    This module displays the "Spend another X to get free shipping for your order" message in the cart just below the product's list, updates the value while adding / substracting product quantity. (demo) You can also set up your own free shipping amount in case you are not using the global prestashop setting (but for example have it set up in carriers) For prestashop 1.5 & 1.6: gmgetfreeshipping.zip For prestashop 1.7: gmgetfreeshipping_17.zip (the module uses widget functionality so you can attach it to any hook, or insert {widget name='gmgetfreeshipping'} code anywhere in your template)
  18. 4 points
    Product Review Module - Revws - This free module allows your customer to create product reviews. Easily. The main goal of this module is to make both review authoring and moderation process as smooth as possible. I have worked very closely with real-world merchants to make sure this module offers just the right features that you guys need. TAKE A TEST DRIVE You can try this module on my demo account Front Office / Back Office SCREENSHOTS Revws at glance ` FEATURES What can this module do for you? review import - you can easily import your reviews productcomments or yotpo. Or use my datakick module to import from any other source compatible with with prestashop 1.6 and 1.7 versions both customer and guest reviews review moderation by administrator multiple review criteria theming options - you don’t have to use standard star symbol anymore google structured data / rich snippets support customers can edit / delete their reviews voting and report abuse buttons review suggestions based on recent purchase comprehensive settings - you can tweak almost anything and much more INTEGRATIONS Revws module can seamlessly cooperate with other modules. DataKick data import / export / modification module - using my paid module, you can easily list your reviews, export or even import them. You can schedule periodic backup of your review data. You can use it to prepare list of customers who has recently purchased some product and send them a review request Loyalty Points - Genzo Krona module* - revws module is integrated with this amazing loyalty points free module. You can then set up your own rewards strategy. Send Review Request module* - you can use this free module to ask your customer for reviews. Remember, if you don't ask for it, you don't get it * due to rules on this forum, I'm not allowed to link to these modules. Use goole BUGS AND FEATURE REQUESTS If you find any bug or issue, of if you would like to see some new functionality in the module, please file an issue on github. Otherwise I might forget about it Report problem / suggest enhancement DOWNLOAD You can download latest version of this free module here version for prestashop 1.7 version for prestashop 1.6
  19. 4 points
    Age verification (popup) by PrestaCraft Current module version: 1.3.1 PrestaShop compatible: 1.6 , 1.7 This module displays the age verification popup and validates user's age. Features User validation by birthday selection or simple button click Variety of configurable display options (colors, size, fonts) Multilanguage ready Responsive Friendly User Interface Screenshots Changelog v 2.0.0 Fixed bug when popup was being closed automatically sometimes Added ability to choose categories (perfect for stores having some 18+ categories) v 1.3.1 Fixed remodal popup loading on empty instance, which caused console error v 1.3.0 Removed “remember” option from database to cookie storage Fixed undefined variables call v 1.2.0 Fixed URL in the code v 1.1.0 Fixed typo in classname Added “version checker” ---- Download ageverification_2.0.1.zip ---- Any feedback is appreciated. IF YOU LIKE THIS MODULE, PLEASE DONATE AND SHARE ❤️
  20. 4 points
    I've written a tutorial about extending registration form by adding your new fields: http://prestacraft.com/adding-new-fields-to-the-registration-form-in-prestashop-1-7/ Enjoy
  21. 4 points
    Hola Dan, muy buena tu exposición pero eso de que hay gente cerrando tiendas por bugs... PrestaShop 1.7 a día de hoy funciona correctamente, el mayor de sus problemas es que le faltan funciones que ya tenia 1.6, pero lo que hay funciona correctamente, el problema es la gente que se empeña en usar lo que usaba en 1.6 en 1.7. o usar templates como Transformer, es es lento, eso es malo... La carencia de funciones, no es nada parecido con las carencias de WooCommerce, cada vez que una tienda que gestionamos en Woocommerce crece un poco, tenemos que migrar a PrestaShop, la falta de funciones e integraciones es desastrosa, si tienes previsión de crecer no vale WooCommerce, no engañemos a la gente. Tengo varias tiendas en 1.7 funcionando sin problemas, pero hay que saber lo que se hace, no es instalar y poner un transforme, como has dicho durante años, eso era poco eficiente y celebro que te dieses cuenta.. Que recomiendes WooCommerce, me parece bien, pero tienes que hablar de la realidad, solo vale para tiendas casi presenciales, olvídate de integraciones con ERP, integraciones de almacenes, transportistas.... hablas de Paypal, ¿hay pluging oficial de Paypal para woocomerce? Yo trabajo con las tres plataformas WooCommerce, PrestaShop y Magento, mi recomendación: -WooCommerce, hacer un test, rapido y barato de montar, pero anda escalable. Si empiezas a vender tienes que salir corriendo por la falta de integraciones. -PrestaShop, entre 10 y 500 pedidos al día se gestionan sin problemas y cubrirá la mayoría de necesidades de integración. -Magento, 10 al infinito con matices, si no tienes un equipo tecnico "in house" olvídate, es un suicidio, la hora de soporte de Magento es de 50€ para arriba y con la compra de Adobe, hasta que no se aclare un poco el panorama, no iniciaría nada en Magento. Dicho esto, respeto tu opinión, pero no comparto. Saludos
  22. 4 points
    Exactly the same problem on several 1.6 sites It's due to very long time to get response fromapi.addons.prestashop.com I've temporarily disabled connection to this api in classes/Tools.php public static function addonsRequest($request, $params = array()) { return false;
  23. 4 points
    Exactly same issue here. AH01630: client denied by server configuration: /changedbecauseitsSecret/translations/cldr/datas/main/de-DE/numbers.json, referer: https://www.mydomain.com/admin/index.php/product/form/111?_token=changedbecauseitsSecret AH01630: client denied by server configuration: /changedbecauseitsSecret/translations/cldr/datas/supplemental/currencyData.json, referer: https://www.mydomain.com/admin/index.php/product/form/111?_token=changedbecauseitsSecret AH01630: client denied by server configuration: /changedbecauseitsSecret/translations/cldr/datas/supplemental/likelySubtags.json, referer: https://www.mydomain.com/admin/index.php/product/form/111?_token=changedbecauseitsSecret AH01630: client denied by server configuration: /changedbecauseitsSecret/translations/cldr/datas/supplemental/plurals.json, referer: https://www.mydomain.com/admin/index.php/product/form/111?_token=changedbecauseitsSecret AH01630: client denied by server configuration: /changedbecauseitsSecret/translations/cldr/datas/main/de-DE/currencies.json, referer: https://www.mydomain.com/admin/index.php/product/form/111?_token=changedbecauseitsSecret Solution: Change content in /translation/cldr/ .htaccess: from: Order deny,allow Allow from all to: # Apache 2.2 <IfModule !mod_authz_core.c> Order deny,allow Allow from all </IfModule> # Apache 2.4 <IfModule mod_authz_core.c> Require all granted </IfModule> Working for me and obviously it should have been changed from the maintainers....
  24. 4 points
    Malheureusement, je ne peux qu'être d'accord avec toi, Eolia ! Du Symfony (ou Zend) dans PS, la "team" n'en voulais pas à une époque, pour ne pas alourdir le code. Quand PS 1.7 est sorti, je me suis dit "chouette, je fais du Symfony depuis X années, ça va être sympa"... Et ben non, quelle merde... Comme bcp, je n'ai jamais mis un site PS 1.7 en prod et je ne le ferai jamais. La 1.8 ou 2.0 (une version toute réécrite, quoi !) peut-être, mais en attendant, la 1.6 a de beaux jours devant elle. Et il faudrait être irresponsable (pour un pro) de conseiller à ses clients de passer à cette version. Reste effectivement le cas de ceux qui se lancent seuls dans leur coin avec une 1.7 parce que la 1.6 est plus difficilement trouvable, ou parce qu'ils ont fait une install en un clic avec OVH (tant qu'à faire des conneries...) et qui viennent ici après quand les galères commencent.
  25. 4 points
    Hi Mustang80, We are also on PS 1.7.2.4 and had the same problem. With help of tips at https://www.prestashop.com/forums/topic/597944-search-two-or-more-words/?tab=comments#comment-2631092we modified the file classes/seach.php. This solved the problem in our site. Seach is getting exact results now.Attached the modified search.php file. Rename the file to search.php and upload to your server.Best regards,Peter PS-1.7.2-modified-for-or_Search.php
×

Important Information

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