Jump to content
Latest News: (loading..)

Tsimi

♥Ambassador
  • Content count

    2,260
  • Joined

  • Last visited

  • Days Won

    81

Tsimi last won the day on September 2

Tsimi had the most liked content!

Profile Information

  • Real Name
    Lambros
  • Gender
    Male
  • Location
    Japan

Recent Profile Visitors

37,665 profile views
  1. Have taken a look at this following add-on? https://apps.oscommerce.com/pA5xs&ajax-product-listing-bootstrap
  2. That depends which version of osC BS exactly you have. I guess in your case the EDGE version? If yes, then to remove that green message just uncomment the messagestack part in the buy_now case inside the application_top.php file FIND case 'buy_now' : if (isset($_GET['products_id'])) { if (tep_has_product_attributes($_GET['products_id'])) { tep_redirect(tep_href_link('product_info.php', 'products_id=' . $_GET['products_id'])); } else { $cart->add_cart($_GET['products_id'], $cart->get_quantity($_GET['products_id'])+1); $messageStack->add_session('product_action', sprintf(PRODUCT_ADDED, tep_get_products_name((int)$_GET['products_id'])), 'success'); } } tep_redirect(tep_href_link($goto, tep_get_all_get_params($parameters))); break; REPLACE WITH THIS case 'buy_now' : if (isset($_GET['products_id'])) { if (tep_has_product_attributes($_GET['products_id'])) { tep_redirect(tep_href_link('product_info.php', 'products_id=' . $_GET['products_id'])); } else { $cart->add_cart($_GET['products_id'], $cart->get_quantity($_GET['products_id'])+1); //$messageStack->add_session('product_action', sprintf(PRODUCT_ADDED, tep_get_products_name((int)$_GET['products_id'])), 'success'); } } tep_redirect(tep_href_link($goto, tep_get_all_get_params($parameters))); break; If you use the Frozen version then you can either create a new buy_now action module to avoid core code changes or just do the same thing I showed above inside the existing buy_now action module. Regarding the page reload that is a different story. osC needs to refresh the page to pass on the paramaters, I think. Using this code here tep_redirect(tep_href_link($goto, tep_get_all_get_params($parameters))); If you don't want a page reload then my guess would be to use AJAX but that is not easy like 1,2,3. You will have to either hire someone to code that for you or search the forum if someone has ever done such work in the past.
  3. Tsimi

    Shopping cart button modification

    in your shopping_cart.php file look for this code around line 100 $products_name .= '<br>' . tep_draw_input_field('cart_quantity[]', $products[$i]['quantity'], 'style="width: 65px;" min="0"', 'number') . tep_draw_hidden_field('products_id[]', $products[$i]['id']) . ' ' . tep_draw_button(CART_BUTTON_UPDATE, 'fas fa-sync', NULL, NULL, NULL, 'btn-info btn-xs') . ' ' . tep_draw_button(CART_BUTTON_REMOVE, 'fas fa-times', tep_href_link('shopping_cart.php', 'products_id=' . $products[$i]['id'] . '&action=remove_product'), NULL, NULL, 'btn-danger btn-xs'); remove the btn-xs class from both buttons so that it looks like this $products_name .= '<br>' . tep_draw_input_field('cart_quantity[]', $products[$i]['quantity'], 'style="width: 65px;" min="0"', 'number') . tep_draw_hidden_field('products_id[]', $products[$i]['id']) . ' ' . tep_draw_button(CART_BUTTON_UPDATE, 'fas fa-sync', NULL, NULL, NULL, 'btn-info') . ' ' . tep_draw_button(CART_BUTTON_REMOVE, 'fas fa-times', tep_href_link('shopping_cart.php', 'products_id=' . $products[$i]['id'] . '&action=remove_product'), NULL, NULL, 'btn-danger'); now you should have bigger update and delete buttons. For the popup on mouse over you could use tooltips to show what the buttons actually do. Check here for more info https://getbootstrap.com/docs/3.3/javascript/#tooltips For example something like this $products_name .= '<br>' . tep_draw_input_field('cart_quantity[]', $products[$i]['quantity'], 'style="width: 65px;" min="0"', 'number') . tep_draw_hidden_field('products_id[]', $products[$i]['id']) . ' ' . tep_draw_button(CART_BUTTON_UPDATE, 'fas fa-sync', NULL, NULL, NULL, 'btn-update btn-info data-toggle="tooltip" data-placement="top" title="' . TEXT_BUTTON_UPDATE . '"') . ' ' . tep_draw_button(CART_BUTTON_REMOVE, 'fas fa-times', tep_href_link('shopping_cart.php', 'products_id=' . $products[$i]['id'] . '&action=remove_product'), NULL, NULL, 'btn-delete btn-danger data-toggle="tooltip" data-placement="top" title="' . TEXT_BUTTON_DELETE . '"'); At the very bottom of the shopping_cart.php file add <script>$(function () { $('.btn-update, .btn-delete').tooltip() })</script> Then add the language definitions and that's it. define('TEXT_BUTTON_UPDATE', 'Update cart'); define('TEXT_BUTTON_DELETE', 'Remove item');
  4. @chuntse This is what I said in the first post of this thread. A horizontal menu is not always the right solution for everyone. There is a Horizontal Megamenu made by Kymation if you want to have a look at that. The horizontal menu in my add-on is just an "extension" of the existing category_tree class meaning that whatever change you apply there (category_tree.php) affects all category menus in the store. So if you limit the categories to a certain amount then it will also limit the categories box. Not sure restricting the categories makes any sense though. Customers would not be able to see all what you have to offer. Another solution would be to copy the category_tree.php class file, rename the functions and all the necessary codes, apply your query there to limit the categories and then extend the horizontal menu from it. That way you can have the categories box with the stock osC layout and the horizontal menu with the limited categories listing. Hope that makes sense. (your_category_tree.php) class your_category_tree { (your_catmenu.php) class explode_your_category_tree extends your_category_tree {
  5. Here is a new version of the Horizontal Menu BS (v1.5). This one is made with CSS only and not using any javascript or jquery. It uses hover, meaning that when you mouse over the category names the drop down tab opens up. However you will have to use this new menu in conjunction with the Categories Menu XS since this new menu cannot be used on XS or SM view port due to lack of touch support. Special thanks to @rulegacy for the pure CSS and hover idea and for testing the menu. Here the package: Horizontal Menu BS v1.5.zip Enjoy!
  6. Tsimi

    KissIT Image Thumnailer

    You can keep the code in there. It shouldn't matter if you use later the horizontal menu or not.
  7. Tsimi

    KissIT Image Thumnailer

    @ce7 Open your ..includes/classes/category_tree.php file FIND: if ( ($this->follow_cpath === true) && in_array($category_id, $this->cpath_array) ) { $link_title = $this->cpath_start_string . $category['name'] . $this->cpath_end_string; } else { $link_title = $category['name']; } REPLACE WITH: if ( ($this->follow_cpath === true) && in_array($category_id, $this->cpath_array) ) { $link_title = $this->cpath_start_string . tep_image('images/' . $category['image'], $category['name'], SMALL_IMAGE_WIDTH*0.5, SMALL_IMAGE_HEIGHT*0.5, 'style="display:inline-block;"') . '&nbsp;' . $category['name'] . $this->cpath_end_string; } else { $link_title = tep_image('images/' . $category['image'], $category['name'], SMALL_IMAGE_WIDTH*0.5, SMALL_IMAGE_HEIGHT*0.5, 'style="display:inline-block;"') . '&nbsp;' . $category['name']; }
  8. @rulegacy I see... Ok let's try the following. First let's add a new custom class to avoid conflicts with other dropdown classes. Open your ../includes/classes/catmenu.php file and look for this code $root_start_string = '<li class="dropdown">', add a new class, in this example I use yourclass (*you can name that whatever you like just make sure you also change the css definition as well.) $root_start_string = '<li class="dropdown yourclass">', Save and close the file. Next let's add the new css definitions inside the user.css file .dropdown-submenu a {text-transform:none;} .yourclass > a {text-transform:uppercase;} Make sure the css code is inserted exactly like that. If you would switch those 2 new css definitions around it won't work. Now you should have all Caps in the first categories only and the rest below inside the sub-menus should be normal.
  9. @rulegacy Your css code gives me this. Is that not what you want?
  10. Of course the example used above is not ideal. You wouldn't choose 16MB and 32MB RAM it would be one or the other. But what if you have a Pizza store and let's say there is an Option called toppings. Do you wanna create one separate option for each topping? Toppings: - Cheddar cheese - Mozzarella cheese - Olives - Pepper - Salami - Bacon - Bugs and so on... Customers should then be able to tick what ever they want and then all gets added to the cart in one go. What you did is add Option: Memory -> Value: 32 MB and Option: Model -> Value: Deluxe Those are two separate options and values. What needs to work is Option: Memory -> Value: 16MB and 32MB
  11. @JcMagpie Thanks. The checkboxes are not a big issue. The main problem when using checkboxes is you cannot pass on multiple values to the cart. For example in your screenshot let's say you tick the 16MB and 32 MB option and then click on add to cart it will only pass on 1 of those option values and not both. The osCommerce core code won't allow you to pass on multiple option values to the shopping cart. It was never necessary with stock osC features which is the select dropdown which allows you only to select one option value. That is what the TC wants to solve and that is what I am willing to pay for. It shouldn't be a big thing to re-code for an experienced osC coder the question is are 50 bugs/bucks enough? If someone else wants to pool in don't be shy.
  12. @Dan Cole 50 bugs or 50 bucks it's the same depending in which country you live. lol Some consider bugs more valuable than paper.
  13. I think this is one of the bigger cons by osCommerce. Not being able to pass on multiple options_values to the cart sucks when it comes to extending the attributes features. osC never needed such function because it only uses select drop downs to select options which is good but just not enough to cover all shop types especially for clothing stores and PC shops. These days multiple checkbox selections, radio buttons and input fields should have been a standard shop feature 10 years ago. Just another thing osC lags behind other carts. Therefore I am putting a $50 bounty on this. I pay $50 bugs to the person who can code this up. The only condition I have is that it will be shared with the whole community later on. If you out there are up to it speak up.
  14. Thanks @Demitry for helping out. I think what she means is, when you add the css code you posted it will also change the looks of the links within the navbar since those also use the same classes. Best would be to give it a new, unique class that only refers to that parent category link. For example; Inside the ..includes/classes/catmenu.php file FIND $root_link_title = '<span><span class="fas fa-list"></span>&nbsp;' . $link_title . '</span>'; REPLACE WITH $root_link_title = '<span class="parent"><span class="fas fa-list"></span>&nbsp;' . $link_title . '</span>'; We added the class parent for this example. Name it whatever you want later. Then add this to your user.css file .parent { color: red; } This should have changed the parent link color to red. Change the css code to whatever you like.
  15. Tsimi

    [Contribution] Option Types v2

    That was like that from the very beginning it has nothing to do with BS or add-on version. The person who coded it, Zappo, mentioned something like this in the past that only one checkbox value can be passed on to the cart.
×