The workflow for U or A is unknown, take a look on model/orders function handleS

[Iryn3l]

I discovered this error after the call of a client who did not receive the order by e-mail and did not reach my e-mail, and in the commands / VM I did not notice it
I recently changed the status A to L but at status U I didn't change anything other than editing its name

---
VirtueMart 3.8.4 10335
Joomla! 3.9.20
PHP 7.3

[Jörgen]

What is the stock handling for A and U in Your system ? In my case both are reserved.

Jörgen @ Kreativ Fotografi

[Iryn3l]

COM_VIRTUEMART_ORDER_STATUS_CONFIRMED_BY_SHOPPER >>> U >>> RESERVED
A that has become U is removed
but I don't use it anymore, it's for older orders, I just changed it to L (that's all)

One more question if we are still in this chapter, should I have only one status "Is Removed" and until then it should only be "reserved"?
Of course excluding these with return to stock.

[Jörgen]

You can not change U to L.

It is like changing You phone number. The old number will have no recipient. The phone number as order status is the key. You can change the content for the key. But changing the key erases the old key. I hope you get what I mean.
You can add L but do not remove U.

U or L are the keys U is still used in every location it is stored, orders and otherwise.

Jörgen

[pinochico]

Status U is used in lot of extensions and I think in core VM.

Why do you think you change it to your custom?

Then you have this result - mistake admin, done

[Iryn3l]

I changed "A" to "L", .... NOT "U" >>> Sorry for my mistake when I explained
I meant "A" that has become "L"  > stock handling is "RESERVED" for this
This "A" was a status that I created (it was not in the standard Vm created)

[Jörgen]

if you change A to L you will break keys. This will impact data already in your database. Trust me on this.

Please add L DO NOT DELETE A.

Jörgen

[Iryn3l]

I recreated A and all the commands that were originally in this A status appeared here. In the meantime, I had noticed some errors, for example in mass invoicing, it generates invoices for very old orders.

Now I have another problem, I made a mistake
While switching bulk 26 orders, I forgot to select only the status I was interested in changing and closed the browser instinctively.


This status in which I wanted to change , sent the recipient contact details to a courier company and receives a transport code back.

I only sent for 6 out of 26 until the browser closes.
Trying to close I destroyed the database it seems and the orders from the last 24 hours or more I can't see them anymore


Can anything else be done to fix this?
You have some advice

[AH]

Dont ever delete an order status code

It causes many unexpected issues!

For example in order list - if the status is no longer available - it will show the order status as being the first in the order status list

[Iryn3l]

Yes now I noticed that it can create errors, I did not delete the status of the order I just renamed it .. I did not think that it can create the same errors as if it were deleted
Now it's solved after I re-created "A"

Can anyone  with the second problem, which has appeared in the meantime, help me with some advice?

<<<< Now I have another problem, I made a mistake
While switching bulk 26 orders, I forgot to select only the status I was interested in changing and closed the browser instinctively.
This status in which I wanted to change , sent the recipient contact details to a courier company and receives a transport code back.
I only sent for 6 out of 26 until the browser closes.
Trying to close I destroyed the database it seems and the orders from the last 24 hours or more I can't see them anymore >>>

[Jörgen]

Please notice, You do not rename it, you change the key value doing that. In practice this is the same as deleting the key and creating a new item. The item IS the key value with properties: reserved etc. The rest of the database does not understand that You have renamed it. The name is the KEY. Please understand this and You will know why you get into trouble.

All existing references to A will not find status A because it does not exist any more when "renamed" or deleted. Do never rename or delete a used status code.

Jörgen @ Kreativ Fotografi

[AH]

Changing the name - I was not aware of any issues regarding this?

[Jörgen]

@AH Changing the "name" of the key from A to L, is of course not the same as changing the descriptive name. Sorry about the confusion. Changing the descriptive name of the status "Cancelled" to Confirmed should not give any issues. I hope I cleared everything up.

Jörgen

[Iryn3l]

Now I understand, thank you for your help