Support » Plugin: Jarvis » Warning after updating to v 1.0.1

  • Installed the 1.0.1 update and see this warning in admin and on every site

    Warning: call_user_func_array() expects parameter 1 to be a valid callback, class ‘Jarvis\Plugin’ not found in /home/xxxxxx/public_html/wp-includes/class-wp-hook.php on line 286

    Have reverted to the earlier version of Jarvis until resolved.

Viewing 9 replies - 1 through 9 (of 9 total)
  • Thread Starter omar1000

    (@omar1000)

    Unfortunately still the same error in the new update 1.0.2

    Warning: call_user_func_array() expects parameter 1 to be a valid callback, class ‘Jarvis\Plugin’ not found in /xxx/xxx/wp-includes/class-wp-hook.php on line 286

    Plugin Author kshaner

    (@kshaner)

    Hi Omar,

    Could you update to 1.0.3? If that does not work please try uninstalling and re-installing.

    If that still does not fix the issue please provide the versions of WordPress and php that you are using and I will ensure that we get it working for you.

    Kurtis

    Hello Kurtis,
    I am having the same issue. I uninstalled, and then installed 1.0.3 but get the same message (ciceroschools.com). I tried reverting to version 0.51.0 but still have the same warning message.
    Wordpress version: 4.9.8

    Thanks,
    Paul

    Plugin Author WDG

    (@wdgdc)

    Hi Paul,

    It seems that you’re missing a file that is included in the standard plugin. I see you’re running WordPress 4.9.8 so that’s good. Could you answer some questions for me:

    1. How did you install the plugin?
    2. What version of php are you running and have any functions been disabled? (If you know this) If any autoloading functions have been disabled that would cause an issue.
    3. What host are you on? (If that’s okay to know).

    Try deleting and uploading the latest zip file from here: https://github.com/WDGDC/Jarvis/releases to see if that solves your issue.

    Kurtis

    Edit: posted from wrong account, but still the same person

    • This reply was modified 2 years, 3 months ago by WDG.
    Thread Starter omar1000

    (@omar1000)

    Hi Kurtis,
    i did uninstall the old version, installed the new version from github, but same error.
    installed directly the current version from wordpress, same error

    wordpress 4.9.8
    php 7.1.15
    host domainfactory

    i tried the plugin on my localhost, with all the same other plugins, and here it is working without any error!

    thx omar

    Hi All,

    same problem here, also running on Host DOMAINFACTORY
    WP 4.9.8
    PHP 7.2.11

    OUTPUT IN WP BACKEND IS:
    <b>Warning</b>: call_user_func_array() expects parameter 1 to be a valid callback, class ‘Jarvis\Plugin’ not found in <b>/MY_PATH_TO_WP/wp-includes/class-wp-hook.php</b> on line <b>286</b><br />
    <br />
    <b>Warning</b>: Cannot modify header information – headers already sent by (output started at /MY_PATH_TO_WP/wp-includes/class-wp-hook.php:286) in <b>/MY_PATH_TO_WP/wp-admin/includes/misc.php</b> on line <b>1126</b><br />

    Note: MY_PATH_TO_WP represents the server path for my specific WordPress install.

    Looks like it may be a Domainfactory specific problem 🙁

    Anguel

    EDIT: Looks like one of the customers having the problem is not at Domainfactory, so it may not be specific to this host.

    • This reply was modified 2 years, 3 months ago by iAnguel.
    • This reply was modified 2 years, 3 months ago by iAnguel. Reason: Maybe not Domainfactory-specific

    Hello,
    Seeing the same issue on Siteground install after updating the plugin.

    Plugin Author kshaner

    (@kshaner)

    To everyone who is having this issue. Could you please send me a copy of your php setup information. The output of a phpinfo(); call would be enough and I’ll try and replicate the settings to see what’s going on. Please send it to kurtis [@] webdevelopmentgroup.com

    Plugin Author kshaner

    (@kshaner)

    Hi all,

    Sorry for the long delay. This has been fixed in the latest 1.0.4 version of the code. The issue had to do with the way the autoloader was converting class names to file names and when the webroot had an _ character in it. E.g. example.com/public_html would fail where example.com/www would work.

    Kurtis

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Warning after updating to v 1.0.1’ is closed to new replies.