I have read this entire thread and the readme for this mod (v. v.0.3a.1) and then installed on a fresh ZC 1.36 shop.
But I observe categories are not displaying in the "Yahoo Menu" sidebox. "All Products" and "New Products" links continue to display. Any recommends?
Shoud I uninstall and go with zc_1.2.7_0.1b version?
(note this is a test shop, so to keep it simple I have two categories, each containing two products and no subcategories).
Some questions and highlights...
In the readme for:
YahooTreeMenuWithAJAX for Zen-Cart v. 1.3.0.2 v.0.3a.1
Updated by: Seethrou [email protected] (2006-08-15)
It says:
For compatability with ZC v1.3.x, in the file:
includes/templates/template_default/tpl_yahootreemenu.php
For the following line of code:
. ' tree = new YAHOO.widget.TreeView("yahooTreeMenu");' . "\n"
Replace by the lines below:
// Replaced yahooTreeMenu by yahootreemenuContent for v1.3.x override
. ' tree = new YAHOO.widget.TreeView("yahootreemenuContent");' . "\n"
Questions:
-
I assume it is meant to place tpl_yahootreemenu.php in:
includes/templates/template_default/sideboxes/
(or includes/templates/YOUR_TEMPLATE/sideboxes/)
-
Is the above edit still required? The version I downloaded (v 1.3.0.2 v0.3a.1) shows that edit is already impemented.
-
In general does this version of the YTM support Zen Cart v.1.36, either out-of the box or requiring patches?
-
Also I see the following commented out section at the top of /sideboxes/tpl_yahootreemenu.php
*/
$content = "";
$content .= '<div id="' . str_replace('_', '-', $box_id . 'Content') . '" class="sideBoxContent">' . "\n";
/**
- // Replaced with v1.3.x override
- $content = '<div id="yahooTreeMenu"></div>' . "\n";
- // Moved to CSS override directory
- $content = '<link rel="stylesheet" type="text/css" href="' . $template->get_template_dir($column_box_default, DIR_WS_TEMPLATE, $current_page_base,'css') . '/tree.css">' . "\n";
- // Moved to jscript override directory
- $content .= '<script type="text/javascript" src="' . $template->get_template_dir($column_box_default, DIR_WS_TEMPLATE, $current_page_base,'jscript'). '/YAHOO.js"></script>' . "\n"
-
. '<script type="text/javascript" src="' . $template->get_template_dir($column_box_default, DIR_WS_TEMPLATE, $current_page_base,'jscript'). '/treeview.js"></script>' . "\n"
- . '<script type="text/javascript" src="' . $template->get_template_dir($column_box_default, DIR_WS_TEMPLATE, $current_page_base,'jscript'). '/loadNodes.js"></script>' . "\n";
*/
What is the source for this commented out code reference? From an earlier version of the mod? If so, which version?
-
I see andrew states that moving the three JS files to the override firectory is not recommended. So does this updated mod (v.0.3a.1) work if placing the files in includes/templates/template_default/ ?
-
And same question regarding the css file?
Or as the above commented out code might suggest does this update REQUIRE installing those files in override directories:
includes/templates/YOUR_TEMPLATE/jscript/
includes/templates/YOUR_TEMPLATE/css/
But then does performance suffer as indicated by andrew previously in this thread?
This thread is a bit confusing as I see different mentions of seethrou's version v. zc_1.3.0.2 v.0.3a.1 (2006-08-15) and also andrew_yer's more recent v. zc_1.2.7_0.1b (08-31-06).
And I see various patches offered.
Are any of the recent patches posted in this thread (by andrew) intended only for v. zc_1.2.7_0.1b ? Or do they also apply to v. zc_1.3.0.2 v.0.3a.1 ?
When posting a patch or a recommendation please specifically state which version of the mod it is intended for and which version of Zen Cart. Otherwise confusion is created.
I've visited Andrew's site at http://zen-cart.org.ua/
Is this using mod version v.0.3a.1 or zc_1.2.7_0.1b ?
Anyone have a URL for a demo to observe behavior of the other YTM version?
And I understand there is a non-ajax version of this YTM mod. Anyone have a demo URL?
And what are the merits (pros and cons) of using the ajax menu version in displaying the categories/subcats in the YTM sidebox, versus the non ajax version?
To lessen the confusion it might be best to merge the documentation for both mod versions? Or if not, then split the threads to support each mod independently. Just a recommendation.
Thanks,
Woody