Skip Navigation

[Resolved] Toolset Update breaks site

This support ticket is created 5 years 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.

Sun Mon Tue Wed Thu Fri Sat
- 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 7:00 – 14:00 -
- 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 15:00 – 16:00 -

Supporter timezone: Europe/London (GMT+00:00)

Tagged: 

This topic contains 7 replies, has 2 voices.

Last updated by joanneP 4 years, 12 months ago.

Assisted by: Nigel.

Author
Posts
#1835965

Tell us what you are trying to do?
I am following the previous advice form our support - to update my toolset kit. After manual update, the website breaks. I have tried to deactivate all related plugin to no effect.

Is there any documentation that you are following?

Is there a similar example that we can see?

What is the link to your site?
hidden link

#1836295

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Can we get some more details from you?

Can you provide the debug info for your site in your next reply (hidden link).

When you say the site "breaks", do you have any specific details?

Are there errors? Check your browser console for JS errors, and check your debug.log for PHP errors.

If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
define('WP_DISABLE_FATAL_ERROR_HANDLER',true);

That will create a debug.log file in your /wp-content/ directory which you can examine in any text editor.

Try repeating the steps that caused the original problem and then inspect the log. If you don't find the debug.log file it means it didn't generate any warnings or errors.

Please share what you find.

#1836585

1. Once we upload types 3.4.2 the site becomes uncreachable and just display a "critical wordpress code error" message whenever you try to reach it. I had to disable the plugin from the ftp backend for the site to come up again.

2. I then reverted to types 2.1 (which was the initial version before update), but the pages created with the plugin no longer come up (Specifically this: hidden link). It just redirect to the home page.

3. I also noted that I can no longer activate the "Tools View" from plugin manager. Each time I click on Activate, it just reload same page without activating the plugin.

#1836789

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

It looks like the problems occur because you are leaping across so many versions and there have been substantial changes in the interim. Had you been updating incrementally I don't expect you would have had the same issues.

Can you provide us with a copy of your site with Types 2.1 and we can look into an upgrade path that might work for you.

Or—better—if you have a backup of the site before you tried to update to Types 3.4.2, pease share that.

See the following link for details about using Duplicator to provide a copy: hidden link

You can just share the backup (via dropbox or similar) here in your next reply, links are hidden from other visitors.

#1837333

Here is a link to download a backup created with the updraft plus plugin. I do hope this will be helpful: hidden link

I was unable to create a copy of the site with Duplicator. It gave error of the db size greater than 500mb. However, you may loggin to the site with details below (I do hope this conversation is private as I cannot find a button to set it to private):

#1838443

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

Thanks, I will install the copy of the site locally for testing and then get back to you.

#1839889

Nigel
Supporter

Languages: English (English ) Spanish (Español )

Timezone: Europe/London (GMT+00:00)

I didn't experience any problems adding Types back to your site on the local copy I have installed.

Expecting to encounter issues I first disabled all plugins, then installed the current version of Types (3.4.2) and activated it, and there were no problems.

I then proceeded to re-activate all the other plugins on the site, and while I found an error arising from the flip box plugin, I didn't find anything connected to Toolset and Types.

I omitted re-activating a few plugins, but they look superfluos (e.g. Forms Commerce requires WooCommerce, which you are not using), and you don't need Toolset Advanced Export, Toolset Framework Installer, Toolset Module Manager, plus you have no API key set for Google maps so you aren't using Toolset Maps, and I doubt you need the Toolset Layouts Migration plugin.

I would go through similar steps to add Types to your site, but it's a live site.

Do you have a staging site to do this? Then you can push updates from staging to production, without risking bringing the site itself down if errors do occur.

#1840589

My issue is resolved now. Thank you!

Thanks Nigel, I removed the plugins you specified as not needed, removed the flipbox plugin, deleted the old types2.1 and then uploaded the latest types3.4.2, and the update succeeded. I also had all pages of the custom type showing 404 error. I was able to fix that with this link: https://toolset.com/forums/topic/permalink-for-custom-post-type-posts-gives-404-error/.
Thanks.