[Resolved] I can't update Toolset Types and Toolset Views in the plugins section.

[Author]

Posts

[izalcoC]

Hello,

I've been having this issue for a month; I can't update the plugins because I received the message:
Update failed: undefined.

I don't know exactly what the problem is, and I don't want to delete and re-install them because I don't know if it will affect my views and all the sections related to Toolset.

So please, if you can help me, it would be great. Thanks!

[Mateus Getulio]

Hey there,

Thank you for contacting us.

There were instances in the past where this issue was resolved with recreating the license and registering Toolset again. Can you please follow these steps to try to fix the issue?

- Go to https://toolset.com/account/ and remove the key for your site
- Click on 'Add new site' and add your site again and save the new generated key(when adding it again, please make sure to add it exactly as it is registered within the site's DB, eg: with or without https, with or without WWW)
- Go to Plugins > Add New
- Click on "Commercial"
- Click on "Register Toolset" and try to register Toolset again with the new generated key

After registering it again, please check if you'll be able to update the plugins now.

If it still doesn’t work, could you please enable debug mode to see if any error message is displayed?

To do so, please add the following code in the wp-config.php file of your site:

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
  
// Enable Debug logging to the /wp-content/debug.log file
define( 'WP_DEBUG_LOG', true );
  
// Disable display of errors and warnings 
define( 'WP_DEBUG_DISPLAY', false );
@ini_set( 'display_errors', 0 );
  
// Use dev versions of core JS and CSS files (only needed if you are modifying these core files)
define( 'SCRIPT_DEBUG', true );

Please check following links to read more about debugging with WordPress.
- https://codex.wordpress.org/Debugging_in_WordPress
- https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging

After adding the code above, please try to reproduce the issue again and check if you'll find a debug.log file inside the wp-content folder.

If you locate it there, please send us the last lines here in the ticket.

Thank you, please let me know.