• plugin does not work on WP 4.8. This is not a theme specific issue, we tested it using the 2017 default WP theme on WPengine. try it out, install it and run it…

    also, prior to 4.8 this plugin worked less than 25% of the time on the STAGE sites
    (tested on 20 sites on WPengine, only 4 worked)

    Please, consider a re-write, this was a good idea…

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Jason Stallings

    (@octalmage)

    Hi Christian,

    Sorry you’re having issues with the plugin. What issues are you seeing? I just tested with 4.8 on WP Engine on a couple of installs and the scan completed without issue.

    Thanks!

    Hi Christian Zagarskas (@thezman),
    We have used this plugin on at least a couple of versions of WP, and at least the last three versions of PHP (prior to each upgrade).
    This plugin has performed its function most of the time; not all of the time.

    But we have never upgraded, until we have run a test through to completion, to identify which plugins are not up to compatibility.
    If it were not for this plugin, we would probably be back at PHP5.6.
    Also, a number of the plugins we use that showed incompatibilities have updated after being notified (may not be directly due to notification).

    The times when plugin scans have gone awry, is usually related to our shared server, getting loaded by other sites on the same share. We have made some suggestion topics for improvements to the “reporting of progress during a scan”, which (reportings) would be quite useful in your type of situation.

    So;
    1) Christian Zagarskas (@thezman), can you try to supply a bit more information about how the failure takes place?
    and
    2) Jason Stallings (@octalmage), is it possible to have the plugin collect some information on the progress of the scan, and maybe server state during the scan (optionally set to be permitted by the user), so this information can be sent back to the plugin author, on completion of scans that took longer than usual, and on scans that did not complete.
    Additional – this information might be made optionally viewable to the user by choosing a “detailed view” for the scan, or “progress indication” for briefer information.

    Thread Starter thezman

    (@thezman)

    Are you testing it directly on WPengine as a “normal user” would?
    Are you using it on the STAGE site version of WPengine?

    Unfortunately I have no way to confirm “why” the plugin fails, I can tell you that when I open the support chat window with WPengine they do not know either, they just say “it’s your theme”. (which does not seem a legit answer since this plugin says it does not run/execute theme files)

    However, they CAN use SSH to monitor the output and then they paste the results in the chat window… since SSH is jailed on all WPengine accounts and the error log is “customized” so am I from debugging the issue effectively

    This leads me to suspect that some kind of output buffering conflict is the issue… at any rate, maybe a simple solution is to add a button that says “raw output” and then just link to whatever the tech support folks are sending me?

    If you like, please feel free to contact me and we can take a look at the sites this was an issue with. Let me know the best way to accomplish this, for example, maybe a live screen session or chat window would work?

    Thank you for looking into this.

    • This reply was modified 7 years, 5 months ago by thezman.
Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘GREAT IDEA- but needs to be REWRITTEN (or Removed)’ is closed to new replies.