Thank you for this thread, big help.
I don't think this is a 1.1.4 upgrade problem.
My client just added a custom user field in VM 1.1.3 and here I am tracking down the "case of the missing orders in Order List".
Yes, I see the 5 "extra_field_N" fieleds in jos_vm_order_user_info.
So I guess I now have to append a new field to this table manually. There is absolutely no end to the, ahem, idiosyncracies that can be learned.
Although it seems that one must use one of the 5 user fields "hard coded" into this table, please ensure that your registration process is flawless after doing so. I had a problem a few weeks ago where the resolution was to leave the 5 user fields alone and create a brand spanking new custom user field.
Now, my very vocal client whom I did this change for has yet to complain about this missing order mystery. Let's look at their admin right now...
... ok, in their admin. Going into the most recent order. Clicking "next [order]". Ah, no link, as no more orders.
Let's look at the 2 sites' "Manage User Fields", shall we... my vocal client has "Required" and "Show in shipping form" unpublished.
Let's look at my affected site's "Manage User Fields". Oh, nice touch, you're going to love this... my very nice client used a "extra_field_1" BUT somehow the field name itself was changed to "vm_extrafield". Strike one! And, "Show in shipping form" is PUBLISHED. Strike two! I'm not delving into the code, it's summertime and the living is supposed to be easy; and, I'm not going to experiment to prove this. But... it looks to me, based on my two client sites, side-by-side, that the critical difference is publishing "Show in shipping form". Bet yer ass there's an IF statement deep in the VM code...
Ok, checking jos_vm_userfield. There it is, vm_extrafield (extra_field_1 is clearly overwritten, fieldid=30 is probably the default install). The fields published, registration, shipping, account follow the columns in "Show in shipping form". So, the "shipping" field = 1.
So my guess is IF (shipping field == 1) {UPDATE jos_order_user_info SET vm_userfield = <value>...}
Of course, the new field "vm_userfield" was not created at all so the UPDATE fails.
Again, thank you for this wonderful thread.
Oh, I'm *NOT* the news guy for VM. That ship sailed last fall...
-Bob