musicmaster

"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

What happens when you regenerate .htaccess?

This looks puzzling. If you copy the project to your Modules directory it immediately crashes your TB. You don't even need to install it. The crash says that it is missing some directory. Some research gave that at least two directories ("Vendor" and "Installation") are missing. I had hoped that there was at least something that I or someone else could work on. But this looks like an unfinished Symfony project of which only a part of the files has been uploaded.

Ok. Thanks.

Ok. So you see it only when you look at your own profile?

I noticed that my email address is visible when I move my mouse over my profile picture in this forum. As that is not what I want I went to look how to change my settings. Unfortunately I cannot find anything. I see pages "edit profile" and "settings" but neither offers the option to change this setting. Neither offers the option to change my password either so I wonder whether I am missing some page. Can anyone help me find those settings?

Prestashop discussion is now about evenly divided over three locations: - the old forum where still much of the community is. It isn't visited by the Prestashop staff and it has a serious spam problem. - the Gitter forums that are visited by the Prestashop staff: https://gitter.im/PrestaShop/home - the Github issues page that is the successor of Forge: https://github.com/PrestaShop/PrestaShop/issues But I doubt whether the Prestashop staff is still interested in 1.6 issues.

Good news that there are plans. However, I found it disappointing that nothing is mentioned about migration. The migration module hasn't been updated since april 2017 - despite some obvious need for improvement. And with each new TB version the migration becomes more convoluted as the module brings you only to 1.03 and after that you still need to go to 1.06. Sure, I know about the plans for a new updater. But my impression is that perfect has become the enemy of good enough. I have been saying this for the past one and half year: Thirty Bees is shooting itself in the foot by neglecting the migration process from Prestashop. When you know the routine it can be done. But someone new to TB is more likely than not to get stuck somewhere in the migration process.

@bankkkai Een testwebshop kan ook op je eigen pc/localhost. Kwestie van XAMPP installeren. Voordeel is dat je niet steeds files moet uploaden als je iets gewijzigd hebt.

You should do some profiling to see whether it is really the database https://dh42.com/blog/prestashop-debug-profiling/

@lesley said in Say hello to release 1.0.5!: It is and there will be one this week. Good to hear!

@lesley said in Say hello to release 1.0.5!: a couple of bugs is not enough to pull a release. At Prestashop I see major releases like 1.7.4 and minor releases that are often mainly bugfix releases like 1.7.4.1. Isn't this a situation where a bugfix release would be justified?

Yes, you can do that perfectly with "replace from field". The only thing that will give a problem are the brackets of (productname). But if you do it with "Download xxxxx now - For just yyyyy if you buy now - zzzz" replacing the strings will work. Just three mass edit commands.

For metadescription these options have been there for quite some time. For metatitle you need to download the latest version.

You can do much of that already with the "copy from field" and "replace from field" mass update functions. The only thing that you can't get is discounted prices.

@cassim Do you have any problem doing that now?