Images not being sized since latest plugin update

This thread is resolved. Here is a description of the problem and solution.

Problem: After updating to the latest version of Types, custom field images are being shown at full size instead of the desired custom size.

Solution: Go to Toolset > Settings > Custom Content and clear both image caches.

This support ticket is created 5 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

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)

Tagged: Views, Views plugin

This topic contains 3 replies, has 2 voices.

Last updated by zoeS 5 years, 10 months ago.

Assisted by: Christian Cox.

Author

Posts

June 21, 2018 at 6:29 pm #916319

zoeS

Hello, since updating Types and Views, the images are all being output at full size, ignoring the custom sizes set in the view. It still works for the whole tag but not for the URL only. Code used for the images on the home page is:

<img src="[types field='main-image' width='400' height='400' url='true'][/types]"/>

June 21, 2018 at 7:38 pm #916359

Christian Cox

Hi, can you try the following troubleshooting steps first?
- Temporarily deactivate all plugins except Types and Views, and activate a default theme like Twenty Seventeen. If you need to activate a maintenance mode plugin during testing that's fine.
- If the problem was resolved, reactivate your theme and plugins one by one until the problem returns
- If the problem was not resolved, go to Toolset > Settings > Custom Content and clear both image caches. Test again. If the problem is not resolved, check both checkboxes and test once more. If still not resolved, I'll need to take a closer look.

Let me know the results of these tests and we can go from there.

June 21, 2018 at 9:24 pm #916398

zoeS

Clearing the cache fixed it – that's good to know about, thank you very much Christian!

June 28, 2018 at 9:00 am #918705

zoeS

Actually spoke to soon, it's not resolved. I will re-open the thread.

This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.