Jump to content

Leaderboard

  1. Mediacom87

    Mediacom87

    Global Moderators


    • Points

      23

    • Content Count

      9,761


  2. El Patron

    El Patron

    Members


    • Points

      17

    • Content Count

      14,614


  3. JBW

    JBW

    Members


    • Points

      16

    • Content Count

      1,266


  4. joseantgv

    joseantgv

    Members


    • Points

      15

    • Content Count

      5,024



Popular Content

Showing content with the highest reputation since 03/01/2020 in Posts

  1. 2 points
  2. 2 points
    Bonjour, Il faut les mettre tous dans un dossier mère et zipper ce dossier .
  3. 2 points
    * nGinx v1.16.1 * Linux CentOS 7 * PHP 7.2.27 (FastCGI FPM) After struggling to get the latest release (1.7.6.4) up and running on nGinx I finally have it working. Both the admin and shop. Enjoy! Please comment when you have issues. I tested it quite a bit but nothing is perfect. server { # Port 80 IPv4/6 # listen 80; # listen [::]:80; # SSL Ipv4/6 listen 443 ssl; listen [::]:443 ssl; # Your SSL Certificates, don't forget to take a look at Certbot (https://certbot.eff.org) include /etc/nginx/ssl_params.conf; ssl_certificate "/your-certificate.pem"; ssl_certificate_key "/your-private-key.pem"; ssl_trusted_certificate "/certificate-chain.pem"; # [REQUIRED EDIT] Your domain name goes here server_name <your domain name>; error_log /var/log/nginx/prestashop.error_log; # [REQUIRED EDIT] Absolute path to your website root on the filesystem root /home/vhost/<your domain name>/shop; index index.php index.html; # to control the amount that can be uploaded. client_max_body_size 50M; # set admin folder name set $admin_dir /<admin_folder_name>; #Example: admin245tm20au location ~ /admin.*/(sell|api|common|_wdt|modules|improve|international|configure|addons|_profiler|product|combination|specific-price)/(.*)$ { try_files $uri $uri/ /index.php?q=$uri&$args $admin_dir/index.php$is_args$args; } # Cloudflare / Max CDN fix location ~* \.(eot|otf|ttf|woff|woff2)$ { add_header Access-Control-Allow-Origin *; } # Do not save logs for these location = /favicon.ico { log_not_found off; access_log off; } location = /robots.txt { auth_basic off; allow all; log_not_found off; access_log off; } location / { # Redirect pretty urls to index.php try_files $uri $uri/ /index.php?$args; # Images rewrite ^/([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$1$2$3.jpg last; rewrite ^/([0-9])([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$2/$1$2$3$4.jpg last; rewrite ^/([0-9])([0-9])([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$2/$3/$1$2$3$4$5.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$2/$3/$4/$1$2$3$4$5$6.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$2/$3/$4/$5/$1$2$3$4$5$6$7.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$1$2$3$4$5$6$7$8.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$7/$1$2$3$4$5$6$7$8$9.jpg last; rewrite ^/([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])([0-9])(-[_a-zA-Z0-9-]*)?(-[0-9]+)?/.+.jpg$ /img/p/$1/$2/$3/$4/$5/$6/$7/$8/$1$2$3$4$5$6$7$8$9$10.jpg last; rewrite ^/c/([0-9]+)(-[.*_a-zA-Z0-9-]*)(-[0-9]+)?/.+.jpg$ /img/c/$1$2$3.jpg last; rewrite ^/c/([a-zA-Z_-]+)(-[0-9]+)?/.+.jpg$ /img/c/$1$2.jpg last; # AlphaImageLoader for IE and fancybox rewrite ^images_ie/?([^/]+)\.(jpe?g|png|gif)$ js/jquery/plugins/fancybox/images/$1.$2 last; # Web service API rewrite ^/api/?(.*)$ /webservice/dispatcher.php?url=$1 last; } # Allow access to the ACME Challenge for Let's Encrypt location ~ /\.well-known\/acme-challenge { allow all; } # Block all files with these extensions location ~ \.(md|tpl)$ { deny all; } # File security # .htaccess .DS_Store .htpasswd etc location ~ /\. { deny all; } # Source code directories location ~ ^/(app|bin|cache|classes|config|controllers|docs|localization|override|src|tests|tools|translations|travis-scripts|vendor|var)/ { deny all; } # Prevent exposing other sensitive files location ~ \.(yml|log|tpl|twig|sass)$ { deny all; } # Prevent injection of php files location /upload { location ~ \.php$ { deny all; } } location /img { add_header Cache-Control public; expires 1d; location ~ \.php$ { deny all; } } location ~ \.php$ { # Verify that the file exists, redirect to index if not try_files $fastcgi_script_name /index.php$uri&$args; fastcgi_index index.php; include fastcgi_params; fastcgi_split_path_info ^(.+\.php)(/.+)$; fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name; fastcgi_param SCRIPT_NAME $fastcgi_script_name; fastcgi_pass unix://var/run/php-fpm/php-production.sock; } }
  4. 2 points
    @ttoine Franchement, comme tu le dis, certaines boutiques le désactivent lorsque leur nombre de ventes augmente, mais en parallèle, ce type de boutique met en place des procédures internes à l'aide d'autres outils pour prendre en charge la logistique de leurs commandes et donc elles remplacent juste ce module par une autre méthode mais toutes, strictement toutes les boutiques actives ce module au démarrage de leur boutique. Retirer ce module est juste une aberration reconnue par l'ensemble des personnes présentes sur ce forum puisque nous avons la demande tous les 4 matins concernant la méthode en 1.7 pour recevoir les commandes par email. Donc, il serait de bon ton de remettre en place rapidement ce module à disposition. Par contre, le discours expliquant que les modules désactivés sont retirés me fait doucement rire jaune dans mon coin. Car des modules comme Gamification sont toujours présents alors que tout le monde doit les désinstaller car ils ne servent à aucun marchand dans le monde. Je ne vais pas lister tous les modules purement marketing totalement inutiles et qui ralentissent le backoffice de tous les commerçants et plante certaines fois avec des beaux messages d'erreur incompréhensibles car ils n'arrivent pas à atteindre un fichier sur les serveurs PrestaShop. Je ne parlerais pas non plus de l'absence de consentement clair pour que les données des commerçants soient envoyées à des fins statistiques à PrestaShop, dont je ne connais pas la procédure d'effacement de ces données dans le cadre du RGPD, mais comme le sujet et envoyé sous le tapis depuis plus de 10ans je n'ai perdu mon temps à éplucher l'ensemble des petites lignes présentes partout concernant PrestaShop et sa politique. Voilà, petit coup de gueule du soir mais serein, car je sais, par expérience, que ce genre de propos restera lettre morte ou me permettra d'être classé dans une case proche de certains autres acteurs majeurs du forum.
  5. 2 points
    Ce n'est pas parce qu'il est gratuit qu'il ne doit pas respecter certains standards, notamment en terme de sécurité. Vous le mettez à la disposition de gens qui ne sont pas capables de déterminer s'il est fiable. Si vous faites ça en amateur dans ce cas vous l'indiquez aux personnes qui vont le télécharger, et là c'est de leur responsabilité d'utiliser le module ou non. Mais si c'est professionnel il faut quand même fournir quelque chose qui passe le validateur PS, au moins en terme de sécurité. Il existe des sites qui référencent tous les modules Prestashop qui présentent des failles. Les bots n'ont plus qu'à scanner les sites pour trouver ceux qui les utilisent et les hacker. Alors oui dans ce cas précis le module ne propose peut-être pas d'upload, mais ça reste des problèmes de sécurité qui peuvent être identifiés en 2 min et corrigés en 10.
  6. 1 point
    Eso es solo un "notice" (aviso), ese no es el error real por el que tus clientes no se pueden registrar. Habilita errores a ver si aparece algo más, aunque primero deberías solucionar ese error para que no te salga. Ese es un error de la plantilla.
  7. 1 point
    @ttoine tu fais de l'enrobage totalement inutile ici. Personne ne dit que Addons est totalement responsable de la qualité déplorable des template mais qu'il pourrait y avoir une amélioration pour éviter certaines pratiques et la première serait que chaque module présent dans le template passe tous totalement au validateur au minimum qu'ils soient tous PPSR2 et qu'on embête les designer autant que les petit développeurs de modules. Mais là n'est pas le soucis. ici, @NOS remonte une fraude, pas un soucis technique une fraude caractérisée. Le créateur de ce template doit, lui et tous ces porduits, être exclus d'addons, purement et simplement. Si vous trouvez, chez PrestaShop Addons que le chantage est une méthode commerciale comme les autres, disons que nous sommes, nous aussi, capable de l'appliquer en remontant sur les réseaux sociaux l'indigeste action d'Addons concernant ce cas.
  8. 1 point
    Hola, A mi también me paso en la 1.6, no recuerdo cual era el problema, dejame investigar. Has probado si te pasa igual con otros nevagdores?
  9. 1 point
  10. 1 point
    ./controllers/admin/AdminAddressController.php after: $temp_fields[] = array( 'type' => 'text', 'label' => $this->trans('VAT number', array(), 'Admin.Orderscustomers.Feature'), 'col' => '2', 'name' => 'vat_number', 'required' => in_array('vat_number', $required_fields), ); add: $temp_fields[] = array( 'type' => 'html', 'html_content' => '<hr style="border-top: 2px dashed red; margin-left: -25%;" />', 'col' => '8', 'name' => 'divider', );
  11. 1 point
    Hallo, Kann man hier aendern: Preferences > Meta-Tags. (unter SEO & URL - index page)
  12. 1 point
    El theme classic estructura la página de producto con dos columnas. Ambas se identifican con la clase "col-md-6". En el primer div encuentras las imágenes, y en el segundo el resto de información del producto. Si quieres eliminar por completo la parte de las características de producto y dejar tan solo la descripción larga en la columna izquierda, localiza este código en tu product.tpl: {block name='product_tabs'} <div class="tabs"> <ul class="nav nav-tabs" role="tablist"> {if $product.description} <li class="nav-item"> <a class="nav-link{if $product.description} active{/if}" data-toggle="tab" href="#description" role="tab" aria-controls="description" {if $product.description} aria-selected="true"{/if}>{l s='Description' d='Shop.Theme.Catalog'}</a> </li> {/if} <li class="nav-item"> ......................... Ese es el código que determina dónde aparecen las pestañas "Descripción" y "Detalles del producto". Corta TODO el bloque ({block name='product_tabs'} .... {/block}) y pégalo dentro del contenedor "col-md-6". El que NO está identificado con la clase "product-data-right". Debes pegarlo al final del bloque para que aparezca debajo de la galería de imágenes. Estílalo con css a tu gusto para conseguir la separación y el efecto que desees. Con esto conseguirás que tanto Descripción como Detalles de producto se muestren bajo las imágenes de la columna izquierda. Ahora, para eliminar del template detalles del producto, localiza este código y BÓRRALO <li class="nav-item"> <a class="nav-link{if !$product.description} active{/if}" data-toggle="tab" href="#product-details" role="tab" aria-controls="product-details" {if !$product.description} aria-selected="true"{/if}>{l s='Product Details' d='Shop.Theme.Catalog'}</a> </li> A continuación debes localizar el contenedor de product details. Busca este código: {block name='product_details'} {include file='catalog/_partials/product-details.tpl'} {/block} Y bórralo. Tienes que entender qué hace cada parte del código. El elemento <li class="nav-item"> contiene un enlace con el texto "Product Details" o "Detalles del producto" con un escuchador de evento. Cuando se pulsa, el contenedor de la descripción se oculta (display:none) y el contenedor de las características se muestra (display:block o inline)
  13. 1 point
    W razie kontroli najpierw patrzą na to czy jest dokumentacja przetwarzania danych osobowych w firmie, a nie czy na jakiejś tam jej stronce jest polityka prywatności.
  14. 1 point
    Hi @electriz Thank you for this module!
  15. 1 point
    Hello guys, I see that lots of PrestaShop 1.7 users are facing this issue. It may have different reasons: As mention earlier, the "config.yml" file or folder might be missing. Go to your theme zip file, check if there's a folder called "config", a file called "config.yml" should be inside this folder. If you don't see the config folder or config.yml file, you may need to contact theme developer. The other reason might be multiple-zip-files inside each other. Sometimes your theme ZIP file contains other zip files for different PS versions or etc. If so, you need to extract it and upload the correct one. The correct zip file should contain the main theme files and folders like "assets, config, dependecies,...". A bug in PrestaShop 1.7 with ZIP files! Yes there's an issue (check here) in PrestaShop (at the time I'm writing this post, the latest version is PS 1.7.6.4) with ZIP files. You may check your theme zip file and see there is no problem with the config file or folder and there are no other zip files inside your theme zip file as well but you still get this error. A lot of theme developers use Windows for their development workspace and do their development using XAMPP or WAMP softwares. When they finish development, they click on "Export Current Theme" and PrestaShop generates a ZIP file automatically inside theme folder. Here the issue appears, if you upload this file in anyway, you'll get "PrestaShop\PrestaShop\Core\Domain\Theme\Exception\ThemeConstraintException code 2" error. It is caused since PrestaShop allows only "application/zip file type" but when you export the theme inside Windows it is generated in "application/x-zip file type". To solve this issue (Issue No. 3): First of all, you need to download "7-zip" software. Download and install the right version based on you OS type. Extract your theme zip file in somewhere on your computer. Select the extracted files, right click on them, go to "7-Zip" menu and click on "Add to archive...". Define a name for it like "theme.zip" and click OK button (Do not remove the .zip extension and do not use Spaces in you file name. You can use the dash (-) character instead. E.g: my-theme.zip). Now upload the zip file that is generated by 7-Zip into your shop. The problem is solved Enjoy your new theme!
  16. 1 point
    Hi, You can use a module to fill the meta description automatically from the product description.
  17. 1 point
    There are several possibilities. The easiest way is to edit PaymentModule.php in ../classes/ Add an entry to the database after sending order_conf email, which is an order confirmation. Find code: if (Validate::isEmail($this->context->customer->email)) { Mail::Send( (int)$order->id_lang, 'order_conf', Mail::l('Order confirmation', (int)$order->id_lang), $data, $this->context->customer->email, $this->context->customer->firstname.' '.$this->context->customer->lastname, null, null, $file_attachement, null, _PS_MAIL_DIR_, false, (int)$order->id_shop ); } and add after: Db::getInstance()->Execute('update '._DB_PREFIX_.'customer set id_default_group = 4 where id_customer = '.$this->context->customer->id; Db::getInstance()->Execute('insert into '._DB_PREFIX_.'customer_group values('.$this->context->customer->id.',4)'); Change 4 to your customer group.
  18. 1 point
    "Movic Leo Theme" should be affected by the choice of "Upgrade/Switch to the default theme" in 1-click upgrade. non-native modules refers to those free/paid modules. You can also re-enable non-native modules after upgrade. I used Prestashop's Default Classic Theme. After I upgrade, I have to re-apply the custom.css (Customized font, color, bullet type...) as well. I usually backup what I have before upgrade. In your case, you have to prepare to re-apply your theme after upgrade, e.g. export or backup your theme. You never know what is the result of the 1-click upgrade as it depends on how many additional module/customization you have in your system. Although, 1-click upgrade is MUCH more stable than in 1.6.x and 1.7.3 ... Also surprise you ... However, you better CLONE your production system and upgrade the CLONED one as a rehearsal. This is my practice even on minor upgrade ... ... Cheers, hope this helps !! David
  19. 1 point
    Σε πελάτη που είχαμε το ίδιο πρόβλημα στην ίδια τράπεζα, ήταν θέμα της php. Όταν βάζαμε php7.1 έκανε αυτό το πρόβλημα, μας έστειλε αναβάθμιση η εταιρία που το έφτιαχνε και λύθηκε το θέμα.
  20. 1 point
    Bonjour, Merci c'est très sympa, est ce entièrement valide pour la nouvelle version de Prestashop ? Tu t'est basé sur https://github.com/PrestaShop/ps_advertising ... ? C'est bien ça ? 😉
  21. 1 point
    {yourServer}/themes/classic/templates/_partials/header.tpl
  22. 1 point
    Hola Roque yo creo que este software te puede ir superbien para lo que necesitas, puedes probarlo gratis unos dias https://store.emagicone.com/store-manager-for-prestashop-standard-edition.html código de descuento: maya-AAEM-15-OFF
  23. 1 point
    Hola, Como ya saben, en la nueva actualización de Prestashop 1.7.6 cambio el registro de carpetas y el antiguo error que contenían las monedas en la posición del signo ($) y (CLP) se encuentra en otra posición. Por lo cual, para solucionar este problema (Bug,) debes ingresar en el siguiente directorio. /public_html/localization/CLDR/core/common/main/es.xml Deben buscar la siguiente linea de código. <currencyFormat type="standard"> <pattern>#,##0.00¤ </pattern> </currencyFormat> <currencyFormat type="accounting"> <pattern>#,##0.00¤ </pattern> Y dejarla así. ¤ <<<---esto es lo que hay que modificar (Solo la ubicación del símbolo) <currencyFormat type="standard"> <pattern>¤#,##0.00 </pattern> <currencyFormat type="accounting"> <pattern>¤#,##0.00 </pattern> Borrar cache y con eso debería funcionar. Saludos www.softcomerce.cl
  24. 1 point
    Merhaba Bu toplantıda gündemimize aldık. Sonraki etkinliği webinar şeklinde düzenleyeceğiz. Buradan haberdar edeceğim.
  25. 1 point
    be warned, if you enable native geo location and the IP does not resolve (high % of free geolitecity free data do not resolve) then the visitor cannot shop. We have geo targeting pro module on addons, it supports amongst other things ip blacklist much like native does but I can see where it would be a nice new feature or new module to block by country. Back to hosting, contact your hosting for advice but this might help as well https://www.ip2location.com/free/visitor-blocker
  26. 1 point
    Bonjour, c'ets là que l'analyse du profil du développeur est important, on a une information qui indique l'attitude du développeur dans la gestion de ses productions et surtout de son support. https://addons.prestashop.com/fr/content/40-echelle-d-expertise-prestashop-bien-choisir-son-developpeur Cette information st précisé sur les information Développeurs de la fiche produit mais, avant on avait cela mis en avant avec une petit image de Preston, maintenant c'ets relégué en 3ème onglet sous forme de texte à cliquer. Perso je me bas tous les jours pour essayer d'avoir le meilleur support possible car cela me saoulerais d'acheter un module qui ne fonctionne pas et surtout que le développeur s'en moque. Donc, vous pouvez déjà regarder comment est noté chaque développeur de ces modules. Ah oui, aussi, sachez que cette notation n'implique pas les équipes de PrestaShop donc tous les modules développés par PrestaShop sont toujours tous super bien notés ... malgré tout.
  27. 1 point
    Also am "besten" ist, wenn du eine contentbox nimmst: http://contentbox.org/ (Ganz unten kannst du eine neue generieren mit passendem Namen) Da kopierst du dann deinen Code rein den du von Analytics bekommen hast. (Denk aber daran den Code Datenshcutzkonform zu bearbeiten: https://www.datenschutzbeauftragter-info.de/fachbeitraege/google-analytics-datenschutzkonform-einsetzen/) Dann kannst du die Contentbox an den Hook "displayafterbodyopeningtag" anhaken und solltest dadurch auf allen Seiten den Analytics Code haben.
  28. 1 point
    Не var/log, а в консоле браузера что пишет, есть ошибки? Попробуйте локально ( если магазин на сервере).
  29. 1 point
    Hi, This is a cached URL , try to delete the cache in var/cache/dev and var/cache/prod .
  30. 1 point
  31. 1 point
    Delete /var/cache and re-generate .htaccess
  32. 1 point
  33. 1 point
    Ah ben oui, avec ce genre de demi information on va tout de suite aider vachement plus. Relisez votre demande, activez votre cerveau, et essayer de trouver toutes les informations qu'il manque car il en manque beaucoup.
  34. 1 point
    Hello Maryjan, Thank you so much for downloading and using our Live Chat free module. We have just updated a new version for Live Chat free module, including the bug fix for translation problem. You can download and use the latest version of Live Chat free module now. Please copy your pl.php file and paste to /translation folder of the new version menu to preserve all of your Polish translation. If you have any more question, feel free to contact me. My best regard.
  35. 1 point
    Estos dias han detectado un posible fallo en algunos ficheros que usan los modulos de Prestashop, tanto por desarrolladores externos como los propios de prestashop. La solución es eliminar los modulos que puedes estar afectados, por ahora el mas instalado el modulo de actualización, Han desarrollado un modulo el cual te dice la versión del PHP ademas de los modulos que usan estos ficheros Aqui el enlace de la pagina desarrollador Armando Salvador ayer público en su Youtube como hacerlo
  36. 1 point
    You can rename you whole /var/cache folder to /var/cache_old - Presta will regenerate it with next page call
  37. 1 point
    I have created/updated origional breadcump.tpl and added pages who i wanted to include. Page to include?/exclude you do update in the lines highligted working perfect in prestashop 1.6 versions. ps dont forget to backup your origional before copy past <!-- Breadcrumb --> {if isset($smarty.capture.path)}{assign var='path' value=$smarty.capture.path}{/if} <div class="breadcrumb" {if $page_name == 'product' or $page_name == 'category' or $page_name == 'cms' or $page_name == 'new-products' or $page_name == 'best-sales' or $page_name == 'prices-drop' or $page_name == 'manufacturer' or $page_name == 'sitemap' or $page_name == 'content' or $page_name == 'stores' or $page_name == 'search'}itemscope itemtype="http://schema.org/BreadcrumbList"{/if}> <!-- <div class="container" > --> <!--<meta itemprop="name" content="{$meta_title|escape:'html':'UTF-8'}"/>--> <span {if $page_name == 'product' or $page_name == 'category' or $page_name == 'cms' or $page_name == 'new-products' or $page_name == 'best-sales' or $page_name == 'prices-drop' or $page_name == 'manufacturer' or $page_name == 'sitemap' or $page_name == 'content' or $page_name == 'stores' or $page_name == 'search'}itemprop="itemListElement" itemscope="" itemtype="http://schema.org/ListItem"{/if}><meta itemprop="position" content="1"><a class="home" itemprop="item" href="{if isset($force_ssl) && $force_ssl}{$base_dir_ssl}{else}{$base_dir}{/if}" title="{l s='Return to Home'}"><meta itemprop="name" content="{l s='Home'}" /><i class="icon-home"></i></a></span> {if isset($path) AND $path} <span class="navigation-pipe" {if isset($category) && isset($category->id_category) && $category->id_category == (int)Configuration::get('PS_ROOT_CATEGORY')} style="display:none;"{/if}>{$navigationPipe|escape:'html':'UTF-8'}</span> {if $page_name == 'product' or $page_name == 'category' or $page_name == 'cms' or $page_name == 'new-products' or $page_name == 'best-sales' or $page_name == 'prices-drop' or $page_name == 'manufacturer' or $page_name == 'sitemap' or $page_name == 'content' or $page_name == 'stores' or $page_name == 'search'} {if $path|strpos:'span' !== false} <span class="navigation_page" > {$path|@replace:'<a ': '<span > <span > <a itemprop="item" '|@replace:'data-gg="">': '> <span >'|@replace:'</a>': '</a></span></span>'}</span> {else} <span itemprop="itemListElement" class="item-breadcrumb" itemscope="" itemtype="http://schema.org/ListItem"><meta itemprop="position" content="1"><meta itemprop="item" content="{if isset($force_ssl) && $force_ssl}https://{$smarty.server.HTTP_HOST}{$smarty.server.REQUEST_URI}{else}http://{$smarty.server.HTTP_HOST}{$smarty.server.REQUEST_URI}{/if}" /><meta itemprop="name" content="{$path}" /><span class="item-breadalone">{$path}</span></span> {/if} {else} {if $path|strpos:'span' !== false} <span class="navigation_page" > {$path|@replace:'<a ': '<span > <span > <a '|@replace:'data-gg="">': '> <span >'|@replace:'</a>': '</a></span></span>'}</span> {else} <span class="item-breadalone">{$path}</span> {/if} {/if} {/if} </div>
  38. 1 point
    Problem rozwiązany. Źródłem problemu okazał się znak [%] w haśle, który instalator odczytał poprawnie i wykorzystał do połączenia z bazą danych na etapie tworzenia tabel sklepu, ale później, podczas zapisu do pliku z konfiguracją w: app/config/parameters.php z niewiadomych powodów zamienił na [%%], więc oczywiście wszystko przestało działać. Po po przywróceniu prawidłowego hasła do bazy danych w parameters.php sklep ruszył.
  39. 1 point
    Si, lo probé y funciona en diferentes idiomas, además permite intentar detectar automáticamente el idioma de la web.
  40. 1 point
    Szólj, ha nem sikerül választ kapni, szólok a fejlesztőnek egy másik csatornán.
  41. 1 point
    Miałem to samo, w modułach znajdź "Customer Reassurance" - to jest to tylko nieprzetłumaczone
  42. 1 point
    tried to add the product to cart but there was an internal server error...I think everyone would appreciate a direct download link. Thank you.
  43. 1 point
    Hello All, I have 2 small modules that are working on 1.6 . I plan to upgrade to 1.7 so I need to upgrade those too. Is there any tutorial for upgrading ? for writing modules to be compatible with 1.6 and 1.7 as well ? Thank you, Daniel
  44. 1 point
    Hi everybody, Excuse me in advance, from my bad practice of English ... I think I have a solution, for me it works. 1/ You must override the class Dispatcher.php (override/classes/Dispatcher.php) for removing id_product_attribute from the default route table 2/ Then you can edit the PS_ROUTE_product_rule parameter directly in database or from the form (/admin/index.php?controller=AdminMeta) SELECT * FROM `ps_configuration` where name like '%PS_ROUTE_%' 3/ it is also necessary to override ProductAssembler.php Prestashop class. Some modules rely on this class to present articles. (override/classes/ProductAssembler.php) 4/ And finally, override Link.php (override/classes/Link.php) for remove from getProductLink method the anchor Here is an example of an url: http://exemple.com/1-hummingbird-printed-t-shirt.html Thank you, iradorn
  45. 1 point
    https://prestabuilder.com/2017-05-19/display-full-width-tabs-product-detail-page-prestashop-1-7/
  46. 1 point
    Try this: http://nemops.com/extending-prestashop-objects/#.V39kafn5jmg Definition is static
  47. 1 point
    This is not the correct code class PDFGeneratorCoreOverride extends PDFGeneratorCore { It should be this... class PDFGenerator extends PDFGeneratorCore {
  48. 1 point
    Check http://doc.prestashop.com/display/PS16/Installing+PrestaShop#InstallingPrestaShop-Quickinstallationinstructions So in your folder where you installed PrestaShop locate admin folder, it have some numbers after admin, like admin12345. And url would be 127.0.0.1/www/prestashop/admin12345
  49. 1 point
    If there's no default attribute set on the product then this will happen. If you go to the combinations tab for the product and set one of the combinations as default then the price will display correctly. Unfortunately this happens even if the combinations have no price impact!!
  50. 1 point
    All I'm getting is a blank file after selecting fields and clicking export. Any clues as to how to fix?
×
×
  • Create New...

Important Information

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