Skip Navigation

[Resolved] types 3.4.7 breaks back end as soon as activated

This support ticket is created 4 years, 4 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
- 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)

This topic contains 3 replies, has 2 voices.

Last updated by Shane 4 years, 4 months ago.

Assisted by: Shane.

Author
Posts
#2019683
db-tables-tools.PNG

I am trying to: Install types 3.4.7 on a server running wordpresss 5.7 and PHP 7.4.3

Link to a page where the issue can be seen: N/A

I expected to see: N/A

Instead, I got:

I recently migrated my site to a new server, then upgraded WordPress to 5.7. On the old server this site was using Types version 1.8. I did not include this old version of types in the migration because it is not compatible with WordPress 5.7 or PHP 7.4.3.

I downloaded Types 3.4.7 and attempted to install that. As soon as I click "activate" on Types I get this error: There has been a critical error on this website. Please check your site admin email inbox for instructions.

There are tables in my wordpres database that were created when Types version 1.8 was installed on the OLD server (see attached). I am not sure if this would be the cause of the critical error above. Please advise.

#2019769

Shane
Supporter

Languages: English (English )

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

Hi Michael,

Thank you for getting.

IN order for us to understand what the exact error is you will need to enable the wordpress debugging and let us know what error is being printed out.

To enable the wordpress debugging, you will need to add the following to your wp-config.php file

define( 'WP_DEBUG', true );

Once you've done this please try activating the types plugin again and let me know what exactly the error is.

If you need some further details the wordpress debugging then you can go ahead and have a look at the article below.
hidden link

Thanks,
Shane

#2019773
fatal-error.png

Thank you, I made that change, then got the error below when I click activate.

Fatal error: Uncaught Error: Call to undefined function simplexml_load_file() in /var/www/sus.org/wp-content/plugins/types/vendor/otgs/installer/includes/class-wp-installer.php:887 Stack trace: #0 /var/www/sus.org/wp-content/plugins/types/vendor/otgs/installer/includes/class-wp-installer.php(93): WP_Installer->load_repositories_list() #1 /var/www/sus.org/wp-content/plugins/types/vendor/otgs/installer/includes/class-wp-installer.php(74): WP_Installer->__construct() #2 /var/www/sus.org/wp-content/plugins/types/vendor/otgs/installer/includes/functions-core.php(6): WP_Installer::instance() #3 /var/www/sus.org/wp-content/plugins/types/vendor/otgs/installer/installer.php(15): WP_Installer() #4 /var/www/sus.org/wp-content/plugins/types/vendor/otgs/installer/loader.php(166): include_once('/var/www/sus.or...') #5 /var/www/sus.org/wp-includes/class-wp-hook.php(292): wpml_installer_instance_delegator() #6 /var/www/sus.org/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters() #7 /var/www/sus.org/wp-includes/plugin.php(484): WP in /var/www/sus.org/wp-content/plugins/types/vendor/otgs/installer/includes/class-wp-installer.php on line 887
There has been a critical error on this website. Please check your site admin email inbox for instructions.

#2019785

Shane
Supporter

Languages: English (English )

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

Hi Michael,

Thank you for the information.

It would appear based on this error that the SimpleXML module is not enabled or isn't installed
What I would recommend is getting in touch with your host and ask them to enable this for you.

Having this module enabled should resolve the fatal error issue.

Thanks,
Shane