Jump to content


Popular Content

Showing content with the highest reputation since 08/21/2018 in all areas

  1. 14 points
    I needed a COD with fee module and since I couldn't find what I was looking for (for free), I decided to make one myself. Some features: Compatible with multiple currencies and multiple shops Ability to either integrate the COD fee with the Carrier's fee, or add a dummy product in the order to reflect the fee, with configurable tax. Many parameters to check for in order to apply the fee (cart total, delivery country, delivery zone, carrier, customer group, product categories, manufacturers, suppliers). Many ways to calculate the fee (fixed value, percentage of the cart value or a combination of the two). All parameters are defined in conditions, which each calculates a fee if is validated. You can choose to use the first one that was validated, or add all of the successful ones to define the fee. Ability to test a scenario to see if your condition will produce the desirable fee. Ability to store all the purchases done with this module, with a complete log of how the fee was calculated. Ability to check (or autocheck if configured) for an update. I intend to keep updating it, so please let me know if you have any problems or suggestions. You can find it in github as well if you want to contribute (sakgiok/codwfeeplus). Edit: v1.0.9 added real time cart summary update during checkout for Prestashop v1.7 Edit: v1.0.10 fixed a bug with carriers not listed when they were added by a module. Edit: v1.1.0 added a condition type field to be able to disable module when these conditions are met, plus a bug fix and some color redesign (Control+F5 to reload the page to see the new css). Edit: v1.1.1 Taxes are now displaying correctly in PS1.7 cart summary and in PS 1.6-1.7 invoice and added some helpful buttons in condition parameter editing. Edit: v1.1.2 Order State is available to be configured plus some bug fixing and visual fixes. Some sanity checks added to make sure all condition values are present in Prestashop. Edit v1.1.3 Fixed a serious bug in payment validation. Edit v1.1.4 Fixed some bugs reported here (cart summary in PS1.7, tax displaying, reordering with COD Product etc). Edit v1.1.5 Added compatibility for PS versions and Edit v1.1.6 Fixed a bug for some PS versions < and added provision for PS version Edit v1.1.7 Added "States" field in conditions to validate against the state of the delivery address. Edit v1.1.8 Fixed a bug that prevented the module to work when installed fresh. Download: codwfeeplus_1.1.8.zip GitHub Link: https://github.com/sakgiok/codwfeeplus Demo: https://ps17demo.sakgiok.gr/admin107ak3oho Username: demo@ps17demo.sakgiok.gr Password: demodemo
  2. 10 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 Add position Left or Right page Product Share Page BUY PRO VERSION PRESTASHOP WHATSAP MODULE DEMO 17-whatsapp-live-chat.zip 17-whatsapp-live-chatV3.zip
  3. 9 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
  4. 8 points
    This is a free module that adds an additional field to the category form, allowing you to enter additional description. It may be usefull for SEO purposes. For PS 1.6: To use the module you need to install it and then add {hook h='displayCategorySecondDescription'} to category.tpl in a place where you want to display the description, you may also add this hook to some other place, letf column, footer, it should work everywhere as long as you are on a category page. For PS 1.7 Install the module and then add {widget name='gmcatseconddesc'} to templates/catalog/listing/product-list.tpl just before the {else} tag or in any other place that you like. You can also attach this module to any hook, where you would like the description to show. Note: The description won't show for pagination pages, where the ?p parameter is greater that 1. gmcatseconddesc_16.zip gmcatseconddesc_17.zip Detailed implementation description: http://greenmousestudio.com/en/cat-desc
  5. 8 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
  6. 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
  7. 6 points
    Display Add To Cart button in product list pages PrestaShop 1.7.x View Demo hiaddtocartbutton_v1.0.6.zip
  8. 6 points
  9. 5 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 ❤️
  10. 5 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)
  11. 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.
  12. 5 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
  13. 5 points
    Hola cómo estáis!, Bueno veo que el tema esta calentito por el foro y que lo que ha pasado con web empresa ha denotado que PrestaShop no está haciendo las cosas como tocan. He creado un video en mi canal comentando mi opinión, y relajando un poco el tema: www.youtube.com/watch?v=pox8rSxXExc Mi opinión personal, para dejarla por aquí también escrita, es que el error principal ha venido dado por las prisas que se provocaron para sacar una versión 1.7. Que nadie se confunda, no tuvo nada que ver con posicionamiento de mercado, Magento en ese momento estaba con grandes problemas y Shopify no había pegado tan fuerte, Woo estaba en pañales todavía. El problema clave aquí es que la directiva necesitaba y apretaba al equipo para sacar la versión antes de fin de año para marcarse un punto con los inversores. Si habéis estado al caso, han cambiado el CEO de PrestaShop y no ha sido por casualidad. Hoy justamente he tenido la oportunidad de hablar con el equipo de PrestaShop sobre mi posición como Partner, agencia etc y como están tratándolas. Esperemos que para mejorar la relación y lo que aportan. (eso es otro tema, no quiero liarme). Recordáis el tema de las Release Candidates??, donde se ha visto que aparezcan 3 RC con errores de inestabilidad, eso fue grave pero se podía gestionar gracias a que era cosas de GitHub. Claramente se sacó algo mucho antes de que se debiese sacar. Sobre el paso a usar Symfony, me parece que es una de las mejores decisiones que se tomaron, puesto que esto hace que el framework se mantenga por otra comunidad y de más tiempo al equipo de PrestaShop de mantener y crear nuevas funcionalidades. El cambio de theme ha sido la leche, y realmente aporta mucha funcionalidad, el Child Theme está haciendo las delicias de mis compañeros, poder extender el tema es lo mejor... Sobre los errores o bugs, creo que esta versión debe servir para cambiar la mentalidad, debe poder actualizarse siempre que se necesite, no puede ser esto de dejar a los usuarios atrapados en versiones porque se trapichea (permitidme la expresión) el código. Relacionado con esto y directamente con el problema de salir antes, está relacionado que la versión 1.7 saliese por ejemplo con la opción de multitienda, lo habéis probado... es la muerte.... hasta la 1.7.4 no se corrigen los errores de Contexto relacionados con el Back Office, no hubiese sido mejor dejar esa opción deshabilitada hasta por ejemplo la 1.7.5, y enviar un newsletter informando con un "Pásate ahora a la 1.7 tu mutitienda esta lista y esperándote"... Realmente lo que se lleva a cabo se prueba, el checkout, es un buen ejemplo, test unity para comprobarlo, ejecutar pruebas de desarrollo etc, pero no está todo en test unity y los módulos de addons están fuera de esa comprobación. No obstante, creo que los avances están dándose, si se hubiese sacada a finales de 2017 parecería que se avanza un montón, pero trayendo lo arrastrado de casi un año parece un siglo.... Sobre Webempresa, como empresa ellos verán, pero como comento en mi vídeo lo mismo esa subida de nivel en el desarrollo les implica hacer un gran esfuerzo en llevar a cabo la formación del equipo para que sea capaz de gestionar dudas sobre Symfony... Bueno no me extiendo mucho más, tengo esperanzas en la 1.7.5 que va a traer novedades y por lo que veo en GITHUB parece que se están centrando en temas de estabilidad y funcionalidad propia de PrestaShop, por tanto iré rescatando información del equipo de Francia e iré actualizándola en el canal. Un abrazo a todos!!
  14. 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
  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
    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 ❤️
  18. 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)
  19. 4 points
    DataSwitchPro - Automatic on/off switch for categories and products free module by crezzur Update 16/05: we are considering adding a cronjob to this module (fires automatically every x time and disable and enable categories). For this we want feedback from the users to know if this update is needed. Features < This module will automatically search for (sub)categories with no products and automatically disable them. > < This module will automatically search for (sub)categories with products and automatically enable them. > < This module will automatically search for products with no quantity's and automatically disable them. > < This module will automatically search for products with quantity's and automatically enable them. > < You can choose the time frame of the DataSwitchpro (how many times a day it has to check to enable/disable products) > < You can disable (sub)categories or products if you don't want to use this feature. > How does this work? Every time a customer visit your site a query will run to see when was the last time the DataSwitchPro was active. If this is longer then the time frame you have selected, a update query will run. Products and (sub)Categories with no products/quantity's will automatically disable. Products and (sub)Categories that are updated with new products/quantity's will automatically be re-activated. This product works with Prestashop versions 1.6.+ / 1.7+ Back office configuration Setup Install the zip file, change the settings if you want, and your ready! Download this FREE module NOW! V1.0.4 (26/05/2019)* Click here to download OR dataswitchpro.zipdataswitchpro.zip Contributors: PrestaMake V1.0.3 (16/12/2018)* DOWNLOAD REMOVED V1.0.2 (09/10/2017)* DOWNLOAD REMOVED * We have updated our module to the prestashop 1.7 codding requirments. Products which allow ordering when out of stock will not be disabled anymore V1.0.1 (08/11/2016)* DOWNLOAD REMOVED * Version 1.0.0 has to be uninstalled first. V1.0.0 (17/02/2015) DOWNLOAD REMOVED ---------------- PS: a like and a thank you for my work is appreciated ----------------
  20. 4 points
    One Click Order (Quick Buy) module is the faster and easier way to order from online shop for the customers. It will be faster and easier for your customer to order on your shop. This module allows to simplify creating orders in your store on product page. Customer or guest will only specify its name and phone. Super easy install and customize. Allow quick orders for customers and guests. Send notice on email to the administrator of the store. Set width for popup. Change background button. Simple and Friendly user interface. Compatible with all web browsers. Multi-language and Multi-store ready. Support and well documented. Video Settings Demo 1.6 Demo 1.7 Update: 21.12.2017 - ver 1.0.1 - Fix: Please check your data and added mails template on languages - en, de, ar, es, fr, it, ru bonorder.zip
  21. 4 points
    Salve e buongiorno a tutti . Dopo aver sviluppato e messo a disposizione della community questo modulo per la versione 1.6 (disponibile a questo post) il nostro reparto tecnico ha trovato un ritaglio di tempo per poterne sviluppare una versione adatta al nuovo PrestaShop, la 1.7 per l'appunto Abbiamo deciso di creare un nuovo post perché questo modulo è totalmente (o quasi) diverso da quello per la 1.6, che di fatto non funzionerebbe. Quindi riscritto appositamente per la 1.7, e compatibile con il nuovo template 'classic' (ovviamente ) Il modulo è stato creato sulla versione di PrestaShop. Testato fino alla Il modulo oltre ad aggiungere uno stato d'ordine specifico per il metodo di pagamento scelto aggiunge anche i template delle email con le specifiche informazioni della PostePay da dover ricaricare, quindi il titolare, il numero di PostePay e il codice fiscale del titolare. Potete personalizzare i testi delle email nel seguente percorso (dopo aver installato il modulo) prestashop/mails/it/tanzopostepay.html Accettiamo qualsiasi suggerimento per delle eventuali migliorie o modifiche da applicare. Il modulo è risk-free, ma consigliamo sempre di provarlo prima in un ambiente di test, mi raccomando. Buon download, e se vi è stato utile un like è sempre gradito v1.0.5-ps_tanzopostepay-ps17.zip Changelog Older version DISCLAIMER THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF THE USE OR INABILITY TO USE THE SOFTWARE OR FROM OTHER DEALINGS IN THE SOFTWARE. DOWNLOADING AND INSTALLING THIS PRODUCT YOU ACCEPT THE TANZO ANALYSIS PROGRAM.
  22. 4 points
    Not really a module, but ... th title says all The CRON module is free and already available in PrestaShop Final Solution for PS 1.6 (not yet tested with 1.7) : Put this file : cron_database_backup.php -> in your admin folder, and then in your "CRON" module config, put one link like this : h t t p :/ / w w w . your_site . com / your_admin_folder / cron_database_backup.php?secure_key=your_key Tip : to find your key look at the other cron tasks Thanks to @NemoPS in this subject, to have putting me on the right way
  23. 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
  24. 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....
  25. 4 points
    Hi, In April of 2017 I wrote a guide on my blog: http://victor-rodenas.com/2017/04/23/crear-pagina-php-en-prestashop-1-7/ specify for Prestashop 1.7 ((It is written in Spanish, but with google translator you can translate the guide) Check if the guide is still working. PD: As you can see in the guide for Prestashop 1.7 with respect to Prestashop 1.6 to create a basic page, no big difference My english is very bad. Sorry for my English

Important Information

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