<?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:"mramm"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:57 -0000</lastBuildDate><item><title>Theme allura for sugarcrm demo</title><link>https://forge-allura.apache.org/p/allura/tickets/3202/</link><description>Put a logo on the default allura theme</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/3202/</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>GIT history revisited</title><link>https://forge-allura.apache.org/p/allura/tickets/1513/</link><description>We need a link in the left nav that shows some kind of representation of the DAG. </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1513/</guid></item><item><title>Add hover text to explain functionality of moderate button [14824]</title><link>https://forge-allura.apache.org/p/allura/tickets/1103/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/14824

&gt;A "Moderate" button shows up in the following page:
https://sourceforge.net/p/scipad/discussion/general/

&gt;whereas it does not show up for the two other forums of the same project, for instance:
https://sourceforge.net/p/scipad/discussion/Future%20of%20Scipad/

&gt;At the same time, no forum is set to be moderated in this project, as the Admin Options page shows:
https://sourceforge.net/p/scipad/admin/discussion/options

&gt;BUGS:

&gt;    * The moderate button shall not be visible for unmoderated forums
&gt;    * The moderation state of a forum should be selectable for a specific forum whatever this status is for other forums </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 23 Jun 2011 18:48:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1103/</guid></item><item><title>Extra data in the milestone view. </title><link>https://forge-allura.apache.org/p/allura/tickets/1007/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1007/</guid></item><item><title>adding a specific developer to my project ends with a 500 error (unicode issue?) [14360]</title><link>https://forge-allura.apache.org/p/allura/tickets/999/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/14360

&gt;project name: tagaprice
&gt;User to add: brandiatmuhkuh

&gt;I've tried to add that user several times always ending in the same result.
When I told the User about the problem, he told me he's getting the same error if he tries to visit the project page (just if he's logged in)

&gt;I've also tried adding another user which worked just fine.

I tried adding one of my test accounts (sillygoose) to a test project (fancypants), and I also got a 500 error. sillygoose has unicode in the public name (Chris "goose" Tsai' ä). Adding a different user without unicode in the public name worked fine.

Trying to visit NF projects logged into the sillygoose account also results in a 500 error.

The user to add (brandiatmuhkuh) also has unicode in his public name (Jürgen Brandstetter)</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/999/</guid></item><item><title>Wiki page edits (occasionally) cause 500 errors</title><link>https://forge-allura.apache.org/p/allura/tickets/909/</link><description>https://sourceforge.net/p/adobetickets/tickets/12/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/909/</guid></item><item><title>Review and update developer documentation</title><link>https://forge-allura.apache.org/p/allura/tickets/835/</link><description>The result of this is to task out updates so that the work can be done in parallel and/or tracked.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dean Henrichsmeyer</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/835/</guid></item><item><title>documentation: clean up the markdown syntax page, add list of approved HTML tags</title><link>https://forge-allura.apache.org/p/allura/tickets/679/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-07-01 15:11:23.523000
Assigned to:nobody
The markdown syntax page linked in help should be updated to include:

- A brief description of what markdown is
- a link to a canonical reference 
- a description of what html tags are allowed
- description of our markdown extensions ( tables, code highlighting (specifically, the language designation), our custom linking conventions)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/679/</guid></item><item><title>Create Tarballs and update requirements.txt </title><link>https://forge-allura.apache.org/p/allura/tickets/666/</link><description>*Originally created by:* sf-overlords

Created by: mramm
Created date: 2010-06-28 17:41:51.848000
Assigned to:mramm

For our new virtual env based sandbox and production installs, we should create some new tarballs, so we don't install from svn. 

The marginal costs of updating these tarballs is very low, so it should be fine. 

* http://bitbucket.org/rick446/easywidgets
* http://bitbucket.org/turbogears/tg-dev
* http://bitbucket.org/turbogears/tgdevtools-2_0
* git://merciless.git.sourceforge.net/gitroot/merciless/merciless
* git://engr.geek.net/sf.phpsession

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/666/</guid></item><item><title>move tickets/wiki off of newforge.sf.geek.net to forge project</title><link>https://forge-allura.apache.org/p/allura/tickets/648/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-06-24 15:57:16.663000
Assigned to:rcopeland
I would like to start moving forge development resources on to the live site, so that the live site is our primary use of the NF code, and non-employee stakeholders can have access to documentation and issue status.

For now, make this a private project (either at the tool or project level).

Tickets - move all tickets. Preserving ticket #s.  Keep discussion.  User accounts do not need to be mapped. 

Wiki - private wiki with tool documentation and priorities.
</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/648/</guid></item><item><title>write general description of the new forge</title><link>https://forge-allura.apache.org/p/allura/tickets/603/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-06-17 16:47:21.222000
Assigned to:mramm

Write a top level document explaining the new forge and linking to documents for each of the features.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/603/</guid></item><item><title>write documentation for the wiki</title><link>https://forge-allura.apache.org/p/allura/tickets/595/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-06-17 15:39:34.345000
Assigned to:mramm

Create a document which describes the basic functionality of the wiki

Include:

- markdown syntax
- wikiwords
- tags
- macros
- attachments
- REST API
- admin functions</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/595/</guid></item><item><title>macros: document the wiki macros</title><link>https://forge-allura.apache.org/p/allura/tickets/522/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-06-04 15:41:15.011000
Assigned to:mramm

Write a syntax document for any macros we have in the wiki.  This should be similar to confluence's style of documentation</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/522/</guid></item><item><title>Reactor traceback sending e-mail</title><link>https://forge-allura.apache.org/p/allura/tickets/502/</link><description>*Originally created by:* sf-overlords

Created by: mramm
Created date: 2010-06-03 16:29:02.326000
Assigned to:mramm

Traceback (most recent call last):

&lt;pre&gt;  
File "/var/local/allura/pyforge/pyforge/command/reactor.py", line 167, in callback
    method(msg.delivery_info['routing_key'], data)
  File "/var/local/allura/ForgeMail/forgemail/reactors/common_react.py", line 116, in send_email
    multi_msg)
  File "/var/local/allura/ForgeMail/forgemail/lib/util.py", line 120, in sendmail
    self._client.sendmail(addrfrom, addrs, content)
  File "/usr/lib64/python2.6/smtplib.py", line 709, in sendmail
    raise SMTPRecipientsRefused(senderrs)
SMTPRecipientsRefused: {None: (501, '&lt;&gt;: missing or malformed local part')}
&lt;/pre&gt;</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/502/</guid></item><item><title>refactor smart_str code in pyforge/model/auth.py</title><link>https://forge-allura.apache.org/p/allura/tickets/499/</link><description>*Originally created by:* sf-overlords

Created by: wolf
Created date: 2010-06-03 14:56:43.306000
Assigned to:nobody

as a quick fix to get unicode working on Wiki REST imports, we added and very slightly modified some code from tg.controllers.util.  This code now needs to be (a) fixed in TurboGears, (b) refactored locally, or converted back to using the updated TG code when (a) is done.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/499/</guid></item><item><title>wiki: authenticated users should see edit link when they have permission to edit</title><link>https://forge-allura.apache.org/p/allura/tickets/453/</link><description>*Originally created by:* sf-overlords

Created by: mramm
Created date: 2010-05-24 17:29:10.540000
Assigned to:mramm

When *authenticated has edit permissions on the wiki, the edit link is not displayed. As an authenticated user, I should see the link.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/453/</guid></item><item><title>e-mail on errors</title><link>https://forge-allura.apache.org/p/allura/tickets/427/</link><description>*Originally created by:* sf-overlords

Created by: mramm
Created date: 2010-05-21 09:15:37.451000
Assigned to:mramm

Configure pyforge to e-mail the allura team whenever there are errors on the web servers.   

Get sog to e-mail us reactor logs when there are errors. 

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/427/</guid></item><item><title>new user registration broken on sandboxes</title><link>https://forge-allura.apache.org/p/allura/tickets/332/</link><description>*Originally created by:* sf-overlords

Created by: jbeard
Created date: 2010-05-04 19:22:38.915000
Assigned to:mramm

[Tue May 04 14:52:04 2010] [error] [client 127.0.0.1] File '/home/jbeard/jbeard-3024/forge/pyforge/pyforge/model/auth.py', line 205 in register
[Tue May 04 14:52:04 2010] [error] [client 127.0.0.1]   n.register_project('u/' + result.username, result, user_project=True)
[Tue May 04 14:52:04 2010] [error] [client 127.0.0.1] AttributeError: 'NoneType' object has no attribute 'register_project'</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/332/</guid></item></channel></rss>