Profile: europhile

Hi, even on latest 3.70, the currencyselector shows horribly clunky on every page, ruining the nice clean look of header and template. We had this in V3.50 but fixed it, although I think the code has changed. So far, I have reduced impact by fixing the styles.css reducing font from 16px to 12px - that's a relief:

        .header-currencyselector .styleSelect_item li span {
            font-size: 12px;

However, the drop-down box container is too short to hold single line text (Euro ok, but British Pound and US Dollar hit 2 lines, which then looks messy) - this need to be sized (lengthened) properly, can you advise best way to do that, thanks!

Hi, am using the Blog posts more now and the links are not highlighted, so effectively useless to users!

They work fine under Categories, so should be the same format as those (coloured, bold and underlined). TIA, Phil.

Hi - on Forums, the Search magniifying glass is missing, just a blank grey square! Could do with that as otherwise all is good with forums! Any quick fix appreciated, expect you can build it into any new releases. Phil.

Ah, so it's not auto adjustable to shrink to size of image - that would be ideal but maybe not easy I expect! Have sent url to Milen for you.

There are mixed images but would be happy to make them all a third of size if nec. If you give me the best place to adjust css or cshtml I can apply any size no prob - would be greatly appreciated! Phil.

Thanks Boyko, but unfortunately if I half the standard nopCommerce "product detail image size" from standard 300 to 150px, it actually halves the size of the picture, but your template still leaves the same huge amount of whitespace after it! Try it (with a fairly small product image) and you'll see what I mean.

So we need to adjust that somehow! Sorry to be a pain, but it's ruining all the other great design with this layout, and many users won't realise there is more content following (need the scroll bar).

Thanks for your attention, Phil.

Hi, some of our product images (both grouped and simple) are small - but the image displayed is so huge and its surrounded by white space - that you can't even see the content (text, price etc) below - some users will assume that is it and not realise you have to scroll down.

What's the best place (presume in CSS) to resize these product image areas? It would be ideal to just have an automatic sizing of course, so that huge whitespace is not included - these images do not have whitspace in them, it is purely generated by the template. However, if not poss, a manual resize is needed!

I'm not using the cloud zoom, just straight Motion theme, although when i did use it, it did not seem to resolve the issue.

TIA, Phil.

Excellent - SKU now there on grouped prods, layout and social bits better too, really good - thanks for quick turnaround also! Cheers, Phil.

Ah yes, applied and double line better now, thanks! Love your clear code, structure and comments. And this one def a good fix for wider release.

Glad you're going to fix back the description and SKU (easier for people to take out rather than put in) - highly appreciated! Even better if you let me know when, or I can apply a code change if nec and there's a long release schedule.

Appreciate your observation on the SKU on Categories, indeed we're not going to be able to have them on those pages yet thanks to source, will bring it up with nopCommerce when have a chance. Meanwhile, as long as on product pages (more important), will suffice!

Keep up the great work! Phil.

Nice one, .topic-wrapper {text-align: left;} does the trick, that's a good way to sort it! Cheers! Phil.

Hi, great menu (v3.20) - like it! However, if you add a MegaMenuTopic, it displays all the text in the ajax drop-down panel as centred!

This doesn't make sense because the Topic is a content page just like any other Topic, so is highly unlikely to be centred text - it's going to be normal text. In fact, clicking this actual menu button will load that page- so why is the panel displaying it differently to the page? That's why this seems to be a bug / design oversight, and it looks a mess! Thanks, Phil.