• Resolved oakleystudio

    (@oakleystudio)


    I have a client who uses Members to control access in their WordPress site. When she tries to update any User account data, she sees error messages on the screen when she hits the “Update Profile” button. It’s disconcerting, but it does not seem to prohibit any edits from being properly stored. Here are the errors we’re seeing…

    Warning: Illegal offset type in isset or empty in /…/plugin.php on line 174

    Warning: Illegal offset type in isset or empty in /…/wp-includes/plugin.php on line 174

    Warning: Cannot modify header information – headers already sent by (output started at /…/wp-includes/plugin.php:174) in /…/wp-includes/pluggable.php on line 1355

    Warning: Cannot modify header information – headers already sent by (output started at /…/wp-includes/plugin.php:174) in /…/wp-includes/pluggable.php on line 1358
    (Note: I have replaced the full file path on the web server with “…” in these error messages, in order to not share that info here in the WordPress forums.)

    Please let me know if you have a solution for this.

Viewing 5 replies - 1 through 5 (of 5 total)
  • I have the same problem. But I only get this error if I add a new role to users by editing their profile. If instead I search for the user in Users in the Dashboard and then select the box besides the user and add or remove the role from there – without editing the profile – I get no php error – actually it’s a warning and doesn’t appear to have any effect on the operation of member roles.
    Warning: Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174

    However, it should be fixed. I am using latest version of Members plugin by the way – v3.2.1

    Thanks
    Robert

    Plugin Author Caseproof

    (@caseproof)

    Hi @oakleystudio and Robert,

    I just tested this on my local installation and couldn’t reproduce this issue. Could you please provide a full stack trace of this warning? All warnings inserted in the previous sections are core WordPress warnings that may be caused by some plugin conflict.

    Best

    Thanks for checking. However, on further investigation it appears the problem is not with the Members plugin but updating User Profiles. The problem looks like it’s coming from the Members plugin if you add new member roles via the User Profile. But in fact if you simply save the User Profile without changing anything, the error recurs. So not your problem I think.

    All the best
    Robert

    Thread Starter oakleystudio

    (@oakleystudio)

    Here is what I see in the debug log (edited to remove file path details):

    [11-May-2022 17:09:00 UTC] PHP Warning:  Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174
    [11-May-2022 17:09:00 UTC] PHP Warning:  Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174
    [11-May-2022 18:10:46 UTC] PHP Warning:  Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174
    [11-May-2022 18:10:46 UTC] PHP Warning:  Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174
    [11-May-2022 18:11:12 UTC] PHP Warning:  Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174
    [11-May-2022 18:11:12 UTC] PHP Warning:  Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174
    [11-May-2022 18:11:26 UTC] PHP Warning:  Illegal offset type in isset or empty in /wp-includes/plugin.php on line 174

    And here is a chunk of the slow PHP log file:

    [11-May-2022 12:26:23]  [pool hikers] pid 12444
    script_filename = /index.php
    [0x00007faf77013ec0] sleep() /wp-content/plugins/mailpoet/lib/Cron/DaemonHttpRunner.php:113
    [0x00007faf77013e50] pauseExecution() /wp-content/plugins/mailpoet/lib/Cron/DaemonHttpRunner.php:101
    [0x00007faf770139c0] run() /wp-content/plugins/mailpoet/lib/Router/Endpoints/CronDaemon.php:42
    [0x00007faf77013940] run() /wp-content/plugins/mailpoet/lib/Router/Router.php:68
    [0x00007faf770138d0] call_user_func() /wp-content/plugins/mailpoet/lib/Router/Router.php:68
    [0x00007faf77013830] init() /wp-content/plugins/mailpoet/lib/Config/Initializer.php:369
    [0x00007faf770137b0] postInitialize() /wp-includes/class-wp-hook.php:307
    [0x00007faf770136d0] apply_filters() /wp-includes/class-wp-hook.php:331
    [0x00007faf77013660] do_action() /wp-includes/plugin.php:474
    [0x00007faf77013580] do_action() /wp-settings.php:609
    [0x00007faf770133d0] [INCLUDE_OR_EVAL]() /wp-config.php:98
    [0x00007faf770131a0] [INCLUDE_OR_EVAL]() /wp-load.php:50
    [0x00007faf77013100] [INCLUDE_OR_EVAL]() /public/wp-blog-header.php:13
    [0x00007faf77013070] [INCLUDE_OR_EVAL]() /index.php:17

    Does this tell you anything useful?

    Plugin Author Caseproof

    (@caseproof)

    Thank you for the logs. The first log is just generic warnings and the second log points to Mailpoet plugin, so you’d need to reach out to their support.

    Best

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Members Causing Errors When Editing Users’ is closed to new replies.