Custom field images are still referencing url from dev site after migration

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

Problem: Several custom field images are showing the wrong URL. It appears to be generated using the original image guid.

Solution: Update to Types 3.2 to get the fix for this bug.

This support ticket is created 6 years, 3 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: Setting up custom fields, Types plugin

This topic contains 3 replies, has 2 voices.

Last updated by Christian Cox 6 years, 1 month ago.

Assisted by: Christian Cox.

Author

Posts

October 26, 2018 at 10:16 am #1134962

katieS

I am trying to: Site has just been migrated from dev site

Link to a page where the issue can be seen: hidden link

I expected to see: hidden link

Instead, I got: Images in types custom fields are still looking for dev site url

October 27, 2018 at 1:04 pm #1135450

katieS

I have been looking further into this problem and have narrowed down the issue.
All custom fields other than images are working fine.
When an image custom field is required in a content template it looks for a url from the old dev site despite the fact that the content of the field is an image with a url from the new site.

I have a workaround that would fix my immediate problem but it is not something that I want to have to use.

If I replace:
[types field='header-image-full' alt='%%ALT%%' title='%%TITLE%%' size='full' align='center']
with:
<img src='[types field='header-image-full' size='full' url='true'][/types]'>
then the image is rendered correctly.

However, this does not explain why the problem has arisen or, more importantly, how I can avoid it happening when future sites are migrated

October 28, 2018 at 2:42 pm #1135689

Christian Cox

Hi, there is currently an issue affecting Types image fields as well as featured image tags, where the image GUID is being used improperly to provide image URLs for standard-size images in certain cases. You can try clearing the image cache by going to Toolset > Settings > Custom Content, but if that doesn't work the permanent fix for this issue will be included in the upcoming Types 3.2 release. Sorry for the inconvenience here, our developers hope to have this upcoming version ready to release soon.

November 29, 2018 at 2:41 pm #1155518

Christian Cox

Hi, Types 3.2 is now available for download or automatic update. Please update to the latest version of all Toolset plugins and let me know if the problem is not completely resolved.