Forum Replies Created

Viewing 13 replies - 1 through 13 (of 13 total)
  • Thread Starter O3 Internet Consulting

    (@o3internet)

    Marking this as resolved.

    Thread Starter O3 Internet Consulting

    (@o3internet)

    Thanks! So it sounds like this is an issue that will be resolved in WP 6.2. Awesome ??

    Thread Starter O3 Internet Consulting

    (@o3internet)

    I am running WP 6.1.1.

    Here is the debug.log:

    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 63
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 73
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 89
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 102
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 111
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82
    [08-Feb-2023 21:38:24 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 63
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 73
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 89
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 102
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Cookie/Jar.php on line 111
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/websitename/public_html/wp-includes/Requests/Transport/cURL.php on line 345
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/websitename/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/websitename/public_html/wp-includes/Requests/Transport/cURL.php on line 345
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/websitename/public_html/wp-includes/Requests/Transport/cURL.php on line 345
    [08-Feb-2023 21:38:25 UTC] PHP Deprecated:  http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/websitename/public_html/wp-includes/Requests/Transport/cURL.php on line 345
    [08-Feb-2023 21:39:12 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function mysql_connect() in /home/websitename/public_html/wp-includes/class-wpdb.php:1807
    Stack trace:
    #0 /home/websitename/public_html/wp-includes/class-wpdb.php(734): wpdb->db_connect()
    #1 /home/websitename/public_html/wp-includes/load.php(562): wpdb->__construct()
    #2 /home/websitename/public_html/wp-settings.php(124): require_wp_db()
    #3 /home/websitename/public_html/wp-config.php(108): require_once('/home/websitename...')
    #4 /home/websitename/public_html/wp-load.php(50): require_once('/home/websitename...')
    #5 /home/websitename/public_html/wp-blog-header.php(13): require_once('/home/websitename...')
    #6 /home/websitename/public_html/index.php(17): require('/home/websitename...')
    #7 {main}
      thrown in /home/websitename/public_html/wp-includes/class-wpdb.php on line 1807
    [08-Feb-2023 21:39:12 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function mysql_connect() in /home/websitename/public_html/wp-includes/class-wpdb.php:1807
    Stack trace:
    #0 /home/websitename/public_html/wp-includes/class-wpdb.php(734): wpdb->db_connect()
    #1 /home/websitename/public_html/wp-includes/load.php(562): wpdb->__construct()
    #2 /home/websitename/public_html/wp-settings.php(124): require_wp_db()
    #3 /home/websitename/public_html/wp-config.php(108): require_once('/home/websitename...')
    #4 /home/websitename/public_html/wp-load.php(50): require_once('/home/websitename...')
    #5 /home/websitename/public_html/wp-blog-header.php(13): require_once('/home/websitename...')
    #6 /home/websitename/public_html/index.php(17): require('/home/websitename...')
    #7 {main}
      thrown in /home/websitename/public_html/wp-includes/class-wpdb.php on line 1807
    
    Thread Starter O3 Internet Consulting

    (@o3internet)

    I actually did put my site in Learning Mode yesterday, and the Facebook Debugger did not work, even after some time had passed.

    HOWEVER, I tried it again today, and the Facebook Debugger worked! I think there must have been some caching at some level (website, browser, Wordfence, or Facebook) preventing it from registering the changes, and it just needed a full day to register them.

    So yes, putting Wordfence Firewall back to Learning Mode resolved my issue with Facebook Debugger timing out.

    Thank you so much!

    Thread Starter O3 Internet Consulting

    (@o3internet)

    Hi everyone,

    I worked directly with the plugin author, and they found the issue and resolved it, which I will repost below.

    I tried this solution on another affected website, and it worked perfectly, with the responsive menu showing up on the site and in the new menu builder preview!

    Also, if you want your wp admin bar to reappear (Responsive Menu 4.0 makes it hide by default), you will need to change that in:

    Responsive Menu | Settings | Advance | Adjust for WP Admin Bar | None

    Your website theme does not have <?php wp_body_open(); ?> tag after HTML body tag in header.php

    This tag is a new requirement by WordPress after version 5.2

    https://make.www.ads-software.com/themes/2019/03/29/addition-of-new-wp_body_open-hook/

    Our developer added <?php wp_body_open(); ?> into customer’s header.php file

    He then switched to version 4.0.0 on customer’s website and it is working now.

    Responsive Menu button is showing up in iPhone and iPad view.

    Note: They really do mean put this in right after the body tag, so that my resulting header.php had the following code:

    <body <?php body_class(); ?>>
    <?php wp_body_open(); ?>

    Thank you very much Kriti and the Responsive Menu team!

    Thread Starter O3 Internet Consulting

    (@o3internet)

    I have rolled my TEC version back to 5.2.1 so that the calendar will work, and took screenshots of what it looked like when it was broken.

    This is a temporary workaround. Please full fix this issue.

    Thread Starter O3 Internet Consulting

    (@o3internet)

    Update: I rechecked my Chrome, and it is broken there, too, it was just very, very cached.

    Thread Starter O3 Internet Consulting

    (@o3internet)

    I will go ahead and mark this ticket as resolved, and hope that we can solve this problem offline.

    Thread Starter O3 Internet Consulting

    (@o3internet)

    Hi Kriti,

    I will go ahead and open an additional ticket there.

    Should I keep this ticket open in the meantime?

    Thread Starter O3 Internet Consulting

    (@o3internet)

    I have not run an optimize table before – is that a function of WF?
    If yes, how do I do it?

    I found another support ticket where the person seemed to have the same issue, but it did not show me how to apply the solution – is this related?

    https://www.ads-software.com/support/topic/large-wfconfig-table-causing-php-crash/

    Thread Starter O3 Internet Consulting

    (@o3internet)

    I just sent it.

    Thread Starter O3 Internet Consulting

    (@o3internet)

    I am wondering if the tables are corrupt in some way. When you say you reinstall the plugin, are you also removing all the tables along with it?

    Correct, I completely deactivated and deleted the plugin, making sure that the option under All Options | General Wordfence Options | Delete Wordfence tables and data on deactivation is selected.

    You can backup your Wordfence settings via the Export option.

    Yes, I do this, and Import the settings upon re-installation and reactivation.

    The firewall will be in Learning Mode by default for 7 days. I would recommend switching this to Enabled and Protected as soon as possible.

    I normally let it stay in Learning Mode for a bit longer so it gets more of a snapshot of normal website behavior / traffic – at least one month – could that be a factor?

    Thread Starter O3 Internet Consulting

    (@o3internet)

    I have done so.

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