Fatal error on activation

Dear,

Thanks for your mail, would it be possible to send our backoffice, ssh and DB access to [email protected] ( our provider). They will investigate this issue with high priority.

Thanks in advance

Michael

Hi Dominic,

Can you enable WP_DEBUG and tell us if you see an error ?

Have you access to the PHP error log ?
It’s a dedicated server or a shared hosting ? to know if you have access to system logs

Thanks for your feedback,

Hi,

In WP_DEBUG I see the following
Notice: tgmpa was called with an argument that is deprecated since version 2.4.0! The parent_menu_slug config parameter was removed in TGMPA 2.4.0. In TGMPA 2.5.0 an alternative was (re-)introduced. Please adjust your configuration. For more information visit the website: https://tgmpluginactivation.com/configuration/#h-configuration-options. in /wp-includes/functions.php on line 3737

Notice: tgmpa was called with an argument that is deprecated since version 2.4.0! The parent_url_slug config parameter was removed in TGMPA 2.4.0. In TGMPA 2.5.0 an alternative was (re-)introduced. Please adjust your configuration. For more information visit the website: https://tgmpluginactivation.com/configuration/#h-configuration-options. in wp-includes/functions.php on line 3737

Warning: Cannot modify header information – headers already sent by (output started at /wp-includes/functions.php:3737) in wp-includes/option.php on line 820

Warning: Cannot modify header information – headers already sent by (output started at wp-includes/functions.php:3737) in wp-includes/option.php on line 821

WP_DEBUG als mentiones this when I try to enable the plugin
Warning: Cannot modify header information – headers already sent by (output started at /wp-includes/functions.php:3737) in /wp-includes/pluggable.php on line 1228

Can’t seem to find the PHP error log
I’m on a shared hosting.

To be honest I’m a little reluctant to share SSH and DB access.

Hope this helps.

Hi,

No problem for the SSH/DB access, I understand that ?? .

The notices are caused by tgmpa plugin (I don’t know it), but we are not alone (https://www.ads-software.com/support/topic/error-the-parent_menu_slug-config-parameter-was-removed-in-tgmpa).
Do all your plugins/themes are up-to-date ?

I will check if I can reproduce your issue with the TGMPA plugin.

Can you send us the list of your plugins to [email protected] ? With that, we will try to reproduce the issue.

Thanks,

I’ve also tried deactivating all plugins to see if it would help but it didn’t.

All plugins and themes are up to date.
I haven’t updated to WP 4.5 yet to give more time to dev’s to update plugins.

I haven’t installed the TGMPA plugin but the library probably came with one of the plugins I’m using

List of plugins has been sent to [email protected]

Thanks

Hi Dominic, Antidot-dev,

One of the devs of TGMPA here. The notices your mention are not (or should not be) the cause of your activation error. A notice is the lightest form of error and will not result in a program stopping execution.
The fatal error causing the problem must be something else.

All the same – to give you some more information on this notice:

We put the notice in there to alert developers to the changed parameters before they ship out a new version of their plugin or theme. Unfortunately there are still devs out there who don’t have WP_DEBUG enabled when they develop, so sometimes the message still gets missed and a plugin/theme shipped using old parameters.

Another possibility is that you have both a plugin (one or more) and your theme all using TGMPA. That in itself does generally not cause an issue, but if one of these is still using an old version with old parameters while another is using the new version with the new parameters, the notices can start popping up.

If you want to see which theme/plugin is causing the notices (and is likely to use an old version of TGMPA – they should really upgrade), you’re best bet is to turn on error logging and use a backtrace.

For an example with extensive instructions on how to do this – see https://gist.github.com/jrfnl/5925642.
If you post a full backtrace of the notices here, I’ll be able to tell you which plugin/theme is causing them, so you can inform the plugin/theme author that they should upgrade.

To solve your current problem: WP_DEBUG does not show you all errors. If you really want to see all errors and notices, you *will* need to turn on error logging. With the information which will gather in the log, you should be able to find out what the actual fatal error is and we can go from there.

Hope this helps!

Hi,

sorry for the late reply after enabling the error log & trying to enable the plugin (twice) I got this:

[21-Apr-2016 14:11:08 UTC] Backtrace from warning ‘Cannot modify header information – headers already sent by (output started at /wp-includes/functions.php:3737)’ at /wp-includes/pluggable.php 1228: /wp-includes/pluggable.php 1228 calling header() | /wp-admin/includes/plugin.php 535 calling wp_redirect() | /wp-admin/plugins.php 42 calling activate_plugin() | /wp-admin/network/plugins.php 16 calling require()

[21-Apr-2016 14:13:37 UTC] Backtrace from warning ‘Cannot modify header information – headers already sent by (output started at /wp-includes/functions.php:3737)’ at /wp-includes/pluggable.php 1228: /wp-includes/pluggable.php 1228 calling header() | /wp-admin/includes/plugin.php 535 calling wp_redirect() | /plugins.php 42 calling activate_plugin() | /wp-admin/network/plugins.php 16 calling require()

Hope it makes sense and thank you very much for the help.

Hello,
Some updates have been made.
We are now at v1.2.16 and normally you should not encounter the issue anymore.
Can you confirm it’s fixed.

KR

Hi Dominic,

I suppose you haven’t the issue anymore, so I close the post.

Thank for your feedback which permit us to fix it.