[[TaggerGetTags? &groups=`1` &resources=`[[*id]]` &rowTpl=`tagName` &toPlaceholder=`taglist` &separator=`,`]]
[[!getResources?
&parents=`[[%guidelines.id? &namespace=`mylex`]],[[%KB.id? &namespace=`mylex`]],[[%news.id? &namespace=`mylex`]]`
&tpl=`related-bottom-list`
&depth=`0`
&showHidden=`1`
&limit=`8`
&sortby=`{"publishedon":"DESC","createdon":"DESC"}`
&includeContent=`1`
&includeTVs=`1`
&includeTVList=`Img`
&where=`[[!TaggerGetResourcesWhere? &tags=`[[+taglist]]` &likeComparison=`1` ]]`
]]
This question has been answered by smg6511v2. See the first response.
This may have been long-ago solved by this user but, after having run into the same issue, I have the solution to share:
The trouble stems from the fact that there is an undocumented property within the TaggerGetResourcesWhere snippet ("tagField") which is set to "alias" by default. Intuitively, at least for myself and the above user, when generating a [[+taglist]] with the TaggerGetTags call, one would use the [[+tag]] placeholder in their rowTpl (and not [[+alias]]). When the tag is just one word this doesn't matter (unless for some reason you explicitly set a tag's alias to something other than its name), as matching in sql is normally non case sensitive. But multi-word tags such as "Global Economy" would have an alias of "global-economy," thus the mismatch.
Bottom line: Either use [[+alias]] in your TaggerGetTags rowTpl, or set the "tagField" property in your TaggerGetResourcesWhere call to "tag." Arguably the former solution is probably best, as the alias is stripped of spaces and special characters that could potentially muddy up a search.