<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to bugs</title><link>https://sourceforge.net/p/rilkecms/bugs/</link><description>Recent changes to bugs</description><atom:link href="https://sourceforge.net/p/rilkecms/bugs/feed.rss" rel="self"/><language>en</language><lastBuildDate>Mon, 19 Apr 2004 14:48:58 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/rilkecms/bugs/feed.rss" rel="self" type="application/rss+xml"/><item><title>Add Preview Entry mode</title><link>https://sourceforge.net/p/rilkecms/bugs/131/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Rilke CMS needs to be able to provide the user with a&lt;br /&gt;
preview of how his/her listing will look before it is&lt;br /&gt;
posted.&lt;/p&gt;
&lt;p&gt;(By request).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jayesh Sheth</dc:creator><pubDate>Mon, 19 Apr 2004 14:48:58 -0000</pubDate><guid>https://sourceforge.neta158a0f00e6940ea72c7e5c10b1fb2214d3ab988</guid></item><item><title>Needs Unicode Support </title><link>https://sourceforge.net/p/rilkecms/bugs/130/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The following was posted by a visitor to the Rilke CMS&lt;br /&gt;
demo site:&lt;/p&gt;
&lt;p&gt;"&lt;br /&gt;
Lacking unicode support&lt;br /&gt;
THis test shows that Rilke CMS can't work with&lt;br /&gt;
multi-script texts. Here is a russian letter "&amp;amp;#1103;"&lt;br /&gt;
and here is a swedish "ה". The swedish is perhaps&lt;br /&gt;
readable while the russiand זרו&lt;br /&gt;
&amp;amp;#1072;&amp;amp;#1073;&amp;amp;#1074;&amp;amp;#1075; appears as a numerical&lt;br /&gt;
character reference. However, if you try to edit it,&lt;br /&gt;
inside HTMLarea again, the russian letter pops up&lt;br /&gt;
again, as it is supposed to do.&lt;/p&gt;
&lt;p&gt;It is problably something with the publishing process&lt;br /&gt;
... because I think HTMLarea are good enough?&lt;/p&gt;
&lt;p&gt;Btw, Rilke CMS lacks a preview of postings, doesn't it?&lt;br /&gt;
"&lt;/p&gt;
&lt;p&gt;We need to test Rilke CMS with non-English languages. I&lt;br /&gt;
think this is a server side processing issue. It&lt;br /&gt;
probably has something to do with the html tag&lt;br /&gt;
indicating the encoding, which in turn is interpreted&lt;br /&gt;
by the server.&lt;/p&gt;
&lt;p&gt;This issue needs more investigation ...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jayesh Sheth</dc:creator><pubDate>Mon, 19 Apr 2004 14:47:06 -0000</pubDate><guid>https://sourceforge.net45a99df07a7c4a1aa7abefdedd99bc33b4836e3c</guid></item><item><title>adminpear/lib/builduserlist.php - need mysql_num_rows </title><link>https://sourceforge.net/p/rilkecms/bugs/129/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;In adminpear/lib/builduserlist.php we need to&lt;br /&gt;
mysql_num_rows() and not mysql_affected_rows().&lt;/p&gt;
&lt;p&gt;mysql_num_rows is only for SELECT queries, which is&lt;br /&gt;
what has been used in this case.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Fri, 16 Apr 2004 16:15:11 -0000</pubDate><guid>https://sourceforge.net8dfc28e21738464efd8b433faee4ef012d5cc031</guid></item><item><title>labels in image manager needs to be clearly distinguishable</title><link>https://sourceforge.net/p/rilkecms/bugs/128/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;To some users, it is not immediately clear which images&lt;br /&gt;
belong to which labels in the image manager.&lt;/p&gt;
&lt;p&gt;We can use hrs or other visual differentiation to fix&lt;br /&gt;
this usability problem.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 28 Jan 2004 15:52:25 -0000</pubDate><guid>https://sourceforge.neteb4758e52f3b8f0223a03e568828c013f84fc2b4</guid></item><item><title>Create categories for Image Manager</title><link>https://sourceforge.net/p/rilkecms/bugs/127/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;It would be nice to have categories for the image&lt;br /&gt;
manager (used in conjunction with image attachments).&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 28 Jan 2004 15:50:32 -0000</pubDate><guid>https://sourceforge.netbbf79694552816d0e207fcecfb968a95f27478eb</guid></item><item><title>make image attachments more multi-user friendly</title><link>https://sourceforge.net/p/rilkecms/bugs/126/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The special security checks for uploaded files (and the&lt;br /&gt;
specialauth table) could cause problems when multiple&lt;br /&gt;
users are trying to attach images to different posts&lt;br /&gt;
simultaneously.&lt;/p&gt;
&lt;p&gt;This should be changed by adding another unique&lt;br /&gt;
(session) identifier to the specialauth table.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 28 Jan 2004 15:41:24 -0000</pubDate><guid>https://sourceforge.netb65486d99530d6b06de93a2996f77305e5b48ab9</guid></item><item><title>add ability to delete themes from admin screen</title><link>https://sourceforge.net/p/rilkecms/bugs/125/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;For 1.0:&lt;/p&gt;
&lt;p&gt;add ability to delete themes from admin screen. Actual&lt;br /&gt;
theme files will not be deleted (security / data loss&lt;br /&gt;
risk). Only the reference in the database will be deleted.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 28 Jan 2004 01:32:50 -0000</pubDate><guid>https://sourceforge.net7961c1a343d443d8c6b3560cb587752e82522826</guid></item><item><title>JavaScript should not warn about Moz 1.5 +</title><link>https://sourceforge.net/p/rilkecms/bugs/124/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Mozilla 1.5 and 1.6 have been released. The JavaScript&lt;br /&gt;
browser detection should be updated and not warn users&lt;br /&gt;
about using a "future browser".&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jayesh Sheth</dc:creator><pubDate>Mon, 26 Jan 2004 15:44:10 -0000</pubDate><guid>https://sourceforge.netfe546dd342ecd45c54056b6d50a805cd22a59d5d</guid></item><item><title>prevent comment flooding and spamming</title><link>https://sourceforge.net/p/rilkecms/bugs/123/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Prevent comment flooding and spamming&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jayesh Sheth</dc:creator><pubDate>Wed, 21 Jan 2004 14:54:24 -0000</pubDate><guid>https://sourceforge.net30c0b17a8621ce1155d9f79902ec36ac61271b22</guid></item><item><title>JavaScript entered into post is mangled</title><link>https://sourceforge.net/p/rilkecms/bugs/122/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;JavaScript embedded in HTML in a post is mangled (due&lt;br /&gt;
to the  bad sanitization functions.)&lt;/p&gt;
&lt;p&gt;Sanitization has been redone in the grand rewrite of&lt;br /&gt;
2004 - so hopefully this should be fixed in the next&lt;br /&gt;
release.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jayesh Sheth</dc:creator><pubDate>Wed, 21 Jan 2004 14:47:43 -0000</pubDate><guid>https://sourceforge.net8462a737a1f22f22c5430889876c46c3d87b9567</guid></item></channel></rss>