Can't update catalogue image sizes

[leewillis77]

Using latest git as of time of report, any attempt to update the image size settings ( WooCommerce > Settings > Catalog > Image Options ) results in them just defaulting back to standard. It looks like they do temporarily get saved in the DB, but then get overwritten again somewhere.

[mikejolley]

I think they are being forced by the theme; woostore? WooTique?

[studioromeo]

Check for !important declarations ;) Those badboys will override absolutely everything which is why I try and avoid them. Failing that any CSS height/width thats applied to an image will override it's standard height/width values.

Easy way to check if your in chrome/firefox is to right click on the image and click on inspect element.
Firefox will need firebug installing first though (https://addons.mozilla.org/en-US/firefox/addon/firebug/).

Hope this helps :)

[mikejolley]

@studioromeo - your right the CSS affects images sizes on the front-end, but in this case I think lee is referring to the actual saving of the image sizes in settings - few of the themes are currently forcing the size options.

[studioromeo]

@mikejolley that's true although the user defined values should never be overridden no? It could be a number of things however css is where I would check first with any presentation related issue. Inspecting elements reveals all..nearly :D

[leewillis77]

Mike's on the money. It's the settings in the admin that don't hold the user-entered values. He's also right that it's the theme that's resetting them (Wootique in this case). So this is probably a "bug" in Wootique. Ideally these fields would show as disabled (With a message) - although I guess woocommerce needs a patch to support that - there doesn't seem an obvious filter to allow this (The options array is filtered, but I can't see a way of toggling disabled/enabled or adding extra content.

[mikejolley]

I've made the options clearer, and instructed Jay to only change the value on theme install so they can be changed by the user if they make customisations. That should clear up the issue for now.