Skip Navigation

[Resolved] Fatal error with Toolset Types

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

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+01:00)

Tagged: 

This topic contains 5 replies, has 2 voices.

Last updated by whitneyF-3 4 years, 9 months ago.

Assisted by: Nigel.

Author
Posts
#1800957

I am trying to update the Toolset Types plug-in on my site (wcmca.org) and when I have done it in the past, it creates a fatal error and then anything within the sites using Toolset functionality disappears.

I have created a staging site to troubleshoot this issue (hidden link) and could provide log-in credentials if somebody could please take a look at this.

I have some major site updates that they have requested to be done and I would like to figure out this update prior to starting on those updates.

Thank you!
Whitney

#1801373

Nigel
Supporter

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

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

Hi Whitney

Let me set up a private reply to get credentials from you so that whoever takes this ticket has them available already.

You may want to create a temporary admin user that you can later delete, and be sure to have a current backup.

Do you have any details of the error?

#1802531

Nigel
Supporter

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

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

Hi Whitney

I should definitely be checking the staging site rather than the live site, so if the credentials you shared were for the live site, let me set another private reply so that you can share credentials of the staging site. I can upload the latest version of the Types plugin without needing to register the site, that's not a problem.

From the credentials you already shared it looks like the login page is protected by flywheel and I also need a password to get past that, please be sure to include it.

#1803297

Hey Nigel,
Yes - the username and password are to the staging site. I have turned off the password protection on the site for now. Please let me know if you need anything else.

Thank you!
Whitney

#1804067

Nigel
Supporter

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

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

Hi Whitney

I see you are using Beaver Builder on the site. There is a known issue with the updates to Views/Blocks that causes a fatal error with Beaver Builder. A patch is available (https://toolset.com/errata/fatal-php-error-on-sites-using-beaver-builder-after-updating-to-blocks-1-3/) but it requires using FTP to replace one of the plugin files.

I tried installing a couple of the file manager plugins that allow access to the server files from the WP admin, but neither of them worked, they are evidently blocked by flywheel.

So, I don't want to update Views because I know it will provoke a fatal error, and without FTP access I can't make sure the debug log is turned on to capture any errors that occur when updating Types to know the source of the problem.

If you don't need to update right now, I'm thinking it might be a better idea to wait for the next plugin releases and update then: the current dev cycle is focused on bug-fixes and we are squashing a lot of bugs, so it should be much less likely you will run into problems.

If you are willing to wait then it is likely to be a few weeks, you can close this and contact us again at the time if needs be (if you experience any problems after updating plugins on a staging site to test first).

If you want to update now, we'll need FTP access, which from the link you shared means we'll need your flywheel credentials.

#1812767

My issue is resolved now. Thank you!