#215 — In any email sent from a response, we see System Message: WARNING Literal block expected; none found.

by dennisharrison — last modified Jul 31, 2009 01:58 AM

State	Resolved
Version:	1.2
Area	Functionality
Issue type	Bug
Severity	Medium
Submitted by	dennisharrison
Submitted on	May 22, 2009
Responsible	Maurits van Rees
Target release:	1.2

Return to tracker

Plone 3.2
Poi 1.2.3 (egg)

Here is what we get in the email.

Response Details:

System Message: WARNING/2 (<string>, line 16)
Literal block expected; none found.

In the initial email (new issue) we don't see this (as there is no response I guess?).

Steps to reproduce:: create a tracker
check send notification emails
put an email address in mailing list
create an issue
respond to the issue
check email
make frowny face at error

Added by Maurits van Rees on May 22, 2009 07:23 PM

Ehm, that is one of the things that I fixed in Poi 1.2.3. Are you quite sure that is the version you are using?

I do not get the error here. Can you paste a response here that triggers the error?

Or even better: the emails also have a plain text part; can you paste the plain text part of an email that has such a warning in the html part?

Added by dennisharrison on May 22, 2009 07:43 PM

Poi 1.2.3 in prefs_install_products_form

--===============5139736139901058109==
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

A new response has been given to the issue **Sheila **
in the tracker **Customer Incidents** by **Keith Taubin**.

Response Information
--------------------

Issue
  Sheila (http://service.ait.la/[…]/20)

**Response Details**::

Called and couldn't leave a message the message center was full.
    I'll try again later

* This is an automated email, please do not reply - AiT - SERVICE
--===============5139736139901058109==
MIME-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/[…]/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
      xml:lang="en"
      lang="en">

  <head>
     <meta http-equiv="Content-Type" content="text/html; charset=US-ASCII" />

    <style type="text/css" media="all">

    </style>

  </head>

  <body>
<p>A new response has been given to the issue <strong>Sheila **
in the tracker **Customer Incidents</strong> by <strong>Keith Taubin</strong>.</p>
<div class="section">
<h4><a id="response-information" name="response-information">Response Information</a></h4>
<dl class="docutils">
<dt>Issue</dt>
<dd>Sheila (<a class="reference" href="http://service.ait.la/[…]/a>)</dd>
</dl>
<p><strong>Response Details</strong>:</p>
<div class="system-message">
<p class="system-message-title">System Message: WARNING/2 (<tt class="docutils"><string></tt>, line 15)</p>
Literal block expected; none found.</div>
<dl class="docutils">
<dt>Called and couldn't leave a message the message center was full.</dt>
<dd>I'll try again later</dd>
</dl>
<ul class="simple">
<li>This is an automated email, please do not reply - AiT - SERVICE</li>
</ul>
</div>

  </body>
</html>

--===============5139736139901058109==--

Added by Maurits van Rees on May 22, 2009 09:14 PM

Issue state: Unconfirmed → Resolved

Responsible manager: (UNASSIGNED) → maurits

Target release: None → 1.2

I cannot reproduce this. The code of htmlrender.py in the 1.2.3 version of Poi specifically fixes this by simply using pre tags in case of restructured text parsing problems.

But I do notice some errors that make parsing problems unavoidable. I fixed that on trunk in r86620. That should fix this for you as well. So if you could test this on trunk that would be nice. Otherwise wait for the next release.

Thanks,

Maurits

Added by (anonymous) on Jul 31, 2009 01:57 AM

No Response. End all messages now. No reply necessary

No responses can be added.