wakabayashi

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?

I am back to this topic. Was quite fun to read the old posts. I have to admit, that my understanding of returns and refunds was a bit naive. My understanding and coding skills are much better now. Who is still using RMA or (partial) refunds? I want to improve this features for my customers. If there is interest in the community I could supply some stuff as PR. Any ideas/wishes? What I plan at least (line-trough) => implemented): Possibility to create rma-slips without an action from an employee. Explanation: In some country the customer has anyway the right, to send products back. Improving the order-slip & return lists. Linking id_order to the actual order. Adding Customer Name to the lists. Allowing returns for non-paid orders. Either adding a configuration switch or just allow it default. There is actually not much relation between payment and a product return. Possibility to make the textarea optional on rma.

Either a cache issue or you didn't delete/change it in the right module. Which module is that? Which theme are you using?

A lot of exciting ideas. But I am looking most for this support ticketing system. Is this a standalone solution or does it use any external service?

And again you don't give the import file that makes the shit... My guess is like datakick: the shit was already long there, you just didn't know it.

Instead of supplying a real bug report (with the file you import, that makes the shit), you prefer to switch the platform. Sorry to say it, but you have no idea what it means.

If this is the full list, there is not much to worry about it. I don't know why, but for me there were also quite a lot vendor files...

Are these all files from the /vendor/ folder?

And some people thought this project is dead 🤔 😅 Good work! Pull request coming from me for sure 🤗

Ja, da haste Recht. Im Prinzip gibt es schon sehr ähnliches. Generell ist es nicht so schwer, so etwas zu programmieren. Aber jeder Shopbetreiber will es halt ein bisschen anders...