[rt-users] Captcha Extension on RT 4.0.2 fails to compile

2011-08-28 Thread Alex Rhys-Hurn
Hello everyone,I am trying to install the captcha extention on RT 4.0.2.I use these commands from the README file:  perl Makefile.PL
make
make installBut when I use the first command perl Makefile.PL I get the following output:

	RTIR 2.4 and newer needs RT 3.8.1 at least, you have 4.0.2 at Makefile.PL line 10, STDIN line 1.And then the second command make fails with:	make: *** No targets specified and no makefile found. Stop.According to the Best Practical RT Extensions page the extension is supposed to work with RT 4.xWhat am I doing wrong?Many thanks in advance.Alex-- Alex Rhys-Hurn | ITworX LimitedP.O. Box 1649, 00502, Karen, KenyaTel: +254 (0) 20 2444824 | Cell: +254 (0) 724 972541Web: www.itworx.co.ke
This e-mail contains confidential information or information belonging to ITworX Limited and is intended solely for the addressees. The opinions therein, explicit or implied, are solely those of the author and do not necessarily represent those of ITworX Limited as a company. The unauthorized disclosure, use, dissemination or copying (either Whole or partial) of this e-mail, or any information it contains, is prohibited. E-mails are susceptible to alteration and their integrity cannot be guaranteed. ITworX Limited shall not be liable for this e-mail if modified or falsified. If you are not the intended recipient of this e-mail, please delete it immediately from your system and notify the sender of the wrong delivery and the e-mail deletion.

RT Training Sessions (http://bestpractical.com/services/training.html)
*  Chicago, IL, USA — September 26  27, 2011
*  San Francisco, CA, USA — October 18  19, 2011
*  Washington DC, USA — October 31  November 1, 2011
*  Melbourne VIC, Australia — November 28  29, 2011
*  Barcelona, Spain — November 28  29, 2011

[rt-users] mysql sphinx

2011-08-28 Thread Arkadiusz Miskiewicz

Hi,

I'm going to setup full text search with mysql 5.5, sphinxse 2.1 and sphinxd 
0.9.9.

max_matches worries me, from docs:

Take, for example, the instance where Sphinx is configured to return a
   maximum of three results, and tickets 1, 2, 3, 4, and 5 contain the
   string target, but only ticket 5 is in status Open.  A search for
   Content LIKE 'target' AND Status = 'Open' may return no results,
   despite ticket 5 matching those criteria, as Sphinx will only return
   tickets 1, 2, and 3 as possible matches.


This means that sphinx will never ever return new matching tickets that are 
above max_matches :-/ Would be acceptable if it use max_matches counting down 
from latest one but this doc suggests it's count from first one.

I assume there is no solution for this other that use some huge number as 
max_matches?

-- 
Arkadiusz MiśkiewiczPLD/Linux Team
arekm / maven.plhttp://ftp.pld-linux.org/

RT Training Sessions (http://bestpractical.com/services/training.html)
*  Chicago, IL, USA  September 26  27, 2011
*  San Francisco, CA, USA  October 18  19, 2011
*  Washington DC, USA  October 31  November 1, 2011
*  Melbourne VIC, Australia  November 28  29, 2011
*  Barcelona, Spain  November 28  29, 2011

Re: [rt-users] mysql sphinx

2011-08-28 Thread Alex Vandiver
On Sun, 2011-08-28 at 13:49 +0200, Arkadiusz Miskiewicz wrote:
 I'm going to setup full text search with mysql 5.5, sphinxse 2.1 and sphinxd 
 0.9.9.
 [snip]
 This means that sphinx will never ever return new matching tickets that are 
 above max_matches :-/ Would be acceptable if it use max_matches counting down 
 from latest one but this doc suggests it's count from first one.

That is not quite what it means.  To make the limitation clearer, assume
there are 100,000 tickets in the database, and only five tickets contain
the word target (once each): ticket ids 3, 44, 555, , and 7.
If max_matches is set to 5, and the search is for Content LIKE
'target', all five tickets will be returned.  If max_matches is set to
3, only tickets 3, 44, and 555 will be returned.  That is, max_matches
need not be set to 100,000 to return results in tickets that high; it
should be set comfortably higher than the number of occurrences of the
words you expect to be searching for[*].

Given the same scenario, but with a query, of Content LIKE 'target' AND
Status = 'Open' and only ticket 7 in the Open status, a max_matches
of 5 would suffice to return that one result.  A max_matches of 3 would
return no results, as Sphinx would return only three results to RT (3,
44, and 555) which would then be filtered to only open tickets, which is
a null set.

Does that help to clarify the limitation?  To be sure, it is still an
irritating limitation, and one that i wish we could work around somehow.
Unfortunately, short of pushing more of the search parameters down into
sphinx, which would be a rather complicated piece of work, I see little
way around it.
 - Alex

[*] To complicate matters, this is technically the number of
_attachments_ matching the full-text criteria, not the number of
_tickets_.  That is, ticket 3 contained 500 emails, each of which
contained the word target, then (contrary to the above example)
max_matches would need to be 501 in order for the results to contain
more than just ticket id 3.


RT Training Sessions (http://bestpractical.com/services/training.html)
*  Chicago, IL, USA  September 26  27, 2011
*  San Francisco, CA, USA  October 18  19, 2011
*  Washington DC, USA  October 31  November 1, 2011
*  Melbourne VIC, Australia  November 28  29, 2011
*  Barcelona, Spain  November 28  29, 2011