Skip Navigation

[Resolved] Fatal error crashes site

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

Our next available supporter will start replying to tickets in about 2.19 hours from now. Thank you for your understanding.

Sun Mon Tue Wed Thu Fri Sat
- 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 9:00 – 12:00 -
- 13:00 – 18:00 13:00 – 18:00 13:00 – 18:00 14:00 – 18:00 13:00 – 18:00 -

Supporter timezone: America/Jamaica (GMT-05:00)

Tagged: 

This topic contains 3 replies, has 2 voices.

Last updated by himanshuS 3 years, 10 months ago.

Assisted by: Shane.

Author
Posts
#1903489

I am getting the following error:

Fatal error: Cannot redeclare func_set_parent_terms_to_child() (previously declared in /srv/htdocs/wp-content/toolset-customizations/add-parent-project-submission-taxonomy-to-expert-review-request.php:10) in /srv/htdocs/wp-content/toolset-customizations/add_parent_taxonomy.php on line 51
xargs: sudo: exited with status 255; aborting

It seems like there are two custom code snippets in toolset custom code with same function name. But I don't know how to deactivate them as when I activate the plugin.. the site crashes and I can even access wp-admin.

What is a work around to solve this error?

#1904033

Shane
Supporter

Languages: English (English )

Timezone: America/Jamaica (GMT-05:00)

Hi Himanshu,

Thank you for getting in touch.

Taking a look at this error, it seems you have activated the function that has the same name of another. What you can do is to log into your site using FTP and delete this file /wp-content/toolset-customizations/add_parent_taxonomy.php

This should clear up the error.

Thanks,
Shane

#1904087

Shane,

The issue is resolved. Thank you for the quick response.

#1904089

My issue is resolved now. Thank you!