The last table on the CF page is not being closed with the </tbody></table>
pair, most likely since p is undefined to break out of the forloop in the first
place (disclaimer: I don’t know Python or Django so that guesswork might be
bananapants). The attached (untested since I don’t have a local running CF
app) instead closes on the final iteration in an attempt to fix it.
Does that make sense?
cheers ./daniel
--
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www
On Sun, Sep 3, 2017 at 11:48 PM, Daniel Gustafsson <daniel@yesql.se> wrote:
The last table on the CF page is not being closed with the </tbody></table> pair, most likely since p is undefined to break out of the forloop in the first place (disclaimer: I don’t know Python or Django so that guesswork might be bananapants). The attached (untested since I don’t have a local running CF app) instead closes on the final iteration in an attempt to fix it.