Leaderboard
Popular Content
Showing content with the highest reputation on 01/19/2019 in all areas
-
Hi everybody. Recently, I decided to record a series of video tutorials aimed to help who knows little about Prestashop in the process of learning and (hopefully) in the end mastering the software. I hope this series will come in handy to anybody who just discovered the software, and also to who wants to learn more about it. In this topic, I'll be posting new links as new lessons are published. Use this thread as reference to know which one is the latest All lessons (last updated May 23, 2013) Day 1 – Introducing and installing Prestashop Day 2 – Basic Prestashop Configuration Day 3 - Prestashop categories and products Day 4 - Prestashop Attributes Combinations Day 5 - Prestashop Upgrade Day 6 - Prestashop Modules Day 7 - Prestashop Shipping, Zones and Countries Day 8 - Prestashop Payments, Currencies and Taxes Day 9 - Order Management Day 10 - Prestashop Customers Day 11 - Prestashop Discounts (Cart rules) Day 12 - Prestashop Themes and visual Tweaks Day 13 – Prestashop CMS Day 14 - Prestashop SEO and Preferences Day 15 - Prestashop Multistore Day 16 - Employees and Languages Cheers!1 point
-
High quality theme, paid for, is in use (not default). The developer was extremely helpful with solving some bits and pieces that I wanted to display differently - this is a theme purchased through Prestashop.com1 point
-
Thanks for all the advice (both of you) I installed your module. Reports: max execution time (local) 0 and (master) 50000 I ought to stress that this is whatever was set by default, either through Prestashop or a module that has modified it, or by the 1&1 settings (I assume the latter) Your plan of preparing a new install then importing customers etc, is exactly what I am doing. The old 1.6 shop is running still; the new one in 1.7 is very nearly ready to make active. Customers are imported already (but I will top up as the new shop goes live); new modules installed, everything running fine. I just thought to update to 1.7.5 before finishing (this version having come out since I started).1 point
-
Please delete this it is full of private details!!!!1 point
-
nniaga, again? you cannot suggest 'try' as you should know or at least have tried it yourself...you seem very lazy to me and are here just to get your post count up?...so you don't know don't reply...community help is not about vague guessing. we talked about this already yes? So if you continue I'll just report you and you can take a timeout...but I"m tired of you wasting community time with your 'guessing' and vague responses. got it? Storm....a little 'google' search we see there are existing modules that might help you accomplish https://addons.prestashop.com/en/search?search_query=products by group I do not have experience but here is example from that search https://addons.prestashop.com/en/customer-administration/27401-product-visible-to-customer-groups.html maybe you find one on addon's, but you can also look for 3rd party module solutions, i.e. off adddons1 point
-
here is generic upgrade project that has little to NO production downtime when we do upgrades, we do it on a copy of production and when ready we replace production with new copy and import out of sync customers/orders..there may be more depending on your shop.... === checklist .doc'ing identify all 3rd party modules and obtain their 1.7 compatible zips identify core changes (mentioned above), you should also identify template changes (.tpl's). .doc existing overrides select new feature rich theme, we like Leo themes but there are lots of others review existing hosting, most age just like your shop. it's best to get new hosting account and move to that rather than try to have old hosting upgraded === pre upgrade build a test copy of your production shop, then back this up so you can refresh your test system until upgrade completes. hopefully your hosting allows php level by domain/subdomain so you start out with php7.2. if not find new hosting. uninstall 3rd party modules make sure overrides clean up php max execution time to 'large', 600 or 1200... === upgrade back up this test system so you can restore if upgrade fails so you do not have to uninstall moudule/override again perform upgrade install/configure modules apply core changes install configure theme ===shake and bake until prod ready == Production installation create a new copy of production to be used for historical purposes import customers/orders from old shop to new shop copy new shop to production or if new hosting (recommended) switch dns happy upgrading el1 point
-
Moi j'avoue je commence à en avoir marre d'essayer de comprendre et ou d'interpréter ce que les gens veulent demander. Je lis: j'ai configuré les restrictions (déjà ça doit être des groupes d'agence d'intelligence , mossad, cia, mi16, car il ne divulgue pas lesquels) ça marche en mobile safari (connecté? non connecté? quel groupe - ah oui j'oubliais c'est secret) et sur pc j'ai pas trop compris c'est pas de soucis ou des soucis Pour conclure, la restriction de moyen de paiement par groupe client marche très bien depuis toujours, et ce quelque soit les versions, donc si problème rencontré, encore faudrait-il expliquer son use case, la méthode utilisé, et là ou pourra aider... car quitte à partir dans les interprétations, je préfère envisager que ça viendrait des électrons recyclés1 point
-
Never be hasty... make sure you backup of the mysql and all files as both together are the shop 🙂 In your hosting account you should have phpmyadmin, [depending with who you host and your control panel] change a field properties is scary first time, but when you have done it a few times its OK, but again be relaxed and double check before you press enter. Adminer is a great tool to do this if your hosting has not phpmyadmin, it's free and very reliable! In the logs you also see folders missing, just create them then they are there for next update. But you must check you are using PHP v7.2 and check other required settings, you can do that with a script found here upload it in your hosting account and browse to it, it will give you a check if the environment is perfect for the shop, this is very important and avoid errors in future upgrades. Let me know if this helps. www.yourdomain/psphppinfo.php psphpinfo.php1 point
-
Bonjour, Si on regarde la stack que vous avez indiqué, la ligne 3 dit: /htdocs/vendor/symfony/symfony/src/Symfony/Component/Translation/Loader/XliffFileLoader.php(42): Symfony\Component\Translation\Loader\XliffFileLoader->extract(Object(Symfony\Component\Finder\SplFileInfo), Object(Symfony\Component\Translation\MessageCatalogue), 'ShopThemeGlobal') #3 On dirait donc que l'erreur vient du catalogue de traduction "ShopThemeGlobal". Les traductions de PS 1.7 sont dans app/Resources/translations, regardez les fichiers appelés ShopThemeGlobal (il y en a plusieurs, un par langue).1 point
-
Vous avez un BOM (Byte Order Markup) en début d'un fichier qui a du être édité avec un logiciel Windows type BlocNote ou NotePad. Utilsez NotePad++ uniquement en mode "UTF8 - Sans BOM" et réenregistrez votre fichier1 point
-
In welchem EU-Land sind denn deutsche Shops, die eine Reorder-Funktion anbieten, nicht erlaubt? Ich hatte noch nie eine Veranlassung gesehen, den Schalter auf NEIN zu stellen. Auch in allen großen Shops wie z.B. Amazon oder in anderen Shopsystemen gibt es eine Nachbestellen-Funktion. Es ist einfach praktisch für die Kunden.1 point
-
attention, le TF/CF n'est qu'un indicateur, pas une mesure de performances SEO. J'ai des sites avec un TF > 40 qui sont mal positionnés et d'autres avec un TF quasi nul qui sont en TOP 3 sur des requêtes phares (plus de 8000 recherches mensuelles). C'est une des bases SEO oui. La question reste encore de savoir ce qu'on entend par "optimisé". Tout comme ma remarque ci-dessus, à lui-seul, le thème optimisé ne permettra pas à ton site de se positionner correctement.1 point
-
yes I did it. I found reason. I had unchecked "automatic compilation after change" thank you1 point
-
OK, I found 32 files with the umask(0000) I will replace them with umask(0022). Hope that is enough.1 point
-
Aggiungi, solitamente dopo il contenitore {$product.name}, il codice sotto. esempio Scheda prodotto (/themes/classic/templates/catalog/product.tpl) e Carrello (themes/classic/templates/checkout/_partials/cart-detailed-product-line.tpl)1 point
-
https://devdocs.prestashop.com/1.7/themes/reference/templates/head/ http://doc.prestashop.com/display/PS17/SEO+and+URLs http://build.prestashop.com/news/prestashop-1-7-5-0-available/1 point
-
en el css de las imagenes tienes un "max-width: 500%;" eso deberái de ser "100%" y en el td que contiene cada imagen tienes un "padding-left:30px" ,y debería de ser "padding: 0px"1 point
-
1 point
-
1 point