Field List

[mc12345678]

Don't know from the above if the issue has been resolved, but another route of identifying the location of the errant code would be/have been to install lat9's mydebug backtrace which would have identifed the location where the sql code was run to find where that additional field pull originated.

[lat9]

Don't know from the above if the issue has been resolved, but another route of identifying the location of the errant code would be/have been to install lat9's mydebug backtrace which would have identifed the location where the sql code was run to find where that additional field pull originated.

Exactly what I was about to suggest! You can download the plugin from https://www.zen-cart.com/downloads.php?do=file&id=1879. Once installed, the myDEBUG log file will "expand" its output to identify the calling-stack that resulted in the error ... the net result being that you'll know which module contains the errant line of code.