<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for labels:"sf-0"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:56 -0000</lastBuildDate><item><title>Better handling of inability to configure logging</title><link>https://forge-allura.apache.org/p/allura/tickets/4894/</link><description>This silently hides major issues:

~~~~
            except Exception: # pragma no cover
                print &gt;&gt; sys.stderr, (
                    'Could not configure logging with config file %s' % self.args[0])
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4894/</guid></item><item><title>Solr syntax is case sensitive: Help syntax uses "and" but it is "AND"</title><link>https://forge-allura.apache.org/p/allura/tickets/4846/</link><description>If you try to search Tracker with this queries:

    status:open and status:closed -&gt; 4384 tickets WRONG
    status:open AND status:closed -&gt; 0            OK

Help for solr syntax uses as an example:

    !status:closed and summary:foo* and _milestone:1.0

but it should be:

    !status:closed AND summary:foo* AND _milestone:1.0</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alvaro del Castillo</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4846/</guid></item><item><title>Add index on audit_log NEEDS ENSURE_INDEX</title><link>https://forge-allura.apache.org/p/allura/tickets/4837/</link><description>audit_log doesn't have any indexes.  I'm sure there are some natural ones that could be used.  project_id comes to mind, and that would be useful for our purge script too.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4837/</guid></item><item><title>Error 500 in Git code browser [ss352]</title><link>https://forge-allura.apache.org/p/allura/tickets/4796/</link><description>[forge:site-support:#352]

&gt;The Git web view for project Open Orienteering returns Error 500, "We're sorry but we weren't able to process this request.":

&gt;https://sourceforge.net/p/oorienteering/code/

&gt;I did a "Refresh Repository" from the admin page, but without success.

&gt;However, the error only occurs for the latest commits in the master branch, such as:

&gt;https://sourceforge.net/p/oorienteering/code/ci/982513985e2902a62f9382a0088fcf2f5e154737/tree/

&gt;Other branches and even earlier commits on master work as they should:

&gt;https://sourceforge.net/p/oorienteering/code/ci/v0.3.1/tree/

&gt;https://sourceforge.net/p/oorienteering/code/ci/8123f5fc89ca6f203c360de38c004cbbabefae5c/log/
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4796/</guid></item><item><title>Fix has_home_tool() implementation</title><link>https://forge-allura.apache.org/p/allura/tickets/4457/</link><description>`Neighborhood.has_home_tool()` checks by mount point.  We need to check tool **type**, not mount point.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4457/</guid></item><item><title>SF2.0: Clicking 'Search' button on tickets/search page does nothing [26301]</title><link>https://forge-allura.apache.org/p/allura/tickets/4430/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/26301

&gt;Pressing 'enter' on my keyboard with focus on the text field works, but clicking on the 'Search' button does nothing. I've tried it in Chrome and on Firefox.

Confirmed. To be clear, he's referring to the search button on the [search page](https://sourceforge.net/p/allura/tickets/search/), not the search form on the left sidebar.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4430/</guid></item><item><title>Option to limit the tools shown in project list</title><link>https://forge-allura.apache.org/p/allura/tickets/4190/</link><description>The `[[projects]]` macro should support an option like ``grid_view_tools=git,wiki,tickets``  When in grid mode then only show the icons for those tool types.  Do a case-insensitive match against the tool types (not the mount point or label).


Update the help documentation also. Allura/allura/templates/neighborhood_help.html</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4190/</guid></item><item><title>Blog tool should be able to pull in rss feeds NEEDS CRON</title><link>https://forge-allura.apache.org/p/allura/tickets/4181/</link><description>The Blog/News tool should be able to pull in one or several external rss/atom feeds on a regular basis, convert new items' text or html to markdown, and create a regular entry in the tool.  The 'feedparser' package should be used for parsing feeds.  I don't know offhand what package can be used to convert html to markdown.

For the periodic fetching of rss feeds, the tool should expose a paster command via setup.py.  Then we can set up a cron job to run it.

Test with both a twitter rss feed, and a wordpress blog feed.  Make sure those work well.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4181/</guid></item><item><title>Reprocess SVN history page? [25367]</title><link>https://forge-allura.apache.org/p/allura/tickets/4143/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/25367

So, apparently, they had to fix some corruption and re-import for some reason, and since then a significant portion of their svn history page is incorrect. Anyway to get this fixed?

According to the user, "everything from commit 886 to commit 952 is wrong".

https://sourceforge.net/p/quazaa/code/961/log/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4143/</guid></item><item><title>Easy copy&amp;paste from the code browser</title><link>https://forge-allura.apache.org/p/allura/tickets/4116/</link><description>Line numbers should not be selected when you try to copy &amp; paste.

We've been working on a small pastebin tool at https://sourceforge.net/p/forgepastebin/code/  That separates the line numbers from the code, quite well.  So that is an excellent example to work from.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4116/</guid></item><item><title>Discussion Forum description displays link as html code [24936]</title><link>https://forge-allura.apache.org/p/allura/tickets/3940/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/24936

&gt;goto this link

&gt;https://sourceforge.net/p/openantz/discussion/

&gt;notice that the link in the 'Description' field for General Discussions displays as html code rather then a proper 'blue' link...
if you click on 'General...' then the topic page displays properly (blue link, no html code.)

&gt;cheers, Shane

Not sure if we want to allow, or disallow html/markup in forum descriptions, but either way, we should be consistent.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3940/</guid></item><item><title>Add Preview button to comment box when editing a ticket</title><link>https://forge-allura.apache.org/p/allura/tickets/3833/</link><description>When editing an existing ticket, a comment box is provided in addition to the ticket description box.  However, only the ticket description box has a Preview button.

Add a Preview button to the comment box as well.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cory Johns</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3833/</guid></item><item><title>Typo in Ming docs</title><link>https://forge-allura.apache.org/p/allura/tickets/3689/</link><description>*Originally created by:* msmeeks

http://merciless.sourceforge.net/tour.html#collection-objects
In the "Declarative versus Imperative" section there is a typo "...the main author or Ming...". Should be "of" not "or."

http://merciless.sourceforge.net/orm.html#mapping-classes
"You might alwo notice..."
Should be "also".</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Mon, 12 Mar 2012 21:40:51 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3689/</guid></item><item><title>Common file types we can display are hidden in scm browse</title><link>https://forge-allura.apache.org/p/allura/tickets/3608/</link><description>In our git file browse, some common file types (php, markdown) that our system can display fine were hidden behind the "cannot be displayed in the browser" message in a newly created project. This shouldn't happen and was a source of frustration for new project admins. We should make these display, but even the ones that don't show up automatically need an easier way to add them to the "Viewable Files". What about a link called "Always display this filetype" (maybe only visible to those with admin permission) that adds the extension to the Viewable Files? Perhaps after that feature has been there a while we can do a report in mongo and see what common extensions people are adding here that should just automatically display.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jenny Steele</dc:creator><pubDate>Sun, 05 Apr 2015 12:08:37 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3608/</guid></item><item><title>Commit browser doesn't work in Opera</title><link>https://forge-allura.apache.org/p/allura/tickets/3020/</link><description>*Originally created by:* driedfruit

On every 'commit browser' page, for example https://sourceforge.net/p/mavscript/code/commit_browser , I get the following error:

&gt; Uncaught exception: TypeError: Cannot convert 'tree[parent]' to object
&gt; Error thrown at line 1311, column 6 in https://a.fsdn.com/allura/nf/1318531438/_ew_/  _slim/js?href=allura%2Fjs%2Fjquery-base.js%3Ballura%2Fjs%2Fjquery.notify.js%3Ballura %2Fjs%2Fsylvester.js%3Ballura%2Fjs%2Fpb.transformie.min.js%3Ballura%2Fjs%2Fallura- base.js%3Bjs%2Fcommit_browser.js:
     var parent_x = x_space+tree[parent].column*x_space;

Unfortunately, there is no stack trace. I'm using Opera 11.56 if that is of any consequence.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 01 Apr 2015 08:48:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3020/</guid></item><item><title>Forking should have a useful label.</title><link>https://forge-allura.apache.org/p/allura/tickets/2886/</link><description>Right now the new fork tool always has the label "Code".  Preserving the original label might help, but in a lot of cases it'll be "Code" anyway and that won't make sense if forking into a user project.  We probably should put a text box for the label on the fork form, and default to including to "$Project - Code" or something like that</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2886/</guid></item><item><title>Forum/Discussion moderated messages do not generate notification emails when approved</title><link>https://forge-allura.apache.org/p/allura/tickets/2670/</link><description>When a post is made on a forum and held in moderation status, a notification email should be generated when the post is approved by a moderator.

Replaced by: [#2653]</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Hoffman</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2670/</guid></item><item><title>Ticket incorrectly in moderation queue</title><link>https://forge-allura.apache.org/p/allura/tickets/2271/</link><description>I just closed a ticket ([#2234]) and then added a comment. The closing went fine, but the comment ended up in the moderation queue as being from "Anonymous Coward". That's despite the fact that I'm clearly still logged in in the upper right and my ticket status change was from a logged in account.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kyle Adams</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2271/</guid></item><item><title>SF2.0: display notice that commit browser doesn't work in IE8 [19266]</title><link>https://forge-allura.apache.org/p/allura/tickets/2098/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/19266

&gt;From this page:

&gt;https://sourceforge.net/p/scipad/svn

&gt;there is a "Browse commit" button in the left margin, which is driving to:

&gt;https://sourceforge.net/p/scipad/svn/commit_browser

&gt;but this page is empty whereas there are currently 231 commits in my project.

That page is working for me in FF4, but in IE8 I don't see the actual commits.

If this isn't going to be fixed for IE, I feel that the page should at least inform the users that it doesn't work for IE instead of just appearing broken.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2098/</guid></item><item><title>improve the interface for picking an initial SCM at project creation time</title><link>https://forge-allura.apache.org/p/allura/tickets/1567/</link><description>John's suggestion: a single checkbox under the icon like all the other tools, but when it is checked three radio buttons appear; when unchecked, they disappear.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wolf</dc:creator><pubDate>Sat, 21 Mar 2015 19:15:04 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1567/</guid></item><item><title>user subscriptions UI cleanup</title><link>https://forge-allura.apache.org/p/allura/tickets/1514/</link><description>Not sure exactly what this will look like yet, but we should define it. </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Wed, 18 Mar 2015 20:43:44 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1514/</guid></item><item><title>Fix feed.rss NoneType is not iterable</title><link>https://forge-allura.apache.org/p/allura/tickets/1467/</link><description>E.g. https://sourceforge.net/p/archtrack/feed.rss

~~~~
Module allura.controllers.project:280 in feed
&lt;&lt;              c.project.url(),
                   title,
                   since, until, page, limit)
               response.headers['Content-Type'] = ''
               response.content_type = 'application/xml'
&gt;&gt;  since, until, page, limit)
Module allura.model.artifact:273 in feed
&lt;&lt;                            unique_id=r.unique_id,
                                 author_name=r.author_name,
                                 author_link=h.absurl(r.author_link))
               return feed
&gt;&gt;  author_link=h.absurl(r.author_link))
Module allura.lib.helpers:285 in absurl
&lt;&lt;  def absurl(url):
           from tg import request
           if '://' in url: return url
           return request.scheme + '://' + request.host + url
&gt;&gt;  if '://' in url: return url
TypeError: argument of type 'NoneType' is not iterable
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1467/</guid></item><item><title>Discussion in my project that belong to another project. [17100]</title><link>https://forge-allura.apache.org/p/allura/tickets/1439/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/17100

&gt;I am also having the same problem. I see "Announcements" from the following project and have no idea how to remove/hide them from my project discussion.

&gt;Is there a way to switch from your 2.0 version back to the other. I like it much better. I am missing things such as screen shots, etc... What happened to basic functionality one would want?

&gt;Can we clear out those discussions from my project? (Displex is mine). The offending posts to my project belong to: http://sourceforge.net/p/lanex/

&gt;This is urgent as it really prohibits effective use of the discussion feature and actually prevents my content from being visible.

----

Confirmed, in https://sourceforge.net/p/displex/discussion/ I see posts for http://sourceforge.net/p/lanex/

Currently the posts I see are:
https://sourceforge.net/p/lanex/discussion/general/thread/fef9bc2d/
https://sourceforge.net/p/lanex/discussion/Storyline/thread/a0f0bcb9/
https://sourceforge.net/p/lanex/discussion/general/thread/1ca2b8c7/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1439/</guid></item><item><title>Add scss renderer to EasyWidgets</title><link>https://forge-allura.apache.org/p/allura/tickets/1131/</link><description>Since we are going to be using sass/scss for the new design, we should extend EasyWidgets to serve up css files from sass/scss sources.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Thu, 18 Aug 2011 14:32:16 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1131/</guid></item><item><title>editing a ticket now clears the 'assigned_to' field</title><link>https://forge-allura.apache.org/p/allura/tickets/686/</link><description>*Originally created by:* sf-overlords

Created by: wolf
Created date: 2010-07-02 20:31:17.643000
Assigned to:nobody
...so if you click to edit, change the status to in-progress, boom: assigned to nobody</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/686/</guid></item></channel></rss>