Search the Community

I have an old Presta shop e-shop Presta Shop™ 1.6.0.9 - What is the minimum PHP version for this? What is the minimum/maximum MySQL version for this? My VPS Server is old and needs to migrate to a new Alma Linux 8.x server.... min PHP 7.2... well...? For now, I just needed to make it work... later may consider changing/migrating to the new Presta Shop™ version... that is supported...

Bonjour à tous Je dois installer un module de paiement "Walle" et me demande d'installer le module "mailhook" . Ce que j'ai effectué. Lorsque je voulais l'activer, j'ai ce message : L'action enable est impossible pour le module mailhook. Impossible d'installer la surcharge : La méthode Send de la classe Mail est déjà surchargée par le module customnumber version 1.8.14 au 2023-02-27 16:48:01 . Vu que j'ai besoin aussi du module "customnumber" pouvez-vous m'aider dans la démarche à entreprendre pour que les 2 modules fonctionnent 😞 Merci d'avance de votre aide Stéphanie

Bonjour à tous, J'ai (encore) un problème surprenant sur PrestaShop 1.7 : lorsque je désactive le mode débug, je n'ai plus accès à mon backoffice... erreur 500. le front reste fonctionnel sans le moindre problème. Opérations effectuées : vider le cache smarty verification des droits dossiers et fichiers vide cache du navigateur test mozilla, google chrome et safari (on sait jamais) aucune erreur de remontée en mode débug... Ma configuration : PrestaShop 1.7.1.2 PHP 7.0, mariaDB chmod OK sur tous les fichiers / dossiers (755 et 644) serveur de dev ubuntu 16.04 local, pas le moindre problème sur es autres sites de dev : Wordpress, Joomla, Drupal et PrestaShop 1.6... Merci pour vos retours, Cordialement,

Hi Im trying to get PrestaShop 1.7.2.4 installed on server. But when I'm trying to access backend (admin) i see error 500 In PHP error logs i've got this: [06-Dec-2017 16:48:44 Europe/Warsaw] PHP Fatal error: Declaration of AdminDashboardControllerCore::setMedia() must be compatible with AdminControllerCore::setMedia($isNewTheme = false) in C:\pr77777.myfreespace.us\www\controllers\admin\AdminDashboardController.php on line 539 [06-Dec-2017 16:48:44 Europe/Warsaw] PHP Fatal error: Uncaught Symfony\Component\Debug\Exception\FatalErrorException: Compile Error: Declaration of AdminDashboardControllerCore::setMedia() must be compatible with AdminControllerCore::setMedia($isNewTheme = false) in C:\pr77777.myfreespace.us\www\controllers\admin\AdminDashboardController.php:539 Stack trace: #0 {main} Next LogicException: Request stack is empty in C:\pr77777.myfreespace.us\www\app\bootstrap.php.cache:3224 Stack trace: #0 [internal function]: Symfony\Component\HttpKernel\HttpKernel->terminateWithException(Object(Symfony\Component\Debug\Exception\FatalErrorException)) #1 C:\pr77777.myfreespace.us\www\vendor\symfony\symfony\src\Symfony\Component\Debug\ErrorHandler.php(606): call_user_func(Array, Object(Symfony\Component\Debug\Exception\FatalErrorException)) #2 C:\pr77777.myfreespace.us\www\vendor\symfony\symfony\src\Symfony\Component\Debug\ErrorHandler.php(668): Symfony\Component\Debug\ErrorHandler->handleException(Object(Symfony\Component\Debug\Exception\FatalErrorException), Array) #3 [internal in C:\pr77777.myfreespace.us\www\app\bootstrap.php.cache on line 3224 Do someone know how to fix this?

Hello community, I've been trying to install PrestaShop 1.7.8.3 locally on Mac OS for several hours with MAMP (PHP 7.4.21). The first steps of my install go smoothly until I get to the store install, where an error occurs 67% through the install. This error: "HTTP 500 - error -" My first instinct was to take a look in the apache logs but nothing appears there, the same for the PHP logs. I then searched on the net and I tried many things, change the PHP version, add the ps_facebook and ps_facebook1 modules to the blacklist, change the rights of my files /index.php and /install/index.php ( or my whole /install file), clear my browser cache, remove SSL and nothing changes. I have made sure to have all the prerequisites (available here) for a smooth installation, but unfortunately I have been looking for a solution for hours, without a concrete answer. I guess it could also be my host's MAMP configuration, but I'm not sure what could be the problem. I think downgrading might fix the problem, but I really want to stay on the most up-to-date version, has anyone come across this kind of problem before and was able to fix it of any kind? another way ? Thank you very much to those who help me

I received the following error when adding an item from a third-party page Fatal error: Uncaught PrestaShopException:Fatal error in /home/var/www/html/classes/Tools.php:1109 Stack trace: #0 /home/var/www/html/classes/Product.php(3153): ToolsCore::displayError() #1 /home/var/www/html/classes/Product.php(4748): ProductCore::getPriceStatic(17, false, 0, 6, NULL, false, true, 1) #2 /home/var/www/html/classes/Cart.php(811): ProductCore::getProductProperties(1, Array) #3 /home/var/www/html/classes/Cart.php(1456): CartCore->getProducts(true) #4 /home/var/www/html/art/tocms/PrestaShop.php(197): CartCore->updateQty(1, 195) #5 /home/var/www/html/part/index.php(187): require_once('/home/var/www/h...') #6 {main} thrown in /home/var/www/html/classes/Tools.php on line 1109

Hello, I am trying to add a Schema.php file in the head of Prestashop. the Schema.php file contains a if statement. basically when a certain URL is loaded then the schema is triggered. if( $_SERVER['REQUEST_URI'] == '/customizable-car.html' ) My knowledge of prestashop is quite frankly a bit dangerous and would appreciate it if someone could direct me to where I can import the schema.php file so that it does its function properly.

Buenas tardes, tengo un problema con la tienda online, la tengo alojada en 1&1 y me mandan actualizar el PHP pero me da un fallo la web en el proceso de compra, es un error 500 es muy amplio y no encuentro el fallo, ya actualicé prestashop y todos los módulos y me sigue dando el error, adjunto captura del error en modo debug a ver si alguien me puede ayudar. Muchas gracias de antemano y un saludo

Hi, my hostinh company send me a mail that I have to upgrade from PHP 5.6 to PHP7.2. After changing PHP version on server I received this Errors: Notice: tempnam(): file created in the system's temporary directory in /srv/www/vhosts/orbithandels.ch/httpdocs/classes/PrestaShopAutoload.php on line 151 Fatal error: Uncaught Error: [] operator not supported for strings in /srv/www/vhosts/orbithandels.ch/httpdocs/classes/db/DbQuery.php:70 Stack trace: #0 /srv/www/vhosts/orbithandels.ch/httpdocs/classes/ObjectModel.php(203): DbQueryCore->from('shop', 'a') #1 /srv/www/vhosts/orbithandels.ch/httpdocs/classes/shop/Shop.php(131): ObjectModelCore->__construct('1', NULL, NULL) #2 /srv/www/vhosts/orbithandels.ch/httpdocs/classes/shop/Shop.php(392): ShopCore->__construct('1') #3 /srv/www/vhosts/orbithandels.ch/httpdocs/config/config.inc.php(97): ShopCore::initialize() #4 /srv/www/vhosts/orbithandels.ch/httpdocs/index.php(27): require('/srv/www/vhosts...') #5 {main} thrown in /srv/www/vhosts/orbithandels.ch/httpdocs/classes/db/DbQuery.php on line 70 Is it possible to fix this and keep Prestashop version 1.6.0.9?

Bonjour La communauté! Je tourne sur la version prestashop 1.6.1.17 serveur ovh mutualisé offre performance. Je voudrais passer en php 7 mais si je passe en php 7 page blanche en F.O. En activant le mode debug voici l'erreur que j'ai: Fatal error: 'continue' not in the 'loop' or 'switch' context in /home/pearlacc/www/modules/leomanagewidgets/leomanagewidgets.php on line 1343 [PrestaShop] Fatal error in module file :/home/pearlacc/www/modules/leomanagewidgets/leomanagewidgets.php: 'continue' not in the 'loop' or 'switch' context Donc je vais voir dans dans le fichier en question la ligne en question et je trouve: if ($use_push && !$moduleInstance->allow_push) continue; Après je ne sais pas quoi faire pour corriger c'est là ou j'ai besoin de vous. Quelqu'un peut-il me guider sur la correction à mettre en place pour que ça fonctionne? Merci de votre aide par avance. Bien à vous Peggy. Mon site :www.pearlaccess.com

Bonjour, je viens de passer un site sous Prestashop 1.6.0.6 sur un nouvelle serveur avec une nouvelle version de php (php 7) , un collègue en a profité pour passer le site en 1.6.1.24. La plupart des erreurs de compatibilité avec php ont ensuite été corrigé mais un problème persiste, je ne peux pas voir mes catégories dans l'espace d'administration. Celles si sont pourtant bien présentes en front sur le site (mais aucun produit n'est dedans), les sous catégories ont par contre des produits mais pas tout ceux qu'ils sont sensé contenir (cela voudrait dire qu'elles existent pour l'admin mais je ne peux pas cliquer sur la catégorie parent pour vérifier vu que je ne les vois pas). Le serveur me renvoi les erreurs suivantes : count(): Parameter must be an array or an object that implements Countable in /html/classes/controller/AdminController.php on line 551PHP ($tabs mal défini ?) count(): Parameter must be an array or an object that implements Countable in /html/classes/controller/AdminController.php on line 3274 pathinfo() expects parameter 2 to be int, string given in html/cache/smarty/compile/[...]file.animation.tpl.php on line 67 je ne sais pas si c'est réellement le php AdminController qui est en cause ou si le problème pourrait venir d'avant. Serait il possible d'avoir une explication afin de savoir ce qui ne me permet pas de récupérer mes catégories s'il vous plait ? Merci Edit : Quand j'ajoute une catégorie, je vois temporairement mes catégories. Celles ci disparaissent à nouveau dès que j'actualise ma page, donc j'ai une autre confirmation que mes catégories sont bien là caché quelque part.

Bonjour à tous ! J'ai un multiboutiques 1.7.6 qui est hébergé sur un serveur dédié avec une version PHP 7.1 Pour le back office, j'utilise le même domaine qu'une boutique en front office. Mon problème est que lorsque j'effectue un processus en back (par exemple une sauvegarde d'un produit via domaine1.com), si j'essaye d'actualiser ce même domaine en front office en même temps, la boutique va attendre que le processus du back se termine pour afficher la page. Même chose si on essaye par exemple de modifier 2 produits en back en même temps, les processus ne se lancent pas en même temps. Le deuxième va attendre que le premier soit terminé pour s’exécuter. Et ça devient gênant lorsque l'on a une équipe de 3 à 4 personnes qui bosse en même temps sur le back. Est-ce un comportement normal ou cela vient-t'il de la configuration php du domaine en question ? Voici la configuration php du domaine : memory_limit = 512M max_input_time = 300 max_execution_time = 300 max_input_vars = 20000

Hi, I keep having this warning in the console for a Prestashop 1.6.1.24 on PHP 7.1: PHP Warning: Declaration of ModuleFrontControllerCore::setTemplate($template) should be compatible with FrontController::setTemplate($default_template, $layout = NULL) in /home/dgyhqty/public_html/classes/controller/ModuleFrontController.php on line 30 Does anyone know what it means? Thanks

Hi I wanted to upgrade one of the client sites manually from 1.6,0,5, May I know what is the best version of PrestaShop 1.6 that is no need to change on database can run smoothly in PHP 1.6 and MySql 5.6.45.? Also i've been looking for prestashop release notes for this versions its already 404 on this site. Thank you all. ML

Hi There, See anyone can give me hint I try to upgrade my PS 1.7.6.3 using PHP 7.2.27 instead of 7.1.33. I have TWO installations of PS 1.7.6.3 on same server. When I switched BOTH from PHP 7.2.27 instead of 7.1.33, ONE installation (FRESH installation) is working fine. Another (Cloned from production), EXCEPT BO->""Image settings", all others don't have error. In latter installation, AFTER switch to PHP 7.2.27, When clicking on BO->""Image settings", I got this error ""500 Internal Server Error". (NO error with same operation when in PHP 7.1.33) Oops! An Error Occurred The server returned a "500 Internal Server Error". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused. After I turned on DEBUG mode, I got this information. Thanks for any comments. David

tengo una tienda Prestashop 1.7.5.0 corriendo en un servidor ubuntu 18.04 con php 7.2.21. El tema instalado es transformer theme y tengo el módulo JA Marketplace. El problema pasa al iniciar sesion con la cuenta de algunos vendedores y quiero entrar al apartado "mi cuenta". Cuando miro en las herramientas del navegador, en la pestaña network veo que hay un error 500 y en el html no está center-column, por esto no aparece el dashboard. Cuando ingreso a mi cuenta con otros perfiles no me salta este error. (1/1) FatalThrowableError Call to a member function getModuleLink() on string in 45bf78bef573835f2b9e70d2e24a2d6ba017c514_2.file.customer-account.tpl.php line 44 at content_5da0b584f30d11_36364393(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render(false, 0) in smarty_internal_templatebase.php line 232 at Smarty_Internal_TemplateBase->_execute(object(SmartyDevTemplate), null, null, null, 0) in smarty_internal_templatebase.php line 116 at Smarty_Internal_TemplateBase->fetch(null, null, null, null, false, true, false) in SmartyDevTemplate.php line 40 at SmartyDevTemplateCore->fetch() in Module.php line 2375 at ModuleCore->display('/var/www/html/clonatu/modules/jmarketplace/jmarketplace.php', 'customer-account.tpl') in jmarketplace.php line 4688 at Jmarketplace->hookDisplayCustomerAccount(array('smarty' => object(SmartyDevTemplate), 'cookie' => object(Cookie), 'cart' => object(Cart), 'altern' => 5)) in Hook.php line 966 at HookCore::coreCallHook(object(Jmarketplace), 'hookdisplayCustomeraccount', array('smarty' => object(SmartyDevTemplate), 'cookie' => object(Cookie), 'cart' => object(Cart), 'altern' => 5)) in Hook.php line 351 at HookCore::callHookOn(object(Jmarketplace), 'displayCustomeraccount', array('smarty' => object(SmartyDevTemplate), 'cookie' => object(Cookie), 'cart' => object(Cart), 'altern' => 5)) in Hook.php line 903 at HookCore::exec('displayCustomeraccount', array('smarty' => object(SmartyDevTemplate), 'cookie' => object(Cookie), 'cart' => object(Cart), 'altern' => 5), null) in smarty.config.inc.php line 165 at smartyHook(array('h' => 'displayCustomeraccount'), object(SmartyDevTemplate)) in SmartyLazyRegister.php line 83 at SmartyLazyRegister->__call('smartyHook', array(array('h' => 'displayCustomeraccount'), object(SmartyDevTemplate))) in ce1448e09011f92c4d9007957728557cc2d67538_2.file.my-account-items.tpl.php line 124 at Block_18378154415da0b584f15439_77278100->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_18378154415da0b584f15439_77278100), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_18378154415da0b584f15439_77278100)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_18378154415da0b584f15439_77278100', 'display_customer_account') in ce1448e09011f92c4d9007957728557cc2d67538_2.file.my-account-items.tpl.php line 110 at content_5da0b584f15da2_66923757(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('file:customer/_partials/my-account-items.tpl', null, 'layouts/layout-full-width.tpl', 0, 31536000, array(), 0, false) in 478b32d5af2779b9a5a0c23aeda8ea7f70addca9_2.file.my-account-nav.tpl.php line 27 at content_5da0b584f08ef8_21973048(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('file:customer/_partials/my-account-nav.tpl', null, 'layouts/layout-full-width.tpl', 0, 31536000, array(), 0, false) in 6c651f57a36328209358a234e9b65b082a40d2d8_2.file.page.tpl.php line 67 at Block_18323052835da0b584ec65f1_72722871->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_18323052835da0b584ec65f1_72722871), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_18323052835da0b584ec65f1_72722871)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_18323052835da0b584ec65f1_72722871', 'account_links', 1) in 6c651f57a36328209358a234e9b65b082a40d2d8_2.file.page.tpl.php line 157 at Block_5404975585da0b584ec6209_47399254->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_5404975585da0b584ec6209_47399254), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_5404975585da0b584ec6209_47399254), object(Block_6141945465da0b3d109ee35_67146184)) in smarty_internal_runtime_inheritance.php line 186 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_6141945465da0b3d109ee35_67146184)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_6141945465da0b3d109ee35_67146184', 'page_content_container', 2) in a7c3a6982b7458bd6b1144ffccd11abce98fcdda_2.file.page.tpl.php line 180 at Block_18148596095da0b3d109db11_32252350->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_18148596095da0b3d109db11_32252350), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_18148596095da0b3d109db11_32252350), object(Block_3386506195da0b3d10a5211_65849910)) in smarty_internal_runtime_inheritance.php line 186 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_3386506195da0b3d10a5211_65849910)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_3386506195da0b3d10a5211_65849910', 'content', 3) in 7f3cfbb48cc2ab003dbfe8915cdd376ed38e496e_2.file.layout-full-width.tpl.php line 133 at Block_3487330155da0b3d10a4e41_76192596->callBlock(object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_3487330155da0b3d10a4e41_76192596), object(SmartyDevTemplate)) in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_3487330155da0b3d10a4e41_76192596), object(Block_14838189935da0b3d10c9498_87000707)) in smarty_internal_runtime_inheritance.php line 186 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyDevTemplate), object(Block_14838189935da0b3d10c9498_87000707)) in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyDevTemplate), 'Block_14838189935da0b3d10c9498_87000707', 'content_wrapper') in acbd29a530c1c0849cd06b6900697394f92158cc_2.file.layout-both-columns.tpl.php line 118 at content_5da0b3d10da2c5_68405630(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('layouts/layout-both-columns.tpl', null, 'layouts/layout-full-width.tpl', 0, 31536000, array(), 2, false, null, null) in smarty_internal_runtime_inheritance.php line 125 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyDevTemplate), 'layouts/layout-both-columns.tpl') in 7f3cfbb48cc2ab003dbfe8915cdd376ed38e496e_2.file.layout-full-width.tpl.php line 50 at content_5da0b3d10a5795_06095531(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('layouts/layout-full-width.tpl', null, 'layouts/layout-full-width.tpl', 0, 31536000, array(), 2, false, null, null) in smarty_internal_runtime_inheritance.php line 125 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyDevTemplate), 'layouts/layout-full-width.tpl') in a7c3a6982b7458bd6b1144ffccd11abce98fcdda_2.file.page.tpl.php line 33 at content_5da0b3d10a0e22_51272441(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('page.tpl', null, 'layouts/layout-full-width.tpl', 0, 31536000, array(), 2, false, null, null) in smarty_internal_runtime_inheritance.php line 125 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyDevTemplate), 'page.tpl') in 6c651f57a36328209358a234e9b65b082a40d2d8_2.file.page.tpl.php line 46 at content_5da0b584ec9488_48174012(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render() in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('customer/page.tpl', null, 'layouts/layout-full-width.tpl', 0, 31536000, array(), 2, false, null, null) in smarty_internal_runtime_inheritance.php line 125 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyDevTemplate), 'customer/page.tpl') in 8c798f26ec12500bf4f26aafc94e6bfecbcf2d71_2.file.my-account.tpl.php line 46 at content_5da0b584ec27c4_74972557(object(SmartyDevTemplate)) in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyDevTemplate)) in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyDevTemplate)) in smarty_internal_template.php line 216 at Smarty_Internal_Template->render(false, 0) in smarty_internal_templatebase.php line 232 at Smarty_Internal_TemplateBase->_execute(object(SmartyDevTemplate), null, 'layouts/layout-full-width.tpl', null, 0) in smarty_internal_templatebase.php line 116 at Smarty_Internal_TemplateBase->fetch('customer/my-account.tpl', null, 'layouts/layout-full-width.tpl', null, false, true, false) in SmartyDev.php line 40 at SmartyDev->fetch('customer/my-account.tpl', null, 'layouts/layout-full-width.tpl') in FrontController.php line 682 at FrontControllerCore->smartyOutputContent('customer/my-account.tpl') in FrontController.php line 666 at FrontControllerCore->display() in Controller.php line 301 at ControllerCore->run() in Dispatcher.php line 509 at DispatcherCore->dispatch() in index.php line 28 He borrado la carpeta var/cache y no cambio nada

Hi, I have the following problem, the prestashop error_log is registering the following message: [13-Nov-2019 22:17:09 America / Santiago] PHP Warning: htmlspecialchars () expects parameter 1 to be string, array given in /home1/lepetito/public_html/site.cl/var/cache/prod/smarty/ compile / layouts_layout_left_column_tpl / 9c / e8 / bd / 9ce8bdd6b78f26915aee31f998ca407a3ad3f2c8_2.file.product.tpl.php on line 329 Prestashop 1.7.5.2 PHP 7.0 Someone could help me find the cause. Thank you so much.

Hi, I keep having this warning in the console for a Prestashop 1.6.1.24 on PHP 7.1: PHP Warning: Declaration of ModuleFrontControllerCore::setTemplate($template) should be compatible with FrontController::setTemplate($default_template, $layout = NULL) in /home/dgyhqty/public_html/classes/controller/ModuleFrontController.php on line 30 Does anyone know what it means? Thanks

Bonjour, Après un upgrade de mon serveur pour pouvoir passer en HTTP/2, mon Prestashop 1.6.1.9 fonctionne mais j'ai encore quelques erreurs étranges et je ne trouve pas de solution. Dans le BO, lorsque je clique sur Paiement j'ai une page blanche 500, dans les logs j'ai : (22)Invalid argument: [client xx.xx.xx.xx:48366] mod_fcgid: ap_pass_brigade failed in handle_request_ipc function, referer: https://www.xxxxx.com Récemment j'ai voulu utiliser le module navigation à facettes (blocklayered), mais lorsque je clique sur Configurer, j'ai cette erreur : Serveur sous Apache, version de PHP 7.0.33-0 Je pense que ces erreurs sont dûes à PHP7 qui ne doit pas être complètement compatible avec ma version de PS1.6, mais est-il possible de les résoudre ?

Hola, tengo un prestashop 1.7.3.1 funcionando con php 5. Cuando lo paso a php 7.1, la tienda y back office siguen funcionando. Pero cuando quiero crear o actualizar un producto, el backoffice me muestra un mensaje de error avisándome de que el proceso no ha podido realizarse, quedando el botón de "salvar" girando constantemente. Pero en realidad sí se guarda el producto. Si salgo del producto y vuelvo a entrar veo que los cambios han sido almacenados. Pero si quiero asignarle combinaciones, estas no se generan, me vuelve a dar el error de fallo de actualización y el producto vuelve a aparecer sin combinaciones. En modo debug no muestra ningún error en pantalla. En php 5 también me muestra algunas veces el mensaje de error de actualización pero si guarda la configuración del producto ya sea simple o con combinaciones. La configuración actual de la tienda es: php: 5.6.4 memoroy limit: 512M max execution time: 7200 Upload max file size: 200M

el apache me genera este log [Wed Mar 07 14:36:47.354629 2018] [php7:warn] [pid 4787] [client 186.94.136.7:28347] PHP Warning: require(/var/www/html/gutierrezc.com.ve/delcuraproducts/app/../vendor/autoload.php): failed to open stream: No such file or directory in /var/www/html/gutierrezc.com.ve/delcuraproducts/app/autoload.php on line 34, referer: https://gutierrezc.com.ve/delcuraproducts/ [Wed Mar 07 14:36:47.354831 2018] [php7:error] [pid 4787] [client 186.94.136.7:28347] PHP Fatal error: require(): Failed opening required '/var/www/html/gutierrezc.com.ve/delcuraproducts/app/../vendor/autoload.php' (include_path='.:/usr/share/php') in /var/www/html/gutierrezc.com.ve/delcuraproducts/app/autoload.php on line 34, referer: https://gutierrezc.com.ve/delcuraproducts/ Al darle al navegador aparece la tipica imagen loading y al llegar al 100% refresca y se queda en blanco...

Hi, I've recently updated the PHP version of my host to 7.1. Everything went fine except my prestashop installation. I'm using prestashop 1.6, and the below message is shown in the error log: PHP Fatal error: Uncaught Error: [] operator not supported for strings in C:\\prestashop\\classes\\db\\DbQuery.php:70\nStack trace:\n#0 C:\\prestashop\\classes\\ObjectModel.php(203): DbQueryCore->from('shop', 'a')\n#1 C:\\prestashop\\classes\\shop\\Shop.php(131): ObjectModelCore->__construct('1', NULL, NULL)\n#2 C:\\prestashop\\classes\\shop\\Shop.php(392): ShopCore->__construct('1')\n#3 C:\\prestashop\\config\\config.inc.php(97): ShopCore::initialize()\n#4 C:\\prestashop\\index.php(27): require('C:\\\\prestashop\\\\m...')\n#5 {main}\n thrown in C:\\prestashop\\classes\\db\\DbQuery.php on line 70 It appears that prestashop is trying to append an array item to a string in its core files. Is there any solution to this problem? I'm on windows server 2008 R2, running PHP 7.1, MySQL 5.7, and Apache 2.4 Thanks are in orders.

Hallöchen allerseits! Hab gestern die 1.7.2.4 runtergaladen und installiert (NOCH! unter PHP5.6), und heute den ganzen Vormittag hier im Forum verbracht, um die zahllosen Beiträge mit Problemen bei den Spracheinstellungen unter die Lupe zu nehmen. Leider ergebnislos: Ich habe sämtliche Tipps ausprobiert, die hier so empfohlen wurden - der Shop mischt im Frontend Deutsch und Englisch nach belieben; das BO bleibt stur auf englisch. Leider habe ich aus diversen Beiträgen auch herausgelesen, dass PrestaShop in der 1.7.x offenbar noch weit von "stable" entfernt ist (deshalb vielleicht auch das Sprach-Kuddelmuddel), und von "rechtssicher" sowieso. Ernsthaft jetzt: Ich hatte in diversen Foren/Websites etc. nach einem Ersatz für unseren (hoch modifizierten/gepatchten) XT:C 3.04 gesucht, und Presta erschien mir dafür am besten geeignet. Weil: Im Gegensatz zu einigen bekannteren Namen, die auch als CommunityEdition zur Verfügung stehen, soll Presta schon unter PHP7 laufen! Genau das ist der Knackpunkt, denn HostEurope stellt in einigen Monaten gnadenlos auf PHP7 um - und bis dahin muss ich den alten XT:C komplett migriert haben. Nun habe ich in einigen Beiträgen hier aber auch mitbekommen, dass PS wohl doch schon ab 1.6.x(?) PHP7 kompatibel sein soll; und dafür gibt es dann vermutlich auch die entsprechenden "Rechtssicherheitspakete"!? Was tun: Lohnt sich der Versuch, das frisch installierte 1.7.2.4 ans laufen zu bringen (wenn ja, WIE???) - oder besser gleich wieder löschen und eine 1.6.xx (welche?) aufspielen? Und wenn 1.6, wie sieht es da mit dem Support aus (speziell Sicherheitspatches)? Es wäre echt toll, wenn mich da jemand mal mit ein, zwei kurzen Sätzen in die richtige Richtung schubsen könnte. ;-) Gruß aus Berlin Belushi

Guys, How can I enable my PS 1.6.1.17 site to work with php7. Currently running under php 5.6, however, other products that I need to run on my hosting site require php7. I would like to get all of my hosted software running under php7. I am getting the Error 500 when I switch my site to php 7.0.22. Thanks, Art

Hi, I have installed clean three times now and am having the same issue each time; the admin folder isn't being renamed during the install process, and therefore my back office doesn't load. The shop with demo data IS loading, so I know the install was ok for that. Since I also had a couple of PHP warnings during the install, I wonder if this is related to the fact that the version of PHP on my host server is PHPv7. Can anyone confirm the PHP version compatible with the latest version of Prestashop and if not v7, are there any updates on when it might be compatible? I can't go back to an earlier version of PHP as my host will only give me the option of v5.6 but will charge me for support, since it's no longer current, and my new install of Wordpress also needs v7. TIA for any and all help or pointers. Kath