Skip Navigation

[Resolved] Can't register plugins on site

This support ticket is created 7 years, 1 month 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+00:00)

This topic contains 9 replies, has 2 voices.

Last updated by Brian 7 years, 1 month ago.

Assisted by: Nigel.

Author
Posts
#591388
toolset plugins.png
toolset key.png

I am trying to: Register the Views and Layout plugin on the site. I put in the key, but it won't save and it doesn't show the plugins when I check the registered sites.

Link to a page where the issue can be seen:

I expected to see:

Instead, I got:

#591459

Nigel
Supporter

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

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

Hi Brian

When you say it won't save, can you check the browser console to see if there are any JS errors or warnings?

#591690

This is the message from the Javascript console as requested:

VM3489:1 POST hidden link 500 (Internal Server Error)
(anonymous) @ VM3489:1
send @ load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils&ver=4.9:4
ajax @ load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils&ver=4.9:4
save_site_key @ admin.js?ver=1.8.2:103
dispatch @ load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils&ver=4.9:3
r.handle @ load-scripts.php?c=0&load[]=jquery-core,jquery-migrate,utils&ver=4.9:3

#591694

Nigel
Supporter

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

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

Hi Brian

There is a 500 error on the server (i.e. a code syntax error) when attempting an ajax request.

To see what the error is you need to have debugging enabled.

If you haven't already, turn on the debug log by editing your wp-config.php file and change the line with WP_DEBUG like so:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

That will create a debug.log file in your wp-content directory which you can examine in any text editor. Try repeating the steps to generate the error, and then consult the debug.log file which should include details of the PHP error.

#591711

Here are the contents of debug.log

===========

[21-Nov-2017 16:34:57 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 72 bytes) in /home/podiatrist2017/public_html/wp-includes/class-wp-hook.php on line 77
[21-Nov-2017 16:34:58 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 40 bytes) in /home/podiatrist2017/public_html/wp-includes/plugin.php on line 109
[21-Nov-2017 16:35:11 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 72 bytes) in /home/podiatrist2017/public_html/wp-includes/class-wp-hook.php on line 77
[21-Nov-2017 16:35:17 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 64 bytes) in /home/podiatrist2017/public_html/wp-includes/plugin.php on line 894
[21-Nov-2017 16:35:47 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 42 bytes) in /home/podiatrist2017/public_html/wp-content/plugins/wp-views/inc/filters/wpv-filter-meta-field.php on line 1026
[21-Nov-2017 16:35:53 UTC] PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 72 bytes) in /home/podiatrist2017/public_html/wp-content/plugins/wp-views/inc/filters/wpv-filter-meta-field.php on line 1026

===========

#591983

Nigel
Supporter

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

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

Hi Brian

From your debug info it looks as if the PHP memory allocation is adequate, but can you edit your wp-config.php file and add the following to make sure WordPress is availing of the maximum allocation:

// Increase memory limit
define( 'WP_MEMORY_LIMIT', '256M' );
define( 'WP_MAX_MEMORY_LIMIT', '256M' );

Let me know if that makes any difference.

#592332

That did the trick. Thanks Nigel!

Should I remove increased memory limits in wp-config.php now that it is registered or do I need to leave it in for the plugins to function properly?

#592333

Please see the question about modifying the wp-config.php file.

#592378

Nigel
Supporter

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

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

Hi Brian

You can leave those settings intact so that you don't run into similar issues again. They set the maximum amount of memory the server can allocate to WordPress, but WordPress will only use as much as it needs.

#592633

Thanks for confirming Nigel.