[Resolved] Creating a Connection between any custom pots and "Mots" we get an error message

[Author]

Posts

[charlesB-5]

Hello, I am trying to:
Trying to create a Relationship between custom post types like Evidence, iConcept, Polarité and "Mots" post, I get an error message.
I do have to refresh or update the page for the error message to disappear and the newly created relatiosship to appear.

Attached is the image sequence of the issue.

Thank you for your help. Let me know if you want me to duplicate the site so you can test.

Charles

[Nigel]

Hi Charles

Thanks for the comprehensive screenshots describing the problem.

I took a look at your site.

I suspect the issue may be because you have many-to-many relationships (e.g. evidence << >> mots ) which has an intermediate post type to store relationship fields, and one of those fields is itself a reference field for recording one-to-one relationships with some other post (of the ouvrages post type).

While the UI lets you set up such connections, I've never seen it done before, and I suspect it wasn't envisaged by the developers.

Before going further can we just confirm that this is your intention, and that it is a requirement for your site?

We can try to reproduce this issue with the same kind of setup if that's the case.

[charlesB-5]

Hi Nigel,

There has been not updates or changes to the site for a long time (beside WordPress and toolset plugins). So all was working well, I am not sure the relationship to MOT is different than the other relationships. I asked the client when he noticed this issue, his answer was September/October 2022. I wish he would have warned us at the time, it might have been easier to link it to an update (maybe). He also didn't take it seriously as in fact the relationship is created. It is just an error message showing up but when the post was updated (or the page just refreshed) the relationship was showing.

Sure you can reproduce the issue, if you prefer. I made a copy of the site with the issue.
You can access it at: hidden link
user: toolset pass: 0fp6*gj5dsA$0*BtuKks*lzy
Let me know if you want the ftp info.

Thank you Nigel

[Minesh]

Thank you for sharing staging site access details.

I install the error log viewer plugin "Error Log Viewer by BestWebSoft" to check the error logs:
=> hidden link

With the logs I found the following fatal error that belongs to the plugin "Dropr – Dropbox Plugin for WordPress":

[17-Jan-2023 05:21:17 UTC] PHP Fatal error:  Uncaught TypeError: method_exists(): Argument #1 ($object_or_class) must be of type object|string, null given in /srv/htdocs/wp-content/plugins/dropr-for-dropbox/awsm-dropr.php:166
Stack trace:
#0 /srv/htdocs/wp-content/plugins/dropr-for-dropbox/awsm-dropr.php(166): method_exists(NULL, 'is_block_editor')
#1 /wordpress/core/6.1.1/wp-includes/class-wp-hook.php(308): Dropr_main->dropr_media('')
#2 /wordpress/core/6.1.1/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
#3 /wordpress/core/6.1.1/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#4 /wordpress/core/6.1.1/wp-includes/media.php(4747): do_action('wp_enqueue_medi...')
#5 /wordpress/core/6.1.1/wp-admin/includes/media.php(642): wp_enqueue_media(Array)
#6 /wordpress/core/6.1.1/wp-includes/class-wp-hook.php(308): media_buttons('wpcf-podcast_39...')
#7 /wordpress/core/6.1.1/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
#8 /wordpress/core/6.1.1/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#9 /wordpress/core/6.1.1/wp-includes/class-wp-editor.php(236): do_action('media_buttons', 'wpcf-podcast_39...')
#10 /wordpress/core/6.1.1/wp-includes/general-template.php(3812): _WP_Editors::editor(NULL, 'wpcf-podcast_39...', Array)
#11 /srv/htdocs/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/classes/class.wysiwyg.php(153): wp_editor(NULL, 'wpcf-podcast_39...', Array)
#12 /srv/htdocs/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/classes/class.wysiwyg.php(52): WPToolset_Field_Wysiwyg->_editor(Array)
#13 /srv/htdocs/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/classes/class.form_factory.php(309): WPToolset_Field_Wysiwyg->metaform()
#14 /srv/htdocs/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/bootstrap.php(66): FormFactory->metaform(Array, 'wpcf[podcast]', Array)
#15 /srv/htdocs/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/toolset-forms/api.php(25): WPToolset_Forms_Bootstrap->field('', Array, Array)
#16 /srv/htdocs/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/field/renderer/toolset_forms.php(79): wptoolset_form_field('', Array, Array)
#17 /srv/htdocs/wp-content/plugins/types/application/viewmodels/fields_input.php(72): Toolset_Field_Renderer_Toolset_Forms->render()
#18 /srv/htdocs/wp-content/plugins/types/application/viewmodels/fields_edit_container.php(104): Types_Viewmodel_Field_Input->get_fields_data('input')
#19 /srv/htdocs/wp-content/plugins/types/application/controllers/ajax/handler/related_content_action.php(697): Types_Viewmodel_Fields_Edit_Container->to_html()
#20 /srv/htdocs/wp-content/plugins/types/application/controllers/ajax/handler/related_content_action.php(536): Types_Ajax_Handler_Related_Content_Action->format_field_data(Array, 34038)
#21 /srv/htdocs/wp-content/plugins/types/application/controllers/ajax/handler/related_content_action.php(320): Types_Ajax_Handler_Related_Content_Action->insert_connect('connect')
#22 /srv/htdocs/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/toolset.ajax.class.php(264): Types_Ajax_Handler_Related_Content_Action->process_call(Array)
#23 /wordpress/core/6.1.1/wp-includes/class-wp-hook.php(308): Toolset_Ajax->__call('callback_relate...', Array)
#24 /wordpress/core/6.1.1/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters('', Array)
#25 /wordpress/core/6.1.1/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#26 /wordpress/core/6.1.1/wp-admin/admin-ajax.php(188): do_action('wp_ajax_types_r...')
#27 {main}
  thrown in /srv/htdocs/wp-content/plugins/dropr-for-dropbox/awsm-dropr.php on line 166

I just deactivated the plugin "Dropr – Dropbox Plugin for WordPress" and it seems everything is working as expected.

Can you please confirm it works at your end as well.

[charlesB-5]

that is the issue. Thank you very much for your help. I really appreciate it.
Charles