Debugging Mode / Stack Trace / What Files Are Being Included?

[koax]

Problem: Trying to figure out how which included file in being used for a certain section in order to override it in a template.

Bad solution #1: Using grep / built-in search tool to navigate horrible maze of "could-be" locations.

Bad solution #2: Scour for hours or ask every little question on the forums and wait.

Is there a way to enable either an application-level or PHP debugging type mode that'll spew the name of each included file to the browser? It's fine if it buggers up the output (running this on a dev server now). I'm just going crazy and spending FAR too much time chasing all of these down. (I'd rather become self-sufficient here.)

Anybody else feeling this pain / have a solution to this?

Please help!

...Failing that, I specifically seek to:
1) have product listings (categories) display in manipulatable little divs instead of tables.
2) modify product pages to my little heart's content
3) modify cart pages

[koax]

As the get_template_dir() function defined in:

/includes/classes/template_func.php

is used to figure out which which files override which, I modified this to output (to the screen) the paths of the files which it decides to include, immediately before the file is returned.

Note: the first commented-out debugging statement comes stock with 1.3.7 and is useless in this regard as it only outputs the inputs of the function, and not the location of the files post-override-rules.


This saved my sanity and hopefully will save a whole slew of you a ton of time, frustration, and questions:

1) edit /includes/classes/template_func.php
2) modify the get_template_dir function to resemble the following:

  function get_template_dir($template_code, $current_template, $current_page, $template_dir, $debug=false) {
    //    echo 'template_default/' . $template_dir . '=' . $template_code;
    $sanitydebug=true;
    if ($this->file_exists($current_template . $current_page, $template_code)) {
        if($sanitydebug==true){ echo $current_template . $current_page . '/' . $template_code . '<br />'; }
      return $current_template . $current_page . '/';
    } elseif ($this->file_exists(DIR_WS_TEMPLATES . 'template_default/' . $current_page, ereg_replace('/', '', $template_code), $debug)) {
        if($sanitydebug==true){ echo DIR_WS_TEMPLATES . 'template_default/' . $current_page . '/' . $template_code . '<br />'; }
      return DIR_WS_TEMPLATES . 'template_default/' . $current_page;
    } elseif ($this->file_exists($current_template . $template_dir, ereg_replace('/', '', $template_code), $debug)) {
        if($sanitydebug==true){ echo $current_template . $template_dir . '/' . $template_code . '<br />'; }
      return $current_template . $template_dir;
    } else {
        if($sanitydebug==true){ echo DIR_WS_TEMPLATES . 'template_default/' . $template_dir . '/' . $template_code . '<br />'; }
      return DIR_WS_TEMPLATES . 'template_default/' . $template_dir;
      //        return $current_template . $template_dir;
    }
  } 

3) To disable these include messages from being displayed, simply change the $sanitydebug line to say:

$sanitydebug=false; 

[DrByte]

There are some FAQ articles on the topic:
https://www.zen-cart.com/tutorials/index.php?article=36
https://www.zen-cart.com/tutorials/i...hp?article=143
https://www.zen-cart.com/tutorials/i...hp?article=232
http://www.zen-cart.com/index.php?ma...roducts_id=378
http://www.zen-cart.com/index.php?ma...roducts_id=298

[koax]

..........

[koax]

Oh yeah, I saw the articles on the

There are some FAQ articles on the topic:
https://www.zen-cart.com/tutorials/index.php?article=36
https://www.zen-cart.com/tutorials/i...hp?article=143
https://www.zen-cart.com/tutorials/i...hp?article=232
http://www.zen-cart.com/index.php?ma...roducts_id=378
http://www.zen-cart.com/index.php?ma...roducts_id=298

Awesome! I've seen all of the directory structure articles before, but the PDF of the application flow:
http://www.zen-cart.com/index.php?ma...78&update_id=2
(Home :: Downloads :: Troubleshooting Tools :: Zen Cart Program Flow Documentation)

is extremely useful in understanding what's going on. Along with modifying the get_template_dir function to include a debugging mode is still very useful in figuring out what is happening where. It even showed me that I was unknowingly calling some extraneous modules unnecessarily.

I'll use this thread to post any more useful tidbits if I find other logical places to enable debuging type info.

Thank you!