Skip Navigation

[Resolved] ToolSet WooCommerce Custom Fields… Replicants

This thread is resolved. Here is a description of the problem and solution.

Problem:
ToolSet WooCommerce Custom Field groups displayed multiple times

Solution:
To remove the unwanted Toolset WooCommerce custom field groups you will require to run custom query on your database.

You can find proposed solution in this case with the following reply:
=> https://toolset.com/forums/topic/toolset-woocommerce-custom-fields-replicants/#post-2060867

Relevant Documentation:

0% of people find this useful.

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.

This topic contains 17 replies, has 2 voices.

Last updated by MarcoS3712 1 year, 4 months ago.

Assigned support staff: Minesh.

Author
Posts
#2062569

Hi Minesh,
I've checked about database extra entries to delete.

I've seen that in wp_posts there are 79 records.

SELECT * FROM wp_posts
where post_title like '%Toolset%'
and ID <> 7020;

I've also seen that in wp_postmeta there are 474 rows related to ID.
Is it better to remove them before?

SELECT * FROM wp_postmeta wpm
join wp_posts wp
on wpm.post_id = wp.ID
where (wp.post_title like '%Toolset%' and
wp.ID <> 7020);

Do you think that there are other table to check?

Thanks in advance,

Marco

#2062653

Minesh
Supporter

Languages: English (English )

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

I suggest you use the search query to search for title ""Toolset WooCommerce".

For example:

SELECT * FROM wp_posts
where post_title like '%Toolset WooCommerce%'
and ID <> 7020;

I've also seen that in wp_postmeta there are 474 rows related to ID.
Is it better to remove them before?

SELECT * FROM wp_postmeta wpm
join wp_posts wp
on wpm.post_id = wp.ID
where (wp.post_title like '%Toolset%' and
wp.ID <> 7020);
==>
If you find such records, yes, you are welcome to delete it but please make sure you took full backup of your database.

#2062683

My issue is resolved now. Thank you!