Skip Navigation

[Gelöst] Custom field image does not work after upgrade to 1.7

This support ticket is created vor 7 Jahre, 7 Monate. 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.

No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 10:00 – 13:00 -
- 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 14:00 – 18:00 -

Supporter timezone: Asia/Kolkata (GMT+05:30)

This topic contains 3 Antworten, has 2 Stimmen.

Last updated by Vladimir vor 7 Jahre, 7 Monate.

Assigned support staff: Minesh.


When I try to add new image via repeating image custom field, it does not work. If I click on select image, nothing happend.

Firebug reports following error.
TypeError: is undefined
frame[$id] = ={

Thanks for help 🙂



Languages: Englisch (English )

Timezone: Asia/Kolkata (GMT+05:30)

Hello and thank you for contacting Toolset support.

Could you please try to check your issue by deactivating all 3rd party plugins as well as with default theme in order to check any possible conflict with any plugins/theme.

If your issue still persist:

Please send me exact steps to reproduce your issue.
*** Please take FULL BACKUP of your database and your website.***
In order to investigate your issue if we require to check things on your install in order to see what could be going wrong there.

If you agree to this please use the form fields I have enabled below this comment box to provide temporary access details (wp-admin and FTP)?

I have set next reply as private.



Languages: Englisch (English )

Timezone: Asia/Kolkata (GMT+05:30)

Please allow me to consult our developers and I'll get in touch with you as soon as I know more.


1.7.2 update fixed this issue 🙂