This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|---|---|---|---|---|---|
| 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | 8:00 – 12:00 | - | - |
| 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | 13:00 – 17:00 | - | - |
Supporter timezone: America/New_York (GMT-04:00)
This topic contains 3 replies, has 2 voices.
Last updated by 5 years, 2 months ago.
Assisted by: Christian Cox.
I have a custom post type with a custom image field which all works fine. When I use the standard shortcode for adding a resized version of the logo to a view, this generally works, but not for .bmp files, e.g.:
[types field='logo' title='%%TITLE%%' alt='%%ALT%%' size='custom' width='100' height='100' resize='pad' padding_color='#ffffff']
For jpg or png files, the url of the resized image will be something like:
.../wp-content/uploads/2019/09/animage-wpcf_100x100-pad-16777215.png
but for bmp files, the resulting url is:
.../wp-content./anotherimage-wpcf_100x100-pad-16777215..jpg
A '.' is added after 'wp-content', another before the file extension and the wrong extension is used.
I encountered this on an existing site, but have set up a clean WP install and added only Toolset Types and Views (no other plugins or themes) and the same thing happens.
This error doesn't occur using standard image sizes, e.g.:
[types field='logo' title='%%TITLE%%' alt='%%ALT%%' size='thumbnail' resize='pad' padding_color='#ffffff'][/types]
The net result is shown in the attached image. In the table, the "Logo - custom" uses the custom resizing in the first shortcode above (size='custom'...). In the column "Logo - thumbnail", it using the second shortcode (size='thumbnail').
