it seems my client has been fiddling and i cant seem to find out what he has done, desperate not to bother you again but stuck now:

www.topiary-balls.co.uk/component/virtuemart/topiary-balls-hotel-bed-and-breakfast-weddings-pubs-restaurants

any idea what is missing to stop the addtocartTiny.png image showing in the product hover ?

no rush - thanks

Hi,

Your client didn't do anything wrong, it is a SEF URL issue.
Open this CSS file:
/templates/it_theshop/html/com_virtuemart/assets/css/flexibleVM2Global.css

Find this CSS rule:
and change the IMAGE url with this:
It should appear now.
By the way, DarkMart is ready to go now ;)
The DEMO can be seen here:
www.flexiblewebdesign.com/virtuemart-2-template-darkmart/

Probably tomorrow it will be listed in flexiblewebdesign.com template library and will be on sale.
We are planing to change the pricing policy. Instead of increasing the price; we are planing to limit the domains that use our template. So we are going to keep the price low but charge each time the template is being used in each domain. Therefore, the updates will be free as well. The pricing is not clear yet, but it is going to be more or less something like that.

Ohh by the way, this template has been built on a strong base joomla template framework. So from now on, developing a new template will be easy for us. The more templates are on the way ;)

Regards.

The image now only shows up when in https as opposed to http - was probably like this before just spotted this by accident ?
any suggestions ?

will look at DarkMart now :-)

Does your secure hosting store files in a different folder?
Some hostings have different folder to separate HTTP and HTTPS://, and most them use the same folder (public_html)

Try to change that background image URL instead with this:
(Make sure the image URL is using HTTPS:// otherwise it would break the encryption.)

I am 100% sure this will work just fine in both situation

Regards.

yes thats cracked it - well done !!!
thanks

I am glad it worked out well.
It was obvious it was a SEF URL issue.

Case solved. Topic is closed.

Regards.
Forum Support.