mani:
Is this version of this module GitHub
https://github.com/Zen4All-nl/Zen-Cart-Dynamic-Price-Updater/releases/tag/v3.1
Same as this one
https://www.zen-cart.com/downloads.php?do=file&id=1301 ?
In Github version there is no ajax folder in includes/classes
If I install GitHub version will it work with 1.5.5e?
No those two versions are no longer the same. While Design75 and I have been talking about moving forward with DPU, we haven't synced (yet) the two distributions. They remain linked however to be able to see the branch history and to locate an updated version.
mani:
I copied the contents of the file from classes/dynamic_price_updater.php from
https://github.com/mc12345678/Dynamic_Price_Updater/blob/9857cf302f2ec06562dc40d60b79eea406dd84cf/Installation%20files/includes/classes/dynamic_price_updater.php
and now it doesnt create a log file
Is it the right approach?
Module version installed is downloaded from
https://www.zen-cart.com/downloads.php?do=file&id=1301
and only
classes/dynamic_price_updater.php has been updated from github!
After issue of 3.0.7, the bug described above was located and corrected on github in the master branch (similar location as identified above, but more "flexible" to reference because it would be up-to-date with the remainder of the software). Considering that for operations sake the only file really changed since 3.0.7 was the includes/classes/dynamic_price_updater.php file, updating the current install with that file is the way to go.
I am working on some additional functionality for the next ZC update such that the starting at: related text would/should be updated from say 'starting at:' (basically for the default values and/or no selections made) to 'at least:' (some selections have been made, but not all that are effectively required and based on attributes being included in the base price through the attributes controller) and then 'Your Price:' once all options have been selected, again somewhat based on the attribute(s) being identified as included in the base price. Still working through some of the "complexities" of options like check boxes (no requirement for one to be selected), text boxes that have pricing applied to the content, radio buttons that don't have a default value (potentially allowing submission of the product without having selected a radio button option which is a flexibility offered by the ZC software).
So yes, the action taken was a good approach to the issue identified in particular that the change(s) made to that file specifically were intended to address the issue observed here in post #1319. :) Had the solution not been there, then posting here about the issue or initiating an issue log on github should support getting the problem corrected once confirmed as an issue.