Re: [Apache Bloodhound] #161: Install fails when trac-hacks is down
#161: Install fails when trac-hacks is down +--- Reporter: jdreimann | Owner: gjm Type: defect | Status: closed Priority: critical | Milestone: Release 3 Component: installer |Version: Resolution: fixed | Keywords: +--- Comment (by rjollos): Just a side-note to say that [trachacks:AccountManagerPlugin] 4.0 is very close to being released (pending license change from !BeerWare to 3-Clause BSD in [http://trac-hacks.org/ticket/10644 #10644]), and the new eggs should be uploaded to PyPI at that time. This had me thinking as to whether the older eggs would be retained on PyPI, and even if they aren't, setuptools will probably just go out and grab the latest version from PyPI, right? I wasn't sure if this had been given much thought already, and whether we might want more explicit control over the version being installed. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/161#comment:14 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #276: Make error notice more prominent on failed login
#276: Make error notice more prominent on failed login -+ Reporter: rjollos | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: plugins |Version: Keywords: starter | -+ The error notice for a failed login is not very prominent. One idea would be to use the ''system-message'' style of notice. [[Image(ErrorMessage.png)]] -- Ticket URL: https://issues.apache.org/bloodhound/ticket/276 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #276: Make error notice more prominent on failed login
#276: Make error notice more prominent on failed login --+- Reporter: rjollos | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: plugins |Version: Resolution: | Keywords: starter --+- Description changed by rjollos: Old description: The error notice for a failed login is not very prominent. One idea would be to use the ''system-message'' style of notice. [[Image(ErrorMessage.png)]] New description: The error notice for a failed login is not very prominent. One idea would be to use the ''system-message'' style of notice, and position it immediately above or below the **Login** text. [[Image(ErrorMessage.png)]] -- -- Ticket URL: https://issues.apache.org/bloodhound/ticket/276#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #277: Reorder enumeration lists on admin panels by drag and drop
#277: Reorder enumeration lists on admin panels by drag and drop -+ Reporter: rjollos | Owner: nobody Type: enhancement | Status: new Priority: minor| Milestone: Component: ui design|Version: Keywords: | -+ [trachacks:AdminEnumListPlugin] provides the ability to reorder enumeration lists on the admin pages by drag and drop. This is implemented completely in javascript, so it should be simple to integrate directly into Bloodhound. We could even offer it as a contribution back to the Trac core. Testing with Trac 1.1.1dev as well as the latest Bloodhound trunk revealed that there is some work to do on the code: * [https://trac-hacks.org/ticket/10655 #10655] Use jQuery UI provided by Trac in 1.0 and later. * [https://trac-hacks.org/ticket/10656 #10656] Add a warning when navigating away from a page that has unsaved changes. * [https://trac-hacks.org/ticket/10657 #10657] Hide the 'Order' column. * The row highlighting does not appear to be correct in all cases. Improvements will be made to the plugin, and a patch will be submitted here when the code is felt to be ready. A ticket can then be opened in the Trac core to offer the patch there as well. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/277 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] InterMapTxt modified
Page InterMapTxt was changed by gjm
Diff URL:
https://issues.apache.org/bloodhound/wiki/InterMapTxt?action=diffversion=4
Revision 4
Changes:
---8--8--8--8--8--8--8--8
Index: InterMapTxt
=
--- InterMapTxt (version: 3)
+++ InterMapTxt (version: 4)
@@ -38,7 +38,7 @@
== Prefix Definitions ==
{{{
-BEP http://issues.apache.org/bloodhound/wiki/Proposals/BEP-$1.html#
Bloodhound Enhancement Proposal $1
+BEP http://issues.apache.org/bloodhound/wiki/Proposals/BEP-$1#
Bloodhound Enhancement Proposal $1
PEP http://www.python.org/peps/pep-$1.html# Python Enhancement
Proposal
PythonBughttp://bugs.python.org/issue$1 # Python Issue #$1
Python-issue http://bugs.python.org/issue$1 # Python Issue #$1
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/InterMapTxt
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'InterMapTxt' page.
If it was not you, please report to .
[Apache Bloodhound] New user registration: wharper
New user registration for user wharper -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #245: Make sure that files that are not part of the release are not included.
#245: Make sure that files that are not part of the release are not included. +--- Reporter: gjm| Owner: nobody Type: task | Status: new Priority: major | Milestone: Release 4 Component: dashboard |Version: Resolution: | Keywords: +--- Comment (by gjm): For release 3, a check was done manually. I don't think that we want to specifically look for certain files as we find them, more verify that a release essentially matches the contents of the repository at the appropriate tag, ignoring any paths that we might want to remove. Basically we need this to be part of a release script. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/245#comment:2 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
[Apache Bloodhound] #278: default setup requires HtDigestHashMethod for reset lost password functionality
#278: default setup requires HtDigestHashMethod for reset lost password functionality ---+--- Reporter: gjm| Owner: nobody Type: defect | Status: new Priority: major | Milestone: Release 4 Component: installer |Version: Keywords: | ---+--- Enable acct_mgr.pwhash.HtDigestHashMethod in default setup. Update for missing setting on upgrades for appropriate settings - presumably: * acct_mgr.pwhash.HtDigestHashMethod disabled and * acct_mgr.htfile.HtDigestStore active -- Ticket URL: https://issues.apache.org/bloodhound/ticket/278 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
svn commit: r1413964 - /incubator/bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py
Author: gjm
Date: Tue Nov 27 01:06:37 2012
New Revision: 1413964
URL: http://svn.apache.org/viewvc?rev=1413964view=rev
Log:
fixing wrong permission in rendering product description - fixes #254 (from
olemis)
Modified:
incubator/bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py
Modified: incubator/bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py
URL:
http://svn.apache.org/viewvc/incubator/bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py?rev=1413964r1=1413963r2=1413964view=diff
==
--- incubator/bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py
(original)
+++ incubator/bloodhound/trunk/bloodhound_multiproduct/multiproduct/api.py Tue
Nov 27 01:06:37 2012
@@ -168,7 +168,7 @@ class MultiProductSystem(Component):
href = context.href.products(product.prefix)
if 'PRODUCT_VIEW' in context.perm(product.resource):
return tag.a(label, class_='product', href=href + extra)
-elif 'MILESTONE_CREATE' in context.perm('product', name):
+elif 'PRODUCT_CREATE' in context.perm('product', name):
return tag.a(label, class_='missing product',
href=context.href('products', action='new'),
rel='nofollow')
svn commit: r1413972 - /incubator/bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_wiki_view.html
Author: gjm Date: Tue Nov 27 02:10:53 2012 New Revision: 1413972 URL: http://svn.apache.org/viewvc?rev=1413972view=rev Log: use enhanced attachment list in wiki pages - #251 (from olemis) Modified: incubator/bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_wiki_view.html Modified: incubator/bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_wiki_view.html URL: http://svn.apache.org/viewvc/incubator/bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_wiki_view.html?rev=1413972r1=1413971r2=1413972view=diff == --- incubator/bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_wiki_view.html (original) +++ incubator/bloodhound/trunk/bloodhound_theme/bhtheme/templates/bh_wiki_view.html Tue Nov 27 02:10:53 2012 @@ -95,7 +95,7 @@ /div div class=span12 -xi:include href=list_of_attachments.html +xi:include href=bh_list_of_attachments.html py:with=alist = attachments; compact = True; foldable = True/ /div
Re: [Apache Bloodhound] #251: Improve attachments section in wiki pages
#251: Improve attachments section in wiki pages --+--- Reporter: olemis | Owner: gjm Type: enhancement | Status: closed Priority: major| Milestone: Release 4 Component: ui design|Version: Resolution: fixed| Keywords: wiki attachment bootstrap --+--- Changes (by gjm): * status: review = closed * resolution: = fixed Comment: r1413972 fixes - thanks olemis -- Ticket URL: https://issues.apache.org/bloodhound/ticket/251#comment:3 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound (incubating) issue tracker
