• Resolved John

    (@dsl225)


    Hello,

    I’m trying to update a site to PHP 8.3 from 7.4 where everything was working fine but I got this fatal error when testing:

    Fatal error: Uncaught Error: Failed opening required '/wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/src/partials/requirements-error-notice.php' (include_path='.:/opt/alt/php83/usr/share/pear:/opt/alt/php83/usr/share/php:/usr/share/pear:/usr/share/php') in /wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/src/class-wp-requirements.php:234

    Stack Trace
    1.
    WP_Typography\Vendor\Mundschenk\WP_Requirements->display_error_notice()
    /wp-content/plugins/wp-typography/includes/wp-typography/class-requirements.php:96
    2.
    WP_Typography\Requirements->admin_notices_dom_disabled()
    /wp-includes/class-wp-hook.php:324
    3.
    WP_Hook->apply_filters()
    /wp-includes/class-wp-hook.php:348
    4.
    WP_Hook->do_action()
    /wp-includes/plugin.php:517
    5.
    do_action()
    /wp-admin/admin-header.php:303
    6.
    require_once('/home/homedirg/...')
    /wp-admin/index.php:137
    7.
    {main}
    thrown in /wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/src/class-wp-requirements.php on line 234

    Warning: require(/wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/src/partials/requirements-error-notice.php): Failed to open stream: No such file or directory in /wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/src/class-wp-requirements.php on line 234

    Now, this is a bit confusing because I tested on another server with exactly the same PHP 8.3.16 version and everything is working fine without errors. Might be a sever misconfiguration or something but I prefer to let you know first if you have another idea.

    Thanks.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter John

    (@dsl225)

    … in fact, yes the other testing server also gets some warnings once I enable some settings:

    Deprecated: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /wp-content/plugins/wp-typography/vendor-scoped/mundschenk-at/wp-settings-ui/src/ui/class-abstract-control.php on line 336

    I didn’t set all settings and neither did I replicate all of them from the main site but it seems that those errors might depend on some settings.

    Plugin Author pepe

    (@pputzer)

    Hi @dsl225! The deprecation warning on the second server is expected, the fatal error is not. Can you check whether the file exists (it should)?

    Thread Starter John

    (@dsl225)

    If you mean this file at this path – no, it doesn’t exist:
    /wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/src/partials/requirements-error-notice.php

    but the structure is as follows:
    /wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/partials/requirements-error-notice.php
    and:
    /wp-typography/vendor-scoped/mundschenk-at/check-wp-requirements/src/class-wp-requirements.php

    Version 5.10.1 

    Plugin Author pepe

    (@pputzer)

    Thanks. There’s indeed a bug related to https://github.com/mundschenk-at/check-wp-requirements/commit/d24532378b15346725b6fe7a02cf26b3e4e2ae23 – looks like I just got lucky that no-one triggered a failed requirements check yet 😮

    I’ll try to release a fixed version later today.

    • This reply was modified 2 months, 1 week ago by pepe. Reason: typo
    Thread Starter John

    (@dsl225)

    OK, thanks!

    Plugin Author pepe

    (@pputzer)

    Should be fixed in 5.11.0.

    Thread Starter John

    (@dsl225)

    All good, many thanks!

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