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.
What are the plans for bringing Views Table Group to Drupal 7?
Comment | File | Size | Author |
---|---|---|---|
#14 | tablegroup-1135500-14.patch | 4.2 KB | yannickoo |
#12 | tablegroup-1135500-12.patch | 4.2 KB | antiorario |
#11 | tablegroup-d7_port-1135500-11.patch | 3.96 KB | yannickoo |
#4 | d7_port_1135500.patch | 8.04 KB | Blackice2999 |
Comments
Comment #1
acolyte26 CreditAttribution: acolyte26 commentedI would also really love to have this ported to Drupal 7. If anyone knows of other similar modules, please let me know.
Comment #2
gmak CreditAttribution: gmak commentedMe too
Comment #3
Blackice2999 CreditAttribution: Blackice2999 commentedworking on it. patch will follow
Comment #4
Blackice2999 CreditAttribution: Blackice2999 commentedplease try this patch
Comment #5
becw CreditAttribution: becw commentedThanks! I guess I should check this out :)
Comment #6
cutmedia CreditAttribution: cutmedia commentedworking on Views 3, D7.7.
Comment #7
acolyte26 CreditAttribution: acolyte26 commentedThe patch works but I am receiving some errors: the error is as follows:
Comment #8
kaizerking CreditAttribution: kaizerking commentedIs there any update on this patch? s it working?
Comment #9
FranckV CreditAttribution: FranckV commentedFirst of all thank you for this simple yet very powerful module. It solved a very "common" problem : showing a timeline.
What is the status with regards to porting this functionality to Drupal 7 ? Any clue how to do the same on D 7 ?
Comment #10
pmusaraj CreditAttribution: pmusaraj commentedI tried the patch and it is working well.
When patching, it failed to modify the .info file, likely because it requires the site to be in a git repo.
Comment #11
yannickooI cloned the git repo and manually customized the code due the patch from #4 and recreated a patch. Blackice2999 did customize the code in a non-drupal-way.
Comment #12
antiorario CreditAttribution: antiorario commented#11 had a bunch of errors in the code (wrong closing brackets, one missing semicolon), and in tablegroup.module the function theme_tablegroup_item() wasn't producing content because it was using $item instead of $variables['item']. I also added an existence check for cell content around line 120 of tablegroup_plugin_style_tablegroup.inc, otherwise previously undeclared cells would throw an error.
The patch will fail for the .info file—this is completely normal. The .info file contained in the git repo is different from the one packaged to be downloaded from drupal.org, so it should be edited manually to contain only the following lines:
Comment #13
yannickoo...or you clone the git repo then you have no errors. You always should use
git apply
instead ofpatch < [patch]
. I missed the part with the$items
instead of$variables['items']
, sorry. Thank you!Comment #14
yannickooFeels like patch battle, you have a whitespace so I updated the patch, sorry.
Comment #15
yannickooI tested this and it works fine so I set the status to RTBC. I message becw, the maintainer now for a Drupal 7 version.
Comment #16
antiorario CreditAttribution: antiorario commentedYou're right about the patch and using git. It's just that not everyone might be using git, so I was going for something that would help those who don't.
Patch battle is good, it keeps things going.
Comment #17
yannickooSo here is quick introduction how to apply the patch. RTFM guys ;)
And when you are a windows user you have to download the patch patch and put it manually into the tablegroup directory.
I sent a message to becw, I hope he'll answer fast.
Comment #18
antiorario CreditAttribution: antiorario commentedAny news?
Comment #19
tchurch CreditAttribution: tchurch commentedI've used the instructions laid out in #17 and the Drupal 7 works great but I have a problem.
As there isn't yet a Version 7.x to report it on, I thought I'd mention it here.
I have a view using Taxonomy terms for the column and row (both attached to the node).
I want the order of the rows and columns to be by their weights but I can't get it to work for both.
If I use the Row and Column sorts, it's not in the correct order.
If I add sort criteria for one or both columns, only one of them is correct.
Can someone check this? Is it something that can easily be fixed?
I never tried the 6.x version as my site is 7.x anyway.
Thanks.
Comment #20
antiorario CreditAttribution: antiorario commentedI had a similar problem to yours, and I solved it with a template function overriding template_preprocess_tablegroup_view_tablegroup(), in which I've forced the sorting of the table according to my own criteria, and regenerated the table itself. It's messy, and probably adds some overhead, but it's the only solution that didn't involve changing the module.
Comment #21
tchurch CreditAttribution: tchurch commentedI'm not that familiar with this module to be able to write a function. Can you offer any help? An example function maybe? Otherwise I'll wait for someone to finish updating the v7 module.
Also, once the maintainer(s) of the module have created a v7 branch, then we can start opening proper issues for it.
Comment #22
yannickooI asked to maintain this module so we can bring this module forward.
Comment #23
yannickooSay hello to Views Table Group 7.x so that we can finally close this issue. Feel free to report new issues for the 7.x version.