2014-06-19 18:17 GMT+02:00 Joe Mistachkin <sql...@mistachkin.com>:
>
> Baptiste Daroussin wrote:
>>
>> I have to repositories, all of which are served by the same version of
>> fossil (1.29 release)
>>
>
> The Fossil 1.29 release does not have the new "TH1 hooks" feature. It does
> have
> TH1 scripting, of course.
>
>>
>> On the second one uuid is not available at all but tkt_uuid has to be
>> used and when I do create a new ticket it fails saying "no such
>> variable: tkt_uuid"
>>
>
> I'm not sure what the precise cause of this error is; however, it may be
> that
> one of the ticket "templates" refers to it when it is not actually available
> (e.g. the ticket view page where there is no "tkt_uuid" column value
> available).
>
> --
> Joe Mistachkin
>
>To be extact I'm talking about admin>tickets/changes I do call that hooks
>because it is executed each time a user is creating/modifying a ticket :) (in
>url form /tktsetup_change)
verry basically here is the code:
----
query { select group_concat(ticketchng.login," ") as log from
ticketchng, ticket where ticket.tkt_id=ticketchng.tkt_id and
tkt_uuid=$uuid } {
set commenters "$log"
}
if {[string length $private_contact] == 0} { set private_contact anonymous }
http -asynchronous "http://127.0.0.1:8085/ticketwarn";
"\[$project_name: ticket\]
$title\n$commenters\n$private_contact\n$uuid\n$login\n$home\nTicket
modified by: $login\nChanges: $baseurl/tktview/$uuid\n\n"
return
----
I would expect here $uuid to be generic and always available? perhaps
I'm mistaking and when would be a reliable value that identify the
ticket that was modified/created?
regards,
Bapt
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
