[Resolved] broken relationship on edit screen (backend)

[Author]

Posts

[pharmaklaus]

I am trying to: edit a custom post type

Link to a page where the issue can be seen: hidden link (also screenshots)

I expected to see: the relantionship table

Instead, I got: errors

----------------------------------------
Sorry i replied to an old thread here https://toolset.com/forums/topic/relationship-e_error-email-and-not-editable/#post-1408661
You can remove it.

When i try to edit a custom post type item a related relationship seems to to be broken.
The relationship is many-to-many Edizioni [*] << Edizioni Partners >> Partners [*].
Another strange thing is that the error is present when i try to edit a item from "Edizioni" all seems to be ok, when i try to edit ad item from "Partners" the error message is shown.

It seems to be happened after the last wordpress update but i'm sure about the relationship.
All toolset plugins are updated to the last version available.

I used ULTIMATE CSV IMPORTER PRO several time to import data, then i add other items manually via backend.
I am frustrated the idea to start from scratch and re-import the data.
The site contains six relationships, only one of this seems to be broken.

----------------------------------------
Uncaught Error: Call to a member function get_element() on null in
[...]wp-content/plugins/wp-views/vendor/toolset/toolset-common/inc/m2m/association/intermediary_post_persistence.php on line 220
create_empty_association_intermediary_post()
wp-content/plugins/types/application/controllers/page/extension/related_content/meta_box_related_content.php:1142
check_field_integrity()
wp-content/plugins/types/application/controllers/page/extension/related_content/meta_box_related_content.php:607
format_field_data()
wp-content/plugins/types/application/controllers/page/extension/related_content/meta_box_related_content.php:570
get_related_content()
wp-content/plugins/types/application/controllers/page/extension/related_content/meta_box_related_content.php:359
build_js_data()
wp-content/plugins/types/application/controllers/page/extension/related_content/meta_box_related_content.php:478
build_metabox_context()
wp-content/plugins/types/application/controllers/page/extension/meta_box.php:206
render_meta_box()
wp-admin/includes/template.php:1343
do_meta_boxes()
wp-admin/edit-form-advanced.php:700
include()
wp-admin/post.php:198

[Christian Cox]

Hello, I'll be glad to take a closer look. Did you keep a backup of the site before you imported these Edizioni and Partner posts? Do you still have the CSV file you used during the import?

I tried to log in but got a password error. Can you check those credentials for me?

[pharmaklaus]

Where I can send you the credentials in private?

[Christian Cox]

I made your previous comment private and reactivated private reply fields here.

[Christian Cox]

Sorry now it's quite impossibile to recostruct all the consequential imports I done...I'm worried about the possibility that this case Is not isolated and a previous bad import could come back likes this one.
Without being able to recreate each step in the import process, it is difficult to know if the problem was caused by a bug in the import software, a configuration issue in the import software, a CSV file formatting problem, a problem with the configurations of the post types and relationships, a bug in Toolset, or something else unexpected. I see one other report of a similar error message, and it looks like you found the same post here: https://toolset.com/forums/topic/relationship-e_error-email-and-not-editable/#post-1408661
The cause of the problem there was undetermined...the User reverted to a backup of the site and resolved the ticket before investigation was complete. The error message is nearly identical to yours, but the import software is different.

But how to check the status of current data? Via db?
I'm not exactly sure I understand what this means, but I can ask my 2nd tier team to investigate the error messages and the current database contents. I have created a clone of the site using the Duplicator plugin, and I'll ask the team to inspect that to see if there's anything we can do to solve the problem without losing the existing data. If they are unable to see any obvious fix, then we could try to create new, more complete import documents, and start over. Then during the site setup and data import process, we can create step-by-step site backups. This will give you the ability to revert and test updates more thoroughly.

I will let you know what I find out from the 2nd tier support team.