Question Old Items and Gifts????

[jl255]

Are all the old gifts and items my members bought and gifted to one another gone after upgrading from vbshop 1.2 to vbshop2.2?? I didn't see any warning on that!

Somehow, all the gifts showing under postpit are now 'bold username'. What happened to all their gifts/items?? Anyway to recover? I'm gonna have a riot in my forum otherwise.

Also, anyway to show the gifts received in profile page?

 

[Fillip H.]

The gifts were converted into the "Custom Item" item type.

The gifts received and items purchased already showed in the profile in v1.2 and continue to do so.

 

[jl255]

yes but like i said, all the gifts in the postbit has are 'bold username'. And I don't see any gift tab anymore in the profile page.

 

[Fillip H.]

It's possible this has got to do with the cache repairing issue in the other thread.

The vBShop tab shows up in all the testing environments I have access to, including a live board that's done a successful upgrade from 1.2 to 2.2

 

[jl255]

repaired cache but nothing has changed. so what shld i do now?

i looked at recent transaction and its ALL 'bold username' too. has the db been corrupted?

 

[Jem]

This happened to me as well. All custom gifts that had been awarded were inexplicably transformed into BOLD.

 

[Fillip H.]

It's sadly impossible for me to go back and fix it, since the upgrade has already happened

 

[jl255]

u sure there is no fix??? argggggg.............

 

[jl255]

any confirmation of this?

and if so, how do i go and delete all previous transactions??

 

[Fillip H.]

My previous post in this thread was a confirmation

Your best bet would probably be to reinstall the mod after writing down the current item configuration, that way you can be sure there's no other upgrade issues lingering

 

[jl255]

i have more than 200 items added. So i'll need to manually add all 200 items again??

Can i go into the DB to delete all transactions?

Needless to say, i'm really quite disappointed and frustrated with this update. You should have included a warning that all past transactions will be corrupted. ensuring that past transactions and records are all kept intact shld be the most impt thing for any upgrade, which is sadly my mistake in assuming that this will be well-taken care of. I'm now stuck between a rock and a hard place and all you can say is too bad.

 

[Fillip H.]

If it was known to happen in 100% of cases, then we would have included a warning

You could try running these two queries:

TRUNCATE TABLE dbtech_vbshop_purchase

UPDATE user SET dbtech_vbshop_purchase = NULL

Remember to add your table prefix if you use any.

 

[jl255]

these db corruptions don't happen randomly. obviously there is something wrong with your upgrade script (perhaps for big boards only or some other conditions) as no one else touches vbshop script. shldnt' you try to find out what went wrong, instead of just saying 'tough luck'? and perhaps if u found out what went wrong, there cld be a fix. it cld be improper table reading or something like that.....

 

[Fillip H.]

Sadly it's not possible for me to look into it and fix it without a reliable way of reproducing it, which thus far I've been unable to aquire.

It's also not due to a "db corruption" and the things that could go wrong do in fact sometimes go wrong randomly. That's why you would hear more or less the same response from vBulletin if you were to upgrade from vBulletin 3 to vBulletin 4 (which is, I assume, part the reason why you're still stuck on vB3) - backups, backups, backups.
Hell, theoretically speaking you shouldn't even upgrade from 3.8.6 to 3.8.7 or some other minor change. Nobody does that though

Truth is, vBShop 1.2 to 2.0 was a significant update that required many complex changes in order to address some fundamental issues that made it impossible to continue extending the mod with the features we were suggested by our users.

People will always tell you that a clean install of a new version of Windows always beats doing an upgrade (Vista to 7, for instance). Sure, it sucks to lose all your installed programs, but upgrade scripts are nigh on impossible to get right.

vBShop v2.2 offers a superior baseline to work from so as to ensure that should such extensive changes be required again, there will be a detailed log to work upon to rebuild the database (for purchases made post-2.2 install) in the event of a "corruption". If you feel you'd rather have your old data and feature set back, you could always restore the vBShop tables from the backup and only run the 2nd query from my previous post