-
ATFolder: no special adapter needed, works like a charm.
Global setting: pretty much needed now. It makes sense for the reason that Balasz mentions: the combination scenario. The alternative is to customize a couple of plone search queries to include the parameter. *If* you want it, you pretty much want it always. Well, a monkeypatch works :-)
We don't know the exact reason for having that...
2007-03-18 18:24:57 UTC in TextIndexNG
-
Andreas, you can close this issue. Txng worked just fine, apart from something that should be better documented. Only when I noticed that I always got 50 results max, I started grepping in the code and found the maxhits parameter that is used when ranking is enabled. Only then did I also find the notice about it in the documentation.
Could you add an extra paragraph in the documentation?...
2007-03-14 16:58:48 UTC in TextIndexNG
-
Found the problem: I *did* manage to find the object when I deleted most of the rest of the content in the site. Only then did I start looking at possible cut-offs and found the ranking_maxhits setting that is fixed at 50. A quick try using the "test" tab turned out that the object I was searching for as a test was number 54 in the list. Sigh.
2007-03-14 01:36:35 UTC in TextIndexNG
-
I know this is a bit of a "soft" bug report, so a pointer to dig further would already be very welcome.
Plone 2.5.2, zope 2.9.6, txng 3.1.14
There is one specific custom contenttype (quite simple subclass of ATFolder) that cannot be found by plone's search mechanism (either livesearch or advanced search).
If I look at the index and metadata data for a specific object, everything looks...
2007-03-13 16:08:13 UTC in TextIndexNG
-
When recataloging, I get the following error for apparently all contenttypes. Plone 2.5.2, zope 2.9.6, txng3 3.2
2007-03-13 16:46:42 ERROR txng extract_content failed (philips/documentation/only-for-it/something.doc)
Traceback (most recent call last):
File "/Users/reinout/instances/pict/Products/TextIndexNG3/src/textindexng/index.py", line 114, in index_object...
2007-03-13 15:55:26 UTC in TextIndexNG
-
Logged In: YES
user_id=149963
Is this especially the case when using it in two plone
portals inside one zope instance? Or is it just a problem
with the second PFM?
It doesn't ring a bell for me. Might the page template (when
editing the form: schemate "template") perhaps be faulty?
Could you resubmit this bug to
plone.org/products/ploneformmailer/issues?.
2005-12-16 22:42:25 UTC in The Plone Collective
-
Logged In: YES
user_id=149963
It works in the current version (0.3 beta). please resubmit
to plone.org/products/ploneformmailer/issues if the problem
remains for you.
2005-12-16 22:35:19 UTC in The Plone Collective
-
Logged In: YES
user_id=149963
I've just tried it locally with an anonymous user and the
latest svn and it seems to work OK. It is probably fixed by
some of the latest fixes. If it still doesn't work, please
resubmit to plone.org/products/ploneformmailer/issues.
2005-12-16 22:30:40 UTC in The Plone Collective
-
Logged In: YES
user_id=149963
Yes, there was a bug regarding this. It's fixed in the
current beta version (0.3 beta, click "show all releases" in
plone.org/products/ploneformmailer).
2005-12-16 21:54:28 UTC in The Plone Collective
-
Logged In: YES
user_id=149963
I can install it just fine in multiple plone sites. This
looks decidedly as a more low-level zope setup problem. I'm
closing the bug here, please re-submit to the bugtracker at
plone.org/products/ploneformmailer if the problem still
persists.
2005-12-16 21:52:01 UTC in The Plone Collective
