musicmaster

If those images don't show up there is likely something with the link. The first thing you might try is disabling pretty urls. Then they should become visible.

I don't understand what you want. If you don't want to show the category image the logical thing would be to adapt the template.

Unzipping can also fail because the PHP zip module isn't loaded.

I made a modification in a query in classes/order/orderInvoice.php. I made some mistake in the process. The result was no error message (despite dev mode on). Instead I got a white page when I tried to generate an invoice or a delivery slip. Predictably it took me much longer to find out what caused this bug then would have happened if there had been an error message. So my questions are: why does this happen? And can this be fixed? BTW. What I did was that I replaced the function getProductsDetail() with the following: public function getProductsDetail() { return Db::getInstance(_PS_USE_SQL_SLAVE_)->executeS( (new DbQuery()) ->select('od.*,p.*,ps.*,m.name AS manufacturer') ->from('order_detail', 'od') ->leftJoin('product', 'p', 'p.`id_product` = od.`product_id`') ->leftJoin('product_shop', 'ps', 'ps.id_product = p.id_product AND ps.id_shop = od.id_shop') ->leftJoin('manufacturer', 'm', p.'id_manufacturer` = m.`id_manufacturer`') ->where('od.`id_order` = '.(int) $this->id_order) ->where($this->id && $this->number ? 'od.`id_order_invoice` = '.(int) $this->id : '') ->orderBy('od.`product_name`') ); } So I added a line for the manufacturer but in that line I put the quotes wrong.

It looks like it has something to do with an installation automatically going to PHP 7.2. Probably not a TB problem.

I decided to look at my TB 1.04 shop in an incognito window of my Chrome browser and got the following error: Undefined class constant 'MYSQL_ATTR_USE_BUFFERED_QUERY' at line 73 in file classes/db/DbPDO.php An 1.07 installation seemed to work well but I would prefer not to upgrade. How can I solve this?

As far as I can see they are still here: https://www.prestashop.com/en/previous-versions

Sorry to make a correction. It is the psorderdetail table (or tborderdetail).

@australisagencies said in Catalog totally trashed: Another issue I wsa having was that I was importing database tables from the new installation, but not renaming them properly. I had tables called “tbsicategoryshop” and I was copying them over “tbg8categoryshop”. Are you really deleting categories directly in the database? That is almost impossible to do right. Not only should you delete all the related tables and take care that no orphaned categories remain but you should also set the nleft and nright fields correctly.

If you deleted the Home category then all bets are off. Much of the software assumes there is a home category.

Looking closer it was the product image that caused the 404. Regenerating .htaccess solved that problem. Strange. I never before needed to do that after downloading a shop. One thing that still puzzles me is that those 500 errors often happen when I go from one tab to another within the product-edit page. That puzzles me: I thought that all tabs were loaded at once so that switching between tabs is a matter of hiding and unhiding some html.

@lesley said in Tab: 500 internal server error: When you run wamp / xamp on local host it is not as optimized as running on a dedicated environment like a server so its slower. Your issue is the ajax call is likely timing out. You can open your console and manually time the call and see if you seem to be hitting like a 30 or 60 second interval. Up your max timeout settings in the php.ini and you should be good. Thank you for your reply. I had a look in my Javascript console and found "Failed to load resource: the server responded with a status of 500 (Internal Server Error)" with the filename of the missing tabs. This is an old installation that never before gave problems. Some of the PHP.ini timeouts are already increased. So I wonder which one of the many I should increase. I replaced my Avira anti-virus with some other program and it looks that improved things a bit. But not much. Overall the problem remains. An interesting side note: it looks like this problem is restricted to virtual products. And they also produce a 404 error for the file of the product. Could it be that the system is trying to load the file and that that delays the rest so much that it fails?

I have a strange problem. I have webshop on a server on the internet based on TB 1.04 and it is running fine. But when I move it to my localhost I suddenly get 500 errors on the product edit page. Switching on development mode doesn't give any result. Neither does looking in the Apache error log file. Specially weird is that the process is random. One time I get an error about the prices tab, the next time about SEO, virtual product or customization. The tab then grays out. I have seen nearly every tab pass along at least once. About 80% of the time there is one error popup, but occasionally there are two or none. Due to the error the Save buttons keep spinning and you cannot change anything. As I had problems with tabs with a prior migration too I am wondering whether there is something wrong there. Any Ideas?

Mysql has an option to export as csv. That shouldn't be a problem then.

Csv import is a function in the backoffice of Thirty Bees and Prestashop. It is core functionality so you don't need any module. As for csv export from Opencart: I don't know. I assume there is at least a module available.

"do you have a database map that explain every tables in the database." Do you really want to study the meaning of hundreds of database fields? Why don't you just use csv-export and import?

@lesley If I remember well the only change in the database structure that Prestashop made to enable multi-feature was the dropping of a unique key. That means that this is backwards compatible: you could implement this in such a way that the shop owner has to change a setting in the backoffice "enable multi-feature" with the warning that you should only do that when your theme supports it. Maybe it is an option to simultaneously bring out a free multi-feature module for Prestashop 1.6. That would encourage theme makers to support this functionality. And it would be a good way to increase Thirty Bees name recognition in the Prestashop community.

You might also consider Prestools. It depends what strategy to have in mind to convert products into attribute combinations.

A partial solution would be to backup only the base files like 123.jpg for the products and to skip all the derived files like 123-home_default.jpg. You can always regenerate them.

This was a little project for a webshop from which the shop part has been disabled for the moment. It originally ran PS 1.6.0.14. The provider switched to PHP 7.1 so something needed to be done. I first upgraded to PS 1.6.1. As the psonesixmigrator module didn't work (an unique key error for the pstab table) I then went straight to TB 1.0.6 by copying tables with my Copyshopdata tool. After that there was quite a lot of finetuning/bug fixing to do which I did under a PHP 7.2 development environment. Of course development mode was enabled and I regularly had to empty the cache. It still has the original theme.

I am a bit puzzled about those claims about many incompatibilities. My experience was that it worked quite well. Except for the problem I mentioned I saw only some error messages in the backoffice from the Cheque module that I don't use. I didn't do a comprehensive test but I used quite a few functions.

Running a shop under TB 1.06 and PHP 7.2 I keep getting this message: <b>Deprecated</b>: The each() function is deprecated. This message will be suppressed on further calls in <b>C:\xampp\htdocs\_myshop\vendor\smarty\smarty\libs\sysplugins\smarty_internal_compilebase.php</b> on line <b>75</b><br /> As it says it will disappear when you look at that page a second time. But it will re-appear when you make some change to that page or when you empty the cache. Is there a solution for this?

Are you sure it isn't the Rijndael error that was mentioned by Foolab in https://forum.thirtybees.com/topic/1954/the-version-1-0-6-release-has-happened

On top of my wishlist for any upgrader module is to be forced to make a choice whether I want a backup or not. Too often I find myself clicking Upgrade and backupping while I really don't want. And then I have to wait forever... Making no backup the default is not really an option. But you can force the user to make an explicit choice and if he forgets to do so give him a popup "please choose your backup option". It is rather simple to implement and I can have a look at it when find some time. But what do other people think about this modification?

I took a fresh 1.01 install and upgraded it to 1.06. I compared the result to a fresh 1.06 install. Not every difference may be significant but I hope the overview of the differences is helpful in fixing things. Note that I took fresh installs. I didn't even look at the front: The results of comparing files: - translations (both nl.php files and files under \translations) are not updated. Maybe this should become an option? - It looks like nothing under the \vendor directory is updated. Changed were ezyang, greenlion,guzzlehttp,jakeasmith,mrclay,pear and swiftmailed. Geoip had disappeared in the fresh 1.06. - I had indicated that the theme should be updated. However, its Modules, Css and Sass subdirectories seem not changed. This also happened to gulpfile.js and package.json. 1.01 had a Stylesheets subdirectory that has disappeared in 1.06. The Tools subdirectory contains three javascript files in 1.06 and one in the updated 1.01. In the root advanced-payment-api.js is missing in the updated 1.01. - the mails directory is not updated. Again: should this be optional? - nothing in the config directory is replaced - the .sass files of the admin theme are not replaced The modules directory: - Nine not installed modules have all files in the updated 1.01 and only a translations directory in 1.06 - many new modules cannot be found in the updated 1.01. The fresh 1.06 Modules directory has 87 subdirectories. The updated 1.01 only 54. Fixerio is the only modules that was present in the updated 1.01 and not in the fresh 1.06. The updated 1.01 offers mails in all languages. 1.06 only in those installed. The result of comparing database structures: - On quite a few places 1.06 has default dates of "1970-01-01" where the upgraded 1.01 has "0000-00-00" - On quite a few fields 1.06 has field length 11 where the upgraded 1.01 has 10. - some of the upgraded 1.01 tables have charset utf8 while 1.06 has utf8mb4 everywhere - the table with the most differences is tbpagecache. The upgraded 1.01 has much more keys. See image. In the configuration table: - PSVERSIONDB is 1.6.1.999 in the upgraded 1.01 and 1.06 in the fresh 1.06 - PSSHIPPINGHANDLING is 2 in the upgraded 1.01 and 0 in 1.06 - PSSTATSRENDER', 'statsmodule' in 1.06 and graphnvd3 in upgraded 1.01 - PSSTATSGRIDRENDER 'statsmodule' in 1.06 and gridhtml in upgraded 1.01 - The 1.06 configuration table has 11 more entries. Examples that are found in 1.06 and not in the updated 1.01 are BLOCKSOCIALAMAZON and TBUSEWEBP