Skip Navigation

[Resolved] Relationships crashing – Beta

This support ticket is created 6 years, 8 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.

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
- - 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00 14:00 – 20:00
- - - - - - -

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

This topic contains 3 replies, has 2 voices.

Last updated by Beda 6 years, 8 months ago.

Assisted by: Beda.

Author
Posts
#621704
Screen Shot 2018-03-03 at 11.15.11 PM.png

Not sure where to leave beta feedback.

I have been testing the new system with one of the sites I will need to update for the new relationships and API.

On Movie CPT connected to Person CPT by Casting Relationship - many to many with fields.

The Movie CPT has a field group, including a WSYIWIG editor for Movie Synposis.

Editing the Person CPT. Added Movie in Casting relationship.

- Quick Editing the Casting Relationshsip
-- Enabled the protected Movie Fields for Editing

--- Wysiwig synopsis field wouldn't take input in visual editor
--- Wysiwig synopsis field did take input in text editor

---> ERROR on saving
---> Page reloaded and all relationship metaboxes disappeared from Person.
---> Movie is now uneditable causes Whoops Crash.

Debug Error:

Whoops\Exception\ErrorException thrown with message "parse_url() expects parameter 1 to be string, array given"

Stacktrace:

#12 Whoops\Exception\ErrorException in /app/public/wp-content/plugins/wp-views/vendor/toolset/toolset-common/toolset-forms/classes/class.file.php:95
#11 parse_url in /app/public/wp-content/plugins/wp-views/vendor/toolset/toolset-common/toolset-forms/classes/class.file.php:95
#10 WPToolset_Field_File:metaform in /app/public/wp-content/plugins/wp-views/vendor/toolset/toolset-common/toolset-forms/classes/class.image.php:18
#9 WPToolset_Field_Image:metaform in /app/public/wp-content/plugins/wp-views/vendor/toolset/toolset-common/toolset-forms/classes/class.form_factory.php:279
#8 FormFactory:metaform in /app/public/wp-content/plugins/wp-views/vendor/toolset/toolset-common/toolset-forms/bootstrap.php:58
#7 WPToolset_Forms_Bootstrap:field in /app/public/wp-content/plugins/wp-views/vendor/toolset/toolset-common/toolset-forms/api.php:13
#6 wptoolset_form_field in /app/public/wp-content/plugins/types/vendor/toolset/types/embedded/includes/fields-post.php:242
#5 wpcf_add_meta_boxes in /app/public/wp-content/plugins/types/vendor/toolset/types/embedded/admin.php:106
#4 wpcf_admin_add_meta_boxes in /app/public/wp-includes/class-wp-hook.php:286
#3 WP_Hook:apply_filters in /app/public/wp-includes/class-wp-hook.php:310
#2 WP_Hook:do_action in /app/public/wp-includes/plugin.php:453
#1 do_action in /app/public/wp-admin/edit-form-advanced.php:334
#0 include in /app/public/wp-admin/post.php:174

Thanks

Jeff

#621709

This is the right place.

I am aware of the error:
https://toolset.com/forums/topic/errors-in-administration/

The developers are informed and will react soon on this.

For now, I have no solution

#621713

Thanks Beda,

Have a good weekend!

Jeff

#622898

This is now solved in the current beta4 of Types