Forum OpenACS Q&A: Re: Project Manager 1.0 Version Released

Collapse
7: Re: Project Manager 1.0 Version Released (response to 6)
Posted by Andrei Popov on 05/01/04 10:32 AM

This is the logger problem I have encountered:

Invalid switch: "-party_id"
    while executing
"logger::entry::new__arg_parser"
    (procedure "logger::entry::new" line 1)
    invoked from within
"logger::entry::new -entry_id $entry_id  -project_id $logger_project_id  -variable_id $variable_id  -value $value  -time_stamp $timestamp_ansi  -descri..."
    (procedure "pm::project::log_hours" line 18)
    invoked from within
"pm::project::log_hours  -entry_id $entry_id  -logger_project_id $project_id  -variable_id $variable_id  -value $value  -timestamp_ansi $time_stamp_ans..."
    invoked from within
"if { [string match [db_string check_if_exists "
        select 1
        from logger_entries
        where entry_id = :entry_id
    " -default "0"] "0"]} {

        pm::pr..."
    ("uplevel" body line 7)
......
Collapse
9: Re: Project Manager 1.0 Version Released (response to 7)
Posted by Jeff Davis on 05/01/04 11:33 AM
Andrei, you should definitely submit a bug to bug tracker for those things; there is a "Project Manager" component to book them against.
Collapse
8: Re: Project Manager 1.0 Version Released (response to 7)
Posted by Andrei Popov on 05/01/04 12:35 PM

Looks like 5.1 logger (or rather 1.0b3) has no -party_id switch for logger::entry::new proc. Naturally, removing the offending bit from pm::project::log_hours resolves the issue.

Collapse
10: Re: Project Manager 1.0 Version Released (response to 8)
Posted by Jade Rubick on 05/01/04 06:49 PM
I submitted a patch for logger that adds a party_id switch for logger::entry. I think removing that switch is okay (I believe it is unnecessary). I added it in for bulk import of hours, so that you could (for example) import hours from ACS, as we did.

Now that I have commit rights, I'll commit that patch, bump up logger a version, and require that for the install. Or I'll remove it from project-manager.

Thanks for finding this.

I'm doing development on Postgres 7.3, so I'm not sure if Randy's problem is coming from using a different Postgres or something else.