Jump to content

burt

Team
  • Content count

    14,692
  • Joined

  • Last visited

  • Days Won

    595

Everything posted by burt

  1. burt

    HazMat fee for only some items

    There is a commercial addon for Hazmat available if you search Google.
  2. Yes, I'm not overly happy with that box in general, I'll take another look at it.
  3. Hi Ken Yep, the "best way" text is defined in the language file of the relevant shipping module. I coded it in such a way that if the "bestway" text is removed, then the extra helper text is also removed from the display in the choosable list in the shipping page. This way, what one could do is promote 1 shipping method over another, by removing all the "best way" rubbish and just having one that says "This is the fastest an most secure shipping method" or such words... -- In post #4 that is a change in the input box of the product, it's not a code change... -- Thanks for the heads up on the Colorbox update :)
  4. Hi Ken Many thanks for testing, I really appreciate it. I always thought the price was in the wrong line on the old file - as the "Best Way" text is just " helper" text to not the actual module being chosen, if that makes sense...that's why I changed it... Not sure on this one to be honest. That stepwizard is nice it's from Jamro's Snip here: http://bootsnipp.com/snippets/featured/process-steps
  5. Checkout Shipping Attached, could someone else test this on their install before I commit it - there's a lot of changes in this file... Also CSS: .stepwizard { margin-top: 20px; } .stepwizard-step p { margin-top: 10px; } .stepwizard-row { display: table-row; } .stepwizard { display: table; width: 100%; position: relative; } .stepwizard-step button[disabled] { opacity: 1 !important; filter: alpha(opacity=100) !important; } .stepwizard-row:before { top: 14px; bottom: 0; position: absolute; content: " "; width: 100%; height: 1px; background-color: #ccc; z-order: 0; } .stepwizard-step { display: table-cell; text-align: center; position: relative; width: 33%; } .btn-circle { width: 30px; height: 30px; text-align: center; padding: 6px 0; font-size: 12px; line-height: 1.428571429; border-radius: 15px; }
  6. burt

    Adding data to Action Recorder

    /includes/classes/action_recorder.php would be the place to start.
  7. Pages still to clean up: account_history_info checkout_confirmation checkout_shipping committed 03 March checkout_payment + language files + included modules (eg the payment modules for checkout_payment) + header changes + footer changes All other pages should be fairly close to being clean and bootstrapped.
  8. Hi Ken - many thanks for your time in testing. I've not yet gotten into the checkout procedure pages, I've been leaving that until last as it;s going to be a nightmare :(
  9. @@bruyndoncx I'm also in learning mode :) I'm just doing what "feels" right....and that could very well be wrong, but my aim is to get something very close to correct which can then be corrected further as time goes on. I backported the 2.4 category box infoBox which has no category counts, so the question you asked seems to have no answer...
  10. Test site is now updated; http://www.template.me.uk/2334bs3/
  11. Hi Ken Will update the test site when I get time ;) Those duplicate btn classes are correct - they aren't dupes (all those are "buttons" that look like buttons but are not passed throught the tep_draw_button function. Only time the dupes are a problem is if the button is made using tep_draw_button and has a parameter that includes just "btn" (if it has eg btn-primary, that's OK). These "fake" buttons are subject to change prior to "gold" release. But thank you very much for testing and posting. Please do continue to do so..
  12. I have no desire to add the ability for shopowners to destroy their Alt tags in the name of SEO. In other words: alt tags for images should never be used as an SEO strategy, not even as a mini part of it, and I won't help anyone do it.
  13. @@Tsimi - many thanks :) Button disappearing: https://github.com/gburton/osCommerce-2334-bootstrap/commit/5fa3731b803f2aac7324c8efe289b6557821a764 Login Page: https://github.com/gburton/osCommerce-2334-bootstrap/commit/abdd9419e85542ed452fa6fed08cbf3f97b9d74b
  14. Just looked at yours - putting the remove button underneath does help a bit. I feel that particular table is better without the class=responsive div...
  15. Here's my dev copy of create_account; http://www.template.me.uk/2334bs3/create_account.php Thoughts ?
  16. Hiding it on small viewports could be the way to go. I'll think on it. http://www.template.me.uk/2334bs3/shopping_cart.php add something to cart and reduce the viewport.
  17. @@mattjt83 - thanks for the heads up on the buttons. Fixed those. Adding that responsive class brings in problems in the table in the shopping cart - I'm going to leave it off for the time being until I can get to the bottom of it. Could you install on localhost and add the code, and you'll see what I mean on a small viewport.
  18. @@bruyndoncx - cast your mind back to when you made your own site responsive - how much effort did it take - I think a lot of time and sweat. This project is no different.. I could just have implement Bootstrap and say "that's it", but I also want to clean up some of the legacy code in the 2.3 series...some code that goes all the way back to 2000 !!, and I also want to introduce some HTML5 ready elements of code (such as the required form inputs in the example account_edit page and so on.
  19. Here's the rework of the account_edit.php page, not committed. Up it to your bootstrap test site to see how it looks... Also a couple of text changes (english.php, also remove the FORM_REQUIRED_INFORMATION from the middle of the file, and change as below): // message for required inputs define('FORM_REQUIRED_INFORMATION', '<span class="glyphicon glyphicon-asterisk form-control-feedback required"></span> Required information'); define('FORM_REQUIRED_INPUT', '<span class="glyphicon glyphicon-asterisk form-control-feedback required"></span>'); And in custom.css .required { color: #B33A3A; }
  20. Take a look at the tep_draw_button function, this is also changed. jqueryui is completely removed, shopwide 100%.
  21. I see what you mean, but we don't already have that type of architecture in the 2.3 series...so it would mean many more changes (both changes in the pages and changes in the functions/classes)...
  22. Considering doing something like this: <tr> <td class="fieldKey"><?php echo ENTRY_LAST_NAME; ?></td> <td class="fieldValue"><?php echo tep_draw_input_field('lastname', $account['customers_lastname']) . ' ' . (tep_not_null(ENTRY_LAST_NAME_TEXT) ? '<span class="inputRequirement">' . ENTRY_LAST_NAME_TEXT . '</span>': ''); ?></td> </tr> to <div class="form-group has-feedback"> <label for="inputName" class="control-label col-xs-2"><?php echo ENTRY_LAST_NAME; ?></label> <div class="col-xs-10"> <?php echo tep_draw_input_field('lastname', $account['customers_lastname'], 'required id="inputName" placeholder="' . ENTRY_LAST_NAME . '"'); ?> <span class="glyphicon glyphicon-asterisk form-control-feedback required"></span> </div> </div> Thoughts ? This changes the look as shown in the attached images.
  23. Mostly. If I have time I update the site to match the latest github. Could you show an example of something and the example function done in a page that would be better in a function ? And if you did not already have a responsive site? The answer would be the same or no ? What we're building here is a blueprint for the way forward...without input like Tsimi and Ken, the community gets what they get and has zero input on the end product. So, I ask everyone to take some time out and test the changes, make comments and then developers can work on some ideas... I'll update the test site this morning to match the latest Git.
  24. None at all - other than 3 new Header Tag modules that would need to be installed. 2 are required (datepicker and colorbox), 1 is optional (grid/list view, if not installed only grid view shows). Reason for these to be HT modules is so that the scripts are called only on the pages needed rather than site-wide.
×