5.10.0 error on 7.4

  • Matt Ortega

    (@mortega)


    3 days, 12 hours ago

    Tested out the recent update for 5.10.0 on local dev environments with 7.4 and every time it produced an error.

    Here are the details produced via the WordPress auto-notification:

    Error Details
    =============
    An error of type E_ERROR was caused in line 205 of the file /nas/content/live/[REDACTED]/wp-content/plugins/redirection/redirection.php. Error message: Uncaught Error: Failed opening required '/nas/content/live/    [REDACTED]/wp-content/plugins/redirection/api/api.php' (include_path='.:/usr/share/pear/php:/usr/share/php') in /nas/content/live/[REDACTED]/wp-content/plugins/redirection/redirection.php:205
    Stack trace:
    #0 /nas/content/live/[REDACTED]/wp-settings.php(597): include_once()
    #1 /nas/content/live/[REDACTED]/wp-config.php(119): require_once('/nas/content/li...')
    #2 /nas/content/live/[REDACTED]/wp-load.php(50): require_once('/nas/content/li...')
    #3 /nas/content/live/[REDACTED]/wp-admin/admin.php(35): require_once('/nas/content/li...')
    #4 /nas/content/live/[REDACTED]/wp-admin/plugins.php(10): require_once('/nas/content/li...')
    #5 {main}
      thrown

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author John Godley

    (@johnny5)

    3 days, 7 hours ago

    How did you update the plugin? api/api.php does not exist in the plugin and I don’t know why your site is trying to load it. Could the update have failed? Do you have a caching system?

    Thread Starter Matt Ortega

    (@mortega)

    3 days, 7 hours ago

    Attempted to update the plugin from within plugins.php locally and on the staging server as well as through WP-Engine’s interface on the staging server.

    Every time the plugin was described as successfully updated.

    No caching system within WordPress itself though WP-Engine’s servers do.

    Plugin Author John Godley

    (@johnny5)

    3 days ago

    Ah, WP Engine, of course. They do seem to use an aggressive caching system. You can see the actual file doesn’t contain the erroring code. It might be worth asking WP Engine support how to clear whatever is cached.

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

You must be logged in to reply to this topic.