• I received this message/warning from WordPress via email:

    WordPress has a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with one of your plugins, wp-Typography.

    First, visit your website (https://www.nealumphred.com/) and check for any visible issues. Next, visit the page where the error was caught (https://www.nealumphred.com/wp-login.php?checkemail=registered) and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can't access your dashboard normally, WordPress now has a special "recovery mode". This lets you safely login to your dashboard and investigate further.

    https://www.nealumphred.com/wp-login.php?action=enter_recovery_mode&rm_token=HQQT9da3bBVKS3NWhKJ5KL&rm_key=aFvl47LVkwwIolbqjbxm8q

    To keep your site safe, this link will expire in 1 day. Don't worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 6.7.1
    Active theme: GeneratePress (version 3.5.1)
    Current plugin: wp-Typography (version 5.10.1)
    PHP version 8.3.14

    Error Details
    =============
    An error of type E_ERROR was caused in line 177 of the file /home2/nealumph/public_html/wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/wp-data-storage/src/class-transients.php. Error message: Uncaught TypeError: get_class(): Argument #1 ($object) must be of type object, false given in /home2/nealumph/public_html/wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/wp-data-storage/src/class-transients.php:177
    Stack trace:
    #0 /home2/nealumph/public_html/wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/wp-data-storage/src/class-transients.php(116): WP_Typography\Vendor\Mundschenk\Data_Storage\Transients->maybe_fix_object()
    #1 /home2/nealumph/public_html/wp-content/plugins/wp-typography/includes/wp-typography/class-implementation.php(571): WP_Typography\Vendor\Mundschenk\Data_Storage\Transients->get_large_object()
    #2 /home2/nealumph/public_html/wp-content/plugins/wp-typography/includes/wp-typography/class-implementation.php(508): WP_Typography\Implementation->get_typography_instance()
    #3 /home2/nealumph/public_html/wp-content/plugins/wp-typography/includes/wp-typography/class-implementation.php(482): WP_Typography\Implementation->maybe_process_fragment()
    #4 /home2/nealumph/public_html/wp-content/plugins/wp-typography/includes/wp-typography/class-implementation.php(370): WP_Typography\Implementation->process()
    #5 /home2/nealumph/public_html/wp-includes/class-wp-hook.php(326): WP_Typography\Implementation->process_title()
    #6 /home2/nealumph/public_html/wp-includes/plugin.php(205): WP_Hook->apply_filters()
    #7 /home2/nealumph/public_html/wp-includes/post-template.php(174): apply_filters()
    #8 /home2/nealumph/public_html/wp-includes/link-template.php(4766): get_the_title()
    #9 /home2/nealumph/public_html/wp-includes/link-template.php(4748): get_the_privacy_policy_link()
    #10 /home2/nealumph/public_html/wp-login.php(354): the_privacy_policy_link()
    #11 /home2/nealumph/public_html/wp-login.php(1243): login_footer()
    #12 {main}
    thrown

    What should I do?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author pepe

    (@pputzer)

    It looks like the transient cache got corrupted. Please try to press the Clear Cache button in the wp-Typography settings page. It should make your system fix itself. Please let me know if it happens again.

    Thread Starter nealumphred

    (@nealumphred)

    PEPE

    Thanks for getting back to me!

    I have cleared the plugin cache. How will I know if I was successful?

    NEAL

    Plugin Author pepe

    (@pputzer)

    Well, it should just work (and you should not see the same error in the logs/Site Health).

    Thread Starter nealumphred

    (@nealumphred)

    P

    It appears to be working fine.

    There is nothing in Site Health calling attention to it as a problem but I had not thought to check that out earlier.

    Thanks!

    N

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.