Re: [Apache Bloodhound] #13: Rename About Trac to System Information and move it to the footer
#13: Rename About Trac to System Information and move it to the footer --+-- Reporter: jdreimann| Owner: nobody Type: enhancement | Status: assigned Priority: minor| Milestone: Component: dashboard|Version: Resolution: | Keywords: starter --+-- Comment (by gjm): Sorry.. I of course meant to say that the footer is also partly specified in the trac.ini. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/13#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Password reset for user: jure
Password reset for user for user jure -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] Password reset for user: jure
Password reset for user for user jure -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #154: Installer fails when providing repository type without a path and vice versa
#154: Installer fails when providing repository type without a path and vice versa +--- Reporter: gjm| Owner: jure Type: defect | Status: assigned Priority: major | Milestone: Release 2 Component: installer |Version: Resolution: | Keywords: starter +--- Changes (by jure): * owner: nobody = jure -- Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #154: Installer fails when providing repository type without a path and vice versa
#154: Installer fails when providing repository type without a path and vice versa +--- Reporter: gjm| Owner: jure Type: defect | Status: assigned Priority: major | Milestone: Release 2 Component: installer |Version: Resolution: | Keywords: starter +--- Comment (by jure): Looking at the trac.do_initenv, the method expects both, repository type and directory, to be passed. There are 2 options, we can either: - require that both (type path) are specified - provide meaningful defaults for type, not sure what that would be I would go with the first option, require the user to specify both and fail if either is missing. Otherwise the setup output is not really what user expected as the warning can easily be overlooked ... -- Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:4 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #154: Installer fails when providing repository type without a path and vice versa
#154: Installer fails when providing repository type without a path and vice versa +--- Reporter: gjm| Owner: jure Type: defect | Status: accepted Priority: major | Milestone: Release 2 Component: installer |Version: Resolution: | Keywords: starter +--- Changes (by jure): * status: assigned = accepted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/154#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #190: Stop the 'More' action on Active Tickets from including the limit on the number of tickets in the custom query
#190: Stop the 'More' action on Active Tickets from including the limit on the number of tickets in the custom query +--- Reporter: gjm| Owner: jure Type: defect | Status: accepted Priority: major | Milestone: Release 2 Component: dashboard |Version: Resolution: | Keywords: +--- Changes (by jure): * status: assigned = accepted -- Ticket URL: https://issues.apache.org/bloodhound/ticket/190#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #203: Regression: wiki toolbar not visible
#203: Regression: wiki toolbar not visible +- Reporter: olemis | Owner: olemis Type: defect | Status: closed Priority: trivial| Milestone: Release 2 Component: ui design |Version: Resolution: fixed | Keywords: starter css +- Changes (by gjm): * status: accepted = closed * resolution: = fixed Comment: r1392311 fixes, adding css rules for the wikitoolbar to the bloodhound.css -- Ticket URL: https://issues.apache.org/bloodhound/ticket/203#comment:13 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #211: Regression : not possible to resize wiki textarea
#211: Regression : not possible to resize wiki textarea
+-
Reporter: olemis | Owner: olemis
Type: defect | Status: accepted
Priority: trivial| Milestone: Release 2
Component: ui design |Version:
Resolution: | Keywords: starter css
+-
Comment (by gjm):
This effectively does not work for Firefox (15.0.1) or Chrome
(21.0.1180.89) on ubuntu when looking at editing wiki pages.
We seem to need to add something like
{{{
#!css
#edit div.trac-resizable { width: 100%; }
}}}
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/211#comment:4
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #204: Activity feed currently breaks new ticket page link
#204: Activity feed currently breaks new ticket page link
+---
Reporter: gjm| Owner: nobody
Type: defect | Status: closed
Priority: critical | Milestone: Release 2
Component: dashboard |Version:
Resolution: fixed | Keywords:
+---
Changes (by gjm):
* status: new = closed
* resolution: = fixed
Comment:
r1392403 fixes this (the {{{py:if/}}}s moved inside the
{{{timeline_empty()}}} function.)
The TicketSystem.format_summary should not have failed for this input but
this will be tracked by a different ticket.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/204#comment:2
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #215: TicketSystem.format_summary raises exception for missing resource id
#215: TicketSystem.format_summary raises exception for missing resource id
---+
Reporter: gjm| Owner: nobody
Type: defect | Status: new
Priority: minor | Milestone:
Component: dashboard |Version:
Keywords: |
---+
This output was from #204 which has been fixed but the underlying problem
appears to be that {{{TicketSystem.format_summary}}} is failing when
perhaps it should not.
{{{
File
/home/bloodhound/bh/bloodhound/bloodhound_dashboard/bhdashboard/widgets/templates/widget_timeline.html,
line 54, in Expression u'summary_of(context.resource)'
No events reported for em${summary_of(context.resource)}/em in the
File /home/bloodhound/bh/bloodhound/trac/trac/resource.py, line 347, in
get_resource_summary
return get_resource_description(env, resource, 'summary')
File /home/bloodhound/bh/bloodhound/trac/trac/resource.py, line 333, in
get_resource_description
return manager.get_resource_description(resource, format, **kwargs)
File /home/bloodhound/bh/bloodhound/trac/trac/ticket/api.py, line 555,
in get_resource_description
return self.format_summary(*args)
File /home/bloodhound/bh/bloodhound/trac/trac/ticket/api.py, line 561,
in format_summary
summary = type + ': ' + summary
}}}
We should check if Trac has already fixed this.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/215
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
