[Resolved] Excessive errors in log

[Author]

Posts

[bradleyS]

Excessive errors logged to the debug file:

[05-May-2023 14:27:50 UTC] WordPress database error Table '<snip>removed</snip>.wp_toolset_relationships' doesn't exist for query SELECT  
			relationships.id AS id,
			relationships.slug AS slug,
			relationships.display_name_plural AS display_name_plural,
			relationships.display_name_singular AS display_name_singular,
			relationships.driver AS driver,
			relationships.parent_domain AS parent_domain,
			relationships.child_domain AS child_domain,
			relationships.intermediary_type AS intermediary_type,
			relationships.ownership AS ownership,
			relationships.cardinality_parent_max AS cardinality_parent_max,
			relationships.cardinality_parent_min AS cardinality_parent_min,
			relationships.cardinality_child_max AS cardinality_child_max,
			relationships.cardinality_child_min AS cardinality_child_min,
			relationships.is_distinct AS is_distinct,
			relationships.scope AS scope,
			relationships.origin AS origin,
			relationships.role_name_parent AS role_name_parent,
			relationships.role_name_child AS role_name_child,
			relationships.role_name_intermediary AS role_name_intermediary,
			relationships.role_label_parent_singular AS role_label_parent_singular,
			relationships.role_label_child_singular AS role_label_child_singular,
			relationships.role_label_parent_plural AS role_label_parent_plural,
			relationships.role_label_child_plural AS role_label_child_plural,
			relationships.needs_legacy_support AS needs_legacy_support,
			relationships.is_active AS is_active,
			relationships.autodelete_intermediary AS autodelete_intermediary,
			relationships.parent_types AS parent_types_set_id,
			relationships.child_types AS child_types_set_id,
			GROUP_CONCAT(DISTINCT parent_types_table.type) AS parent_types,
			GROUP_CONCAT(DISTINCT child_types_table.type) AS child_types
			FROM wp_toolset_relationships AS relationships 
			JOIN wp_toolset_type_sets AS parent_types_table
				ON (relationships.parent_types = parent_types_table.set_id )
			JOIN wp_toolset_type_sets AS child_types_table
				ON (relationships.child_types = child_types_table.set_id )
... 

See hidden link

This is the staging server, but the issue is the same on the live server.

[Mateus Getulio]

Hello there,

Thanks for your contact, and welcome to our support forum!

Is there any specific action that triggers these logs? The error indicates the 'relationships' table from Toolset does not exist, but it might be just a false negative.

By chance, do you have any relationships, Repeatable Field Groups or Post Relationship Fields in your website? If they exist and are working fine, then this error is a false negative and most probably occurred during a huge load.

In case you do not have these kind of content in your website:

- please get access to your database
- check if the table "wp_toolset_relationships" exists or not
- if it does not exist, deactivate Toolset Types, then reactivate it, and go to the Toolset -> Relationships section
- see if the table will be created now

If this does not help, I would like to request temporary access (wp-admin and FTP) to your site to take better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Our Debugging Procedures

I will be checking various settings in the backend to see if the issue can be resolved. Although I won't be making changes that affect the live site, it is still good practice to backup the site before providing us access. In the event that we do need to debug the site further, I will duplicate the site and work in a separate, local development environment to avoid affecting the live site.

Privacy and Security Policy

We have strict policies regarding privacy and access to your information. Please see:
https://toolset.com/privacy-policy-and-gdpr-compliance/#data-shared-with-our-support
**IMPORTANT**

- Please make a backup of site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box. The private box looks like this: hidden link

Please, let me know if you need any additional details. Have a nice day.

[Mateus Getulio]

Hello Bradley,

Thanks for providing the website credentials.

I checked this out but so far I couldn't find a fix for it. I asked my colleagues to have a look at this issue in order to see if there's anything I'm missing. I'll come back to you here as soon as one of my colleagues reply back to me (which it shouldn't take long).

But in the meantime, may I kindly ask you to provide us with more context about the website? For example, have you checked if there was any specific action that might have caused this issue?

It seems that almost all Toolset tables were removed from the database. Did the website face a big change in the past few days?

Please keep us posted about it.

Best,
Mateus.

[bradleyS]

Hi Mateus,

I don't know of any specific action that could have caused the DB tables issues you describe. I inherited the site from a agency and was asked to add a Review functionality. I added Types for the CPT and wanted to use the integration with Elementor as that is what most of the site was built with (I'm not a big fan of page builders). So initially I tried to build the Reviews front-end display in Elementor and it wasn't working well with Types so I built the Review loop in Blocks. Only to discover I couldn't embed the blocks easily in Elementor. So I ended up building a template in Views ( the way I've built a number of sites in the past) and embedding that in Elementor (very clunkly to say the least). In the process, I discovered that enabling Views disables Blocks and vice versa. Perhaps the constant switching between Views & Blocks is problematic. That's the only thing I can think of.

[Mateus Getulio]

Hi Bradley,

Thank you for sharing these details.

I have escalated this ticket to our 2nd tier of support where our 2nd tier specialists will take a deeper look at this issue and will try to find a solution.

I will get back to you as soon as I get an answer from them.

Best regards,
Mateus

[Mateus Getulio]

Hello there,

Thanks for your patience.

Upon further inspection, we could solve the issue in the staging website by following these steps:

- First, we deactivated Types
- Then we've accessed the table 'wp_options' in the database (we added the "Database Management tool - Adminer" plugin to be able to do that)
- We deleted these two entries in the options table: 'wpdb_toolset_relationships_version' and 'toolset_relationship_db_layer'
- Then we re-activated Types, and navigated to Toolset -> Relationships

We checked in the database and the missing wp_toolset_relationships table has been created. That should prevent the errors occurring.

Could you please try the same in the original website? Just make sure to have a complete website and database backup before trying it.

Please keep us posted about your results. Thank you.

[bradleyS]

Thank you Mateus.

As requested, I have performed the steps you outlined on the live site.

I will monitor the site to see if it solves the issue.