Quote Originally Posted by linuxguy2 View Post
Love this plugin for iPads! however.....

In come cases "CheckBoxTextBoxIcon06V1.0.0" (CBTBI) and "column_layout_grid_2_3_1" (CLG) don't play well together.
I suspect it may a simple matter of layout formatting.

On a clean test install (default classic template) of CLG merged with CBTBI everything is cool until you enable Display Cart Quantity and/or the add to cart/remove from cart buttons.
I could not determine what part (if any) of the code in tpl_modules_product_listing(dot)php controls the layout of that portion of the new code in CBTBI.

Display Product Add to Cart Button (0=off; 1=on; 2=on with Qty Box per Product; 3=on with Adj per Product) 3
Display Multiple Products Qty Box Status and Set Button Location 0
Display Check Box and Text Box for Checkout 0
Display Check Box for Checkout 0
Display Cart Quantity (0 - None, 1 - Greater than 0, 2 - Always) (1 or 2)
Display Product Description 150

Product Listing - Layout Style columns
Product Listing - Columns Per Row 4
Product Listing - Layout Style - Customer Control 0
Product Listing - Show Sorter for Columns Layout 0

The product to the right of the product you enable with the above mentioned features (And any following products) get shoved down the page
If you change the file tpl_modules_product_listing(dot)php provided by CGL back to the original (classic) tpl_modules_product_listing(dot)php the layout is correct.
What happens when you use the original tpl_modules_product_listing(dot)php file is the system picks up the tabular (Tables version) form of the layout and therefore there are no div's to deal with.
However it still does the column layout which puzzles me.



Attachment 13654

This is the additional code in the tpl_modules_product_listing(dot)php file by CGL to load the columnar layout.
<?php
/**
* load the list_box_content template to display the products
*/
if ($product_listing_layout_style == 'columns') {
if (PRODUCT_LISTING_GRID_SORT) {
echo "\n" . '<div id="gridSorter">' . PRODUCT_LISTING_GRID_SORT_TEXT . '<ul>';
for ($col=0;$col<sizeof($grid_sort);$col++) {
if ($grid_sort[$col]['text']) echo '<li class="item">' . $grid_sort[$col]['text'] . '</li>';
}
echo '</ul></div>' . "\n";
}
require($template->get_template_dir('tpl_columnar_display.php',DIR_WS_TEMPLATE, $current_page_base,'common'). '/tpl_columnar_display.php');
} else {// (PRODUCT_LISTING_LAYOUT_STYLE == 'rows')
require($template->get_template_dir('tpl_tabular_display.php',DIR_WS_TEMPLATE, $current_page_base,'common'). '/tpl_tabular_display.php');
}
?>
This plugin was originally developed on a template that included a CLG like installation. The tpl_modules_product_listing in essence coordinates how to present the individual items to be displayed (tabular versus columnar). In this case, each of those types call the product_listing module. In regards to the incorporation of CBTBI, the important part from here, is that the product_listing module provided does not include/incorporate the changes made by CLG; however, the instructions indicate that the changes made by CBTBI should be merged with the existing files of the site. Following the recommended style of installation, the CLG modified version of product_listing(dot)php should be located in the includes/modules/YOUR_TEMPLATE/ folder. The instructions indicate that the existing product_listing(dot)php file should be merged with the new version (either before or after installation; though preferably before) to maintain the presentation afforded by the CLG (or other) product_listing module.

The default version of product_listing (essentially included in this plugin) does not include columnar style layout and therefore, if not merged will result in a row like layout regardless of the settings associated with row/column.

Having already incorporated this into plugin into CLG related template, it would be good to include that development; however, one issue associated is making the installation flexible/understandable enough to work out. (Ideally, there would be a check that could be performed during installation so that the applicable product_listing(dot)php file could be uploaded/incorporated based on the installed template.) Perhaps can test against the options for the available display choices (rows and columns available versus "rows" (or whatever the default options are) only). If the options available are both, then incorporate the one type of product_listing(dot)php file, if only the default option then incorporate the default version of the file... If there are any suggestions, please feel free to offer!