Beta 3 and 4: Plugins page broken

Hi!

The WordPress plugins page is broken, displaying a lot of errors such as this one:

**Warning** : Undefined array key "advanced-custom-fields-pro" in **/home/customer/www/*/public_html/wp-content/themes/pro/framework/legacy/functions/updates/class-tgm-plugin-activation.php** on line **1828**

Thanks!

@Misho, is this the same site you were experiencing other warnings on that you mentioned elsewhere in the forum? I was unable to replicate those same warnings just as I am unable to replicate these. Perhaps it is something unique to this install? Are you seeing similar warnings across all of your sites / any others?

Hi @kory,

sorry for missing to reply here.

It just happened again.

This time this is a new website (Still not public). It had two migrations along the way, but that never posed a problem. It was updated to Beta 4. This issue wasn’t immediately visible. The other website that has it is a website that was recently upgraded from X to Pro.

Downgrading fixes the issue.

Here is the sample of the error:

Warning: Undefined array key "advanced-custom-fields-pro" in /home/customer/www/*/public_html/wp-content/themes/pro/framework/legacy/functions/updates/class-tgm-plugin-activation.php on line 1898

Warning: Trying to access array offset on value of type null in /home/customer/www/*/public_html/wp-content/themes/pro/framework/legacy/functions/updates/class-tgm-plugin-activation.php on line 1898

Warning: Undefined array key "advanced-custom-fields-pro" in /home/customer/www/*/public_html/wp-content/themes/pro/framework/legacy/functions/updates/class-tgm-plugin-activation.php on line 1915

Warning: Trying to access array offset on value of type null in /home/customer/www/*/public_html/wp-content/themes/pro/framework/legacy/functions/updates/class-tgm-plugin-activation.php on line 1915

Credentials included.

Thanks!

Thanks, @Misho! I’ve noted this down and we will see what we can do here.

1 Like

Hi @kory, you probably didn’t even get the chance to work on this before the RC, but just FYI, plugin page is still broken after updating to RC. Switching to a stock theme is currently the only way to work with plugins.

I’m curious as well about that is going on here, since it seems that not everyone is affected by this.

1 Like

We took a look at removing the warning @Misho. This is a 3rd party plugin we are using for determining plugins installed, file_path is the array access key that it is trying to grab. This error would only happen if it thought ACF was installed, but couldn’t find it. I would try reinstalling ACF, we’ll take a look at your site in this cycle too. Thanks!

Thanks @charlie!

I did removed the ACF completely while testing, and that didn’t changed the fact. It also happens with all plugins deactivated.

Noted, okay we’ll take a look at your site thanks!

1 Like

Hey @Misho. This is a strange one we might have to try some things. You’ll notice the Pro extensions page is also missing extensions. that’s where we use this library to check plugins that is giving you the warnings. I remember seeing another version of the second site, is there anything different hosting wise for this staging to another?

Try this, it might fix it.

  • Delete site wp_options where option_name equals x_extension_list
  • revoke validation
  • revalidate the site.

Can you access this endpoint from either server that is giving these warnings? Only interested if you getting anything other than JSON.

curl https://theme.co/api-v2/packages/test

1 Like

Hi @charlie!

I just found out what was going on. It looks like Siteground spined up those installs with PHP 8.2.0.

As soon as I reverted PHP to 8.1.12, the plugins showed up again.

Is it possible that Pro is compatible up to 8.1.12?

Thanks!

1 Like

That’s very possible, I’ll have to try it out in 8.2. Ubuntu 22 is still on 8.1.2 for my packages and I’m not sure WP supports 8.2 yet, but I’ll get you some answers on support. I do see the extension page is back on your site. Thanks so much for bringing this to our attention.

1 Like