@boochamoocha Doesn’t WooCommerce use default thumbnail images? In that case you probably can do (like in the Image Cookbook):
<img src="{{ post.thumbnail.src|letterbox(250, 250, '#FFFFFF') }}" />Remarks
- If you’ve got an image attachment id that you want to convert to a Timber Image, you might want to use
TimberImage(except when you addedImageas a shorthand forTimberImageyourself). - You can’t use as hex color value with the resize filter. The third parameter for
resize()defines how you want to crop the image. Instead, you need to use theletterboxfilter. - You can always use
{{ dump(yourvariable) }}to debug variables.
Previously I just made
TimberImage() objects from all types of files because that seemed to work. At some point the .srcmethod/property seemed to stop working for non-images though
Now I'm wondering what would be the best way to deal with an ACF repeater which has file fields. I would like to be able to get the file url in the same way for all items, but now it seems I can't or it's a bit tricky.
I mean, I can't wrap all items in
TimberImage() because not all of them are images. I also wouldn't want to handle all those files as default WP attachment objects, because I'd like to access the thumbnails easily with Timber features.
Looks like Timber\Image extends Timber\Post. But looking even further, it looks like the Timber\Image::src method should be checking to see if it is an image or not, and returning the url appropriately https://github.com/timber/timber/blob/master/lib/Image.php#L444
thank you for pointing me in the right direction, i just need to wait until the new release is available @stevep
no prob
Good news for i18n and Timber: Twig support arrived in Poedit. You can download the latest beta version of Poedit 2 from https://poedit.net/download. What this means:
- You can use
__(),_x(),_n()and_nx()in your Twig files, just like you would do use them in your PHP files. - No more custom extractors based on the Python parser. No more Twig-Gettext-Extractor. Disable your custom extractor and you’re good to go.
- Translations inside HTML tags that didn’t work with custom extractors are now recognized. E.g.
<button role="button" aria-label="{{ __('My Label', 'my-text-domain') }}">works just like you would expect.
is it faster when i use real po files?
woa wpml is complicated
nvm
wpml does not save in the theme folders everything ok then :D
We cannot get twig function {{ dump(record) }} to work, possibly because DEBUG is not set to true, which is not configured the way WP normally does because in this case we use Azure/Docker (for a reason, long story).
So, how can I check on the frontend whether debug is true?
otherwise use the print_r filter
its awesome
and then i do
if ( defined( 'WP_DEBUG' ) && true === WP_DEBUG ) {
TimberHelper::function_wrapper( 'pc_debug' );
}
function pc_debug( $some ) {
PC::debug( $some );
}
and in timber {{ pc_debug(whatEver) }}
and get the stuff in my console in chrome
but dont forgot to remove all pc_debug things in production
or maybe just add else and create a new pc class with a static debug and just return nothing
i hate this big ass arrays
i need the php code later
i dont merge my dev db with the production db xD
i was thinking about create a
small electron app
to generate this
in wpml i see very old fields
this sucks