Forum Replies Created
I got the same and even worse problem.
First, do not trust the WordPress thumbnails resizer, what you get is just good to trashcan, unless your pictures are strictly squared (amazing, isn’t it ?)
You’ll have to resize them by yourself. The best way to do this is to use a batch images resizer which is smart enough to resize your pictures using the greatest dimension of our image to be resized (not that easy to find). If you are a lucky Mac OS/X user, just pick the Automator app up, it will do it in a blink, it can either rename, move copy, whatever you want.
Second, since neither Woocommerce (here 1.5.8 version) nor Abundance (1.3.2 version) are able to manage any new image featured sizes through the Woocommerce>Catalog>Images options, for the first one, or through /web-content/themes/abundance/woocommerce-config/config.php, for the second, you may spend a year resizing images, your images would be cropped since the containers sizes and their own sizes will never match.
The solution I used, after removing and reinstalling everything merely from the scratch with no improvement, is quite a “dirty” solution : let’s be more clever than the plugin ! They expect 300×300 px to match a 200×200 px (catalog list) or a 279px container to match a 350x350px (no kidding !) image (product details page) ? Easy :
1 resize the image to match their containers,
2 rename them as expected by the framework.
For instance, I have tweaked the catalog list image containers sizes through custom.css, I use 130x130px resized images and I renamed them 300×300. Regarding the product detail page, the inner image should match 269x269px (beware !), I resized my images to these dimensions and then renamed them 350×350. That’s rather dirty but that’s quite tricky.
Moreover, my lightbox featured image option is definitively broken. I don’t have the faintest idea why. It wouldn’t have been a big deal if the choice of using the zoom or the lightbox option might have been optionally offered as a per default global option. That means I’ll have to check it manually. Days and days of work just to have these plugins working fine like they did in the past, at least they work fine for me in the previous versions.
Hope this might have been useful.
Keep in mind this is an “alpha” release.
download the file wherever you want
copy the 4 files (fr_FR.po, fr_FR.mo, en_GB.po, en_GB.mo) in you abundance/lang subfolder
(optional) remove dafault.po and default.mo files
enjoy it !
Voici la première version “alpha” des fichiers de traduction pour abundance. Cette version est fonctionnelle et peut très facilement être customisée ou améliorée grâce au plugin que j’ai mentionné dans mon précédent message.
Guide pas à pas :
télécharger l’archive ici :http://www.mediafire.com/download.php?yp6k9sg3hg74t7o
décompresser le fichier où vous le voulez
copier les 4 fichiers inclus (fr_FR.po, fr_FR.mo, en_GB.po, en_GB.mo) dasn le sous-dossier abundance/lang
(facultatif) supprimer les fichiers dafault.po et default.mo
Et normalement ça doit passer en français !
I have released the first French translation with CodeStyling Localisation (http://www.code-styling.de/english/development/wordpress-plugin-codestyling-localization-en), a great plugin !
Please, let me know how to upload the files: fr_FR.po/mo and en_GB.po/mo (former default.po/mo).
The translation is working fine, though I guess it might easily be improved and customized.
I’d like to stress out one major point regarding the translation issue. The front-end switches automatically to WordPress installation language BUT the avia sub nav, since it uses plain text strings in config.php > function avia_shop_nav().
Dude, is possible to tweak it passing parameters or querying any po/mo file according to the localization ?
That would be kind of you.