Re: [Apache Bloodhound] #676: Relax constraints on ProductEnvironment callable contract
#676: Relax constraints on ProductEnvironment callable contract ---+--- Reporter: olemis| Owner: gjm Type: enhancement | Status: closed Priority: major | Milestone: Release 8 Component: multiproduct |Version: 0.7.0 Resolution: fixed | Keywords: product env, bep-0003 ---+--- Changes (by gjm): * status: review = closed * resolution: = fixed Comment: Calling this done. Thanks for the help olemis. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/676#comment:8 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] #681: Problems updating milestones, components, etc. does not show
#681: Problems updating milestones, components, etc. does not show ---+--- Reporter: ogaerick | Owner: nobody Type: defect | Status: new Priority: blocker| Milestone: Release 8 Component: siteadmin |Version: 0.7.0 Keywords: | ---+--- There seems to be a cache somewhere that prevents updates made in the admin to be reflected correctly afterwards in the tickets. - Dropdowns still have old values. - pressing refresh on the browser sometimes helps, next ticket might show old value again - renaming a value does not reflect change to all db records -- Ticket URL: https://issues.apache.org/bloodhound/ticket/681 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #681: Problems updating milestones, components, etc. does not show
#681: Problems updating milestones, components, etc. does not show ---+--- Reporter: ogaerick | Owner: nobody Type: defect| Status: new Priority: blocker | Milestone: Release 8 Component: multiproduct |Version: 0.7.0 Resolution:| Keywords: milestone ---+--- Changes (by olemis): * keywords: = milestone * component: siteadmin = multiproduct Comment: Replying to [ticket:681 ogaerick]: There seems to be a cache somewhere that prevents updates made in the admin to be reflected correctly afterwards in the tickets. [...] I've noticed this behavior before , see #613 and #614 . Have you deployed PostgreSQL ? PS: I'm tempted to close this ticket as duplicate of #613 -- Ticket URL: https://issues.apache.org/bloodhound/ticket/681#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #640: MP DB version newer than supported
#640: MP DB version newer than supported ---+ Reporter: olemis| Owner: Type: defect| Status: new Priority: critical | Milestone: Unscheduled Component: multiproduct |Version: 0.6.0 Resolution:| Keywords: trac-admin, postgresql ---+ Changes (by olemis): * status: needinfo(new) = new * owner: rjollos = * milestone: Release 8 = Unscheduled Comment: I'm not seeing this kind of errors anymore . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/640#comment:5 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #640: MP DB version newer than supported
#640: MP DB version newer than supported ---+ Reporter: olemis| Owner: Type: defect| Status: closed Priority: critical | Milestone: Unscheduled Component: multiproduct |Version: 0.6.0 Resolution: worksforme| Keywords: trac-admin, postgresql ---+ Changes (by olemis): * status: new = closed * resolution: = worksforme Comment: I'll close this ticket since it'll be possible to reopen it later if the problem is recurrent . -- Ticket URL: https://issues.apache.org/bloodhound/ticket/640#comment:6 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #675: Allow configuring the default retargeting option when closing or deleting a milestone
#675: Allow configuring the default retargeting option when closing or deleting a milestone --+-- Reporter: rjollos | Owner: nobody Type: enhancement | Status: new Priority: major| Milestone: Component: ui design|Version: Resolution: | Keywords: trac-1.2 --+-- Comment (by rjollos): Upstream change committed in [trac 12121], for inclusion in trac:milestone:1.1.2. -- Ticket URL: https://issues.apache.org/bloodhound/ticket/675#comment:1 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #667: Error rendering forbidden pages
#667: Error rendering forbidden pages +- Reporter: olemis | Owner: olemis Type: defect | Status: accepted Priority: blocker| Milestone: Release 8 Component: ui design |Version: 0.7.0 Resolution: | Keywords: permissions, chrome +- Changes (by olemis): * status: assigned = accepted * owner: rjollos = olemis -- Ticket URL: https://issues.apache.org/bloodhound/ticket/667#comment:7 Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #667: Error rendering forbidden pages
#667: Error rendering forbidden pages
+-
Reporter: olemis | Owner: rjollos
Type: defect | Status: review
Priority: blocker| Milestone: Release 8
Component: ui design |Version: 0.7.0
Resolution: | Keywords: permissions, chrome
+-
Comment (by rjollos):
The patch appears to be effectively the same as the one in comment:3. Is
there a difference I'm not seeing, or just style differences? I'm fine
with using the `.get('mainnav', []))` since I think it's cleaner.
Is the `setdefault` needed? There won't be any iteration if `mainnav`
isn't in the dictionary, so it doesn't appear that the line with
`setdefault` would even be hit.
--
Ticket URL: https://issues.apache.org/bloodhound/ticket/667#comment:9
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
[Apache Bloodhound] New user registration: pmontepagano
New user registration for user pmontepagano -- Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker
[Apache Bloodhound] BloodhoundInstallNginx modified
Page BloodhoundInstallNginx was changed by pmontepagano Diff URL: https://issues.apache.org/bloodhound/wiki/BloodhoundInstallNginx?action=diffversion=5 Revision 5 Comment: template0 allows UTF-8 encoding in Debian Wheezy Changes: ---8--8--8--8--8--8--8--8 Index: BloodhoundInstallNginx = --- BloodhoundInstallNginx (version: 4) +++ BloodhoundInstallNginx (version: 5) @@ -20,7 +20,7 @@ #!sh sudo su - postgres createuser -U postgres -S -D -R -E -P bloodhound -createdb -U postgres -O bloodhound -E UTF-8 bloodhound +createdb -U postgres -O bloodhound -E UTF-8 -T template0 bloodhound logout }}} ---8--8--8--8--8--8--8--8 -- Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundInstallNginx Apache Bloodhound https://issues.apache.org/bloodhound/ The Apache Bloodhound issue tracker This is an automated message. Someone added your email address to be notified of changes on 'BloodhoundInstallNginx' page. If it was not you, please report to .
[Apache Bloodhound] BloodhoundInstallNginx modified
Page BloodhoundInstallNginx was changed by pmontepagano
Diff URL:
https://issues.apache.org/bloodhound/wiki/BloodhoundInstallNginx?action=diffversion=6
Revision 6
Comment: python-dev permits us to compile genshi code which would otherwise run
slowly
Changes:
---8--8--8--8--8--8--8--8
Index: BloodhoundInstallNginx
=
--- BloodhoundInstallNginx (version: 5)
+++ BloodhoundInstallNginx (version: 6)
@@ -12,7 +12,7 @@
System packages to install:
{{{
#!sh
-sudo apt-get install python python-setuptools python-pip python-virtualenv
postgresql python-psycopg2 nginx
+sudo apt-get install python python-setuptools python-pip python-virtualenv
postgresql python-psycopg2 nginx python-dev
}}}
Database user and database creation:
---8--8--8--8--8--8--8--8
--
Page URL: https://issues.apache.org/bloodhound/wiki/BloodhoundInstallNginx
Apache Bloodhound https://issues.apache.org/bloodhound/
The Apache Bloodhound issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'BloodhoundInstallNginx' page.
If it was not you, please report to .
