musicmaster

Did you try profiling? https://dh42.com/blog/prestashop-debug-profiling/

Solved. I discovered that clicking the one line that is shown wil result in the showing of the other lines.

When I enable profiling in a PS 1.6.0.9 shop I get information like the following: However, when I do the same on my TB shop I get reduced information with the path part (enclosed with red lines in the picture) left out. Is there reduced functionality in Thirty Bees (or already in PS 1.6.1)? Or am I missing some setting?

Smile (=Chiel) heeft het bedrijf overgenomen:

Look also in your browser console for javascript errors

The reason why the page was almost empty was the lack of hooks. Most themes do that straight away. For example displayNav in header.tpl <nav>{hook h="displayNav"}</nav> or {hook h='displayNav'} In Panda the relevant section looks like this: {if (isset($HOOK_NAV_LEFT) && $HOOK_NAV_LEFT|trim) || (isset($HOOK_NAV_RIGHT) && $HOOK_NAV_RIGHT|trim)} <div id="top_bar" class="nav {Configuration::get('STSN_HEADER_TOPBAR_SEP_TYPE')|default:'vertical-s'} {if !$sttheme.sticky_topbar} hide_when_sticky {/if}" > <div class="wide_container"> <div class="container"> <div id="top_bar_row" class="flex_container"> <nav id="nav_left" class="flex_float_left">{$HOOK_NAV_LEFT}</nav> <nav id="nav_right" class="flex_float_right">{$HOOK_NAV_RIGHT}</nav> </div> </div> </div> </div> {/if} By default neither $HOOK_NAV_LEFT nor $HOOK_NAV_RIGHT is defined. So there will be no displayNav hook and thus the content linked to that hook is not displayed. The override FrontController.php contains the following text that inserts the hook: $this->context->smarty->assign(array( 'HOOK_NAV_LEFT' => Hook::exec('displayNavLeft'), 'HOOK_NAV_RIGHT' => Hook::exec('displayNav'), )); For some other hooks the same thing applies. As my FrontController override hadn't been installed my page stayed empty.

@Theo I found that the main file is already 1.5.5. The update directory is only for updating existing installations. I found that the error message was misleading: The problem is that this CategoryController override was not the only override that was "not installed properly". Panda tries to install 8 overrides. But after this initial failure it just stopped. It didn't even try to install the other seven - even though in many cases there was no conflicting override.

The algorithm works at the moment on order level. So when all products in an order have the same VAT rate things work. But when you have a mixed order there is a problem. It is somewhere on the things-to-do list.

Sounds like you got either a timeout or a bad record. Check the error log: it may contain relevant information. And look at the newest product to see whether it is one of the uploaded.

What is this patch? Is it a file? With what name? I am busy with other things so I won't be able to react for some time

Here is the config.xml Config.xml

When I use the module compare function of Prestools to compare the hooks I see this for the Stmegamenu module. I compared the shop I am working on with a shop I migrated a long time ago to TB. They use quite different hooks (all hooks that are not on the other side are highlighted). For many other modules there is a similar picture. Specially the Header/displayheader and displayMainMenu/displayMainmenu differences puzzle me.

I am trying to install Panda on a migrated shop that worked ok under Prestashop.

This is the latest version of the Panda theme - the only third party theme for Thirty Bees that is still supported. That should work. It evades me why you claim that it shouldn't.

Yes. I am afraid that it is something like that. I checked my migrated shop and I saw that it has 63 modules with Prestashop as author and only 2 modules with Thirty Bees as author. I haven't checked yet but I am afraid the situation is similar with hooks. That would mean that many of the hooks that Panda assumes essential in Thirty Bees just aren't present. But that would imply that the migration module is not doing what it is supposed to do.

If this table had 2.5 million records quite likely some other statistics tables were too big too. Look at ps_connections, ps_connections_source and ps_pagenotfound. Prestools has a cleanup page with the most common operations. With tables this big you might also consider truncating them when they aren't used. It will be much quicker. As Datakick mentioned these are statistics. But not everyone uses statistics or they use Google's tracking instead.

It looks like not having the hooks isn't a recipe for succes. This is how my homepage looks after the installation:

When I install the Panda theme on a TB 1.3 installation I get the following warning: Following non-theme related hooks were ignored. I never before saw such a thing. How should I understand this? Does this affect the working of the theme?

Obviously "localhost" for _DB_SERVER_ will have to be replaced by some server name. Note that not all database servers accept such external access.

I have a problem with a updated/migrated website with the admin carts page. When I look at it on my development computer I see a total value for each cart. However, after I uploaded to the server all carts had value zero. When I open a cart I see the products but they too are shown with value zero. Only new carts have a real value. After some searching in the code I found that the problem happens in the function priceCalculation() in /classes/Product.php. This function contains the lines if (!isset(static::$_pricesLevel2[$cacheId2][(int) $idProductAttribute])) { return; } and there the code execution takes the wrong turn and returns. The result is an empty price field. I have no idea what this code is checking for and how I can fix this. Can anybody enlighten me?

It might help when you published the lines of code around that line 217.

Just copy the files to the root of the domain and runit.

Copy the files and the database.

One line in the Prestashop article says that versions 2.0.0~2.1.0 of the Wishlist (blockwishlist) module are vulnerable. That means that the Thirty Bees version - that is derived from Prestashop - may be vulnerable too. Does that module need an upgrade?

No