For MAP, will need to intercept output of this plugin so that it doesn't attempt to actually show what is in the cart for those product. There is I thought a section of code that somewhat covers this situation. Recommendation would be that the plugin be disabled for product that are tracked by MAP which is done at the beginning of the associated code set in the files added to includes/modules/pages/PRODUCT_TYPE/.
As far as the "sold by the box" versus square foot. This module works off of providing the cost and associated information based off of what the shopping cart itself reports. It is possible to intercept that information and alter it to what is needed for the various product, but whatever it is that makes the product's price display unique upon landing there, needs to be carried over to that processing so that the appropriate "type" of price is shown.
The shopping_cart class has notifiers that could potentially be used knowing that the current page is say the product_info page and/or that the source function/class is/was the DPU class or a function within it, etc... even perhaps one of the notifiers in the DPU class could be used to intercept the value(s) and do some sort of conversion based on information captured from earlier gathered information when the shopping_cart class ($_SESSION['cart']) was "triggered"/accessed.



Reply With Quote
