musicmaster

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?

Did you try re-installing Store commander? I noticed that the upgrade caused some strange effects with my modules. One disappeared - but I am not aware of having deleted it. And my payment modules became kind of inactive. That is: they didn't show in the front office but when I activated them in the backoffice they said that they were already active (but doing so solved the problem).

I believe this is a good solution. My idea of implementation would be: - Make this a extra property of an attribute: obligatory choice or not. This means part of the core. - An alternative would be to make it a product attribute but that would automatically involve all attributes. Here you run in the same limitation that causes trouble when a product has too much attribute options: the Prestashop code knows no product-attribute combination as a useful concept. - The best implementation would require that the template is adapted for it so that it can handle that extra flag and insert a class and a "please choose" text (with the option for translations). You could make it template independent but that would involve some extra overhead. - Defaults might still be used when you put the product in the cart on a category page where there are no select fields. I don't believe that this is complicated to do. The main action happens in javascript on the product.tpl template. In the core you only need to add the option to set an extra flag and to transfer that option to the template. Of course, as this a core modification, the ultimate decision is with Lesley and Michael. I wonder how Yaniv14's code would work. Do you have to select a product and an attribute? And how do you insert the changes into the template?

@zimmer-media I am sorry to see you go. I hope Lesley may tell us something that will make you reconsider. If not so: I wish you te best, personally and in business. @Traumflug I still remember that Prestashop had its spinning button problem when Chrome had changed some settings. It was Friday and the guy from Prestashop on the forum wrote that he was going to have a very nice weekend. And the forum exploded from indignation because that meant that at least until Monday (and it fact it took even longer) they had a shop where they couldn't add products. When TB was founded the argument was that we could do this better. Opensource software is not just take it or leave it. Even if he doesn't pay for the software the user invests often a lot of time (and often money) in learning and customizing the software. That puts him in a position where on the one hand he will often be prepared to pay for additional services but where on the other hand he expects some reliability from the author. He should feel responsible that the functionality that he promises actually works. You are right that these are not legal obligations. See it as a kind of moral obligation: unsupported opensource software seldom lasts long. My impression is that Zimmer-media is disappointed at that point. I don't know the technical details so I don't know whether he is right - a lot of problems are caused by third party modules and themes and custom modifications. But given his position in the community we should take his complaints seriously.

This is a tbupdater version with my updates. I have tested it. You can unzip it, rename it and then copy it to your modules directory. https://www.prestools.com/tbupdater126.zip

@lesley The module is not unstable. The bugs that were there were caused by the migration of the code from Prestashop to TB. Sure, there is always room for improvement but the problems weren't so serious that the backup part of the module had to be kept dysfunctional for over a year. I made some bugfixes and they were implemented in tbupdater 1.2.4. There was still one problem left but I needed to work on other things. Finally I came back and fixed the last problem and sent it to Michael. And then he published 1.2.5 that undid all the fixes of 1.2.4. And I never got an explanation... @wakabayashi Except for the update backup everything did what it was designed to do - and that's the problem. Even the backup part's dysfunction was more or less intentional when you consider how long it has been the case and how my code that should repair it was being ignored.

My experience with migration from Prestashop was as follows: - after a seemingly successful migration I opened my shop's front end to find little more than my logo. It took me considerable time before I understood that in the process TB had disabled all non-TB modules. And as it doesn't replace Prestashop modules with their Thirty Bees equivalent that is nearly everything: blockcart, blockcategories, blockcms, homefeatured, etc. So you end up with a very empty screen. - having arrived at 1.01 I wanted to update to 1.03. Being a lazy person I went for the default - and hang forever. Only when I tried to upgrade without the backup did I succeed. - with the migration I had opted to keep my old template (the PS default). But now I decided to try the TB default one. Strangely enough there isn't some place where you can get this just like any other theme. Instead there was some button to install the default theme. So I clicked that button - and I lost my frontoffice. It pointed to an empty directory that was supposed to contain the default theme. Copying the theme from a fresh installation solved the situation. If you asked 100 people to start this journey how many would not give up half way? This is basic functionality that a large part of the potential users will encounter. It should just work fluently and according to what the average ignorant user expects. I started to work on the update module to do something about these problems. It was a rather strange experience. The code is just the old Prestashop code with some changes. Unfortunately those changes had introduced quite a lot of bugs and two of those bugs created an eternal loop. It really puzzles me why this had to stay dysfunctional for such a long time. Was it slow? It depends how you look. The backup might take hours if you had a megashop with gigabytes of data but for the average shop it was ok. Prestashop has been able to live with it for many years without much complaints. And the starting point for optimization was obvious: the present algorithm makes many ajax calls a second that each backup a few files or database elements. Increasing the chunk size would be a quick and easy solution.

@wakabayashi said in Progress sharing: @MockoB with seriously I meant like "if they can devote all their time into tb". Now tb doesn't generate income, so they have to agree on many other coding projects, to save their incomes. Thirty Bees started aiming to be a Prestashop 1.6 without the bugs. Prestashop is making millions so if they accomplished even a part of this they would have stuck gold. Yet I have been puzzled by the implementation. Prestashop's strength is that 9 out of 10 times it works out of the box. Of course it has it problems but they tend to be deeper down. But the basis is very smooth. Unfortunately I am missing that smoothness in Thirty Bees. The core looks great but it has a lot of rough edges. It is easy to work around those rough edges when you know a bit about software but it is a big obstacle when Thirty Bees wants to be the successor of Prestashop. Try to do an upgrade or a migration from Prestashop: it is a disaster. What is worrying in this respect is that I don't see any indication that this will change. Michael seems to love the heavy stuff - like speed optimization, payment modules and search modules. But getting things working smoothly is mostly attention to detail - and a dedication to userfriendliness. From a technical point of view the problems are often trivial. The love of innovation has also harmed the maintenance of compatibility with Prestashop. Was it really necessary that compatibility of themes became a major problem? I made some contribution to the upgrade module - and saw my contribution disappear in smoke without explanation. My feeling is sometimes that Lesley and Michael are disappointed by the speed of adoption of Thirty Bees and are developing doubts about the project. It looks like they haven't given up yet, but that they don't have a clear idea any more on how to go forward.

Today I found suddenly that my shop was down. Whatever I did I got ERRCONNECTIONREFUSED. I have no idea what was the problem. In the end I got the shop running again by rebooting. I have no idea whether this was caused by 30Bees or not. But I hope someone can give me suggestions what did happen so that I can prevent a recurrence.

I want to enable the left column on my product pages. So I went in my backoffice to Preferences->Themes and chose Advanced settings. And then I get a very long list of pages where I can enable or disable the left column. But the product page is not among them. Neither is the home page. Is this not possible?