musicmaster

There is also an option to do it without using the schema. In pseudocode: select * from ps_order_state limit 1 $row = mysqli_fetch_array() if(isset($row["active"])) ...

Isn't it a better solution to use SHOW COLUMNS? Something like: 'show columns from ps_order_state where field="active"'?

Thank you for the explanation.

This problem happened when I pressed "My Shop" in the back office. I got the screen below - the home page with an error on top. This happened in the new 1.1 version. One thing to note it that if you look good you see that the cart contains zero items. After I refreshed the page - as the error suggests - the cart contained one product. It should be noted that this is a product with combinations. I checked the javascript console but didn't see any errors. I probably added that product yesterday but I don't remember all the details of what I did then.

This is not just about analytics. The consequence of this error is that lower on the page the productscategory and crossselling modules show only the name of the products and not their picture:

You can use Prestools for that. The function Attribute List in the menu. Prestools is free.

When online (not on localhost) I get the error "MBG is not defined" on my product pages (not on the category pages). This error is caused by Google Analytics. But I have no idea where to look for the problem. This is with the new 1.1 version.

When I make a bankwire payment in the new 1.1 version the next screen is an error screen that there is a query for a column "active" in the table ps_order_state. Indeed when I checked this column doesn't exist in this table. When I look at the code it seems that this is some kind of coreupdater check that is done for many tables and goes wrong here. I "solved" the problem by manually adding an active field to this table. When I checked on my server - where I had started with a direct payment instead of bankwire - I noticed that the system had added there an active field by itself.

I found exactly the same problem with the Panda template. Note that it doesn't happen in all configurations. In a fresh installation with only the default carriers I didn't see the problem. However, In a live shop with installed carriers I did see it. That isn't strange when you how deep the routine is in the code.

Previously your error message was: Property Order->total_discounts is not valid The purpose of my improvement was to show after that message the content of that total_discounts variable. You didn't show that content in your last post. Even if it was empty at least the dash (-) would be shown.

You need two changes in /modules/coreupdater/classes/GitUpdate.php. In both cases you check whether the first char of $adminDir is a backslash and if so you remove it: In the function downloadFileList() (around line 425) the following part will be changed: $fileList = false; if ($response) { $fileList = []; $adminDir = false; if (defined('_PS_ADMIN_DIR_')) { $adminDir = str_replace(_PS_ROOT_DIR_, '', _PS_ADMIN_DIR_); if($adminDir[0] == "\\") $adminDir = substr($adminDir,1); /* new */ $adminDir = trim($adminDir, '/').'/'; } The beginning of the function downloadFiles() (around line 870) will become: protected function downloadFiles() { $adminDir = false; if (defined('_PS_ADMIN_DIR_')) { $adminDir = str_replace(_PS_ROOT_DIR_, '', _PS_ADMIN_DIR_); if($adminDir[0] == "\\") $adminDir = substr($adminDir,1); /* new */ $adminDir = trim($adminDir, '/').'/'; }

That looks like the html was entered in something like TinyMCE and converted by the program.

I saw there was a dot missing in my code: now repaired.

<p><p>text</p></p> is perfectly legal html and shouldn't show the second p as unprocessed html. I assume PC149Y comes from the description or short description field and those fields are enclosed by <p> Of course this is easy to work around. But the root of the problem is a riddle for me.

Some thoughts on debugging this: - the "total_discounts" field for the order is checked for being a float and that check fails. - so it is interesting to know what its contents is. - to see that you can change line 1037 to throw new PrestaShopException($message." - ".$this->$field);