Hello,
I have moved over to views 3 and was wondering if HS needs any changes to support it and will support it?
Many other modules have been making changes over the past months.
content profile #670092: Content Profile Views 3 integration
cck #670344: Make CCK compatible with both, views 2 and views 3
flag #673508: Use option_definition to support both views 2 and views 3 integration
Thanks!
Comments
Comment #1
wim leersWow that patch is INCREDIBLY simple. Let's hope it'll be equally easy for HS … I'll roll a patch soon that you can test.
Comment #2
wim leersHS Taxonomy Views apparently doesn't use options(), so that's one thing we don't have to change.
Are there any other API changes? It'd be awesome if Views 3 support didn't require any code changes at all! :)
Could you look into that? Thanks!
Comment #3
robby.smith commentedRouting to Views queue to see if any further changes need to be made to HS besides options() for Views 3 support.
Thanks!
Comment #4
dawehnerThere are some changes you perhaps have to do:
I suggest to try it out, and see whats happening.
Comment #5
robby.smith commentedThe above info was provided by one of the maintainers of Views.
Maybe HS doesn't need much changed to support Views 3?
Comment #6
wim leersI'm not using options, nor am I using $display->get_foo_plugin.
Hence I guess it should work. Just try it? :)
Comment #7
wim leersComment #8
Bilmar commented#721774: HS Taxonomy Views + Views 3 + taxonomy term filter: You have an error in your SQL syntax warning message began to show with HS + Views 3. I have included details, screengrab and a screencast at that post.
Regards
Comment #9
wim leersThanks for the notification! Replied.
Comment #10
wim leersLet's continue in #721774: HS Taxonomy Views + Views 3 + taxonomy term filter: You have an error in your SQL syntax. Also note that #714530: Views 3 compatibility has been fixed.