I have a strange issue on a live site. The prices are being removed completely somehow, and I dont personally administrate it myself to work out how.
In some circumstances a price is totally removed - has anyone solved what this could be or atleast experienced it themselves?
There are multiple people using the same login to administrate virtuemart, could this be an issue when both saving and updating a product?
I have something simular on a 2.0.21c test site haven't found out what is is. which version do you use?
Please provide more information.
Are you talking about a parent product? child product?
Hello.
I'm talking about a Parent Product. Further investigation reveals that there are no cron/backups within the server that interferes with the data.
VM2: 2.0.18a
I think something within the CMS is causing the price to be wiped, and I cannot replicate it myself.
Any advice to track this bug so I can help is appreciated.
PS, I have no rules set, i'm using all default or unset groups etc.
I place the price in cost price and let the system output that price.
@Milbo I have a completely cloned private development site should you want to check anything out.
I have the same issue ... see topic http://forum.virtuemart.net/index.php?topic=114895.msg386982#msg386982 (http://forum.virtuemart.net/index.php?topic=114895.msg386982#msg386982)
when deleting a product, the price of the previous or next product_id is removed
version Joomla 2.5.9
Virtuemart 2.0.20b
i use these extensions
- sourcerer for php coding
- jotcache
- easyfrontend seo
- cdn for joomla
- custom dropbox
and some tweaks in these files that could be related to this problem, but i haven't found the link
/administrator/components/com_virtuemart/helpers/vmtable.php
/administrator/components/com_virtuemart/models/product.php
/components/com_virtuemart/router.php, but i don't think this has any influence
VM2: 2.0.18a
I don't get the above issue. Deleting a product does not remove the price of the adjacent prouduct_id.
AbsoluteVM, did you read the update notes of vm2.0.20b?
It is imho fixed there. The problem of Peter seems to be different. There is no problem to update 2.0.18 to the latest. You should directly take 2.0.21D
I have 2.0.20b version.
My client complains random price disappears on some products, but I can't reproduce the issue.
Is this bug resolved? Where can I see the changelog where the bug is addressed?
Thanks.
Hello Milbo, has there been any reports of this bug other than when a product is deleted?
Could there be any other logical way, old browser, multiple users, that this bug is being created?
This is not fixed on VM 2.0.20b. My client has this version installed and prices are still deleted from products. The products are not being deleted. They remain in the database with nothing done to them in the admin. Everything is fine, the all of a sudden prices are missing from products that have not been edited. That field is just blank all of a sudden. It's not on all products, just a few. But they are different products every time. Very frustrating! They only way we know is a product disappears from the website frontend.
Richard
We are on 2.0.22E. But it should also correctly work for 2.0.20b. You said it happens only with some and not all products. Maybe this are "old" products, created with an older version? that could be a hint, to write a db updater checking for this.
Atm I have no clue.
Okay, so products created under old versions would retain the bug and products created after the bug would be fine.
So have you replicated the bug, is it just deleting Product Y and Product X's price deletes?
Is there any way to fix the tables of all products?
Quote from: AbsoluteVM on September 24, 2013, 22:59:03 PM
Is it just deleting Product Y and Product X's price deletes?
No. Several products price vanishes even when no other product is deleted. It seems to have no pattern that we've been able to discern.
Milbo makes a good point though, old products using the old database links?
Quote from: AbsoluteVM on September 25, 2013, 11:56:41 AM
Milbo makes a good point though, old products using the old database links?
Yes. So how do I test that assumption, and fix it. I'm not skilled at MySQL enough to write a DB updater to check this.
If I fix it - I'll post it here.
I upgraded the core so version 'e', and don't experience the bug - even with older products.