Notice: Jetpack_Options was called incorrectly

Resolved almendron
(@almendron)

6 years, 3 months ago

I have updated to version 8.2.3 and an error message has appeared:

Notice: Jetpack_Options was called incorrectly. Not all plugins have loaded yet but we requested the class Jetpack_Options Please see Debugging in WordPress for more information. (This message was added in version 1.1.2.0.) in /xxxxxx7wp-includes/functions.php on line 4989

I have deactivated, deleted and reinstalled Jetpack without any results.

I will return to the previous version because I have no connection to JetPack
Debug: Revista de Prensa is not connected.: 200. Please contact Jetpack support.

The page I need help with: [log in to see the link]

Viewing 8 replies - 1 through 8 (of 8 total)

Plugin Support darnelldibbles
(@darnelldibbles)

6 years, 3 months ago

Hi there,

Yes, this is an issue we have recently encountered and have submitted and an issue has been created in GitHub to work on a fix:

https://github.com/Automattic/jpop-issues/issues/4799

However, would you please send us a copy of the debug log through our contact form https://jetpack.com/contact-support/? We can have the developers take a look to determine if it’s an issue with the plugin or if it would be something else.

Thank you!

Thread Starter almendron
(@almendron)

6 years, 3 months ago

https://github.com/Automattic/jpop-issues/issues/4799 : page not found

apache.error.log

[Fri Feb 28 17:00:03.188423 2020] [proxy_fcgi:error] [pid 725] [client 8.29.198.25:33715] AH01071: Got error ‘PHP message: PHP Notice: Jetpack_Options was called incorrectly. Not all plugins have loaded yet but we requested the class Jetpack_Options Please see Debugging in WordPress for more information. (This message was added in version 1.1.2.0.) in /usr/home/almendron/www/tribuna/wp-includes/functions.php on line 4989′
Thread Starter almendron
(@almendron)

6 years, 3 months ago
More data:

1) In almendron.com there are three sites. In two of them the error does not occur.

2) The three sites share themes and plugins

3) Local server: no problem

4) Version 8.1.1: no problem
- This reply was modified 6 years, 3 months ago by almendron.
Thread Starter almendron
(@almendron)

6 years, 3 months ago

Debug: https://www.almendron.com/compartir/jetpack/jetpack.txt

Thread Starter almendron
(@almendron)

6 years, 3 months ago

I have found the origin of the problem: plugin https://es.wordpress.org/plugins/publicize-with-hashtags/

Have you changed the way to check if a specific JetPack module is activated?

In the mentioned plugin:

if (!class_exists('Jetpack') || !Jetpack::is_module_active('publicize')) return;

In addition to that check, only the use of “_wpas_mess” could be the problem. The code restraint should not affect.

Plugin Contributor James Huff
(@macmanx)

6 years, 3 months ago

It would be have to be parse out of an array from https://developer.jetpack.com/hooks/jetpack_active_modules/

Since this is a third-party plugin though, it would be up to that plugin’s developer to get this fixed.

Thread Starter almendron
(@almendron)

6 years, 3 months ago

1) https://github.com/Automattic/jpop-issues/issues/4799 : page not found

2) How to verify if a Jetpack module is active?

if (!class_exists('Jetpack') || !Jetpack::is_module_active('publicize')) return;

It worked until version 8.1.1
Now it doesn’t work
How is it verified in the current version?

Plugin Support darnelldibbles
(@darnelldibbles)

6 years, 3 months ago

Hi there,

1) https://github.com/Automattic/jpop-issues/issues/4799 : page not found

Sorry for providing that link – it is a private Github issue that isn’t visible to you.

2) How to verify if a Jetpack module is active?

As @macmanx mentioned, verifying active Jetpack modules would have to be parsed out of an array from

https://developer.jetpack.com/hooks/jetpack_active_modules/

I would reach out to the developer of Publicize with Hashtags because ultimately, they would need to look into the issue on their end as a result of our update. It doesn’t look like they have updated their plugin in quite some time, so it was inevitable that it would have some eventual conflicts.

We do not provide support for custom code, so if you wanted to do this yourself, we recommend hiring someone from https://jetpack.pro/

Thanks,

Viewing 8 replies - 1 through 8 (of 8 total)

The topic ‘Notice: Jetpack_Options was called incorrectly’ is closed to new replies.