wakabayashi

You need to download the error file and upload it in the logs (or alternatively you enable debug mode)... Then you post the error here. Should be an easy fix.

Yeah, cisero is a clean/great looking theme. It could become the default one. But to force the usage of a certain framework is not wishful imo. I still like the component approach. It is, what I am setting up on my new shop. It's not easy, but it offers many advantages. But this would be (earliest) a project for tb 2.0.

Thanks for the report! On github we know about that:https://github.com/thirtybees/thirtybees/issues/1468. Maybe it's better to discuss the code related stuff there 🙂

@Pietroalberto I guess the important question for you is: Is it more important to sell products or to get bookings? By answering this question you will chose TB or qloapps as your cms. Afterwards you will extend the chosen cms by a module (TB) or Add-ON(qloapps). Combining both needs probably a lot of custom work... Maybe if you give more information, what you actually want to achieve, we can give you a better advise, how to set it up.

Ok, fine. I won't take any action then. Takes too much time, to guess, what could be the reason.

That's not a good assumption. The link_rewrite is defined under SEO tab (in product form). This should be unique. I guess you, that you are using multiple times the same value there. In the BO under preferences, you should even have a point "Duplicate Urls" or so. You can also check there, if there are some issues...

From experience I can say, that very strange things happens, when you have dupliacte urls. Few weeks ago I had the following: - shop1.com/quiz -> was leading to a module site (as intended) - shop2.com/quiz -> was leading to an error like "product no more active". The strange thing was, that the dispatcher in shop2 was leading to the product and in shop1 to the module site. I still don't know, what the difference was there actually. But just wanted to make clear, that duplicate urls are very tricky and confusing.

Aha! One second. Your are importing xlsx files directly into PhpMyAdmin or so? Well then I am even more sure, that it is an link_rewrite problem. Please check this column for duplicates.

Ok I have to give up then. I don't know, what you are actually doing. Your naming "upload" / "1 by one" probably confuses me. I don't even know, if the core allows xlsx files. Cause my BO says: "Allowed formats: .csv" IMO you are using multiple times the same rewrite_link.

This is wrong. As I said... There were recent changes: https://github.com/thirtybees/thirtybees/commit/b13ae185818fa83bb65813fc58bd64a159e36e9f So if you want to get this fixed, please give us reproducable data...

Hm ok. It seems to me, that you prefer to stay on 1.3 than fixxing the problem. Sounds now like an auto-import issue. There were some changes made in the recent past...

Actually I would bet, that its a rewrite problem. What are the urls of the both?

I dont get it. Have you messed image 3 and 4? Then it would make more sense to me. In general I would suspect a rewrite problem (same rewrite link) or just try to reindex the search.

Cool! But that means it's already working out for you well or are there any clear improving needs on your side?

To prevent such unwanted issue, I can give you this adivse: First make a clone of your current system. Long time ago I created a video tutorial (Offtopic: wtf it has over 1150 views!?), one part is about cloning If you can, make the clone with a subdomain. If you can, only switch the php version of the subdomain. In my case this was possible. It's probably depending on your hosting subscription. It helps to test without any risk at all.

Ok, I will make a PR in the future. For me there is no problem, if it's later factored to a module. It surely makes sense for feature that aren't used by the majority of merchants. I am always surprised how many features are just used by a little percentage of merchants. Same is true for ASM. But I guess the only reason is, that they are either a little buggy or unfinished. Cause return handling modules on prestashop store seem to be quite popular.

Relax Master @Havouza.

Well post the whole error message... Maybe we can see then the file, that throws it. And make sure, you make backups...

Isnt there a file, that states this error? Probably you can edit this file and it will work again. Not the nicest fix idea, but maybe a quick win. Maybe afterwards you should redo the core updater under php 7.4. Please also tell, which modules aren't compatible. That may help other customers too...

I have started with some improvements... Returns: Refunds: Are they useful for anyone else?

@jnsgioia I have looked one hour into it. There is some issue, but it's not about the separator but about some character in your data. You use "¾". This seems to break in the new version. @datakick My knowledge is not too good about special characters. I can imagine, that the fix or at least the understanding of the problem is much easier for you.

Thanks a lot! Your example is great to underline my point. The fact, that you need "Shipped" and "Shipped - Unpaid" shows the problem I see in the current system. I have thought about this "solution" too, but it would ask for a lot of additional states in my case. I wonder about a few things: "Being prepared for shipping". How do you know, if its paid? Wouldn't you need there two states as well? "Refunded". Does this mean, that this products are always returned and sellable again? Are you using AdvancedStockManagement? Cause if yes, there happens an auto restock imo. You are from germany, right? Looks like a DACH setup, like mine. Sorry for the questions, but I really think this system could need some cleanups/improvements.

If you update to a php 8 version, this could likely become an issue, if the modules aren't updated anymore. But basically this has not much to do with TB. If you stay on older php version, I don't expect too much issues. The problem is only: end of month only php 8 has further support.

I wonder, how you handle your order states? Do you have some custom states like "Customer complaint" or anything like this? If yes, when do you activate "shipped" or "paid"? I have looked into the code and IMO it's not possible to set this things correctly up. Here are my order states. Would be interesting to see, how other merchants are using this feature:

I don't know exactly, what you are talking about. Do you mean 1.4 vs 1.3? Can you provide the csv file? Do you get any specific error?