Opened 10 years ago
Closed 10 years ago
#659 closed defect (fixed)
stopwords in php not detected
Reported by: | Jan Mienert | Owned by: | Olly Betts |
---|---|---|---|
Priority: | normal | Milestone: | 1.2.19 |
Component: | Xapian-bindings (PHP) | Version: | 1.2.18 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Operating System: | All |
Description (last modified by )
includefile: (xapian.php): methods: set_stopper It looks like the stopper is always null. I've changed lines 2907, 3120 from "$this->_stopper=$stop=null;" to "$this->_stopper=$stop;" and the stopper works as expected. version: 1.2.18 - maybe not an 1.2.18-issue. I've updated from 1.2.7...
Change History (4)
comment:1 by , 10 years ago
Component: | Other → Xapian-bindings (PHP) |
---|
comment:2 by , 10 years ago
Description: | modified (diff) |
---|---|
Version: | → 1.2.17 |
comment:3 by , 10 years ago
Milestone: | → 1.3.2 |
---|---|
Status: | new → assigned |
Version: | 1.2.17 → 1.2.18 |
OK, I see the problem - this reference handling is added by post-processing the SWIG-generated wrapper, but the script which does this is dumbly picking up the default parameter value as well as the parameter name (which is where the =null
is coming from).
Shouldn't be hard to actually fix - will try shortly.
comment:4 by , 10 years ago
Milestone: | 1.3.2 → 1.2.19 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Which version is this with?