<?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 assigned_to:"spiffk"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:57 -0000</lastBuildDate><item><title>Upgrade allura to jquery 1.8</title><link>https://forge-allura.apache.org/p/allura/tickets/4698/</link><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/4698/</guid></item><item><title>Tweaks to scm getting started text</title><link>https://forge-allura.apache.org/p/allura/tickets/4545/</link><description>* SVN needs a new section: importing an existing SVN repo.  Have a link to /p/PROJECT/admin/TOOL/importer/
* The message boxes have cursor:pointer.  Perhaps we need to change/refactor that SCSS class a bit.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4545/</guid></item><item><title>ticket subscriptions not working for migrated projects</title><link>https://forge-allura.apache.org/p/allura/tickets/4532/</link><description>https://sourceforge.net/p/forge/site-support/10/
https://sourceforge.net/apps/trac/sourceforge/ticket/26577
https://sourceforge.net/apps/trac/sourceforge/ticket/26540

I have reports from three different projects that subscription emails aren't working after upgrade.

I've had one check his [subscription preferences](https://sourceforge.net/auth/prefs/) and everything seems fine there.

Another has mentioned that the subscription emails work fine for the tickets he logged in the [new support tickets instance](/p/forge/site-support).

So, seems to be something affecting just migrated projects.</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/4532/</guid></item><item><title>Tracker - strange behaviour after project upgrade [26540]</title><link>https://forge-allura.apache.org/p/allura/tickets/4515/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/26540

&gt;I upgraded my project HoDoKu and had strange behaviour in "Bugs and feature Requests". For item 219 (https://sourceforge.net/p/hodoku/bugs-and-feature-requests/219/) the discussion was missing, although I had already posted a reply (reply1) and gotten an answer (answer1).

&gt;I assumed that those posts were lost, so I posted a new reply (reply2). After clicking on "Post" the new reply2 disappeared and the old posts (reply1 and answer1) were shown.

&gt;Now I wrote a reply (reply3) to the old posts. After pressing "Post" the old posts disappeared again and reply2 was shown. The new post (reply3) was absent again.

----

&gt;Just posted a reply to another topic and now 5 pages of comments are gone!

----

&gt;Further testing: I added another post to the second thread and now all the old posts have reappeared (but the latest is missing).</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/4515/</guid></item><item><title>NEEDS MONGO QUERY Migrated forum bugs</title><link>https://forge-allura.apache.org/p/allura/tickets/4502/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/26504  
https://sourceforge.net/apps/trac/sourceforge/ticket/26505  
https://sourceforge.net/apps/trac/sourceforge/ticket/26506

&gt; I upgraded my project vllasku to SourceForge 2.0 beta, and now the forum posts have lost all empty lines. It seems that multiple consequent line feeds are always converted to a single one. This also affects new messages created within 2.0 and makes quite a few of the messages look messy.

----

&gt; I upgraded my project vllasku to 2.0 beta, and now I'm unable to add new topics to the discussion forum. The url https://sourceforge.net/p/vllasku/discussion/save_new_topic throws error 500 "We're sorry but we weren't able to process this request."

----

&gt;I upgraded my project vllasku to 2.0 beta, and now the discussion forum displays all topics in ascending date order instead of descending order, and I couldn't find a place where this could be controlled. How can I change the order to descending?</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/4502/</guid></item><item><title>Nbhd controller bindings are cached too heavily</title><link>https://forge-allura.apache.org/p/allura/tickets/4448/</link><description>Revert the caching part of d305c88 (keep the nbhd model passing improvement).  We have to load then nbhd model for each request, but we should make it only load the relevant neighborhood.  (Perhaps add a unique index on url_prefix if that is what we use to query it)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4448/</guid></item><item><title>Paragraph spacing in markdown rendering</title><link>https://forge-allura.apache.org/p/allura/tickets/4442/</link><description>Markdown content should have spacing between paragraphs.

Make sure it matches spacing used on code blocks and lists, so that it all looks good when they are interspersed.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4442/</guid></item><item><title>fceultra : new services bug comments just disappeared [26299]</title><link>https://forge-allura.apache.org/p/allura/tickets/4428/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/26299

&gt;we're missing bug comments again in project fceultra on the new services. while adding a comment to this thread, all the comments vanished:

&gt;https://sourceforge.net/p/fceultra/bugs/480/

&gt;you can see the old thread here:

&gt;http://webcache.googleusercontent.com/search?q=cache:KvcSuZiVKd0J:sourceforge.net/support/tracker.php%3Faid%3D3500911+&amp;cd=1&amp;hl=en&amp;ct=clnk&amp;gl=us

&gt;we're also missing comments from this

&gt;https://sourceforge.net/p/fceultra/bugs/516/

&gt;maybe we're missing 98% of comments and attachments

</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/4428/</guid></item><item><title>Wiki translates carriage-returns in markdown to breaks in html [26285]</title><link>https://forge-allura.apache.org/p/allura/tickets/4423/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/26285

&gt;e.g., the markdown:

~~~~
One
Two
Three
~~~~

&gt;Output the html:

~~~~
&lt;p&gt;One&lt;br /&gt;Two&lt;br /&gt;Three&lt;/p&gt;
~~~~

&gt;Instead of the expected:

~~~~
&lt;p&gt;One Two Three&lt;/p&gt;
~~~~

&gt;According to the wiki documentation at https://sourceforge.net/p/forge/documentation/Wiki/, the wiki markdown is as specified at http://daringfireball.net/projects/markdown/syntax, except for the noted exceptions.

&gt;One of the features of markdown is that it supports 'hard-wrapped' text paragraphs. (See "PARAGRAPHS AND LINE BREAKS" at http://daringfireball.net/projects/markdown/syntax ). I.e., the plain-text paragraphs may have hard carriage returns to keep each line under 80 characters, but the output html does not insert breaks.

&gt;This does not seem to be the behavior of (Beta-style) wiki.

&gt;This is particularly a problem for using an external editor (emacs), and when copying and pasting back and forth between plaintext documentation and wiki pages.</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/4423/</guid></item><item><title>Getting started text for scms</title><link>https://forge-allura.apache.org/p/allura/tickets/4382/</link><description>For each of Git, SVN, and Hg we should have instructions for how to get started with a brand new (empty) repo, and for pushing existing code to the new repo.  Provide specific commands.  Show the text/commands on the repo page to developers/admins if the repo is empty (or r1 for SVN)</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/4382/</guid></item><item><title>Root controllers shouldn't query each neighborhood for every request</title><link>https://forge-allura.apache.org/p/allura/tickets/4353/</link><description>In root.py, RootController `__init__` loops through each neighborhood and binds it.  And the bind creates a NeighborhoodController which does a query for the neighborhood.  As far as I can tell, it does this for every request.  I see two opportunities for improvement:

* pass the Neighborhood object through the binding calls, so it doesn't have to be queried again in the nbhd `__init__` method
* change the root controller's bind loop to only happen once (at the class level, or as a lazy/cached property, rather than every time in the `__init__`)

The paster command to create new neighborhoods should print out a message explaining that the webserver needs to be restarted for the new neighborhood urls to work.</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/4353/</guid></item><item><title>Autofill ticket fields by url param</title><link>https://forge-allura.apache.org/p/allura/tickets/4333/</link><description>There should be a way to pre-fill ticket fields, possibly using arguments in the URL like Trac does. We currently do this for reporting 404 and 500 errors to support Trac.

Eg. &lt;https://sourceforge.net/apps/trac/sourceforge/newticket?summary=Page+Missing+%28404%29%3A+https%3A//sourceforge.net/projects/not-a-project/&amp;description=I+found+this+link+here...&gt;

</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/4333/</guid></item><item><title>TypeError on _discuss url with pagination param</title><link>https://forge-allura.apache.org/p/allura/tickets/4310/</link><description>Example URL http://sourceforge.net/p/forge/comm-docs-tickets/_discuss/thread/fc476f50/?limit=50&amp;page=0

~~~~
Module /var/local/allura/Allura/allura/templates/widgets/thread_header.html:4 in top-level template code
&lt;&lt;    {% if limit %}
         &lt;div&gt;
           {% set cur_page = page / limit %}
           {% set num_pages = count / limit %}
           &lt;div class="span-3"&gt;Page {{1 + cur_page}} of {{1 + num_pages}}&lt;/div&gt;
&gt;&gt;  {% set cur_page = page / limit %}
TypeError: unsupported operand type(s) for /: 'int' and 'unicode'
~~~~</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/4310/</guid></item><item><title>TypeError in sitemap() for some projects</title><link>https://forge-allura.apache.org/p/allura/tickets/4309/</link><description>This occurs on many projects, including https://sourceforge.net/p/waznexserver/admin/ and pformat and bikesimulator for example.

Seems like it is a data issue?

~~~~
Module allura.model.project:418 in sitemap
&lt;&lt;                      entry = sm.bind_app(app)
                           entry.ui_icon='tool-%s' % ac.tool_name.lower()
                           ordinal = ac.options.get('or    dinal', 0) + delta_ordinal
                           if ordinal &gt; max_ordinal:
                               max_ordinal = ordinal
&gt;&gt;  ordinal = ac.options.get('ordinal', 0) + delta_ordinal
TypeError: coercing to Unicode: need string or buffer, int found
~~~~</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/4309/</guid></item><item><title>markdown preview not aligned correctly</title><link>https://forge-allura.apache.org/p/allura/tickets/4295/</link><description>The second "edit" button on markdown previews floats up, and pushes the content to the right:

http://screencast.com/t/nj52gnpAuZ

And comment preview is worse, due to the user icon &amp; name.  Content is hidden on the left sometimes:

http://screencast.com/t/Adfc4sM3

http://screencast.com/t/QgK1kl6dX

</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/4295/</guid></item><item><title>Attachments of content-type image/* should be displayed inline</title><link>https://forge-allura.apache.org/p/allura/tickets/4277/</link><description>It is safe to show image attachments directly, rather than serving them as downloads (like we must do for everything else, for security)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4277/</guid></item><item><title>Validate SVN import url</title><link>https://forge-allura.apache.org/p/allura/tickets/4259/</link><description>When import svn repos (using the tool's admin menu), we should validate the input.  This error can happen if it is blank.  We should also validate that it's a real url.  Limit to http(s) and svn (if that works).

~~~~
Traceback (most recent call last):
 File "/var/local/allura/Allura/allura/tasks/repo_tasks.py", line 31, in clone
   cloned_from_url)
 File "/var/local/allura/Allura/allura/model/repository.py", line 227, in init_as_clone
   self._impl.clone_from(source_url)
 File "/var/local/allura/ForgeSVN/forgesvn/model/svn.py", line 176, in clone_from
   subprocess.check_call(['svnsync', 'init', self._url, source_url])
 File "/usr/lib64/python2.7/subprocess.py", line 506, in check_call
   retcode = call(*popenargs, **kwargs)
 File "/usr/lib64/python2.7/subprocess.py", line 493, in call
   return Popen(*popenargs, **kwargs).wait()
 File "/usr/lib64/python2.7/subprocess.py", line 679, in __init__
   errread, errwrite)
 File "/usr/lib64/python2.7/subprocess.py", line 1228, in _execute_child
   raise child_exception
TypeError: execv() arg 2 must contain only strings
~~~~</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/4259/</guid></item><item><title>Nav arrow looks bad in ie9</title><link>https://forge-allura.apache.org/p/allura/tickets/4249/</link><description>See screenshots.  This needs to fixed in sfpy also.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jenny Steele</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4249/</guid></item><item><title>500 error on 'df-win-dos' discussion thread [25603]</title><link>https://forge-allura.apache.org/p/allura/tickets/4194/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/25603

&gt;https://sourceforge.net/p/df-win-dos/discussion/general/thread/2e7c8258/

&gt;500 error

&gt;https://sourceforge.net/p/df-win-dos/discussion/general

Don't know if it's related to [#4166] or not...</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/4194/</guid></item><item><title>500 Error On Discussion Board [25540]</title><link>https://forge-allura.apache.org/p/allura/tickets/4166/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/25540

&gt; I was replied to on this board
https://sourceforge.net/p/openrokn/discussion/general/thread/9dd0371c/
and its very important but its giving me a 500 error

Also: perhaps we should consider ways for this to fail more gracefully? Like just showing the raw text for this if it errors in processing? So that folks can still get at the content instead of just being locked out?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4166/</guid></item><item><title>Upgrade jquery to latest</title><link>https://forge-allura.apache.org/p/allura/tickets/4114/</link><description>There are some fixes that would be good to get.</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/4114/</guid></item><item><title>Refactor neighborhood levels as feature flags NEEDS CMDS RUN: set-neighborhood-features</title><link>https://forge-allura.apache.org/p/allura/tickets/4056/</link><description>We recently added support for neighborhood levels: 'silver', 'gold', 'platinum', None.  Features are enabled based on those settings.  We should still store the neighborhood level as a name (could be useful for reporting), but refactor the level checks to be feature checks so we can control them with more granularity.  There is also an 'allow_private' flag that we should move into the features.  Here's what I think a new field could look like:

~~~~
:::js
features: {
    private_projects: true;
    max_projects: 500;
    css: 'custom'; // options: 'none', 'picker', 'custom'
    google_analytics: true;
}
~~~~

Paster commands are used to change settings and need to be updated too:

~~~~
    set-neighborhood-level = allura.command:SetNeighborhoodLevelCommand
    set-neighborhood-private = allura.command:SetNeighborhoodPrivateCommand
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4056/</guid></item><item><title>Unable to import svn repo on beta project [25103]</title><link>https://forge-allura.apache.org/p/allura/tickets/4015/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/25103

Importing SVN repos doesn't seem to be working, I tried importing a repo via the [svn import tool](https://sourceforge.net/p/fancypants/admin/svn-new/importer/), it displayed a notice saying it was importing, but the import didn't happen (code browser doesn't show "importing" like it used to).</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/4015/</guid></item><item><title>Add documentation for ticket sorting</title><link>https://forge-allura.apache.org/p/allura/tickets/4006/</link><description>There's no way to sort tickets based on date created or date updated.  Date created can be fudged by sorting on ticket number, but it would be useful to sort on when tickets were last updated, e.g., to see which ticket was most recently closed.

Apparently, manually adding "&amp;sort=mod_date_dt+desc" to the URL does allow sorting by last-modified, so we really just need some documentation and/or UI for it.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cory Johns</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4006/</guid></item><item><title>SVN repo didn't migrate correctly</title><link>https://forge-allura.apache.org/p/allura/tickets/3983/</link><description>This issue turned up in [#3657]. During migration, the svnsync failed and left the repo in a bad state. Here's a traceback:

~~~~
Module /var/local/allura/Allura/allura/templates/widgets/repo/tree_widget.html:3 in top-level template code
&lt;&lt;  {% import 'allura:templates/jinja_master/lib.html' as lib with context %}
       &lt;table&gt;
       {% set ls = list(tree.ls()) %}
         &lt;thead&gt;
           &lt;tr&gt;
&gt;&gt;  {% set ls = list(tree.ls()) %}
UndefinedError: 'None' has no attribute 'ls'
~~~~

This is the repo that failed: https://easyitsp.svn.sourceforge.net/svnroot/easyitsp/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jenny Steele</dc:creator><pubDate>Sat, 07 Feb 2015 11:01:27 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3983/</guid></item></channel></rss>