Double HTML entity encoding in logs view

  • Resolved witters

    (@witters)


    9 months, 1 week ago

    Firstly, thank you for a first-rate plugin 🙂

    I’ve noticed an issue with the logs display when the subject line contains special characters. These are being double encoded as HTML entities.

    I’ve run some tests to ensure the plain characters are passed in to wp_mail as their original characters, and they are. These values are are also stored correctly in the wp_fsmpt_email_logs table.

    Examples:

    • wp_fsmpt_email_logs.subject value: Subject Q&A with £ of success; displayed on log screen as Subject Q&A with £ of success
    • wp_fsmpt_email_logs.subject value: £ & < <strong> ç; displayed on log screen as £ &amp; &lt; <strong> ç

    Please can the logs display be corrected to accurately reflect the data in the logs database.

    Thanks

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

Viewing 1 replies (of 1 total)
  • Plugin Support Ibrahim Sharif

    (@ibrahimsharif)

    7 months ago

    Hello @witters,

    Thank you for your kind words about FluentSMTP, we truly appreciate your feedback! It’s always a pleasure to hear that our plugin is making a positive impact.

    Your detailed examples, such as “Subject Q&A with £ of success” appearing as “Subject Q&A with £ of success”, perfectly illustrate the problem. You are absolutely correct that the raw values are passed to wp_mail and stored accurately in the database. This behavior suggests that the subject strings, which are likely already HTML-escaped during storage (or before being presented to the display function), are then being escaped again when rendered on the log screen. This leads to the undesirable double encoding you’re seeing.

    Please be assured that this is purely a display issue within the log interface and does not affect the actual email content or its delivery. The emails themselves are sent with the correct subject lines as intended.

    This observation aligns with an area for improvement in our logging feature, and we have already prioritized and forwarded your detailed report to our development team. They will be looking into correcting this display behavior to ensure the logs accurately reflect the data as stored in your database. Hopefully, they will implement the improvements soon.

    Thank you for bringing this to our attention; your thorough testing and detailed explanation are incredibly helpful.

Viewing 1 replies (of 1 total)

The topic ‘Double HTML entity encoding in logs view’ is closed to new replies.