You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@roller.apache.org by "Kohei Nozaki (JIRA)" <ji...@apache.org> on 2015/02/28 03:40:06 UTC
[jira] [Updated] (ROL-2065) Gaurav renders the summary of an entry
as unresolved "$entry.summary" while no summary in the entry
[ https://issues.apache.org/jira/browse/ROL-2065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kohei Nozaki updated ROL-2065:
------------------------------
Attachment: ROL-2065.patch
> Gaurav renders the summary of an entry as unresolved "$entry.summary" while no summary in the entry
> ---------------------------------------------------------------------------------------------------
>
> Key: ROL-2065
> URL: https://issues.apache.org/jira/browse/ROL-2065
> Project: Apache Roller
> Issue Type: Bug
> Components: Themes and Macros
> Affects Versions: 5.1.1
> Reporter: Kohei Nozaki
> Assignee: Roller Unassigned
> Priority: Minor
> Attachments: ROL-2065.patch
>
>
> day.vm in Gaurav checks existence of summary in following code:
> {code:html}
> #if($entry.summary != "")
> <p>$entry.summary</p>
> <a class="btn btn-primary" href="$url.entry($entry.anchor)">Read More <i class="icon-angle-right"></i></a>
> #else
> <p>$entry.displayContent</p>
> #end
> {code}
> I experienced WEBLOGENTRY.SUMMARY went null accidentally (https://twitter.com/lbtc_xxx/status/549181370908430338). in such case, Gaurav thinks the summary is exist and render it as "$entry.summary". I don't know how summary went null, but the db schema allows null so I guess changing comparison logic to more safer one (use $utils.isNotEmpty() instead) is reasonable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)