Major failure when log object is too long

  • Resolved axelkratel

    (@axelkratel)


    10 months, 2 weeks ago

    The log manager stopped working properly when one log item become too long and the display overlaid on top of the bottom UI elements to clear the log. The drop down for selecting the type of error to display also stopped working. Trying to log more errors would not get rid of the oversized object at the bottom, which was very strange, so the oversized log object would stay as item 39 no matter how many more log entries accumulated. Nuking the log file manually in the uploads dir fixed the issue. The layout should be fixed so that an oversized object doesn’t float over the clear log button, alternatively, move the clear log button to the top, which honestly is where it belongs anyway. As for why this fails, sorry I don’t have more debug info. I think it’s easy to reproduce by creating a large log string.

    • This topic was modified 10 months, 2 weeks ago by axelkratel.
    • This topic was modified 10 months, 2 weeks ago by axelkratel.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Bowo

    (@qriouslad)

    10 months, 2 weeks ago

    @axelkratel thanks for reporting this. I just wished you shared a screenshot as well, so I have a clear visual idea of how it looks, and what plugin/theme caused the error, just so it can be more easily reproduced (and fixed). So, this is well-noted for now. Thanks again.

    Thread Starter axelkratel

    (@axelkratel)

    10 months, 2 weeks ago

    I don’t think it was a plug-in that was interfering. What happened Is that the CSS caused a really large log entry to overflow on top of the clear log button. That should be easy to reproduce with a really big log entry that contains a bunch of HTML. The giant log entry was a mistake it didn’t belong in a log dump. Nevertheless, it just overflowed. I can try to reproduce and see what happens. I also wonder if HTML in the log entry could interfere with the actual layout. Although the way, I assumed that you do a WP sanitize on those fields before displaying them.

    Plugin Author Bowo

    (@qriouslad)

    10 months, 2 weeks ago

    @axelkratel Yes, output to the DLM dashboard should already be properly escaped, so, the HTML code should not be interfering with the layout. If you’re able to reproduce the issue, please also share the log entry content (maybe copied from the raw debug.log file somewhere, e.g. to google docs). This is so I can reliably reproduce the issue to investigate the fix. Thank you.

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

The topic ‘Major failure when log object is too long’ is closed to new replies.