COmanage Developers List

[Scott Koranda <>]

> Hi,
> 
> I am also finding that after the pull, when I am authenticated
> as a user that is a CO admin but NOT a CMP admin, I cannot see
> 
> /registry/co_dashboards/dashboard/co:2
> 
> I receive a "Permission Denied" session flash.

Arlen, you can ignore this "Permission Denied" problem.

I used git to step back through commits and the problem starts
before your recent large commit.

It happens at fd8d759bf7ef5af10d28b4f155194262c7c0390a

I am looking at that now...

Thanks,

Scott

> 
> I am looking in detail now but I suspect a somewhat large
> issue because the values I am seeing returned for 
> 
> $this->Role->calculateCMRoles()
> 
> in isAuthorized() for the CoDashboardsController
> 
> are quite wrong. 
> 
> I have cleared the cache by the way but the problem still
> persists.
> 
> Thanks,
> 
> Scott
> 
> 
> > Thanks, Scott - I'm taking a look.
> > A
> > 
> > On 7/8/15 8:55 AM, Scott Koranda wrote:
> > 
> >     Hi Arlen,
> > 
> >     After pulling these changes when I look at 
> > /registry/co_people/canvas/<id>
> >     I see errors like
> > 
> >     Undefined index: Search.given
> > 
> >     A screenshot is attached.
> > 
> >     Thanks,
> > 
> >     Scott
> > 
> >     On Tue, Jul 7, 2015 at 4:58 PM, Arlen Johnson 
> > <>
> >  wrote:
> > 
> >         Ok - I just pushed a fairly large commit - 52 files, almost all in
> >         View, though I touched the language file as well.
> > 
> >         A
> > 
> > 
> >         On 7/7/15 3:55 PM, Arlen Johnson wrote:
> > 
> >             Sounds good (-:
> >             A
> > 
> >             On 7/7/15 2:28 PM, Benn Oshrin wrote:
> > 
> >                 Commit as you're ready. I'll announce a freeze for 0.9.4 
> > at
> >                 some point,
> >                 but I need to finish a couple of tickets first.
> > 
> >                 Thanks,
> > 
> >                 -Benn-
> > 
> >                 On 7/7/15 8:58 AM, Arlen Johnson wrote:
> > 
> >                     Upcoming commits from me will not be "big" changes, 
> > but
> >                     will touch 50+
> >                     files.
> > 
> >                     My most current updates change some behaviors, but 
> > should
> >                     not change
> >                     screenshots (in any way that would matter).
> > 
> >                     If 0.9.4 is not yet tagged, I can commit fixes (and 
> > close
> >                     some tickets) for
> >                     CO-1014 - Incorrect I18n in breadcrumbs (and in side 
> > menus)
> >                     A number of fixes to improve the existing search 
> > interfaces
> >                     (for
> >                     co_people, org_identities)
> > 
> >                     There's potentially more cleanup I can do and commit 
> > as
> >                     well. The
> >                     alternative is for me to retag all the 0.9.4 tickets 
> > to
> >                     1.0, wait for
> >                     the 0.9.4 tag to be pushed out, and then start 
> > committing.
> > 
> >                     Preference?
> > 
> >                     Arlen
> > 
> > 
> >                     On 7/1/15 12:53 PM, Arlen Johnson wrote:
> > 
> >                         Hi, Heather, Benn -
> > 
> >                         I'm in full accord with all - and I'll also hold 
> > off on
> >                         pushing any
> >                         updates for 0.9.4 (I'm bogged down at the moment
> >                         anyway). So - go for
> >                         the tagging, and I'll try to give 1.0 tickets for 
> > UI a
> >                         solid look in
> >                         the latter half of this week.  Functional QA in
> >                         particular I'm ready
> >                         to dig into - and there are other items I'll want 
> > to
> >                         pursue.
> > 
> >                         My plan is to devote July and August /primarily/ 
> > to
> >                         Comanage
> >                         development (or at least make it the majority of 
> > what I
> >                         do) to wrap up
> >                         the tickets that remain (and are achievable) in 
> > the UI.
> > 
> >                         Arlen
> > 
> > 
> >                         On 6/29/15 5:46 PM, Heather Flanagan wrote:
> > 
> >                     On 6/24/15 12:56 PM, Benn Oshrin wrote:
> > 
> >                                     Given Scott is on vacation, I'll be 
> > in LA,
> >                                     and Heather is probably
> >                                     just plain exhausted, let's skip 
> > Friday's
> >                                     call.
> > 
> >                     It was an ... interesting trip home.
> > 
> > 
> >                                     Instead, please assemble a list of 
> > JIRA
> >                                     issues that you think
> >                                     should be blockers for 0.9.4 and then
> >                                     1.0.0. My current thought is
> >                                     to finish up CO-310 and a few other 
> > small/
> >                                     critical/low hanging
> >                                     issues and then tag 0.9.4 probably
> >                                     mid-to-late next week. If
> >                                     there's anything you want included 
> > before I
> >                                     tag, be sure to include
> >                                     it in your list, or flag it as a 
> > Blocker in
> >                                     JIRA.
> > 
> >                                     The theme of 0.9.4 is "it's been 
> > almost 4
> >                                     months, it's time to
> >                                     tag".
> > 
> >                     I expect you all have this part covered, so I'm 
> > focusing on
> >                     the 1.0.0
> >                     items
> > 
> > 
> >                                     For 1.0.0, I'd like to keep the scope
> >                                     fairly small. My primary task
> >                                     will be "installation 
> > simplification", as
> >                                     well as any fixes that
> >                                     shake out of 0.9.4 or are sponsored 
> > by a
> >                                     client. I'm thinking we
> >                                     could tag 1.0.0 as early as mid July.
> > 
> >                                     The theme of 1.0.0 is "it's been 
> > almost 5
> >                                     years, it's time to
> >                                     tag".
> > 
> >                     A-yup. Here's what I'd leave in 1.0.0
> > 
> >                     CO-297 and related tickets (CO-305, CO-489) (the 
> > Simplify
> >                     Installation
> >                     tickets)
> > 
> >                     Unless you think the Europeans and Scandinavians will 
> > need
> >                     it, I would
> >                     push the VOOT ticket out (CO-607)
> > 
> >                     CO-224 (Review Accessibility, because that makes the 
> > US
> >                     gov't happy)
> > 
> >                     CO-375 (Do not allow extended type to be deleted...) 
> > seems
> >                     a rather
> >                     important bug to fix (For the most part, I think 
> > pushing
> >                     the "don't be
> >                     stupid" bugs (e.g., CO-790) out makes sense, but this 
> > one
> >                     is rather
> >                     sneaky)
> > 
> >                     How likely is it that Scott and Jim's grant is going 
> > to
> >                     fund the QA
> >                     work? If not likely, then I think that's the last big 
> > thing
> >                     I'd put in
> >                     1.0.0 because if we don't, I don't know where else 
> > we'll
> >                     get the money
> >                     for it.
> > 
> >                     I'll push on the documentation component to try and 
> > make
> >                     that more 1.0
> >                     suitable. Arlen, how many UI changes are you planning 
> > for
> >                     0.9.4?
> >                     Should I wait for it to be tagged and the demo server
> >                     updated before I
> >                     start taking new screenshots?
> > 
> >                     -Heather
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> >