strict_error_reporting.php - Where to access error messages?

[MeltDown]

Your /logs folder definition, based on the DIR_FS_CATALOG setting, should be:

define('DIR_FS_LOGS', '/home/xxxx/public_html/tubularwiremeshribbon.com/logs');

Now, is there actually such a folder in your store?

OK, I've been able to successfully access the myDEBUG Backtrace plugin error logs in my /logs file:

[04-Jul-2015 11:30:29] PHP Warning:  Wrong parameter count for debug_print_backtrace() in /home/xxxx/public_html/tubularwiremeshribbon.com/includes/extra_configures/enable_error_logging.php on line 20
[04-Jul-2015 11:30:29] 
[04-Jul-2015 11:30:29] PHP Fatal error:  1109:Unknown table 'p' in field list :: select count(p.products_id) as total  in /home/xxxx/public_html/tubularwiremeshribbon.com/includes/classes/db/mysql/query_factory.php on line 120

Now to decode them. I'm not seeing Unknown table 'p' in field list in query_factory.php...

[lat9]

The first one is described here (a change I need to make to the myDEBUG Backtrace plugin: https://www.zen-cart.com/showthread....91#post1282991

Once the issue with the debug_backtrace is corrected, the 2nd log will have additional details that trace the calls that wind up at the failing call to the $db function.

What did you do to be able to view the log files?

[MeltDown]

The first one is described here (a change I need to make to the myDEBUG Backtrace plugin: https://www.zen-cart.com/showthread....91#post1282991

Once the issue with the debug_backtrace is corrected, the 2nd log will have additional details that trace the calls that wind up at the failing call to the $db function.

What did you do to be able to view the log files?

I must have had an error in the "define('DIR_FS_LOGS', '/home/xxxx/public_html/tubularwiremeshribbon.com/logs');" line, which I finally corrected :)

OK, I've updated your plugin files and here is the error log:

[04-Jul-2015 12:21:33] #1  trigger_error(1109:Unknown table 'p' in field list :: select count(p.products_id) as total , 256) called at [/home/xxxx/public_html/tubularwiremeshribbon.com/includes/classes/db/mysql/query_factory.php:120]
#2  queryFactory->show_error() called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/classes/db/mysql/query_factory.php:105]
#3  queryFactory->set_error(1109, Unknown table 'p' in field list) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/classes/db/mysql/query_factory.php:227]
#4  queryFactory->Execute(select count(p.products_id) as total ) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/classes/split_page_results.php:78]
#5  splitPageResults->splitPageResults(, 30, p.products_id, page) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/modules/responsive_sheffield_blue/product_listing.php:34]
#6  include(/home/ xxxx 0/public_html/tubularwiremeshribbon.com/includes/modules/responsive_sheffield_blue/product_listing.php) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/templates/responsive_sheffield_blue/templates/tpl_modules_product_listing.php:13]
#7  require(/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/templates/responsive_sheffield_blue/templates/tpl_modules_product_listing.php) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/templates/responsive_sheffield_blue/templates/tpl_products_new_default.php:19]
#8  require(/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/templates/responsive_sheffield_blue/templates/tpl_products_new_default.php) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/templates/responsive_sheffield_blue/common/tpl_main_page.php:229]
#9  require(/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/templates/responsive_sheffield_blue/common/tpl_main_page.php) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/index.php:97]

[04-Jul-2015 12:21:33] PHP Fatal error:  1109:Unknown table 'p' in field list :: select count(p.products_id) as total  in /home/ xxxx /public_html/tubularwiremeshribbon.com/includes/classes/db/mysql/query_factory.php on line 120

Still mysterious but I'm off to try and decipher it and appreciate and comments :)

[lat9]

To my eyes it looks like line #5 identifies the source of the error:

#5  splitPageResults->splitPageResults(, 30, p.products_id, page) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/modules/responsive_sheffield_blue/product_listing.php:34]

So, you need to look at line 34 in /includes/modules/responsive_sheffield_blue/product_listing.php to determine how it got there!

[MeltDown]

To my eyes it looks like line #5 identifies the source of the error:

#5  splitPageResults->splitPageResults(, 30, p.products_id, page) called at [/home/ xxxx /public_html/tubularwiremeshribbon.com/includes/modules/responsive_sheffield_blue/product_listing.php:34]

So, you need to look at line 34 in /includes/modules/responsive_sheffield_blue/product_listing.php to determine how it got there!

It looks as though I'm not going to be able to avoid coming off as a total eejit: First: How did you know to look at that line on that page? And Second: How does one go about determining how it got there?

Thanks :)

[mc12345678]

It looks as though I'm not going to be able to avoid coming off as a total eejit: First: How did you know to look at that line on that page? And Second: How does one go about determining how it got there?

Thanks :)

I would say it is a combination of information that identifies the "line" in question. The issue is something related with the sql that is being sent to the query_factory and so the area that generates the sql is the area in question. The list of "lines" is a look backwards in the call history, going much further back and looking at the basic instruction to initiate display of the information, but usually that far back there is no direct connection to the resulting sql error.

As for "how it got there" need to look at the program code to see what logic is required to provide the sql that was provided, was something copied and pasted incorrectly, you know sort of investigate the code and try to identify the issue, maybe there was a syntax error or something.

If necessary, can post the code at and before that/those lines and perhaps something can be spotted...

[RixStix]

If necessary, can post the code at and before that/those lines and perhaps something can be spotted...

Or compare the file to the template distribution file to remind yourself what may have been changed. Sometimes that happens when you make changes to a templates distribution files. Been there, done that.