musicmaster

I found the solution. The function callHookOn() in /classes/Hook.php has its code inside a try{} construction. When i removed the try enclosure I saw the real error.

Prestashop's autoupgrade module works step by step, processing sql files that list what must be changed in the database for the next version. And at some point during that process it will cross the 1.4-1.5 border and add the root category. Those files are found in the /install/upgrade/sql directory (up to 1.7.0) and /modules/autoupgrade/upgrade/sql (after 1.7) Of course third party tools can choose to work in another way.

When I change an image in the topmenu program of my template I get the error "The file "/tmp/phpnWYRUf" does not exist" with the file name every time different but always starting with /tmp/php. The pictture is at the bottom. The location of the code indicates that the error happens in a hook. Adding some debug code produced that it happens in the autoupgrade module in the displayBackofficeHeader hook. The relevant code in the autoupgrade module looks so: public function hookDisplayBackOfficeHeader() { if (!$this->initAutoloaderIfCompliant()) { return ''; } if (isset($this->context->controller->ajax) && $this->context->controller->ajax) { return ''; } return (new \PrestaShop\Module\AutoUpgrade\Hooks\DisplayBackOfficeHeader($this->getUpgradeContainer()))->renderUpdateNotification(); } Does anyone know how to solve this? In the error log file under /var/logs I find the following two errors The File.php Symfony file contains this (summarized): class File extends \SplFileInfo { /** * Constructs a new file from the given path. * @throws FileNotFoundException If the given path is not a file */ public function __construct(string $path, bool $checkPath = true) { if ($checkPath && !is_file($path)) { throw new FileNotFoundException($path); } parent::__construct($path); } It throws the FileNotFoundException. The original error looks so:

That is not correct. When you upgrade from 1.4 to 1.5 it will create a new category with the name "root" and that category will get the next available id number.

It appeared that this had to do with problems connecting to the database. There was an override for /classes/hook.php and that contained a call to Module::isEnabled()). When it was impossible to connect to the database (usually too many connections) this caused in some cases this error. Probably the query to retrieve the shop had gone wrong.

As you don't describe how you removed this company name it is hard to say what went wrong. But if it is really a bug you can report it here: https://github.com/PrestaShop/PrestaShop/issues

A long time ago I published a post about how to debug this kind of errors:

The new category is "root". It comes below your Home category. It was introduced in version 1.5 together with multi-shop. As it is created during the update to 1.5 it will have a high id number. Your category tree problems signal some problem with the nleft and nright fields. You could try my free Prestools. It has an Integrity Checks function that includes an option to regenerated this tree. I made some upgrade tools (Copy_shopdata and UpgradeHub ) but they won't go further back than 1.4.9 at the moment.

This is what I am talking about. I clicked the Link button on a product page with a price of 72.95. And now it ask me to pay 7295.- Sorry for the language. But I assume that it looks the same in other languages.

To enable debug mode: - download /config/defines.inc.php - open it in a text eeditor - set _PS_MODE_DEV_ to true (It should look so: define('_PS_MODE_DEV_', true);) - save the file and upload it again.

I have the Stripe_official module installed under PS 8.2.3. When I click the ">Link" button it shows the login page with at the bottom the price times 100. So 23,95 becomes 2395,00. What could cause this behavior? When I look at the page source in the browser I see the javascript variables stripe_amount and stripe_express_amount both having the value as 2395.

No

It is online again. I found that the problem was a bit wider. The new version - 1.36m - should solve it.

There is some rather serious bug in the Prestools Integrity-repair code in version 1.36k that was available last week. If you have that version please update to version 1.36l.

I uploaded a new version that fixed both problems.