Jump to content

npn2531

Members
  • Content count

    1,159
  • Joined

  • Last visited

  • Days Won

    11

Everything posted by npn2531

  1. npn2531

    OSC to CSS v2

    The latest github post of 2.3 is a complete shop, with all the latest programming and security updates. OSC to CSSv2 will not have the 2.3 upgrades, as it installs on the existing version of OSCommerce. Otherwise the difference is in how the 960 grid tableless structure is incorporated, and these differences are not fundamental. But with both you are using the same 960 grid structure. I would make my decision not on these differences in how the 960 grid is implemented, but rather on whether or not you want to use the existing version of OSCommerce 2.2a or 2.3. To get a good understanding of these differences examine and compare the two files, includes/template_top.php and includes/template_bottom.php in both 2.3 and in OSC to CSS v2.
  2. npn2531

    OSC to CSS v2

    Leonardo, Paul has posted a little bit better search box than the stock search box. This looks like the one posted by 'Chris' uptread, which has the nice feature of clearing when you click on it.
  3. npn2531

    OSC to CSS v2

    Yes, first do a regular install of OSCommerce 2v2a and then overwrite the files.
  4. npn2531

    OSC to CSS v2

    It will say the full version, and try downloading from a different platform. It is a good download link and file, but you are not the first to have a bit of trouble. Look upstream on this thread and you will find a couple of other solutions that have been used.
  5. npn2531

    OSC to CSS v2

    It sounds like you may have gotten the OSC to CSS one page template contribution installed. Make sure you have installed this version of OSC to CSS: http://addons.oscommerce.com/info/7263 and are using the Sept 15 OSC to CSS v2 download on that page.
  6. npn2531

    OSC to CSS v2

    Hi Leonardo, I have run across the magnifying glass issue on my site as well. Here is the solution: Add this to a stylesheet: input.search-field{ /*input field */ float: left; } This will float the two elements, the searchbox and the image horizontally
  7. npn2531

    plcontentBoxHeading not found error

    OSC to CSS v1 and/or 2 is an addon for the stock OSCommerce 2.2a download that change changes the html structure of OSCommerce. Bill Kellum is correct, you need to pick either STS or OSC to CSS. One will not fit over the other as it now stands.
  8. npn2531

    OSC to CSS v2

    'a' beer?
  9. npn2531

    OSC to CSS v2

    Thanks! That's quite a list, geez.
  10. Thanks, was the p1 there to begin with? Also, what page is this from?
  11. Well, there is also OSC to CSS v2, but yes, 2.3 is also CSS 960 grid and frankly looks pretty good. 2.3 is going to have all the security updates. But now you are familiar with the grid system and that's worth a couple of days.
  12. I had to paste it a text doc and change the font before I was sure I was seeing a 1 instead of an L. If you find the place to fix it other than the stylesheet let me know. I can't believe I can't find it, I put it there (where ever there is) in the first place.
  13. Somehow you've got, instead of 'pl' (letter p letter l) in the products listing, a 'p1' (letter p number one) for the categories. I cannot remember where in the files the pl class is added (which is where it should be fixed) , but to test my theory, if you go to your stylesheet and add a p1 (letter p number one) to this, your categories should float horizontally. .pl, .pl-odd, .pl-even, .productlisting-new, .categorylisting{ float:left; border:1px solid #A6BFB9; border-width:0px 0px 0px 0px; margin:20px 10px 30px 10px; padding:10px 21px 18px 0px; width:150px; } change to: .p1, .pl, .pl-odd, .pl-even, .productlisting-new, .categorylisting{ float:left; border:1px solid #A6BFB9; border-width:0px 0px 0px 0px; margin:20px 10px 30px 10px; padding:10px 21px 18px 0px; width:150px; }
  14. Better a dumb mistake, than some unfathomable issue you struggle with endlessly!
  15. If you view the source on your page, you find this: <div class="grid_8" id="content"> <!-- /*** Begin Header Tags SEO ***/ --> if (isset($HTTP_GET_VARS['manufacturers_id'])) $db_query = tep_db_query("select manufacturers_htc_title_tag as htc_title, manufacturers_htc_description as htc_description from " . TABLE_MANUFACTURERS_INFO . " where languages_id = '" . (int)$languages_id . "' and manufacturers_id = '" . (int)$HTTP_GET_VARS['manufacturers_id'] . "'"); else $db_query = tep_db_query("select categories_htc_title_tag as htc_title, categories_htc_description as htc_description from " . TABLE_CATEGORIES_DESCRIPTION . " where categories_id = '" . (int)$current_category_id . "' and language_id = '" . (int)$languages_id . "'"); $htc = tep_db_fetch_array($db_query); ?> Somewhere after the '<!-- /*** Begin Header Tags SEO ***/ -->' and before the 'if(asset' there is a '<?php' needed. Once this is properly in place, and that code is rended as code and not as html, the out of place category/subcategory issue may resolve without you needing to do anything else.
  16. npn2531

    OSC to CSS v2

    Hi Paul, Can you provide a link or instructions to the 2.3 upgrade files? I'm not finding anything that says something like 'upgrade to 2.2 a to 2.3'. Thanks!
  17. Are you using OSC to CSS v2? I'm asking because in v1 there are some extra div tags in some the infoboxes put there in a less than 100% successful attempt to deal with those boxes wrapped in conditional statement in the left and right columns. My guess, however, is that from reading your 3 and 4 above, there is a typo somewhere. Almost always when I have code showing, it is a result of either dropping off the final '>' on some tag, or having a ?> or <?php out of place. Not hard things to do. If you want to pm or post a link to you site, I will take a look. BTW, did you see the lastest post today on 2.3? http://forums.oscommerce.com/topic/364291-oscommerce-v-23-when/
  18. npn2531

    OSC to CSS v2

    1) text on index page: open up catalog/index.php and look for the text and just retype. On that page I typed the text directly on the catalog page instead of using includes/languages/your_language/index.php (which is the usual OSCommerce method.) 2) The searchbox textbox and thus the maginifying icon is wrapping around to the next line, because the search box is too wide for the infobox. Open up that infobox, Brzo Nadi, and look for width="79" and change the width to a smaller number. Yes, using the grid system makes it so much easier.
  19. npn2531

    OSC to CSS v2

    1) Updated version The current version as posted is pretty much it and it works well. By updated I meant that I would take the four corrections I made after I posted the contribution and roll them into one download. They are not much more than fixing typos, and you can get it all by downloading what's here http://addons.oscommerce.com/info/7263 2) Faqs: It is this contribution: http://addons.oscommerce.com/info/7345. Since you already have the JQuery reference on OSC to CSS it is pretty simple to install. If you have trouble, pm me your email and I'll email you my copy of my faqs.php. But really installing the contribution is as easy as installing my file. I should have deleted that link before I posted the contribution 3) You can move the infoboxes really easy in OSC to CSS. Just put it's reference to the infobox anywhere you like. It's foolproof moving them from left col to right col, and no different than how you move them on the stock version of oscommerce. For example, to move the 'What's New' box just open up includes/column_right.php and copy this: require(DIR_WS_BOXES . 'whats_new.php'); and paste it in includes/column_left.php. You can paste it in the header or the footer for that matter, in OSC to CSS. Some boxes have a bit of code around them, but just pick that up as well to move it. For example to move the order_history box, you have to get all this: if($customer_id!=null){ require(DIR_WS_BOXES . 'order_history.php'); } That's just a little php that says, it the customer isn't signed on, don't bother displaying the order history box.
  20. npn2531

    OSC to CSS v2

    Wow, that seems kind of like driving two blocks to the corner store in your new BMW for a soda. But it probably works really well.
  21. npn2531

    OSC to CSS v2

    The 'target' is no big deal, and there must surely be an updated version of 'target' that validates. Check google. Target="blank" for example simple opens the link in a new window, a really common function. If you took out all the instances of target from the OSC to CSS nothing integral or important to OSC to CSS would be changed.
  22. npn2531

    OSC to CSS v2

    Thanks! converting to 2.3: Impressive! You are inspiring me to get this done as well as the W3 validation, and it is nice to know it can be done.
  23. For w3 validation, use <br />. However, you can argue that is it is a bit more 'professional', more visually consistent, to use a CSS class similar to what you mentioned above: <div class="spacer"></div> The reason is that the vertical space the <br /> clears, is tied to the line height at that point, plus you need more than one <br />to 'clear' an element such as an image that is taller than the line height, whereas with a class in the stylesheet you can control the top or bottom margin more consistently. for example: .spacer{ margin-bottom:5px clear: both; } or perhaps .spacer-tall{ margin: 5px 0px 5px 0px; clear: both; }
×