DUAL Pricing v2

[hairydog]

the wholesale invoice in admin loads the original retail price just below the product description

Seems that this is still the case. Can anyone help me here? Either with a fix, or some clue about where this is being generated? I'd really like to fix this glitch, because a wrong price on an invoice does not look good.

[jackie.taferner]

hairydog, I can't seem to replicate this issue on my end. The invoice shows the correct product price and order total. Can you try re-uploading all the files included with the Dual Pricing installation? If it still does not work as expected, are you using the latest version?

[hairydog]

I uploaded all the files for the latest version (for 1.3.9h) as part of checking. The item prices are fine: it is the attribute prices that are displaying as the wrong amounts. It correctly charges the trade prices for the attributes, and the invoice line total is correct, but the attributes are listed with the retail price on the invoice.

In this example, the product is priced by attributes and the trade prices are £22.95, £100.00 and £34.95 - a total of £157.90, which is that the line total correctly shows.

The problem is that it is showing the retail prices for the attributes as part of the line description.

GU Tilt & Slide Patio Bogie Wheels 38514 - Accessory Pack: White (+£24.95) - Bogie Wheels (Pair): Left Hand (+£105.00) - Centre Cover: White (+£36.95)

GUBOGIE

20.00%

£157.90

£157.90

[jackie.taferner]

Ok, I've made a note of the issue and will work on a fix for the new v2.2 release. I can't guarantee a release date, as we try to support the community in our free time.

On a side note, I do suggest that you upgrade to the latest version of ZenCart (1.5) as it has been out for more than a year. Using an old version leaves you vulnerable to hackers/ID thefts. In fact, the PCI Compliance board requires that you upgrade within 3 months of any new cart release.

[hairydog]

On a side note, I do suggest that you upgrade to the latest version of ZenCart (1.5) as it has been out for more than a year. Using an old version leaves you vulnerable to hackers/ID thefts. In fact, the PCI Compliance board requires that you upgrade within 3 months of any new cart release.

That is all very well, but some of the addons in use are not 1.5 compatible. And all the 1.5 users hate it because of the enforced password changes. We have a few 1.3.9h installations and all of them pass PCI checks.

[jackie.taferner]

I would recommend upgrading your add-ons using the new 1.5 files and/or hiring a developer to do this for you. The enforced password changes are a PCI requirement - precisely the sort of thing business owners are supposed to do, but are never bothered with because of the inconvenience of remembering a new password.

Owning an online store is much easier than a physical storefront, but it comes with great responsibility to keep your customer's information safe. Running older cart software is not safe for your customers or for your business, regardless of the effort required to upgrade it.

[hairydog]

Thank you for the unwanted lecture, and FYI monthly password changes reduce security because they need to be written down. I don't own an online store and have no interest in doing so, but I do understand the economics of them, as you clearly do not. Without a business case, an upgrade to 1.5 is a hard sell. And there is no business case right now.

What I do want is a fix to a bug that has been around for years.

[jackie.taferner]

Business case = preventing ID theft and lawsuits

The bugfix will be applied to the latest Dual Pricing version, which is 1.5 compatible.

Clearly this thread is degenerating, so I will politely back away and will not respond further. I was just trying to be helpful and provide some advice on the matter. I am sorry you did not find it useful.

[jpietrowiak]

Update on current problems & issues please?
I have read through alot of posts trying to figure out exactly where this module is with attribute functionality.

I see in the changelog that the following was supposedly fixed?
"v2.1- Fix attribute pricing during checkout"
"v2.0- fix attribute pricing when adding to cart"

However I have installed a base 1.5.1 of Zen cart and have issues with attributes pricing defaulting to level one price when added to cart. This only happens when a customer is set to level 2,3 or 4 pricing. The drop down menu on he product page however displays proper wholesale pricing for attribute. Is this fixed and what other issues can we expect at this point.

Thanks for anyone that has input on this!

[hairydog]

I think you can assume that it is not fixed (and may never be). Three or four years after being reported this bug remains outstanding, so I assume it is too fundamental to sort out. The basic trouble for me is that the code is a complex mesh of interconnected parts (made worse because I have some other added bits in the pricing)

Attributes are a bit of a mess anyway, because we really need proper stock/availability checking of various combinations and that is hard to describe, let alone code! Conor was working on this towards the end of his life, but I hadn't managed to persuade him to do wholesale pricing in there as well.