Search the Community

i activated debug mode and I send submit order request and create cart request but i can't get Webservice API request information in the Symfony Profiler, only to find back end request such as /administration/index.php/configure/advanced/performance instead. I am not the merchant but i have to send request to merchant's REST api to get information or submit order. i have to solve internal server error 500 problem when i send submit order request to REST api.So i will be very thankful if you can tell me more details about where to check error logs. thank you in advance

Hi everyone ! I could use some help. I'm using Prestashop 1.7.7.7, and since a few weeks, I'm experiencing a really slow back office (10 to 20seconds between pages). I have no issues with the front office. I upgraded to a faster server (doubled the CPU/RAM), but nothing changed. Trying to know which module or hook could be responsible for this slowness, I enabled debug mode to have timings on the request. And in debug mode, the back office is super fast. I don't have the same issue at all. I already tried to clear the 'prod' and 'dev' cache, my smarty recompilation settings are on "never recompile". I'm a bit clueless right now, do you have an idea what could case such a difference between debug and prod modes ? My first idea was to enable debug mode as it enables performance monitoring using Symfony, but as I said, debug mode seems to "solve the issue"... It is obvious that I just can't let the shop in debug mode while in production, so I must find the real issue. Do you have ideas for me to dig deeper ? Thanks a lot 😄

Hello, I need your help please! 😞 In the debog mode I see the following error (while trying to open in BO the "Module management" or "Paiement Module" for instance): Compile Error: Declaration of Mobile_Theme::disable() must be compatible with ModuleCore::disable($force_all = false) The fatal error seems to be located in modules/mobile_theme/mobile_theme.php (line 400) * When disabling the module, we need to edit the settings to also disable the theme swtich. * When enabling it, the settings will be rewritten automatically with the performances system. * */ public function disable() { Configuration::updateValue('PS_MOBILE_MODULE_ENABLED', 0); $this->editSettings(false); return parent::disable(); } => What should I do now? How can I fix it? In the normal mode I see the famous "500 Internal Server error"... I tried to contact the technical service of Prestashop Marketplace for a week but nobody replies. Thank you in advance for any kind of advice. Best, Julienne

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,

Hola a todos, acabo de actualizar el prestashop a la última versión pero me sale este error 500 y no me queda claro qué hacer

Hello everyone, i need some help please. So i initially created a backup of my website to copy my site and create one test environnement etcc ... in another domain i had many error but finally it works but only in debug mode when i disable it it gives me a blank page with nothing, also when it works in debug mode the back office works good but the page of module configuration does not work and gives me I don't really know how to fix it :/

Salve, come purtroppo capita di consueto, durante un'ennesima migrazione da un PS 1.6 ad una nuova installazione 1.7(.8.7), qualcosa deve essere andato storto. Non mi fa accedere ai moduli se non in debug, l'errore è questo (scusate per le censure ma è il sito di un cliente): Compile Error: require_once(): Failed opening required '/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/home/modules/statsforecast/statsforecast.php' (include_path='/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/pear_exception:/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/console_getopt:/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/pear-core-minimal/src:/var/www/vhosts/M24243-publi.linp047.arubabusiness.it/XXX.it/vendor/pear/archive_tar:.:/opt/plesk/php/7.4/share/pear') [Symfony\Component\Debug\Exception\FatalErrorException 0] Andando per tantivi, ho provato ad eludere la cartella del modulo in FTP indicato nella prima riga del log, ma me ne mostra sempre un altro, sono arrivato ad eludere circa dieci moduli quindi penso che il problema sia legato a PS in sè; ho provato a cambiare versioni del PHP ma è sempre uguale; ho provato a pulire cache sia automaticamente che manualmente; ho provato ad aggiornare tutti i moduli che mi segnalava da aggiornare giusto per; Vedo che il problema riguarda la cartella /vendor/pear/ ma non capisco il motivo. Aggiungo che la migrazione era stata fatta in una sottocartella temporanea, poi ho sposato tutti i file nella root e adattato il db (rimuovendo tutte le stringe che richiamavano la vecchia cartella). Se attivo il debug funziona correttamente; il resto dell'admin ed il front funziona correttamente. Se qualcuno sa indicarmi ringrazio in anticipo

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; Edit: Debug mode on PrestaShop 8.0 PrestaShop Dashboard > Advanced Parameters > Performance > DEBUG MODE PANEL > Set it to YES Debug mode on PrestaShop 1.7 PrestaShop Dashboard > Advanced Parameters > Performance > DEBUG MODE PANEL > Set it to YES 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 Debug mode on PrestaShop 1.5.3 to 1.6 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. Debug mode for Admin or specific IPs Because Debug mode should not be visible for your customers here's a smart solution that allows you to enable it only for admins or for some provided IPs. This way your shop will not be vulnerable while you debug.

Hi, I was having issue with a payment gateway module so I tried installing an older version of it while the new one was on the website. It created more issues, and so I deleted the folders from /modules to get rid of it as I was unable to access my backend anymore. Now, the module is still showing in my modules page and I can still configure it. I am getting "Cannot uninstall module (MODULENAME). The module is not installed." when I try to uninstall from back end. How do I completely get rid of it? Edit: in debug mode the following was shown - "Exception thrown by module (MODULENAME) on uninstall. Table 'DBNAME.ps_MODULENAME' doesn't exist"

Buongiorno, come da oggetto visualizzo molti errori con debug attivo. Vi allego gli errori che visualizzo e le informazioni del server + un'altro errore. Come posso risolvere? Grazie a chi mi aiuterà.

Hello everyone: I am having an error when I access the modules section in the prestashop control panel. When I do so, I get the following message: Compile Error: require_once(): Failed opening required '/home/###/public_html/"OLD FOLDER USED FOR WEB DEVELOPMENT"/modules/statsbestcategories/statsbestcategories.php' (include_path='/home/###/public_html/###.com/vendor/pear/pear_exception:/home/###/public_html/###.com/vendor/pear/console_getopt:/home/###/public_html/###. com/vendor/pear/pear-core-minimal/src:/home/###/public_html/###.com/vendor/pear/archive_tar:.:/opt/cpanel/ea-php74/root/usr/share/pear') [Symfony\Component\DebugException\FatalErrorException 0] I can access the modules, delete and install, but it forces me to do it with debug mode. So far what I have done is: 1) Deleted and re-installed the module referenced in the first line, but I still get the error pointing to the path where I had the website before. 2) Deleted the files in the "dev" and "prod" folders in the var/cache directory. ---- I don't know if it's related, but in Advanced Settings > Information, I see that the following files are missing: var/.htaccess var/bootstrap.php.cache var/SymfonyRequirements.php --- If you've made it this far, thank you very much. If you know how to solve this error, please let me know. Regards

Hola a todos: Estoy teniendo un error cuando accedo al apartado de módulos en el panel de control de prestashop. Cuando lo hago, me aparece el siguiente mensaje: Compile Error: require_once(): Failed opening required '/home/###/public_html/"ANTIGUA CARPETA USADA PARA EL DESARROLLO DE LA WEB"/modules/statsbestcategories/statsbestcategories.php' (include_path='/home/###/public_html/###.com/vendor/pear/pear_exception:/home/###/public_html/###.com/vendor/pear/console_getopt:/home/###/public_html/###.com/vendor/pear/pear-core-minimal/src:/home/###/public_html/###.com/vendor/pear/archive_tar:.:/opt/cpanel/ea-php74/root/usr/share/pear') [Symfony\Component\Debug\Exception\FatalErrorException 0] Puedo acceder a los módulos, borrar e instalar, pero me obliga a hacerlo con modo de depuración. Hasta el momento lo que he hecho ha sido: 1) Borrado e instalado de nuevo el módulo al que hace referencia en la primera línea, pero sigue apareciendo el error apuntando hacia la ruta donde tenía la web antes. 2) Borrado los archivos de las carpeta "dev" y "prod" del directorio var/cache ---- No sé si estará relacionado, pero Parámetros Avanzados > Información, me aparece que faltan los siguientes archivos: var/.htaccess var/bootstrap.php.cache var/SymfonyRequirements.php --- Si has llegado hasta aquí, muchas gracias. Si sabes por donde pueden ir los tiros para resolver este error, dime, por favor. Saludos ---- Hello everyone: I am having an error when I access the modules section in the prestashop control panel. When I do so, I get the following message: Compile Error: require_once(): Failed opening required '/home/###/public_html/"OLD FOLDER USED FOR WEB DEVELOPMENT"/modules/statsbestcategories/statsbestcategories.php' (include_path='/home/###/public_html/###.com/vendor/pear/pear_exception:/home/###/public_html/###.com/vendor/pear/console_getopt:/home/###/public_html/###. com/vendor/pear/pear-core-minimal/src:/home/###/public_html/###.com/vendor/pear/archive_tar:.:/opt/cpanel/ea-php74/root/usr/share/pear') [Symfony\Component\DebugException\FatalErrorException 0] I can access the modules, delete and install, but it forces me to do it with debug mode. So far what I have done is: 1) Deleted and re-installed the module referenced in the first line, but I still get the error pointing to the path where I had the website before. 2) Deleted the files in the "dev" and "prod" folders in the var/cache directory. ---- I don't know if it's related, but in Advanced Settings > Information, I see that the following files are missing: var/.htaccess var/bootstrap.php.cache var/SymfonyRequirements.php --- If you've made it this far, thank you very much. If you know how to solve this error, please let me know. Regards

Hi, I have just installed prestashop 1.7.6.7 on the latest xampp server which is running PHP 7.2. My installation was succesful and I had no issues accessing both the front page and back office. However, I started experiencing a problem when trying to acces the back office, it will only show a blank page. I thought this was due to an error so I decided to switch into developer mode to see if there will be any debug info. Therefore I modified the defines.inc.php file by changing define('_PS_MODE_DEV_', false) to define('_PS_MODE_DEV_', true) When I refresh the back office admin login page, it loads without problems and presents me with the login form etc. If I reset _PS_MODE_DEV_ to its initial value of 'false', the back office immediately goes blank and cannot be loaded again. Has anyone observed this before? Any help will be appreciated. Thanks.

Bonjour, j’ai un soucis sur PS 1.7 avec une version php 7.3 que je ne peux pas changer. Le mode debug a été activé et cela m’affiche le message suivant : Fatal error: Uncaught Error: Cannot access protected property Shop::$id_shop in /homepages/38/d875055532/htdocs/Web/src/Adapter/EntityMapper.php:100 Stack trace: #0 /homepages/38/d875055532/htdocs/Web/classes/ObjectModel.php(264): PrestaShop\PrestaShop\Adapter\EntityMapper->load(‘1’, NULL, Object(Shop), Array, NULL, true) #1 /homepages/38/d875055532/htdocs/Web/classes/shop/Shop.php(128): ObjectModelCore->__construct(‘1’, NULL, NULL) #2 /homepages/38/d875055532/htdocs/Web/classes/shop/Shop.php(411): ShopCore->__construct(‘1’) #3 /homepages/38/d875055532/htdocs/Web/config/config.inc.php(118): ShopCore::initialize() #4 /homepages/38/d875055532/htdocs/Web/index.php(27): require(‘/homepages/38/d…’) #5 {main} thrown in /homepages/38/d875055532/htdocs/Web/src/Adapter/EntityMapper.php on line 100 J’ai déjà essayé de le désactiver sur define.inc.php avec la mention ‘false’ et ‘off’. Si vous pouviez m’aider ça serait super !

Ciao a tutti, Sto aggiornando in sandbox una copia del mio sito web prestashop live in MAMP (gratuito) seguendo questa iterazione: - il mio sito web è su 1.6.1.3 - Eseguo un aggiornamento da 1.6.1.3 a 1.6.1.24 con modulo aggiornamento in 1 clic e tutto va liscio, quindi cambio in MAMP il php da 5.6.40 a 7.1.33 e proseguo la disinstallazione e l'eliminazione (in questo ordine) di tutti i moduli e temi non nativi eccetto revws e payplug - Installo, in una diversa directory di htdocs e in un diverso database, un prestashop 1.6.1.24 e copio manualmente al suo interno i moduli revws e payplug, la cartella img e il file di impostazione - Cancello la directory 1.6.1.3 aggiornata a 1.6.1.24 e il database della nuova appena effettuata installazione 1.6.1.24 e collego, per mezzo di una copia del file settings, la directory prestashop 1.6.1.24 di questa nuova installazione al database dell'installazione 1.6.1.3 aggiornato a 1.6.1.24 e modifico la directory della nuova installazione 1.6.1.24 affinché combaci con quella originariamente aggiornata e che ora è stata cancellata - Quindi mi ritrovo con una nuova installazione di prestashop collegata al mio precedente database storico completo - In tutto questo processo ho mantenuto i moduli non nativi e gli override disattivati e ho eseguito il check up dei database con il modulo prestashop cleaner 1.8 e, una volta tornato al tema ufficiale, mi sono ritrovato ad una situazione molto "vanilla" e priva di errori se visulaizzata con la debug mode attiva. A questo punto, ho testato tutte le funzioni di questo sito web locale che mi ritrovo ibridato (vecchio database, nuova installazione) e tutto sembra andare bene, con nessun errore durante l'utilizzo della modalità di debug. Mi sento quindi a mio agio nell'usare il modulo 1-click per aggiornare a PS 1.7.7.4. - Metto lo zip nella cartella dei download e procedo con l'aggiornamento. Tutto fila liscio nell'aggiornamento dei file (tutto verde), ma quando il processo va al database, mi ritrovo con un errore e un back office poco accessibile, con front-office e back office zona ordini, clienti e setting inaccessibili a causa di troppi reindirizzamenti. Ecco la situazione e gli errori di aggiornamento del database: Updating database schema... Executing: CREATE TABLE ps_translation (id_translation INT AUTO_INCREMENT NOT NULL, id_lang INT NOT NULL, `key` TEXT NOT NULL COLLATE utf8_bin, translation TEXT NOT NULL, domain VARCHAR(80) NOT NULL, theme VARCHAR(32) DEFAULT NULL, INDEX IDX_ADEBEB36BA299860 (id_lang), INDEX `key` (domain), PRIMARY KEY(id_translation)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_module_history (id INT AUTO_INCREMENT NOT NULL, id_employee INT NOT NULL, id_module INT NOT NULL, date_add DATETIME NOT NULL, date_upd DATETIME NOT NULL, PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: CREATE TABLE ps_admin_filter (id INT AUTO_INCREMENT NOT NULL, employee INT NOT NULL, shop INT NOT NULL, controller VARCHAR(60) NOT NULL, action VARCHAR(100) NOT NULL, filter LONGTEXT NOT NULL, filter_id VARCHAR(191) NOT NULL, UNIQUE INDEX admin_filter_search_id_idx (employee, shop, controller, action, filter_id), PRIMARY KEY(id)) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci ENGINE = InnoDB Executing: DROP INDEX lang_iso_code ON ps_lang Executing: ALTER TABLE ps_lang CHANGE active active TINYINT(1) NOT NULL DEFAULT '0' , CHANGE iso_code iso_code VARCHAR(2) NOT NULL, CHANGE language_code language_code VARCHAR(5) NOT NULL, CHANGE date_format_lite date_format_lite VARCHAR(32) NOT NULL DEFAULT 'Y-m-d' , CHANGE date_format_full date_format_full VARCHAR(32) NOT NULL DEFAULT 'Y-m-d H:i:s' , CHANGE is_rtl is_rtl TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_2F43BFC7BA299860 ON ps_lang_shop (id_lang) Executing: ALTER TABLE ps_lang_shop RENAME INDEX id_shop TO IDX_2F43BFC7274A50A0 Executing: DROP INDEX id_lang ON ps_attribute_lang Executing: CREATE INDEX IDX_3ABE46A77A4F53DC ON ps_attribute_lang (id_attribute) Executing: CREATE INDEX IDX_3ABE46A7BA299860 ON ps_attribute_lang (id_lang) Executing: DROP INDEX deleted ON ps_shop_group Executing: ALTER TABLE ps_shop_group CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: DROP INDEX id_parent ON ps_tab Executing: DROP INDEX class_name ON ps_tab Executing: ALTER TABLE ps_tab ADD route_name VARCHAR(256) DEFAULT NULL, CHANGE position position INT NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE hide_host_mode hide_host_mode TINYINT(1) NOT NULL DEFAULT '0' , CHANGE icon icon VARCHAR(32) DEFAULT '' Executing: DROP INDEX id_shop_group ON ps_shop Executing: DROP INDEX id_category ON ps_shop Executing: ALTER TABLE ps_shop CHANGE id_category id_category INT NOT NULL DEFAULT '1' , CHANGE theme_name theme_name VARCHAR(255) NOT NULL, CHANGE active active TINYINT(1) NOT NULL DEFAULT '1' , CHANGE deleted deleted TINYINT(1) NOT NULL DEFAULT '0' Executing: CREATE INDEX IDX_CBDFBB9EF5C9E40 ON ps_shop (id_shop_group) Executing: ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' 01:24:42 ERROR [console] Error thrown while running command "prestashop:schema:update-without-foreign --env=prod". Message: "An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20" ["exception" => Doctrine\DBAL\Exception\DriverException { …},"command" => "prestashop:schema:update-without-foreign --env=prod","message" => """ An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE color color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ':\n \n SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 """] In AbstractMySQLDriver.php line 106: An exception occurred while executing 'ALTER TABLE ps_attribute CHANGE colo r color VARCHAR(32) NOT NULL, CHANGE position position INT NOT NULL DEFAULT '0' ': SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 90: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 In PDOConnection.php line 88: SQLSTATE[01000]: Warning: 1265 Data truncated for column 'color' at row 20 prestashop:schema:update-without-foreign [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-e|--env ENV] [--no-debug] [--id_shop [ID_SHOP]] [--id_shop_group [ID_SHOP_GROUP]] [--] Avete qualche soluzione da suggerire? Come posso stabilire quali tabelle stanno provocando il problema per correggerle prima di procedere con l'aggiornamento 1.7.7.4? Grazie mille per qualsiasi suggerimento possiate fornirmi. Di seguito sono riportate le specifiche di MAMP al momento dell'errore: PHP: 7.1.33 max_execution_time30000 max_file_uploads20 max_input_nesting_level64 max_input_time60000 max_input_vars10000 memory_limit1024M post_max_size256M Server web: Apache [RISOLTO] Dopo aver postato il problema anche su stackoverflow mi è stato fatto notate che chiaramente il messaggio d'errore rimandava ad un campo regolato in database da un VARCHAR di massimo 32 caratteri spazi inclusi che si presentava popolato in eccesso. Trovato il campo, ridotto il contenuto da 35 a 29 caratteri e questo errore si è risolto, permettendomi di raggiungere il compimento dell'aggiornamento. In ogni caso, data l'eccedenza di errori da precedente installazione (database e prestashop vengono portati avanti, senza reset, dal 2013), ho collegato il database aggiornato alla 1.7 ad una fresh install 1.7. Attualmente ho dei problemi di permessi su tale nuovo database, ma questo problema è stato risolto.

Hallo, ich konnte in meinem Shop die Bestellungen mir nicht mehr anzeigen lassen. Es erschien ein 500 internal server error. Daher habe ich einmal versucht, mit Hilfe des Debug Modus, mir zumindest die Quelle des Fehlers anzeigen zu lassen, was auch funktioniert hat. Leider komme ich nicht mehr zurück auf die Seite unter dem Menupunkt Leistung, auf der ich den Debug Modus wieder ausschalten kann, weil ich immer auf eine Fehlerseite komme, siehe Attachment. Nun habe ich 2 Probleme, den Debug Modus, den ich nicht mehr ausschalten kann, und die nicht mehr anzeigbaren Bestellungen. Liveseite https://www.haenselgret.de funktioniert leider nun auch nicht mehr. Bin für jede Hilfe dankbar. LG Ralf

Hallo, ich konnte in meinem Shop die Bestellungen mir nicht mehr anzeigen lassen. Es erschien ein 500 internal server error. Daher habe ich einmal versucht, mit Hilfe des Debug Modus, mir zumindest die Quelle des Fehlers anzeigen zu lassen, was auch funktioniert hat. Leider komme ich nicht mehr zurück auf die Seite unter dem Menupunkt Leistung, auf der ich den Debug Modus wieder ausschalten kann, weil ich immer auf eine Fehlerseite komme, siehe Attachment. Nun habe ich 2 Probleme, den Debug Modus, den ich nicht mehr ausschalten kann, und die nicht mehr anzeigbaren Bestellungen. Bin für jede Hilfe dankbar. LG Ralf

Private debug mode module We have created and used this module internally when we need to debug on a site without interrupting the front-end users. The module makes it possible for you to work and debug on your active store based on your IP-address. Your customers will see a normal functional shop without any error messages. While you can read the errors. This is all possible because the module works based on the given IP-address. The module requires minimal configurations. You simply add your current IP-Address and you are good to go. From the module page, you can activate or deactivate debug mode. And from the performance page, you now have an extra button for advanced debugging. Check it out here: Private debug mode module

Hello, I'm back.... Again. Im having an issue accessing homepage configuration. When I do click it, it shows error 500. So I turned on Debug Mode, and this file came up. Can anybody tell me what to do next Thank you

The section of Installed Modules is missing. I cannot see which modules have bee installed. Offcourse there are modules which have been installed. Also, if I try to search for any module and click on configure, it redirects me to this page. What could be the possible error?

Hi, I have problem with changing order status in PS 1.7.7.0 so I want to see what happen in debug mode, but only in BO orders page it doesn't work: An error occurred while loading the web debug toolbar. What can I do now?

Bonjour, Je rencontre un souci avec la fonctionnalité mot de passe oublié. Normalement au clique sur ce dernier j'inscris mon adresse mail, je reçois par la suite un mail avec un lien qui normalement doit générer un nouveau mot de passe aléatoire. Cependant, au clique sur ce lien je suis redirigé sur ma page de connexion de ma boutique, ma boutique utilise le module https://addons.prestashop.com/fr/ventes-flash-ventes-privees/20141-magasin-prive-connexion-pour-voir-la-boutique.html. (je suis en multi boutique) J'ai donc mis le mode debug et voici le résultat.(cf capture d'écran). J'ai donc regardé le fichier du premier message et voici son contenu. <?php /* Smarty version 3.1.33, created on 2020-10-26 16:22:52 from '/var/www-presta/themes/leo_bread/modules/appagebuilder/views/templates/front/profiles/id_gencode_5e467bdcbe175_1581677532.tpl' */ /* @var Smarty_Internal_Template $_smarty_tpl */ if ($_smarty_tpl->_decodeProperties($_smarty_tpl, array ( 'version' => '3.1.33', 'unifunc' => 'content_5f96e9ccd26079_77335849', 'has_nocache_code' => false, 'file_dependency' => array ( '0fa642c1e13e1718ce213f28eba1195820e9cbce' => array ( 0 => '/var/www-presta/themes/leo_bread/modules/appagebuilder/views/templates/front/profiles/id_gencode_5e467bdcbe175_1581677532.tpl', 1 => 1603725772, 2 => 'file', ), ), 'includes' => array ( ), ),false)) { function content_5f96e9ccd26079_77335849 (Smarty_Internal_Template $_smarty_tpl) { if ($_smarty_tpl->tpl_vars['logged']->value) { echo htmlspecialchars($_smarty_tpl->tpl_vars['customerName']->value, ENT_QUOTES, 'UTF-8'); } } } Version PrestaShop: 1.7.6.1 Quelqu'un a une solution ? Merci d'avance

Hello, i have Prestashop 1.7.6 and this problem on debug mode in product listing pages: (1/1) ContextErrorException Notice: Undefined index: manufacturer in 7f35d568adb832c0542642dec3089a44f84f543e_2.file.product-list.tpl.php line 195 at Block_20025463665f06feb4204180_76546672->callBlock(object(SmartyCustomTemplate))in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_20025463665f06feb4204180_76546672), object(SmartyCustomTemplate))in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyCustomTemplate), object(Block_20025463665f06feb4204180_76546672), object(Block_17899038085f06feb4220337_95037557))in smarty_internal_runtime_inheritance.php line 186 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyCustomTemplate), object(Block_17899038085f06feb4220337_95037557))in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyCustomTemplate), 'Block_17899038085f06feb4220337_95037557', 'content', 2)in b032e36db9090d3aa17261e820ada8b0d1c94542_2.file.layout-full-width.tpl.php line 101 at Block_14712312085f06feb42174c3_11001533->callBlock(object(SmartyCustomTemplate))in smarty_internal_runtime_inheritance.php line 248 at Smarty_Internal_Runtime_Inheritance->callBlock(object(Block_14712312085f06feb42174c3_11001533), object(SmartyCustomTemplate))in smarty_internal_runtime_inheritance.php line 184 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyCustomTemplate), object(Block_14712312085f06feb42174c3_11001533), object(Block_4084943985f06feb422dee0_46915914))in smarty_internal_runtime_inheritance.php line 186 at Smarty_Internal_Runtime_Inheritance->process(object(SmartyCustomTemplate), object(Block_4084943985f06feb422dee0_46915914))in smarty_internal_runtime_inheritance.php line 156 at Smarty_Internal_Runtime_Inheritance->instanceBlock(object(SmartyCustomTemplate), 'Block_4084943985f06feb422dee0_46915914', 'content_wrapper')in 9c21373596dbee0ba6baa8e9171eda74e89f0fcb_2.file.layout-both-columns.tpl.php line 87 at content_5f06feb4232d30_71332889(object(SmartyCustomTemplate))in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyCustomTemplate))in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyCustomTemplate))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, 3600, array(), 2, false, null, null)in smarty_internal_runtime_inheritance.php line 125 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyCustomTemplate), 'layouts/layout-both-columns.tpl')in b032e36db9090d3aa17261e820ada8b0d1c94542_2.file.layout-full-width.tpl.php line 42 at content_5f06feb42211b5_79166795(object(SmartyCustomTemplate))in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyCustomTemplate))in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyCustomTemplate))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, 3600, array(), 2, false, null, null)in smarty_internal_runtime_inheritance.php line 125 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyCustomTemplate), 'layouts/layout-full-width.tpl')in 7f35d568adb832c0542642dec3089a44f84f543e_2.file.product-list.tpl.php line 37 at content_5f06feb420f362_73035315(object(SmartyCustomTemplate))in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyCustomTemplate))in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyCustomTemplate))in smarty_internal_template.php line 216 at Smarty_Internal_Template->render()in smarty_internal_template.php line 385 at Smarty_Internal_Template->_subTemplateRender('catalog/listing/product-list.tpl', null, 'layouts/layout-full-width.tpl', 0, 3600, array(), 2, false, null, null)in smarty_internal_runtime_inheritance.php line 125 at Smarty_Internal_Runtime_Inheritance->endChild(object(SmartyCustomTemplate), 'catalog/listing/product-list.tpl')in 5182c5e00737af934c094615827ba9ed9c980036_2.file.category.tpl.php line 34 at content_5f06feb41f4e15_54731437(object(SmartyCustomTemplate))in smarty_template_resource_base.php line 123 at Smarty_Template_Resource_Base->getRenderedTemplateCode(object(SmartyCustomTemplate))in smarty_template_compiled.php line 114 at Smarty_Template_Compiled->render(object(SmartyCustomTemplate))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(SmartyCustomTemplate), null, 'layouts/layout-full-width.tpl', null, 0)in smarty_internal_templatebase.php line 116 at Smarty_Internal_TemplateBase->fetch('catalog/listing/category.tpl', null, 'layouts/layout-full-width.tpl', null, false, true, false)in SmartyCustom.php line 112 at SmartyCustomCore->fetch('catalog/listing/category.tpl', null, 'layouts/layout-full-width.tpl')in FrontController.php line 683 at FrontControllerCore->smartyOutputContent('catalog/listing/category.tpl')in FrontController.php line 667 at FrontControllerCore->display()in Controller.php line 312 at ControllerCore->run()in Dispatcher.php line 515 at DispatcherCore->dispatch()in index.php line 28 What could it be?

Boa noite pessoal! Estou trabalhando com o Prestashop versão 1.7.6.5, e estou com o seguinte problema: Na minha maquina local ele funciona normalmente, porém ao subir no servidor o painel admin só funciona se estiver com o modo debug ativo, ou seja, define('_PS_MODE_DEV_', true); Já tentei encontrar nos arquivos algo que possa me ajudar mas não localizei nada. Alguém sabe se fiz algo errado? PS: Alterei o nome da pasta admin "na mão" direto no diretório.

Hello everybody I have activated debug mode in config/defines.inc.php and some errors are showing and don't know how to solve it. The first one is at BO, at modules tab it shows next: Notice: Undefined property: stdClass::$type in /var/www/vhosts/mydomain.es/httpdocs/cache/smarty/compile/5b/0b/8b/5b0b8b44b2339610fc8e3f35149aec1939cfb715.file.list.tpl.php on line 47 I have checked the file and this is what I got: This is line 47: <?php if ($_smarty_tpl->tpl_vars['module']->value->type!='addonsMustHave'){?> <?php /* Smarty version Smarty-3.1.14, created on 2014-10-01 15:45:01 compiled from "/var/www/vhosts/mydomain.es/httpdocs/admin5678/themes/default/template/controllers/modules/list.tpl" */ ?> <?php /*%%SmartyHeaderCode:1853432802542c055d0a9016-72549457%%*/if(!defined('SMARTY_DIR')) exit('no direct access allowed'); $_valid = $_smarty_tpl->decodeProperties(array ( 'file_dependency' => array ( '5b0b8b44b2339610fc8e3f35149aec1939cfb715' => array ( 0 => '/var/www/vhosts/mydomain.es/httpdocs/admin5678/themes/default/template/controllers/modules/list.tpl', 1 => 1406026738, 2 => 'file', ), ), 'nocache_hash' => '1853432802542c055d0a9016-72549457', 'function' => array ( ), 'variables' => array ( 'modules' => 0, 'module' => 0, ), 'has_nocache_code' => false, 'version' => 'Smarty-3.1.14', 'unifunc' => 'content_542c055d228d54_98352138', ),false); /*/%%SmartyHeaderCode%%*/?> <?php if ($_valid && !is_callable('content_542c055d228d54_98352138')) {function content_542c055d228d54_98352138($_smarty_tpl) {?> <?php if (count($_smarty_tpl->tpl_vars['modules']->value)){?> <table cellspacing="0" cellpadding="0" style="width: 100%; margin-bottom:10px;" class="table" id=""> <thead> <tr class="nodrag nodrop"> <th class="center"> <input type="checkbox" rel="false" class="noborder" id="checkme"><br> </th> <th class="center"></th> <th><?php echo smartyTranslate(array('s'=>'Module name'),$_smarty_tpl);?> </th> <th></th> </tr> <tbody> <?php $_smarty_tpl->tpl_vars['module'] = new Smarty_Variable; $_smarty_tpl->tpl_vars['module']->_loop = false; $_from = $_smarty_tpl->tpl_vars['modules']->value; if (!is_array($_from) && !is_object($_from)) { settype($_from, 'array');} foreach ($_from as $_smarty_tpl->tpl_vars['module']->key => $_smarty_tpl->tpl_vars['module']->value){ $_smarty_tpl->tpl_vars['module']->_loop = true; ?> <?php if ($_smarty_tpl->tpl_vars['module']->value->type!='addonsMustHave'){?> <tr> <td> <?php if ((isset($_smarty_tpl->tpl_vars['module']->value->id)&&$_smarty_tpl->tpl_vars['module']->value->id>0)||!isset($_smarty_tpl->tpl_vars['module']->value->type)||$_smarty_tpl->tpl_vars['module']->value->type!='addonsMustHave'){?> <input type="checkbox" name="modules" value="<?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> " <?php if (!isset($_smarty_tpl->tpl_vars['module']->value->confirmUninstall)||empty($_smarty_tpl->tpl_vars['module']->value->confirmUninstall)){?>rel="false"<?php }else{ ?>rel="<?php echo addslashes($_smarty_tpl->tpl_vars['module']->value->confirmUninstall);?> "<?php }?> class="noborder"> <?php }?> </td> <td><img class="imgm" alt="" src="<?php if (isset($_smarty_tpl->tpl_vars['module']->value->image)){?><?php echo $_smarty_tpl->tpl_vars['module']->value->image;?> <?php }else{ ?>../modules/<?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> /<?php echo $_smarty_tpl->tpl_vars['module']->value->logo;?> <?php }?>"></td> <td> <div class="moduleDesc" id="anchor<?php echo ucfirst($_smarty_tpl->tpl_vars['module']->value->name);?> " title="<?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> "> <h3><?php echo $_smarty_tpl->tpl_vars['module']->value->displayName;?> <span style="display:none"><?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> </span> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->type)&&$_smarty_tpl->tpl_vars['module']->value->type=='addonsMustHave'){?> <span class="setup must-have"><?php echo smartyTranslate(array('s'=>'Must Have'),$_smarty_tpl);?> </span> <?php }else{ ?> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->id)&&$_smarty_tpl->tpl_vars['module']->value->id>0){?> <span class="setup<?php if (isset($_smarty_tpl->tpl_vars['module']->value->active)&&$_smarty_tpl->tpl_vars['module']->value->active==0){?> off<?php }?>"><?php echo smartyTranslate(array('s'=>'Installed'),$_smarty_tpl);?> </span> <?php }else{ ?> <span class="setup non-install"><?php echo smartyTranslate(array('s'=>'Not installed'),$_smarty_tpl);?> </span> <?php }?> <?php }?> </h3> <div class="metadata"> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->author)&&!empty($_smarty_tpl->tpl_vars['module']->value->author)){?> <dl class=""> <dt><?php echo smartyTranslate(array('s'=>'Developed by'),$_smarty_tpl);?> :</dt> <dd><?php echo $_smarty_tpl->smarty->registered_plugins[Smarty::PLUGIN_MODIFIER]['truncate'][0][0]->smarty_modifier_truncate($_smarty_tpl->tpl_vars['module']->value->author,20,'...');?> </dd>| </dl> <?php }?> <dl class=""> <dt><?php echo smartyTranslate(array('s'=>'Version'),$_smarty_tpl);?> :</dt> <dd><?php echo $_smarty_tpl->tpl_vars['module']->value->version;?> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->version_addons)){?>(<?php echo smartyTranslate(array('s'=>'Update'),$_smarty_tpl);?> <?php echo $_smarty_tpl->tpl_vars['module']->value->version_addons;?> <?php echo smartyTranslate(array('s'=>'Available on PrestaShop Addons'),$_smarty_tpl);?> )<?php }?> </dd>| </dl> <dl class=""> <dt><?php echo smartyTranslate(array('s'=>'Category'),$_smarty_tpl);?> :</dt> <dd><?php echo $_smarty_tpl->tpl_vars['module']->value->categoryName;?> </dd> </dl> </div> <p class="desc"><?php if (isset($_smarty_tpl->tpl_vars['module']->value->description)&&$_smarty_tpl->tpl_vars['module']->value->description!=''){?><?php echo smartyTranslate(array('s'=>'Description'),$_smarty_tpl);?> : <?php echo $_smarty_tpl->tpl_vars['module']->value->description;?> <?php }else{ ?> <?php }?></p> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->message)&&(empty($_smarty_tpl->tpl_vars['module']->value->name)===false)&&(!isset($_smarty_tpl->tpl_vars['module']->value->type)||($_smarty_tpl->tpl_vars['module']->value->type!='addonsMustHave'||$_smarty_tpl->tpl_vars['module']->value->type!=='addonsNative'))){?><div class="conf"><?php echo $_smarty_tpl->tpl_vars['module']->value->message;?> </div><?php }?> <div class="row-actions-module"> <?php if (!isset($_smarty_tpl->tpl_vars['module']->value->not_on_disk)){?> <?php echo $_smarty_tpl->tpl_vars['module']->value->optionsHtml;?> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->preferences)&&$_smarty_tpl->tpl_vars['module']->value->preferences['favorite']==1){?> <a class="action_module action_unfavorite toggle_favorite" data-module="<?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> " data-value="0" href="#"><?php echo smartyTranslate(array('s'=>'Remove from Favorites'),$_smarty_tpl);?> </a> <a class="action_module action_favorite toggle_favorite" data-module="<?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> " data-value="1" href="#" style="display: none;"><?php echo smartyTranslate(array('s'=>'Mark as Favorite'),$_smarty_tpl);?> </a> <?php }else{ ?> <a class="action_module action_unfavorite toggle_favorite" data-module="<?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> " data-value="0" href="#" style="display: none;"><?php echo smartyTranslate(array('s'=>'Remove from Favorites'),$_smarty_tpl);?> </a> <a class="action_module action_favorite toggle_favorite" data-module="<?php echo $_smarty_tpl->tpl_vars['module']->value->name;?> " data-value="1" href="#"><?php echo smartyTranslate(array('s'=>'Mark as Favorite'),$_smarty_tpl);?> </a> <?php }?> <?php }else{ ?> <?php }?> </div> </div> </td> <td> <ul id="list-action-button"> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->type)&&$_smarty_tpl->tpl_vars['module']->value->type=='addonsMustHave'){?> <li> <a href="<?php echo $_smarty_tpl->tpl_vars['module']->value->addons_buy_url;?> " target="_blank" class="button updated"><span><img src="../img/admin/cart_addons.png"> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->id_currency)&&isset($_smarty_tpl->tpl_vars['module']->value->price)){?><?php echo $_smarty_tpl->smarty->registered_plugins[Smarty::PLUGIN_FUNCTION]['displayPrice'][0][0]->displayPriceSmarty(array('price'=>$_smarty_tpl->tpl_vars['module']->value->price,'currency'=>$_smarty_tpl->tpl_vars['module']->value->id_currency),$_smarty_tpl);?> <?php }?></span></a> </li> <?php }else{ ?> <?php if (isset($_smarty_tpl->tpl_vars['module']->value->version_addons)&&$_smarty_tpl->tpl_vars['module']->value->version_addons){?> <li><a href="<?php echo $_smarty_tpl->tpl_vars['module']->value->options['update_url'];?> " class="button updated"><span><?php echo smartyTranslate(array('s'=>'Update it!'),$_smarty_tpl);?> </span></a></li> <?php }?> <li> <a <?php if (isset($_smarty_tpl->tpl_vars['module']->value->id)&&$_smarty_tpl->tpl_vars['module']->value->id>0&&!empty($_smarty_tpl->tpl_vars['module']->value->options['uninstall_onclick'])){?>onclick="<?php echo $_smarty_tpl->tpl_vars['module']->value->options['uninstall_onclick'];?> "<?php }?> href="<?php if (isset($_smarty_tpl->tpl_vars['module']->value->id)&&$_smarty_tpl->tpl_vars['module']->value->id>0){?><?php echo $_smarty_tpl->tpl_vars['module']->value->options['uninstall_url'];?> <?php }else{ ?><?php echo $_smarty_tpl->tpl_vars['module']->value->options['install_url'];?> <?php }?>" class="button installed"> <span><?php if (isset($_smarty_tpl->tpl_vars['module']->value->id)&&$_smarty_tpl->tpl_vars['module']->value->id>0){?><?php echo smartyTranslate(array('s'=>'Uninstall'),$_smarty_tpl);?> <?php }else{ ?><?php echo smartyTranslate(array('s'=>'Install'),$_smarty_tpl);?> <?php }?></span> </a> </li> <?php }?> </ul> </td> </tr> <?php }?> <?php } ?> </tbody> </table> <div style="margin-top: 12px;"> <input type="button" class="button big" value="<?php echo smartyTranslate(array('s'=>'Install the selection'),$_smarty_tpl);?> " onclick="modules_management('install')"/> <input type="button" class="button big" value="<?php echo smartyTranslate(array('s'=>'Uninstall the selection'),$_smarty_tpl);?> " onclick="modules_management('uninstall')" /> </div> <?php }else{ ?> <div style="margin-top: 12px;color: #585A69;font-size: 16px;"><p align="center"><?php echo smartyTranslate(array('s'=>'No modules available in this section.'),$_smarty_tpl);?> </p></div> <?php }?> <?php [spam-filter] ?>