ptmr.io

Hi, happens also in my store. Might be a bug but I could never reproduce it. AFAIK this is a very old behavior. So maybe somebody will one day find a solution 🙄

It's due to faulty numberin in ps_tabs. Did not fix it until now though. You would have to manually renumber the positions in the db.

*push* anyone having similar problems?

Hi, just wanted to ask, isn't stock managment available since 1.7.2? I'm on 1.7.2.2 and can't find the stock option at all. It's not showing up, where it should be (as seen in the screenshots here). Is there any need to activate it? Regards

Hi, the POST Method to index.php?controller=statistics from the front end returns a error 500 and I have no idea why. It returns an empty response. Enabling _PS_MODE_DEV_ returns the folling response: Whoops, looks like something went wrong. 1/1 SmartyException in smarty_internal_template.php line 678: Missing template name in smarty_internal_template.php line 678 at Smarty_Internal_Template->__get('source') in smarty_internal_templatebase.php line 119 at Smarty_Internal_TemplateBase->fetch(null, null, 'layouts/layout-full-width.tpl', null, false, true, false) in SmartyDev.php line 41 at SmartyDev->fetch(null, null, 'layouts/layout-full-width.tpl') in FrontController.php line 660 at FrontControllerCore->smartyOutputContent(null) in FrontController.php line 644 at FrontControllerCore->display() in Controller.php line 225 at ControllerCore->run() in Dispatcher.php line 379 at DispatcherCore->dispatch() in index.php line 28 Any Ideas or help? Thanks! Serverdaten Linux #1 SMP Mon May 22 13:12:26 CEST 2017 x86_64 Version der Server-Software Apache/2.4.27 PHP-Version 5.6.30 Speichergrenze 256M max_execution_time: 180 Upload (max. Dateigröße) 8M PrestaShop-Version 1.7.2.2

already posted: http://forge.prestashop.com/browse/BOOM-3625

After debugging a while, I found that $this->getPathFromUri($fullPath) in AbstractAssetManager.php returns false if one uses an absolute path (like _PS_MODULE_DIR_) and therefore no errors are displayed, the line is simply ignored. However using the correct relative path, file_exists() returns true, but in JavascriptManager.php the corresponding file_get_contents returns false which causes the error. on can fix this by changing file_get_contents($item['path']); to file_get_contents(_PS_ROOT_DIR_ . $item['path']); in JavascriptManager.php I guess it's a bug.

Thanks, however: calling file_get_contents works when called directly. The file definitly exists and will be included when inline => false Provinding the full path does not show an error, however it also doesn't show the javascript code at all in the source code with inline => true: _PS_MODULE_DIR_ . $this->name . '/js/cookieconsent.inline.js' So, what could be the problem?

/modules/xxx/js/cookieconsent.inline.js The file location itself is correct, as it loads the file with inline => false correctly. Is thr views Subfolder required?

Hi, I want to register a Javascript file within an module by using registerJavascript(). While using it with inline = false, everything works fine. However I want it to be inlined, so I use inline = true and the debug tool throws an error: Are inline .js files handled different? What's my error? public function hookActionFrontControllerSetMedia( $params ) { ... $this->context->controller->registerJavascript( 'cookieconsentinline', 'modules/' . $this->name . '/js/cookieconsent.inline.js', [ 'position' => 'bottom', 'inline' => true, 'priority' => 100, ] ); ... }

I'd guess the answer is no and according to ps support on the phone it should be save.

Anyone has got any info on this?

I would have expected that the Prestashop order Status is somehow changed to "shipped" or "paied" when I enter a tracking code/payment sum to the order. However it is even worse and the systems sends 2 emails per default, one when entering the tracking code, a second when changing the status to "shipped". So is this the desired behavior or am I getting something wrong? I'd guess it would best to automatically change the order status whenever I enter a tracking code or a payment info. Version: 1.7.1.2

Basically I know manual upgrades and successfully upgraded 1.3.x shops to 1.6.x. With the upgrade module still being in beta, I tend to use a manual upgrade on one client - as we do not want to create two themes (one for 1.6 now and one for 1.7 in about a year...). So is there any possible danger in doing a manual upgrade following the manual upgrade routine by executing install/upgrade/upgrade.php and doing all the other things manually? Reference: https://www.prestashop.com/forums/topic/612118-when-upgrade-to-17-and-how/?p=2562384

This is a hard one... I need to upgrade a shop from 1.3.2.3 to 1.7.1. I do this by manually updating to 1.6 first (works!) and then I try the beta version of the new 1 click upgrade tool, which fails. I get pretty far, but this is the error I encounter: [OK] SQL 1.7.1.0 : ALTER TABLE `ps_tab_lang` CHANGE `id_lang` `id_lang` INT(11) NOT NULL Error upgrading Doctrine schema Doctrine SQL Error : Updating database schema... Doctrine SQL Error : Doctrine SQL Error : Doctrine SQL Error : [Doctrine\DBAL\Exception\DriverException] Doctrine SQL Error : An exception occurred while executing 'ALTER TABLE ps_translation ADD CONSTRAINT FK_ADEBEB36BA299860 FOREIGN KEY (id_lang) REFERENCES ps_lang (id_lang)': Doctrine SQL Error : SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint Doctrine SQL Error : Doctrine SQL Error : Doctrine SQL Error : Doctrine SQL Error : [Doctrine\DBAL\Driver\PDOException] Doctrine SQL Error : SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint Doctrine SQL Error : Doctrine SQL Error : Doctrine SQL Error : Doctrine SQL Error : [PDOException] Doctrine SQL Error : SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint Doctrine SQL Error : Doctrine SQL Error : Doctrine SQL Error : doctrine:schema:update [--complete] [--dump-sql] [-f|--force] [--em [EM]] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-s|--shell] [--process-isolation] [-e|--env ENV] [--no-debug] [--] Doctrine SQL Error : Doctrine SQL Error : Database upgrade completed. Disabling modules now... I there is anything to do on my side, please let me know. If this helps you to enhance your software, please use this as a bug report. Regards.