Drupal 7 patch for Views attach

+1, subscribe

I'm not sure that I want to go there until Views has at least a tagged alpha for Drupal 7. At the moment I'm focusing on Views 2/3 for Drupal 6. So, um, I'll be back eventually. ;-)

If you want to offer a Drupal 6 Views 3 patch, that would be a great place to start.

subscribing.

Views has a tagged alpha now.

subscribing

subscribing

looks good. i have d7-alpha1 running with latest dev of views3. only issue i ran across is that you have to have the title set to show when it's a node_content display or you get an error about undefined title variable.
Error messageNotice: Undefined variable: title in include() (line 30 of /path_to_views_attach/views-attach-display-node-content-view.tpl.php).
once i changed that to yes, this goes away.

Crell, can we get your thoughts on at least rolling this in as an alpha of views_attach 7.x ?

Given that Views 3 for D7 is still highly volatile, and just recently had heavy API changes (requiring ctools), I'm still reluctant to commit a D7 branch that would have to be maintained as the API still changes.

Thanks for the update, and for your work. I'm mostly asking because this, views_slideshow and i18n are about all that is left of my drupal toolbox that doesn't yet have some wild and wooly 7.x branch to play with. I totally understand wanting to release the first branch after views for d7 stabilizes.

Subscribing.

subscribe

checking in.

Chiming in. Any news on the Drupal 7 status? Are currently building a site that I'm moving into D7 before taking it live but is relying heavily on views attach. If there not going to be a D7 release any other modules that provide similar functionality. I know I prob. could use panels to and just override the node and insert av view that way or perhaps pull it off by using the display suite. Any thoughts?

There will be a Drupal 7 version of this module. I just don't have a timeframe for it at the moment. :-( I definitely need to go through the issue queue first and flush out anything I can before doing the port so as to reduce duplicate effort.

The best way to help get a D7 port out faster, therefore, is for me to see lots of RTBC issues when I have time to get to them. :-) That would make me happy and the process faster and easier for everyone.

Subscribing

subscribe

subscribe

Subscribe

A brief update here, Eaton has been working on a D7 version of this module with a new name that is less confusing than "views attach" (which is not the same as attachment views). :-) It's not yet released, but that's the likely way forward here due to changes in the Field API. More information when it exists.

Thanks for the update Crell. Not sure if the name change is gonna help or hurt (it's a bad initial name with huge name recognition at this point). But sounds wonderful that it's getting a true D7 version soon.

subscribe

Subscribe.

subscribing

subscribe

subscribe

Sub.

subscribe

subscribe

subscribe

+1, subscribe

subscribe

Subscribe

subscribe

Hey by the way I use the patch at #2 and it's live on my D7 installation ! Could be a good start for people who would like to start DEV for views attach in D7.

And subscribing here to get updates on Eaton's secret project ;-)

Subscribe

Subscribe.

+++ views_attach.info	2 Mar 2010 22:43:49 -0000
@@ -1,7 +1,11 @@
+files[]=views_attach_plugin_display_node_content.inc
+files[]=views_attach_plugin_display_profile.inc
+files[]=views_attach.views.inc

files should contain only files that declare classes or interfaces

Powered by Dreditor.

Not true. All files should be declared in the files array; just because core only uses it for finding classes doesn't mean other modules won't have other uses for that data.

@Crell, I have heard it widely declared that files[] is now just for autoloading of classes. #915174: Remove unnecessary files[] declarations from core info files seemed to declare this... and all core files were scoured for files[] declarations that weren't classes.

I could easily be mistaken, but I think this late D7 change means that files[] is just for class loading.

Ugh! So nice of people to not notify me about that patch. I suspect I was the one that "shot down" the idea originally. I see no benchmarks in that issue that say it speeds anything up, but it does mean we now do not have a proper index of all Drupal files. That means, for instance, we couldn't realistically do a precompiler to concatenate files together (something that some have suggested to improve APC performance).

*expletive deleted* late-changes that aren't even bloody announced...

Irrelevant to this issue anyway, since as noted above views_attach is going to be supplanted by a renamed D7 module anyway. I'm tempted to close this issue but someone would just open a new one in its place. :-)

Subscribe

Unfortunately, the patch is still only partially ported to D7. I get errors on some pages and some things just don't work.

Case in point.... the hook_user() function is no longer in D7 because it has been split up into various hook_user_ functions. The hook_user_view() function, which looks like the best match for case 'view', doesn't have the $category variable which the module does use.... leaving it in limbo. So something will have to be done to figure out how to determine the category.

I'm just hacking at it myself, because I haven't worked with drupal code before 2 weeks ago. The code isn't particularly well commented and me being quite rusty with PHP... well, it doesn't help.

Is there a project page for the new D7 version of this module?

sub

@Crell Where can we go to to follow development of the new D7 module?

sub

Subscribe

subscribe

subscribing

subscribe

subscribe

subscribe

Subscribe

Subscribing

Subscribing

Subscribing

Subscribing

Subscribing.

Subscribing

I don't want to spoil the fun in this queue, but I did some nice things with http://drupal.org/project/viewreference

I can't speak for any of the others, but I need ViewsAttach not for ViewsAttach per se, but as a prerequisite for Views Gallery. Unfortunately, wonderful though ViewReference undoubtedly is, it's not a lot of help in that context.

Might be worth having a chat with the maintainer of that project, see if they'll consider a swap-over, but I'd be surprised, given that this and the other two not-yet-dev dependency modules appear to be closing on dev releases.

In that spirit, I use Views Attach for it's "node content" abilities, which allows me to embed a view into my Display Suite regions. (http://www.drupal.org/project/ds). Without it, a view has no "field" which DS needs, otherwise there's nothing to drag into my regions. Specifically this lets me pull in related fields from other content types using a node reference as an argument through views.

I tried the patch in #2 and it worked for me as far as Views was concerned and I could create my Node Content views, however they don't show up for me in DisplaySuite (there's no field/handle to drag) so I guess it's a limitation of the basic port.

ViewReference might solve my issue, just haven't spent time to investigate yet.

Subscribe

subscribe

Subscribe

@#65
There is a better alternative for your use case called viewreference(http://drupal.org/project/viewreference) that allows you to reference views the same way you would reference other nodes with nodereference and include them in your content. I use it all the time on my drupal 7 site & it works like a charm.

@lloydpearsoniv - in what way is that better than views attach? I see that the same result can be achieved, but I can't see how either one is better than the other.

Well for one...views reference does not require a patch to work with D7 & its alot more flexible.

View Reference is more flexible for sure. However, not everyone needs to be able to have the ability to select which views will be enabled for a piece of content. Additionally, say you already have content created on your site and you want to add some other views to it. You have to go back and save each piece of content so their view will get added in with view reference. They both have their places.

I'm going to try and look at it this week to see what needs to be done with the above patch to better work with Views (dunno how the dev version of views plays with the patch). Also, was there ever any update to what Jeff Eaton was working on?

Ack, double post.

I guess before I try anything, Crell has mentioned the module is being supplanted by a renamed module. What is the new name of the module and is working going on in there already? Would make more sense to pool people into one area...

Edit: it seems like eva is the new project? (http://drupal.org/project/eva)

Eva is the new project, yep.
To quote the initial commit message, Eva is the module "Formerly known as Views Attach. Now with more magic."

Yep, EVA is the Drupal 7 version of Views Attach. There will be no Views Attach Drupal 7 release. I've updated the project page accordingly, and am closing this issue.

This may be a strange question but how do you get a version 6 contrib to work in version 7.x? I assume you run the patch but also need to change the version in the info module to version 7 so the contrib loader does not complain? Has anyone got this to work and can anyone provide a development version of this contrib.

Henry: You don't. Drupal 6 modules need to be updated for Drupal 7 and have a D7 release. This module will never, ever have one because EVA (a new module) supplants it in Drupal 7.

What's EVA? Is it the D7 equivalent of View Attach?

It is - https://drupal.org/project/eva