• Resolved monkeyleo13

    (@monkeyleo13)


    We realized that since Tablepress 2.2 and 2.2.1 don’t work if we need to enter “Edit site” and we got error. Otherwise, Tablepress works fine on post/page. We thought it’s Wordfence but turned out it was Tablepress. We had to downgrade it to 2.1.8 and it works fine. We’re running WP multisite.

    It throws error info: Fatal error: Uncaught Error: Undefined constant “SECURE_AUTH_COOKIE” in …\wp-includes\pluggable.php?on line?929 when we enter “Edit site” page.

Viewing 15 replies - 1 through 15 (of 18 total)
  • Plugin Author TobiasBg

    (@tobiasbg)

    Hi @monkeyleo13!

    Thanks for your post and sorry for the trouble!

    Hhm, I can not reproduce this on my sites and haven’t seen similar reports so far. Could you maybe post the full stack trace that you should be seeing in that error message?

    Note that it’s possible that the actual bug here is in another plugin, and that TablePress just happens to “uncover” it. Can you therefore please try again after temporarily deactivating all other plugins one by one? That way, we can find what’s causing this.

    Regards,
    Tobias

    Thread Starter monkeyleo13

    (@monkeyleo13)

    That would be Wordfence plugin.

    PHP Fatal error:  Uncaught Error: Undefined constant "SECURE_AUTH_COOKIE" in F:\inetpub\wwwroot\site\wp-includes\pluggable.php:929
    Stack trace:
    #0 F:\inetpub\wwwroot\site\wp-includes\pluggable.php(694): wp_parse_auth_cookie()
    #1 F:\inetpub\wwwroot\site\wp-includes\class-wp-hook.php(310): wp_validate_auth_cookie()
    #2 F:\inetpub\wwwroot\site\wp-includes\plugin.php(205): WP_Hook->apply_filters()
    #3 F:\inetpub\wwwroot\site\wp-includes\user.php(3622): apply_filters()
    #4 F:\inetpub\wwwroot\site\wp-includes\pluggable.php(70): _wp_get_current_user()
    #5 F:\inetpub\wwwroot\site\wp-includes\l10n.php(98): wp_get_current_user()
    #6 F:\inetpub\wwwroot\site\wp-includes\l10n.php(152): get_user_locale()
    #7 F:\inetpub\wwwroot\site\wp-includes\l10n.php(1300): determine_locale()
    #8 F:\inetpub\wwwroot\site\wp-includes\l10n.php(1331): _load_textdomain_just_in_time()
    #9 F:\inetpub\wwwroot\site\wp-includes\l10n.php(185): get_translations_for_domain()
    #10 F:\inetpub\wwwroot\site\wp-includes\l10n.php(297): translate()
    #11 F:\inetpub\wwwroot\site\wp-content\plugins\wordfence\modules\login-security\classes\controller\ajax.php(60): __()
    #12 F:\inetpub\wwwroot\site\wp-content\plugins\wordfence\modules\login-security\classes\controller\wordfencels.php(36): WordfenceLS\Controller_AJAX->init()
    #13 F:\inetpub\wwwroot\site\wp-content\plugins\wordfence\modules\login-security\wordfence-login-security.php(90): WordfenceLS\Controller_WordfenceLS->init()
    #14 F:\inetpub\wwwroot\site\wp-content\plugins\wordfence\lib\wordfenceClass.php(52): require('...')
    #15 F:\inetpub\wwwroot\site\wp-content\plugins\wordfence\wordfence.php(125): require_once('...')
    #16 F:\inetpub\wwwroot\site\wp-settings.php(407): include_once('...')
    #17 F:\inetpub\wwwroot\site\wp-config.php(101): require_once('...')
    #18 F:\inetpub\wwwroot\site\wp-load.php(50): require_once('...')
    #19 F:\inetpub\wwwroot\site\wp-admin\admin.php(34): require_once('...')
    #20 F:\inetpub\wwwroot\site\wp-admin\site-editor.php(12): require_once('...')
    #21 {main}
      thrown in F:\inetpub\wwwroot\site\wp-includes\pluggable.php on line 929
    PHP Fatal error:  Uncaught Error: Undefined constant "SECURE_AUTH_COOKIE" in F:\inetpub\wwwroot\site\wp-includes\pluggable.php:929
    Stack trace:
    #0 F:\inetpub\wwwroot\site\wp-includes\pluggable.php(694): wp_parse_auth_cookie()
    #1 F:\inetpub\wwwroot\site\wp-includes\class-wp-hook.php(310): wp_validate_auth_cookie()
    #2 F:\inetpub\wwwroot\site\wp-includes\plugin.php(205): WP_Hook->apply_filters()
    #3 F:\inetpub\wwwroot\site\wp-includes\user.php(3622): apply_filters()
    #4 F:\inetpub\wwwroot\site\wp-includes\pluggable.php(70): _wp_get_current_user()
    #5 F:\inetpub\wwwroot\site\wp-includes\l10n.php(98): wp_get_current_user()
    #6 F:\inetpub\wwwroot\site\wp-includes\l10n.php(152): get_user_locale()
    #7 F:\inetpub\wwwroot\site\wp-includes\l10n.php(894): determine_locale()
    #8 F:\inetpub\wwwroot\site\wp-includes\class-wp-fatal-error-handler.php(47): load_default_textdomain()
    #9 [internal function]: WP_Fatal_Error_Handler->handle()
    #10 {main}
      thrown in F:\inetpub\wwwroot\site\wp-includes\pluggable.php on line 929
    Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    thanks for that! I’ve been trying to replicate this with only Wordfence 7.10.6 and TablePress 2.2.2 on a WordPress 6.3.2 site with the Twenty Twenty-Three theme installed, but can’t see any issues or errors. (Of course, I don’t have the same Wordfence configuration, so that might be a reason as well.)

    What WordPress version are you using?

    Can you check if this problem happens only with Wordfence and TablePress active (and all other plugins deactivated), and with a WordPress default theme like Twenty Twenty-Three?

    Regards,
    Tobias

    Thread Starter monkeyleo13

    (@monkeyleo13)

    I did test with default theme (Twenty Twenty-Three) before but now I disabled all plugins while leave wordfence and tablepress (2.2.2 now) enabled, same issue. Oh we’re running latest WP: 6.3.2 and PHP 8.1.

    Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    ok, thanks for testing that! I’m really confused why I can’t reproduce this with the same plugins/theme then…

    Now, as WordPress 6.4 will be released tomorrow (and will contain quite some changes for the site editor as well), I suggest that we wait until after that. Maybe the update to WordPress 6.4 already helps here (as I can imagine that WordPress might also play a role here — after all, TablePress isn’t doing anything special regarding the site editor, except for offering a block for the block editor).

    Best wishes,
    Tobias

    Thread Starter monkeyleo13

    (@monkeyleo13)

    Thank you for your time! I think it’s not Tablepress but… I have another dev site and I tested it, it works fine but I realized it’s single WP site so I will test another dev WP multisite pretty soon.

    Thread Starter monkeyleo13

    (@monkeyleo13)

    Ok I had chance to test another dev for WP Multisite and I think I found it that I thought maybe you able to replicate issue: if you enable network activate on both Tablepress and Wordfence, that’s where there is problem with “Edit site” unless you’re not use “network activate” on Tablepress but enable it on specific site, it works fine.

    Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    wow, great findings! I don’t have a multisite environment to test this in right now, but I’ll look into getting one set-up.

    I would still suggest that we also check this out with the mentioned WordPress 6.4, coming tonight.

    And just to confirm: This only happens with the combination of TablePress and Wordfence being network-activated, but not when just one of them is active?

    Regards,
    Tobias

    Thread Starter monkeyleo13

    (@monkeyleo13)

    …the combination of TablePress and Wordfence being network-activated, but not when just one of them is active?

    Correct. And when Wordfence begin network-activated while set Tablepress activated (not newtwork), works fine. I rather to set Tabledpress network-activated since it really best plugin for table solution out there so I don’t have to enable it every time I add a new site for clients.

    Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    thanks for the clarification!

    And now that WordPress 6.4 is available: Does that make any difference?

    I’m currently setting up a multisite for testing and will then look into this in more detail! Maybe I can find out what’s going on here…

    Regards,
    Tobias

    Thread Starter monkeyleo13

    (@monkeyleo13)

    Oh yea I forgot to mention on previous, yea same issue on 6.4.

    Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    ok, thanks for testing that! I’ll check this out in more detail!

    Regards,
    Tobias

    Plugin Author TobiasBg

    (@tobiasbg)

    Hi @monkeyleo13,

    I have now set up a multisite for testing and can reproduce the issue.

    From my findings, it involves the Freemius SDK, the software component that TablePress uses for things like licensing and handling of premium upgrades.

    Now, It seems that the Freemius developers have been made aware of this issue in https://github.com/Freemius/wordpress-sdk/issues/667 already (involving other plugins that use that SDK). I have also reached out to their support team in order to get their developers to take a look.

    So, I’m afraid that for now there’s nothing really that we can do here, except for waiting for a fix from Freemius. In the meantime, my recommendation is to either stay on TablePress 2.1.8 or to use the per-site activation. Thanks for your patience here!

    Regards,
    Tobias

    Thread Starter monkeyleo13

    (@monkeyleo13)

    Hey, seems like 2.2.3 fixed this issue which is good! Wonder if you got fixed from Freemius or something you update with js? Well anyway, want to say thank you!

    Plugin Author TobiasBg

    (@tobiasbg)

    Hi,

    thanks for the update! Well, that’s interesting ?? TablePress 2.2.3 doesn’t have any changes or fixes in this regard, at least not intentionally…

    Also, for me the error still happens on a fresh WordPress 6.4.1 multisite, when network activating (the only plugins) Wordfence 7.10.7 and then TablePress 2.2.3, and then going to the Site Editor.

    But if everything is fine for you now: Perfect! ??

    Regards,
    Tobias

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘2.2+, Error if enter “Edit site”’ is closed to new replies.