Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi, thanks for the module.
I just tried the modules with views 3 instead of views 2, but could get it to work.
Is the module currently compatible with views 3, are there any plans?
Thanks
Comment | File | Size | Author |
---|---|---|---|
#10 | 1181566-v3compability.patch | 2.36 KB | dawehner |
#9 | 1181566-v3compability.patch | 1.36 KB | dawehner |
#6 | 1181566-v3compability.patch | 1.36 KB | dawehner |
Comments
Comment #1
fourmi4x CreditAttribution: fourmi4x commentedHi, I also can't get it to work with views 3... Is it normal? Any plans to make it compatible?
Comment #2
liland CreditAttribution: liland commentedi have same problem. Didnt work with view3. I have error:
user warning: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal if there is no GROUP BY clause query: SELECT node.title AS node_title, node.nid AS nid, node.language AS node_language, COUNT(node.nid) AS node_count FROM node node LEFT JOIN term_node term_node ON node.vid = term_node.vid WHERE (node.moderate = 0) AND (node.status = 1) AND (term_node.tid = 7) AND (node.nid != 23) ORDER BY node_count DESC LIMIT 0, 7 in /var/www/site.com/sites/all/modules/views/plugins/views_plugin_query_default.inc on line 1150.
Comment #3
funana CreditAttribution: funana commentedsame here. Views 3, not working. Block is not showing up.
Comment #4
fourmi4x CreditAttribution: fourmi4x commentedI got it to work with views 3 finally, with a quick (and probably very dirty) workaround : http://drupal.org/node/1014524#comment-4871192
Comment #5
dawehnerAssign for myself.
Comment #6
dawehnerHere is a patch
a) It uses the views3 api to add a COUNT(). This automatically adds the right group_by part
The resulting query is
b) For views2 it still uses the old code, because only views3 has proper groupby support.
Comment #7
Caseledde CreditAttribution: Caseledde commentedWorks. My bugs are gone.
Thank you dereine
Comment #8
R.Hendel CreditAttribution: R.Hendel commentedHmm. I am not sure...
When comparing terms of node with therms of nodes, selected by similar-by-terms, than there are exactly no terms corresponding.
Content of field "similarity" displays 0% similarity. There seems to be something wrong in method which selects nodes.
Comment #9
dawehnerMh due to whatever reason COUNT doens't work, you have to use count()
Comment #10
dawehnerThis patch fixes the display of the field similarity as well.
Comment #11
R.Hendel CreditAttribution: R.Hendel commentedI could not apply patch directly, but after copying changes manually in code everything works perfectly :-)
Thanks, dereine!
Comment #12
funana CreditAttribution: funana commentedconfirmed: http://drupal.org/node/1181566#comment-5240362 patch is working.
Had to uninstall, delete the view and reinstall the module though.
Danke!!
Comment #13
asb CreditAttribution: asb commentedThe patch from #10 applies cleanly and seems to fix the compatibility issues with Views3. A "Clear all caches" through 'admin_menu' seems to suffice vor my View.
Thank you, Daniel!
Comment #14
Dries ArnoldsI also tested this patch in #10 and it works fine. Only had to clear cache.
On my site the problem wasn't that it wasn't working, but that the view always gave only one result. That's solved now.
Comment #15
asb CreditAttribution: asb commentedWith the latest views-6.x-3.x-dev, smilarterms got hickups again. "Similar by term" blocks now show up on the weirdest places, including views pages (without a nid!). Also some links in "Similar by term" blocks point to strange targets (nid=1). I'll try to post more details if I find time to dig into this.
Comment #16
udvranto CreditAttribution: udvranto commentedDoes it work with the final version of Views 3.0?
Comment #17
asb CreditAttribution: asb commented@udvranto: Except for a number of other oddities of 'smilarterms' (that already existed in Views 2) it is working, as long as the patch is applied (#10).
Comment #18
chichilatte CreditAttribution: chichilatte commentedBrilliant thank you! This should probably be committed as a working views 3 version?
Comment #19
vishnu.kumar7 CreditAttribution: vishnu.kumar7 commentedHello Everyone,
Thanks for your help..We are using Views 3 with Similar terms 6x.-2.2.... I have also applied the patch mentioned on comment 10.... However Similar content block is only appearing for one node type despite of proper setting of the block...
We have two different node type (articles and blogs) and having the same taxonomy for these node type... while browsing nodes of blog type, we are getting similar content nodes (which include both article and blogs) however while browsing nodes of articles type, similar content block is missing...
similar terms block is only visible for one node type...
Anyone else faced such issue ?
Regards
Vishnu Kumar
Comment #20
vishnu.kumar7 CreditAttribution: vishnu.kumar7 commentedHello Team,
Would like to report following issue which I experienced while using SBT2 (tested all the versions) with Views 3.0.
Node 1 (Content type: Blog)
Vocab: Tags
Tags: Term A, Term B, Term C
Node 2 (Content type: Article)
Vocab: Tags
Tags: Term C, Term D, Term E
Node 3 (Content type: Blog)
Vocab:Tags
Tags: Term A, Term C
Viewing node 1: Similar terms block is appearing (node 2 and node 3)
Viewing node 2: Similar terms block is not appearing
Viewing node 3: Similar terms block is appearing (node 1 and node 2)
similar terms block is configured for both of the node type however block is not appearing while navigating to content type = article
When i passed nid of node 1 or 3 (type=blog) in the argument, I am getting a result but when i pass nid of node 2 (type=article) in the argument, no query is run....
Block/query is only appearing for content type=blog
Please include this issue in the compatibility list..
Note: I have not changed anything with the default view while testing this scenario. Patch also did not helped. It only fixed the problem block display only one result
I am returning back to SBT1 (1.8) until it gets resolved... let me know if you need more information from my end...
Regards
Vishnu Kumar
Comment #21
hachreak CreditAttribution: hachreak commented+1
When I upgraded the views module from 2 to 3, I had this problem: Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is illegal ......
The patch #1181566-10: Compatibility with views 3 seem to work for me! :)
When the patch can be integrated in the module?
Best,
hachreak
Comment #22
quicksketchThanks guys. Committed and pushed up to 6.x-2.x branch. This brings the module closer inline with the new 7.x-2.x branch too.