Hi mc12345678
so will the code you posted fix the v_options_values_price_w issue? or is that an added feature of an update in the works?
$row2 = ($ep_uses_mysqli ? mysqli_fetch_array($result2) : mysql_fetch_array($result2));
Hi mc12345678
so will the code you posted fix the v_options_values_price_w issue? or is that an added feature of an update in the works?
$row2 = ($ep_uses_mysqli ? mysqli_fetch_array($result2) : mysql_fetch_array($result2));
No, unfortunately the posted fix does not address the field that is in question.
Perhaps I could get a little help based on the following:
To ensure that the new field is incorporated only for those that have the applicable plugin installed, what "flag" on the right side of the screen indicates "on" or "yes" when only the applicable plugin is installed?
If the answer is none, then I have a clear path forward.
If something specific, then need to account for that "other" plugin and this one.
Verification on my side to identify requires me to install the. Plugin upfront to correct (a bit of a time issue involved and I'd like to provide a resolution rapidly)
Jeking, able to identify this?
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
unfortunately I'm not sure what you mean.
however I can provide access to the admin & ftp of an installation that has the plugins installed.
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
is this what you are after?
![]()
Yup. Thanks.
It'll be a new section to add for support. Clear path as identified above. :)
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
I just tried the attribute pricing for the first time. My results are different than Hugo's. I had existing product with attribute prices that I just created. I exported the file to see how it all looked. I also entered attribute pricing for another new product I had just created. The new prices updated into catalog.
But, the prices are all prefixed with a "0". In my drop-down list, instead of "$2.50", it's "[email protected]". And this is not just for the new prices I entered. The existing prices on the product that already had prices before the export are also changed to "0$x.xx" now.
Since this is different than Hugo's issue, I'm just mentioning it in case the fix is different.
Okay, I just went back to figure out what happened. Since this is my first time with attribute pricing, I now see what happened. Importing the file has somehow changed the prefix from "+" to "0". Now that I can explain it better, it should be easier to understand. :)
ZC Installation/Maintenance Support <- Site
Contribution for contributions welcome...
Bookmarks