Skip Navigation

[Resolved] Error in types prevents viewing plugins page

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

Problem: I am unable to access the Plugins page after updating Types, and a fatal error occurs.

Solution: Activate Types, go to the core WP updates page, and click "Check for Updates". Then return to the plugins page to verify the workaround.

100% of people find this useful.

This support ticket is created 5 years, 8 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
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 2 replies, has 2 voices.

Last updated by Steve 5 years, 8 months ago.

Assisted by: Christian Cox.

Author
Posts
#1228993

Hi I just logged in to do some work on a site i haven't been involved in for a couple of years and when i goto the plugins page i get the error below which prevents the page from loading. It appears from the updates page that both plugin and wordpress core are up to date,

Fatal error: Call to a member function get_external_repo() on null in /home4/gloucest/public_html/wordpress/wp-content/plugins/types/vendor/otgs/installer/includes/class-wp-installer.php on line 2335

Im not sure how to proceed

#1228997

Hi, sorry for the inconvenience here. The workaround is as follows:
- Activate Types if it is not active
- Go to the WordPress Updates page ( /wp-admin/update-core.php )
- Click "Check for Updates"
- Return to the plugins page. If the plugins page is still blank, return to the WordPress Updates page and click "Check for Updates" one or two more times, then test again.

#1229009

My issue is resolved now. Thank you!