33829Fix Atom feed for issues to correctly use the updated time for "updated" element instead of the created timeThere are **updated** tags in the Atom of issues list.
However, the **created on** is exported.
I have attached a patch to fix this.0falseFixed1602020-08-08T07:38:16Z2024-03-06T14:10:16Z2024-03-04T14:26:39Z14038Ordered/unordered lists inside table cell are mangledHere is an example:
|test name|test|
|test formatting|*bold* +underlined+ -striked out- _italic_ @code@ www.redmine.org !coffee.jpg! [[Wiki page link]]|
|test multiline|*bold*
+underlined+
-striked out-
_italic_
@code@
[[Wiki page link]]
www.redmine.org
!coffee.jpg!
<pre>
preformatted test
with indents
</pre>|
|test numbered list|numbered list:
# item 1
# item 2|
|test bulleted list|bulleted list:
* item 1
* item 2|
|record after bad rows|some data|
Look at the rows with "test numbered list" and "test bulleted list" in the first column.
As I understood I can't use quotations inside of table cell as well, but it's not critical.0falseFixed2013-05-13T10:32:07Z2022-06-27T09:34:35Z2013-05-14T16:34:06Z10535Atom feeds for the Project Activity contain incorrect hostnameThe link in the Atom feed (at least for Project Activity) contains a hostname detected by Rails, but not the one specified in settings.
This makes link unusable if the requests to Rails are proxified.
Versions:
Redmine:
<pre>
SVN: http://redmine.rubyforge.org/svn/branches/1.3-stable revision 9240
</pre>
Env:
<pre>
Ruby version 1.8.7 (x86_64-linux)
RubyGems version 1.3.7
Rack version 1.1.2
Rails version 2.3.14
Active Record version 2.3.14
Active Resource version 2.3.14
Action Mailer version 2.3.14
Active Support version 2.3.14
Application root /opt/redmine
Environment production
Database adapter mysql
Database schema version 20110902000000
</pre>0falseFixed362012-03-23T23:14:34Z2020-12-22T11:52:50Z2020-06-04T14:23:51Z6969Less-than sign in issue description and comments are not escapedWhen an issue description or comment contains a less-than sign (@<@), this sign is output verbatim in the issue page, instead of being escaped with ampersand-"lt"-semicolon. This causes the issue details page to be invalid XHTML, which is contrary to the page's doctype, and makes it impossible to read the page with an XML parser. I created "an issue on the demo site":http://demo.redmine.org/issues/38181 to demonstrate the problem.
To reproduce, run @xmllint URL-OF-ISSUE-PAGE@, like this:
<pre>$ xmllint http://demo.redmine.org/issues/38181
http://demo.redmine.org/issues/38181:166: parser error : StartTag: invalid element name
<p>Hm: <</p>
^
http://demo.redmine.org/issues/38181:241: parser error : StartTag: invalid element name
mg alt="Comment" src="/images/comment.png?1286930539" /></a></div><p>And this? <
^
http://demo.redmine.org/issues/38181:330: parser error : Entity 'copy' not defined
Powered by <a href="http://www.redmine.org/">Redmine</a> © 2006-2010 Je
^
</pre>
The third error is a false positive (xmllint doesn't know XHTML entities), but the first two errors are symptoms of this problem.
2010-11-240falseFixed252010-11-24T17:51:00Z2020-10-28T01:21:47Z2015-11-08T08:51:37Z5114New issue statuses not showing up in old workflowsIn trunk (r3596) if I add a new issue status it does not appear in the Administrator -> Workflow work flow check-box forest for each trunk. If I create a new tracker then the new issue status is present but old tracker do not get the new status.2010-03-180falseFixed2010-03-18T04:56:43Z2013-06-17T16:39:16Z2010-03-18T22:09:37Z1759Migration from trac/postgresql fails with SQL error (probably important - postgres 8.3)Migration from trac (with data in postgres database) ends with:
<pre>
Migrating components...
Migrating milestones...
Migrating custom fields
Migrating tickets.rake aborted!
PGError: ERROR: operator does not exist: text = integer
LINE 1: ...CT * FROM "attachment" WHERE ("attachment".id = 1 AND (a...
^
HINT: No operator matches the given name and argument type(s). You might need to add explicit type casts.
: SELECT * FROM "attachment" WHERE ("attachment".id = 1 AND (attachment.type = 'ticket'))
</pre>
The same SQL fails when issued from psql, to have it working one must *quote* this identifier - WHERE ("attachment".id = "1" ....)
PS Postgres 8.3 is restrictive on datatypes....2008-08-080falseFixed52008-08-08T20:38:42Z2013-02-06T10:07:41Z