Quote from: donquicky at Feb 20, 2017, 01:47 PMHi clutchmarketing,
That is a little complicated. Tagger stores its data in custom tables like modx_tagger_groups, modx_tagger_tags en modx_tagger_tag_resources.
So you have to point SimpleSearch to search in these tables.
Like this example for searching the tables used by Quip
&customPackages=`QuipComment:body:quip:{core_path}components/quip/model/:QuipComment.resource = modResource.id`
See documentation on https://docs.modx.com/extras/revo/simplesearch/simplesearch.simplesearch
Does it means it is possible to use directly an existing installed package (e.g. Quip or Tagger) ?
I'm trying this :
Tagger
className ->
TaggerTagResource | taggergroup | taggergateway | tagger | taggertag
Tagger tables :
modx_tagger_groups
modx_tagger_tags
modx_tagger_tag_resources
Should we use TaggerTagResource class ?
Field → tag
packageName → tagger
packagePath → {core_path}components/tagger/model/
joinCriteria → tagger.resource = modResource.id (?)
Test 1
TaggerTagResource:tag:tagger:{core_path}components/tagger/model/:TaggerTagResource.resource = modResource.id
-> without success (I used the Tagger tag ID as search criteria in simpleSearch field) :-/
Anyway even with the Quip exemple it doesn't work : in MODX log I have :
(
[0] => 42S02
[1] => 1146
[2] => Table 'tableName.QuipComment' doesn't exist
)
[ed. note: johnxx last edited this post 6 years, 2 months ago.]