Skip Navigation

[Resolved] Cannot Install Types on a Mac running MAMP for localhost

The Toolset Community Forum is closed, for technical support questions, please head on to our Toolset Professional Support (for paid clients), with any pre-sale or admin question please contact us here.
This support ticket is created 7 years ago. There's a good chance that you are reading advice that it now obsolete.
This is the community support forum for Types plugin, which is part of Toolset. Toolset is a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients and people who registered for Types community support can post in it.

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 3 replies, has 2 voices.

Last updated by Christian Cox 7 years ago.

Assisted by: Christian Cox.

Author
Posts
#580896

When I activate the types.2.2.16. plugin on localhost, I get a 500 error.

#580918

Okay there's nothing inherently problematic about using MAMP so it's most likely a configuration issue. Can you try the following troubleshooting steps?
- Check to see if your localhost installation meets the requirements for Toolset: https://toolset.com/toolset-requirements/
- Enable server logging to see what the error is. Copy + paste anything from the relevant time period in the Apache logs. Go in your wp-config.php file and look for define(‘WP_DEBUG’, false);. Change it to:

define('WP_DEBUG', true);

Then add these lines, just before it says 'stop editing here':

ini_set('log_errors',TRUE);
ini_set('error_reporting', E_ALL);
ini_set('error_log', dirname(__FILE__) . '/error_log.txt');

Refresh the page where you get a 500 error. This will create an error_log.txt file in your site's root directory. Please send me its contents. Once that is done, you can revert the updates you made to wp-config.php.

- Next, rename the folder at wp-content/plugins/types to temporarily disable the plugin and regain access to wp-admin. Temporarily disable all plugins and activate a default theme like Twenty Seventeen. Reactivate Types. If the 500 error returns, you've got a configuration issue. If the 500 error does not return, you probably have a theme or plugin conflict. Reactivate your theme and plugins one by one until the conflict is revealed. Let me know the results.

#580928

Here's what appears on the browser:
Fatal error: Uncaught Error: Call to a member function get() on boolean in /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php:139 Stack trace: #0 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(121): Types_Interop_Mediator->get_theme_slug() #1 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(80): Types_Interop_Mediator->is_the7_active() #2 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(32): Types_Interop_Mediator->initialize_interop_handlers() #3 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(22): Types_Interop_Mediator->__construct() #4 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/main.php(137): Types_Interop_Mediator::initialize() #5 in /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php on line 139

And here's the ERROR LOG
[22-Oct-2017 22:26:08 UTC] PHP Fatal error: Uncaught Error: Call to a member function get() on boolean in /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php:139
Stack trace:
#0 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(121): Types_Interop_Mediator->get_theme_slug()
#1 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(80): Types_Interop_Mediator->is_the7_active()
#2 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(32): Types_Interop_Mediator->initialize_interop_handlers()
#3 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php(22): Types_Interop_Mediator->__construct()
#4 /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/main.php(137): Types_Interop_Mediator::initialize()
#5 in /Applications/MAMP/htdocs/Metaglyphics/website/wp-content/plugins/types/application/controllers/interop/mediator.php on line 139

Thanks

#581161

Okay this line of code is related to retrieving information about the parent and child themes, so I suspect something is going on there. Please try these troubleshooting steps:
- Rename the Types plugin folder to temporarily disable it and regain access to wp-admin. The folder is at /wp-content/plugins/types. Deactivate all other plugins.
- Activate the default Twenty Seventeen theme, then reactivate Types.
- If the error does not reappear, then reactivate and test your parent theme, child theme, and plugins one by one until the conflict is revealed. Let me know the results.
- I have a copy of the7 version 5.4.1 that I'm testing with right now and it seems fine on a clean installation with Types 2.2.16, so if the error reappears, I'll need to investigate further by making a clone of your site.

The forum ‘Types Community Support’ is closed to new topics and replies.