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.
Posts made by musicmaster
RE: Prestools - the mass edit toolset
RE: (partly solved) module "Store Commander" stopped working
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).
RE: Forcing customer to choose an attribute
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.
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?
RE: I will say goodbye
@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.
RE: Progress sharing
@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.
RE: Progress sharing
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.