Jump to content


  • Content count

  • Joined

  • Last visited

  1. arbr

    [Contribution] oscThumb

    Ok, played around a bit more. The main issue is that the contrib also affects the tep_draw_separator function. If we can find someway to avoid the contrib messing with this function and just let it put 'height and 'wídth' in the HTML, than all should be fine. There is no need to mess with the size of spacer.gif or comparable images as this will almost always result in design issues.
  2. arbr

    [Contribution] oscThumb

    Problem located: if ($width) { $image .= ' w="' . tep_output_string($width) . '"'; } if ($height) { $image .= ' h="' . tep_output_string($height) . '"'; } The original html_output sets width and height for all images, the contrib only when it has to change dimensions. This results in the strange problems with the images. Anybody a suggestion on how i can force that for every picture there is dimension specified, even if the image is already that size? Correction: it seems that the script sometimes loads some essential images like spacers with 'h=' and 'w=', which messes up the design. The only problem is, when changing h to height and w to width, the design is fine, but the product do not load properly resized...
  3. arbr

    [Contribution] oscThumb

    Here's an interesting one: - Installed oscThumb, without a single problem - Contrib works fine, resizes images just the way i want it - BUT: some background images run into trouble. As soon as i turn on the contrib some background gif's and jpeg's just repeat themselves or become transparant. To be clear: these are the page images, not product images, the product images work fine. - AND: it seems it works with more contribs like this. - SO: might this be a GD problem, is it in the contrib or am i overlooking something. I have the most current version of GD2 on PHP5 - by the way: VERY nice plug-in, easy to install, simple configuration, good job!
  4. I'm not sure if this has been posted yet, but just to be sure: When trying to install a new install SQL the script will give errors on all 'insert into' when using MySQL5. I'm not sure if mysql5 is even officially supported and there probably is a config possible to avoid this error as it occurs on: insert into <table> values ('' The auto increment demands a number and cannot handle 'null' input. If you use a 0, everything will work fine. Another way is to configure mysql to accept null as an autoincrement, but mysql5 does not accept it out of the box. Of course somebody must have noticed this before and i was wondering what their solution was.