njohn Posted August 28, 2016 Share Posted August 28, 2016 On ALL of the T-Shirt products the select size drop down includes additional items not found in products option window: See example images attached. How can I delete SM+19.99, LG+19.99, and XLG+19.99 ? For some reason Med not included. Quote Link to comment Share on other sites More sharing options...
bsmither Posted August 28, 2016 Share Posted August 28, 2016 Not seen anything like that before! Do you have any plugins enabled that may affect options? I will dismiss any edits having been made to the skin template as that would show the extraneous choices grouped together. Quote Link to comment Share on other sites More sharing options...
bsmither Posted August 28, 2016 Share Posted August 28, 2016 In the browser viewing the storefront, ask it to show you the HTML of the page. You will be looking for the drop-down selector code. It will look something like... <div class="row"> <div class="small-12 columns"> <label for="option_1" class="return">Colors</label> <select name="productOptions[1]" id="option_1" class="nomarg" > <option value="">-- Please Select --</option> <option value="10" data-price="0">Black</option> <option value="6" data-price="0">Blue</option> <option value="2" data-price="0">Red</option> </select> </div> </div> ...but with wild spacing - probably. That depends on what skin you are using. All of the option values (example, 10, 6, and 2 above) are what we need to examine this further. Quote Link to comment Share on other sites More sharing options...
njohn Posted August 28, 2016 Author Share Posted August 28, 2016 If I understand what you ask, It shows: <div class="row"> <div class="small-12 columns"> <label for="option_11" class="return">Select Size (Required)</label> <select name="productOptions[11]" id="option_11" class="nomarg" required> <option value="">-- Please Select --</option> <option value="366" data-price="19.99">SM +$19.99</option> <option value="359" data-price="0.00">SM</option> <option value="365" data-price="0.00">Med</option> <option value="364" data-price="19.99">Lg +$19.99</option> <option value="360" data-price="0.00">Lg</option> <option value="362" data-price="0.00">XLg</option> <option value="363" data-price="19.99">XLg +$19.99</option> <option value="358" data-price="2.00">XXL +$2.00</option> <option value="357" data-price="3.00">3XL +$3.00</option> </select> </div> </div> Only using "Authorize" and "By Weight" Using default skin- Foundation Quote Link to comment Share on other sites More sharing options...
bsmither Posted August 28, 2016 Share Posted August 28, 2016 Ok. Now we need to look at the daabase using an external utility such as phpMyAdmin. Look at the contents of the table CubeCart_option_assign. Find the rows where 'assign_id' is 363, 364, and 366. Take note of the numbers in the rest of the columns. The 'option_id' should be 11. The 'product' should be the product_id of this T-shirt. If there is anything other than a zero in 'set_member_id', we then need to look in the table CubeCart_options_set_product. Do you recall working the page at admin.php?_g=products&node=optionsets? These issues are still open, but I do not know if they apply to this situation. https://github.com/cubecart/v6/issues/788 https://github.com/cubecart/v6/issues/1060 You can try to manually delete the rows found for the 'assign_id' values identified above. Quote Link to comment Share on other sites More sharing options...
njohn Posted August 28, 2016 Author Share Posted August 28, 2016 I don't think I ever worked with admin.php?_g=products&node=optionsets? <?php /** * CubeCart v6 * ======================================== * CubeCart is a registered trade mark of CubeCart Limited * Copyright CubeCart Limited 2015. All rights reserved. * UK Private Limited Company No. 5323904 * ======================================== * Web: http://www.cubecart.com * Email: [email protected] * License: GPL-3.0 https://www.gnu.org/licenses/quick-guide-gplv3.html */ if (!defined('CC_INI_SET')) die('Access Denied'); Admin::getInstance()->permissions('products', CC_PERM_READ, true); ## Option Sets - Assign if (isset($_POST['set'])) { $updated = false; foreach ($_POST['set'] as $set_id) { foreach ($_POST['product'] as $product_id) { $set_search = array('product_id' => (int)$product_id, 'set_id' => (int)$set_id); if (!$GLOBALS['db']->select('CubeCart_options_set_product', array('set_product_id'), $set_search)) { if ($GLOBALS['db']->insert('CubeCart_options_set_product', $set_search)) { $updated = true; } } } } if ($updated) { $GLOBALS['main']->setACPNotify($lang['catalogue']['notify_option_sets_updated']); } else { $GLOBALS['main']->setACPWarning($lang['catalogue']['notify_option_sets_already_assigned']); } httpredir(currentPage()); } ############################################# $GLOBALS['main']->addTabControl($lang['catalogue']['title_product_list'], null, currentPage(array('node'))); $GLOBALS['main']->addTabControl($lang['catalogue']['product_add'], null, currentPage(array('node'), array('action' => 'add'))); $GLOBALS['main']->addTabControl($lang['catalogue']['title_category_assign_to'], null, currentPage(null, array('node' => 'assign'))); $GLOBALS['main']->addTabControl($lang['catalogue']['title_option_set_assign'], 'assign'); $GLOBALS['gui']->addBreadcrumb($lang['catalogue']['title_option_set_assign'], currentPage()); ## List option sets if (($option_sets = $GLOBALS['db']->select('CubeCart_options_set')) !== false) { $GLOBALS['smarty']->assign('OPTION_SETS', $option_sets); } ## List products if (($products = $GLOBALS['db']->select('CubeCart_inventory', false, false, array('name' => 'ASC'))) !== false) { $GLOBALS['smarty']->assign('PRODUCTS', $products); } But I do recall that originally those (19.99 price) options were originally assigned because the product price was set at Zero and and price was assigned when the size was selected on the drop down. This resulted in the price on the product window was shown as Zero which caused complaints SO I changed to to the layout now shown. However the Med was originally set at 19.99 and THIS was NOT carried over (??). I deleted 363, 364, and 366 from db and THAT took care of the problem for that product. However I have 30+ products with the same problem and hope we can find a way to correct without doing "all of the above" 30+ times. Never the less thank you for your assistance so far! Quote Link to comment Share on other sites More sharing options...
njohn Posted August 28, 2016 Author Share Posted August 28, 2016 Found a way to speed up corrections. AOK now. Thank you!!! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.