bobinfrance

Will do – many thanks.

I can send you admin access if you’re happy to have a look?

No cache
SVI 3.2.17 – I haven’t changed anything and have deleted and re-installed
Redux 3.6.8
Woocommerce 3.3.4
WP 4.9.4

I’ve other plugins running, I have deactivated and tested but happy to repeat the exercise.

Is your pro version different enough, in this aspect, to suggest it might work? Happy to purchase to get it working as it should.

https://angeldemo.co.uk/tintin/product/2-tone-handbag/
temp front end username david
password svi

I’ve just looked at it in IE for the first time and it doesn’t appear to be loading the image at all – side issue for now perhaps – it loads as descriped above in Firefox.

Hi David,
Thanks for your help. I’ve done a regenerate with Regenerate Thumbnails plugin.
Am I right in thinking the background image in the code should be the full size original image and that’s how the zoom effect is achieved?

Without SVI I’m getting the standard zoom working fine with the theme(storefront) and woocommerce.

If it helps the code looks like this for the div class=”zoomLens”:
element {
position: absolute;
float: left;
height: 150px;
width: 150px;
border: 4px solid rgb(136, 136, 136);
background-position: 59.385px -328.186px;
background-repeat: no-repeat;
background-color: white;
cursor: pointer;
border-radius: 79px;
background-image: url(“https://my-site/wp-content/uploads/2018/03/black-2tone-416×416.jpg”);
left: -60px;
top: 324px;
display: none;
}
I’m assuming the background image should be the full size image not the cropped 416 one? In this case the original image is 1200 by 1200

OK thanks

Many thanks it’s a great plugin regardless.

If I wanted to add something to deal with this directly to my .htaccess file any advice on how to advoid redirection chains – I fully understand if this is an over the top question for here.

Thanks John,

When you say currently does that suggest it might be an option in the (near) future?

I have the same issue.
I have tried deleting and re-adding the and creating a new facebook app and neither worked.

Marc,

View the translated version of your product in the front end then go to the String Translation Module and you’ll find the custom attribute for that product there ready for translation.

(Naturally if that’s wrong David please correct me.)

Many thanks.

OK I can see that it’s working but I don’t think it’s the right way to do it in my humble opinion.

Would it not be possible to be able to enter the translation on the product page in the same way as the main text for the product. I understand this may not be possible or be far more complex for you but I think for an end user it would be a much better solution.

Requiring end users to go through this additional step is a real pain, I try and “protect” them from string translation but since the custom attributes are free text I don’t think I’m going to be able to in this case.

Thanks for the fix and I’d like to know what you think about those comments.

Thanks, my fault what I said was confusing.

No the attributes I am having a problem with are custom attributes and the issue is I can’t translate them. Any changes made in the second language are overwritten by the default language when I save.