Logging the click data

[Vivek Pal]

> The only thing you cannot do is to change the HTTP status code, so you'll
> need a new omegascript command for that. (You could probably have
> $httpredirect{URL}, avoiding having to have a separate $httpheader{}.)

There's ShellExecute function which can potentially be used for the
implementation of $httpredirect command but it'll only work on Windows.
Although, I'm not aware of anything reliable similar to ShellExecute for
UNIX based system.

I was wondering if it would be better to use a meta tag for redirection
like so? <meta http-equiv="refresh" content="0.1;url=$cgi{URL}">

I have updated the clicklog template [1] with what I have locally now.

I was also wondering if there's a faster way of checking that the new
log command works along with other changes than actually installing
the Omega (system wide) from the branch I'm corrently working on? I
tried doing that but messed up already running omega installation and
had to spent almost whole yesterday just to get it back in working
condition.

Also, it would be great if you could just take a quick look at the git
diff output [2] and let me know if anything needs work. I'm currently
working on writing a preprocessing script in python and will open a
PR soon after that's done. clicklog template might be missing in the
output but can be found at [1].

[1] https://gist.github.com/ivmarkp/374fc8781d3789b0522713a79416edc8
[2] https://gist.github.com/ivmarkp/46f71c445e2fcb81fa6e1a5cb2273186

Thanks,
Vivek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20170617/5b6b9cd5/attachment.html>