• Resolved 4mostip

    (@4mostip)


    On several, but not all, of my blogs

    https://example.com/wp-admin/update-core.php?action=do-plugin-upgrade

    does not report progress or completion.

    It does (usually) install a single plugin OK, but short of manual scrutiny of the plugins page, there is no way to know whether the update actually worked or not.

    Also it does not return control to enable mission control to launch update tasks for any subsequent plugins in a queue for update.

    Whilst not a big deal for a single blog, this becomes a major time-waster across multiple blogs times multiple plugins.

    So I’d like to debug and fix this – and port the fix to other blogs suffering similarly.

    To start, I need to trace the actions of “update-core.php” and its subtasks (if any).

    Can anyone guide me towards a reasonably accessible reference or resource for tracking wordpress internals?

    Thanks in advance.
    Steve

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter 4mostip

    (@4mostip)

    PS Forgot to mention, this problem is NOT specific to WP version 3.8
    Steve

    Try turning debug on and enabling error logging. Also check your site’s error logs.

    Thread Starter 4mostip

    (@4mostip)

    @esmi – debug and error logs reveal nothing useful.

    However, researching the forum history turned up some old tips I had neglected to try before asking for help. Shame on me – sorry.

    • disable all plugins
    • swap themes
    • increase RAM allocation

    Disabling plugins fixed this issue.
    Now just remains to isolate the little monkey responsible.
    Steve

    Thread Starter 4mostip

    (@4mostip)

    The plugin <WP HTTP Compression(version 1.0)> is the one causing the problem.

    Why it is a problem is as yet unknown, but it has not been updated since 2012-7-11 and compatibility has not been verified beyond WPv2.9.2

    Since original installation, I later implemented use of Cloudflare as Content Delivery Network, with compression option activated. I suppose this could perhaps be source of confusion for <WP HTTP Compression>. In any event, the latter is now redundant and can be suppressed.

    Topic Resolved
    Steve.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Updates are not communicating progress’ is closed to new replies.