<?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:"jwh"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:57 -0000</lastBuildDate><item><title>Clarify difference between Summary and Description</title><link>https://forge-allura.apache.org/p/allura/tickets/3599/</link><description>The difference between Summary and Description in the Project Metadata admin were not obvious to new users. Maybe we could at least add the "X characters left" to show them how short the Summary should be compared to the Description. Help text could be good too.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jenny Steele</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3599/</guid></item><item><title>options for "home" tool not working with nbhd templates any more POST: update prod nhbd templates</title><link>https://forge-allura.apache.org/p/allura/tickets/3515/</link><description>Since [#3250] (I think), the nbhd template config for Motorola hasn't been working with regard to the home settings and text.

&gt; An example of a home page - https://sourceforge.net/motorola/testing123/home/Home/
You'll notice the tool options for Home page which are set (show attachments, discussion, etc.) and the home page text doesn't match what is supposed to be there.

I think we have some tests around templates, but we should add one that checks the home wiki page text too.</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/3515/</guid></item><item><title>Use *anonymous instead of 'nobody' in ticket ownership</title><link>https://forge-allura.apache.org/p/allura/tickets/3268/</link><description>Example: http://sourceforge.net/p/familysite/support-requests/1/ has owner 'nobody', it should use '*anonymous' like other places in the migration script do.</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/3268/</guid></item><item><title>Change Home/Wiki default wikis</title><link>https://forge-allura.apache.org/p/allura/tickets/3250/</link><description>Projects get a default "Home" wiki and /p/add_project creates a "Wiki" wiki.  That's duplicative, and also 'Home' in the menu is confusing when a 'Summary' tool is installed.

* the "Home" wiki should not be created by default any more
* change /p/add_project's wiki checkbox (still on by default) to cause a "Docs" wiki to be installed (in the first position)
* the default contents of the Home wiki page should go into the Docs wiki page
* migrate_sfx_project.py should not install any wiki tool</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/3250/</guid></item><item><title>[[project_blog_posts]] Markdown macro does not work for 'smb4k' project [22669]</title><link>https://forge-allura.apache.org/p/allura/tickets/3218/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/22669

&gt;Hello!

&gt;I tried to include my project's blog posts on the my Sourceforge 2.0 beta project site (https://sourceforge.net/p/smb4k/home/Home/), but ist seems that the `[[project_blog_posts]]` Markdown makro does not work: No posts are included on the "Home" page. Has it not been implemented yet?

&gt;Best regards
Alexander Reinholdt

His syntax is okay (I copy/pasted it into my test project, where the exact same text worked). Perhaps there's something in the content of the blog post that's causing issues? My test blog posts have different text.</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/3218/</guid></item><item><title>Project list macros should let you filter by award</title><link>https://forge-allura.apache.org/p/allura/tickets/3214/</link><description>OWASP would like to start using awards and be able to use the project list macro to show all projects with a certain award.</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/3214/</guid></item><item><title>Duplicate ticket change notifications</title><link>https://forge-allura.apache.org/p/allura/tickets/3038/</link><description>Since last push &lt;https://control.siteops.geek.net/sog/trac/ticket/19248&gt;, a single change to a ticket generates two emails with the same content.  One has headers:

~~~~
:::text
To: "[allura:tickets] " &lt;2985@tickets.allura.p.re.sf.net&gt;
From: "Kyle Adams" &lt;kadams54@users.sf.net&gt;
Reply-To: "[allura:tickets] " &lt;2985@tickets.allura.p.re.sf.net&gt;
Subject: [allura:tickets] #2985 Add download button to cross merch section
Message-ID: &lt;/p/allura/tickets/2985/3270dfc82c780b2e0058a8b70289c3cba63e17b9.tickets@allura.p.sourceforge.net&gt;

....

Sent from sourceforge.net because you indicated interest in &lt;https://source=
forge.net/p/allura/tickets/2985/&gt;
~~~~

And the other (incorrect) has:

~~~~
:::text
To: "[allura:tickets] " &lt;noreply@in.sf.net&gt;
From: "Kyle Adams" &lt;kadams54@users.sf.net&gt;
Reply-To: "[allura:tickets] " &lt;noreply@in.sf.net&gt;
Subject: [allura:tickets] #2985 Add download button to cross merch section
Message-ID: &lt;/p/allura/tickets/_discuss/3270dfc82c780b2e0058a8b70289c3cba63e17b9.tickets@allura.p.sourceforge.net&gt;

....

Sent from sourceforge.net because you indicated interest in &lt;https://source=
forge.net/p/allura/tickets/_discuss/&gt;
~~~~</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/3038/</guid></item><item><title>SF2.0: no emails sent when a new message is awaiting moderation [22096]</title><link>https://forge-allura.apache.org/p/allura/tickets/2963/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/22096

&gt;SF2.0, project scipad.

&gt;When:

&gt;    a user adds a comment on an existing ticket 

&gt;or

&gt;    a user adds a message in a discussion forum 

&gt;these messages are sent to the moderation queue.

&gt;Issue is there is no message sent to the admin of the project.

&gt;New postings then go unnoticed for weeks, thus sending a very bad signal to the users who made an effort to post.

&gt;Happens for:

&gt;    https://sourceforge.net/p/scipad/tickets/
    https://sourceforge.net/p/scipad/discussion/general/

&gt;If I don't visit these pages manually often enough, then new contributions to my project are unnoticed.</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/2963/</guid></item><item><title>Add Scala to categorization [21800] *NEEDS SCRIPT*</title><link>https://forge-allura.apache.org/p/allura/tickets/2856/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/21800

&gt;Hi,

&gt;My project is written in scala, which is not listed among the programming languages for categorization. Any chance it might get added in some moment?

&gt;Thanks,

&gt;Pablo

It appears Scala has been in Classic Trove for some time, but it's not in allura's categorization, should be added.</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/2856/</guid></item><item><title>Awards need several fixes</title><link>https://forge-allura.apache.org/p/allura/tickets/2837/</link><description>* page takes forever to load, because it generates a drop-down of every single project.
    * change it to a text box, especially since long names in a drop-down make the "Grant" button hidden
* the revoke links don't work, need to be a POST
* when creating an award, if you don't upload an icon, you get a 500 error but it seems to work regardless</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/2837/</guid></item><item><title>Rtstats-format logging from allura - REQUIRES PROD.ini UPDATE</title><link>https://forge-allura.apache.org/p/allura/tickets/2802/</link><description>Allura's zarkov logging should be changed to match the way we're doing it for classic rtstats:

* write to a file instead of inserting directly to zarkov

See [#3337] for zarkov processing and [#3338] for the scm events</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/2802/</guid></item><item><title>Errors from sidebar should be handled [21552]</title><link>https://forge-allura.apache.org/p/allura/tickets/2742/</link><description>When the sidebar throws an error, handle that better (for all tools, ideally).  The menu item in the top nav should still be there, and the rest of the page body should still render.  See also @exceptionless and [#1599]

------

https://sourceforge.net/apps/trac/sourceforge/ticket/21552

&gt;I have yesterday opened a new project, committed some code and opened some tickets. But after some time I got an error 500 on the ticket page: https://sourceforge.net/p/xprofile/tickets</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/2742/</guid></item><item><title>Tickets should have a custom field for "user" type</title><link>https://forge-allura.apache.org/p/allura/tickets/2654/</link><description>This would allow us to have a "QA assigned to" custom field.</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/2654/</guid></item><item><title>Add macros to default home wiki text</title><link>https://forge-allura.apache.org/p/allura/tickets/2640/</link><description>Use new macros `[[project_admins]]` and `[[download_button]]` in the project home wiki text.</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/2640/</guid></item><item><title>Funky table width on ticket list pages in safari (and chrome)</title><link>https://forge-allura.apache.org/p/allura/tickets/2636/</link><description>http://sourceforge.net/p/allura/tickets/ has a table too wide for it's container now (on safari): http://screencast.com/t/t6yfE1LrdGBC</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/2636/</guid></item><item><title>Prevent 'delete project' selection for sf.net - INI UPDATE</title><link>https://forge-allura.apache.org/p/allura/tickets/2635/</link><description>On the admin page, remove the option for a project to delete themselves.  If it's easy enough, add a config option that enables it (so OSS can allow it, sf.net would not).

When the config does not allow deletion, make sure that deleting subprojects still works.            </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2635/</guid></item><item><title>Wiki sends weird redirects instead of 404s</title><link>https://forge-allura.apache.org/p/allura/tickets/2614/</link><description>~~~~
:::bash
$ curl -I 'http://sourceforge.net/motorola/wiki/Android/wiki/wiki/Projects'
HTTP/1.1 302 Found
Location: http://sourceforge.net/motorola/wiki/Android/wiki/wiki/wiki/Projects


$ curl -I 'http://sourceforge.net/motorola/wiki/Android/wiki'
HTTP/1.1 302 Found
Location: http://sourceforge.net/motorola/wiki/wiki
~~~~</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/2614/</guid></item><item><title>Creating an anonymous discusstion thread in the Beta system [20865]</title><link>https://forge-allura.apache.org/p/allura/tickets/2522/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/20865

&gt;I created a new topic in the "discussion" section of my project,
"runtimes", without being logged in.

&gt;Later the topic was attributed to the user "anonymous coward"
(which is ok, I suppose), but the content of the topic, i.e.
the text I entered, was empty or at least not visible. Everything
I entered was lost.

&gt;I had expected that the system either would accept the text being from
an anonymous user, or would ask me to log in, conduct the login,
and accept the entered text from the logged in user.

Looking into this further, I realized that the reason he's not seeing anything since anonymous posts are moderated by default. Perhaps instead of displaying a blank post, we should put up a notice that says "Post awaiting moderation" or "Pending moderation" or something like that...</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/2522/</guid></item><item><title>Monitoring emails have encoding issues? [20723, 20806]</title><link>https://forge-allura.apache.org/p/allura/tickets/2519/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/20723

&gt; I have read MikTeX forum e-mails originating from
https://sourceforge.net/projects/miktex/forums/forum/33790
for many years. Very recently, something changed in the messaging
format, and now non-printing characters appear as text strings in the
body of the message. So the typical message is filled with strings such as =0A and =0A=0A and ).=0A=0D=0A. No amount of tweaking of my e-mail client (Eudora 7) can restore legibility to my messages, and I must conclude that something changed at sourceforge.net.

Example email: 
&gt; =0ARead and respond to this message at: =0Ahttps://sourceforge.net/project=
s/miktex/forums/forum/33790/topic/4619709=0ABy: clembibou=0A=0A=0D=0AHi=0D=
=0A=0D=0ASince the last update MikTex (23/07/2011), if I try to launch the=

&gt;    updater the=0Afollowing error pop-up appears:=0A=0D=0AWindows API error 1=

&gt;113: No mapping for the Unicode character exists in the target=0Amulti-byt=
e code page.=0A=0D=0AI understand this could be related to Windows version=

&gt;    with accentuated path=0A(my username has an accent). However, I never got=
    this problem before with MikTex=0A(or any other software) which I use for=
    years on French MS Windows systems.=0AI executed "fc-cache --verbose" as=
    suggested by a post on the Internet, but=0Ano problem are reported and fc=

&gt;-cache succeeds. MikTex (LaTeX, PdfLaTeX...) works=0Afine, only the update=
r generates the error.=0A=0D=0AAnybody with an idea for a workaround?=0D=
=0AThanks in advance=0D=0A(a Spanish speaking member of the forum reports=

&gt;    a similar problem)=0D=0A=0A=0A_=

&gt;=0AYou are receiving this email=

&gt;    because you elected to monitor this topic or entire forum.=0ATo stop moni=

&gt;toring this topic visit: =0Ahttps://sourceforge.net/projects/miktex/forums=
/forum/33790/topic/4619709/unmonitor=0ATo stop monitoring this forum visit=
: =0Ahttps://sourceforge.net/projects/miktex/forums/forum/33790/unmonitor

And also from https://sourceforge.net/apps/trac/sourceforge/ticket/20806:

&gt;Hi.

&gt;I have a query regarding monitoring feature in forums(e.g. Open discussion).

&gt;If I enter topic title and its contents with English, there is no issue. Relevant reply to specific topic is beautifully delivered into my email inbox via monitoring feature. Thanks for this, i don't need to bother to log in to my project site every once in a while to check other team mate's reply. great!

&gt;But the problem is once I use Korean language (yes, i am Korean) as a topic title, delivered email messages are all broken like what i provided with the screenshot(1.png).

&gt;Strangely, if i use English with a topic title, email message is not broken even if reply content is written in Korean language (refer to 2.png).

&gt;Is it supposed to work like this? or unreported glitch something?
Thanks for your support in advance. 

I'm not sure if these two issues are related, but they appear to be at least.</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/2519/</guid></item><item><title>Milestone progress uses SOLR value, not mongo value</title><link>https://forge-allura.apache.org/p/allura/tickets/2500/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2500/</guid></item><item><title>Bug with blog engine and umlaut chars on the title</title><link>https://forge-allura.apache.org/p/allura/tickets/2472/</link><description>*Originally created by:* takedap

If I try to create an blog post (as an test user on fresh installation) and use umlaut chars (ä, ö) on title I get 'Internal server error' when trying to save post. However, regardless of the error message those blog posts are stored and they show up on blog.

But, even if the posts are stored I can't open the posts for editing (as an logged in user) nor open them for reading as an anonymous user. When I try to access URL http://192.168.10.175:8080/u/test-user/blog/2011/07/ääöö/ I just get 404.</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/2472/</guid></item><item><title>Error when registering project with unicode name</title><link>https://forge-allura.apache.org/p/allura/tickets/2466/</link><description>~~~~
Module sfx.sfx_main:157 in register_project
&lt;&lt;          # Reserve project name with SFX
               try:
                   ug_name = self.api.create(user, neighborhood, shortname, project_name, private_project)
                   log.info('SFX Project creation returned: %s', ug_name)
               except sfx_exc.SFXNotFound, exc:
&gt;&gt;  ug_name = self.api.create(user, neighborhood, shortname, project_name, private_project)
Module sfx.lib.sfx_api:172 in create
&lt;&lt;                  user_id=user.get_tool_data('sfx', 'userid'),
                       unix_group_name=ug_name,
                       group_name=lsub_utf8(project_name.encode('utf-8'), 40),
                       private=is_private_project,
                       short_description=lsub_utf8(short_description.encode('utf-8'), 255))
&gt;&gt;  group_name=lsub_utf8(project_name.encode('utf-8'), 40),
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 1: ordinal not in range(128)
~~~~</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/2466/</guid></item><item><title>Fix our own discussion threads</title><link>https://forge-allura.apache.org/p/allura/tickets/2461/</link><description>https://sourceforge.net/p/allura/discussion/general/ has several problems:
    
* negative post counts
* some post counts of 2, but actually just 1 post there.
* we haven't replied
* many have just a title - is that right? or should we require a description?
    * lack of post makes the 'last post' column empty sometimes too</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/2461/</guid></item><item><title>Search edit box on saved searches needs UX cleanup</title><link>https://forge-allura.apache.org/p/allura/tickets/2369/</link><description>We should know that this is a saved search (and we do because we highlight the correct button on the left nav bar) and show both the name and search field, and show an Update Search button if you have permissions.   Otherwise we should not show the save search button at all (I think this is the case already). </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2369/</guid></item><item><title>Fix ticket numbers on milestone counts to use mongo counts</title><link>https://forge-allura.apache.org/p/allura/tickets/2368/</link><description>Currently they use cached values derived from solr.  The cache is still fine, but should use mongo count not solr.   This ticket should also include a review of the cache invalidation logic.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2368/</guid></item></channel></rss>