http://drupal.org/project/viewreference (outdated only has d7 release) http://drupal.org/project/viewsreference perhaps joining forces makes sense.
http://drupal.org/project/viewreference (outdated only has d7 release) http://drupal.org/project/viewsreference perhaps joining forces makes sense.
Comments
Comment #1
sunI wasn't aware of that module. Indeed looks fairly similar.
Comment #2
keithm commentedI was aware of it. While there are some similarities, there are some significant usage differences too. One of the biggest is that viewreference uses literal values or PHP code rather than tokens to produce Views arguments. As I recall I don't think it supports the viewfield force_default concept either.
Comment #3
nancydruNor was I until a few minutes ago. But if you can join forces, perhaps the combination would also be a good candidate for the References module.
Comment #4
Dret commentedI agree with Nancy,
Could be very useful to have a page with a comparing grid between:
Comment #5
megachrizAn other similar module: EVA: Entity Views Attachment
Comment #6
danielb commentedThere are also these related modules you could mention if doing a grid
http://drupal.org/project/insert_view - This is not a field module, but rather allows you to use [macros] in body content and blocks to output the view.
http://drupal.org/project/embed_views - Provides a Views display plugin to create views output that works more cleanly with embeded views.
Comment #7
klonosHaving a single module with a consolidated user base and more maintainers is always a good idea. It will confuse people less as to which module to choose.
Personally I went with EVA: Entity Views Attachment, but it would be great if all these modules came to be a single one and all users slowly migrated to "the one to rule them all" ;)
PS: I've just filed #2042619: Allow EVA Fields to be created and reused from content type edit -> "Manage fields" tab. against EVA which will make it include the functionality/behavior or both Viewfield and View Reference, but I don't know whether the maintainer has the time or energy to implement it. If the maintainers of the other two modules tagged along, they could help in that area ;)
PS: cross-posting in #2042655: Join forces with the Viewfield project.
Comment #8
steinmb commentedNot much movement here. Anyone talked? Many drupalcon have passed since this first was posted.
Comment #9
sinasalek commentedVery confusing indeed, it took me a while to finally pick one. All these modules are quite similar. At least a note on the each module's page pointing out similarities and link to the other module can be quite helpful
Comment #10
danielb commentedI think for Drupal 8 I will make View Reference depend on ViewField, and attach View Reference specific functionality to it. If the code is small enough perhaps that would be open the door to roll the features into ViewField ?
Comment #11
jerdavisComment #12
anruetherThe View reference (viewreference) does not have a d8 release, the Views Reference Field (viewsreference) has and it is very popular. Although maintainers do not seem to be very active. Still viewfield might join in there: https://www.drupal.org/project/viewsreference
Meanwhile another module makes it possible to reference a view from a field: [Entity Extra Field | Drupal.org](https://www.drupal.org/project/entity_extra_field)
Comment #13
anruetherComment #14
gambryWith the latest contribution credit tune-up, joining forces among modules is encouraged as credit score is not bundled with modules usage/popularity.
Comment #15
colanI reopened the related issue in the other project as a documentation task.
Let's do the same over there. While this is a longer-term project, could we at least add a Similar Modules section to the project page here, listing Views Reference Field explaining any differences? Thanks! (Otherwise, folks need to dig through all of these issues to figure out which one to pick.)
Adding a link to this issue would be great too.
Comment #16
jasonawantI've done a cursory comparison, and posted at https://www.drupal.org/project/viewsreference/issues/2890949#comment-133....
Comment #17
gambryAlthough I like more the code on this module, Views Reference Field plugin system is really promising and flexible.
I've been working on #3004636: Add View filter plugin to improve experience for content editor which with few lines of code will make the module even more flexible, allowing site-builder to pre-filter the views.
Please consider to join.
Comment #18
jasonawantAgreed, #3004636: Add View filter plugin to improve experience for content editor will provide a lot of flexibility for the Views Reference field module.
Is there an upgrade path from Viewfield 7.x to 8.x version?
#2996881: Migrate from D7 viewfield provides a patch to migrate from Viewfield 7.x to Views Reference field, but hasn't been reviewed.
Comment #19
jerdavisRight now my plan is to finish troubleshooting the remaining blocking issue and provide a stable release for Viewfield. I currently have no plans to work on a merge/migration to Viewsreference. If Views Reference wants to support that migration path for folks on Viewfield for 7.x or 6.x, I certainly support giving folks options.
Other than some issues with entity updates following some of the feature patches that have been merged, the 8.x stream of Viewfield is quite stable at this point and we now have a start on tests.
Comment #20
jasonawantThanks for the input! I'll mark this as postponed for now.
Comment #21
colanThere's also Views Field View. Perhaps a new entry for these at
Comparison of contributed modulesModules that embed views in fields is in order?Edit: I created a placeholder for the D8 version of that doc page.
Comment #22
colanLet's fill in that doc page, and then link to it from the project page here. The other modules should do that as well.