CommentFileSizeAuthor
#7 p6UO6yKl.png.jpg29.73 KBphelix
#7 Ekq2f3o.png52.06 KBphelix
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Manuel Garcia’s picture

Status: Active » Postponed (maintainer needs more info)

I need more info to duplicate this.

Manuel Garcia’s picture

Status: Postponed (maintainer needs more info) » Fixed

I think i know now where this could be coming from. The problem was how we were adding the js and producing the variables if field grouping was enabled. I've moved all this to the render() function, and this now looks to be working properly, at least as far as I've tested. I made a commit with these changes, and will be releasing the beta2 in a bit.

Anonymous’s picture

Hi

Is there a possibility of having the grouping work differently? I'm trying to list all team names within a province (node: title) within an accordion fold which displays the province (cck field: province) only as the header/drop-link.

Using beta2, it groups the provinces and shows each one of the teams in their own accordion fold. The province is shown, but shown once for each team name, so I'm getting:

Ontario
> Team A

Alberta
> Team B
Alberta
> Team C
Alberta
> Team D

Manitoba
> Team E
Manitoba
> Team F

I've tried with arguments, but then it does not display the accordion quite the same. Infact, they are just links with numbers beside (item count) and does not have an accordion (but I sense the grouping has worked with this result, but accordion has not rendered)

But I like the way this view has been written and so far so good... and it helped me to make sense of views and blocks.

thnx =)

Manuel Garcia’s picture

I'm not sure I understand what you are trying to do there Careless... though if you think the grouping should function differently, please open a new feature request with as much info as you can, screenshots if possible, so that I understand what is being proposed :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

phelix’s picture

Version: 6.x-1.x-dev » 7.x-1.x-dev
Issue summary: View changes
Priority: Normal » Major
Status: Closed (fixed) » Active
Issue tags: +taxonomy term, +relationship, +parent

Only local images are allowed.
I am having the exact same issue. If I change the style to either HTML List or Grid they are grouped by the parent and all the items show properly below. This is organized properly but the accordion is applying the style to the items under the parent. I am trying to get this accordion to have that affect to the parent item above in blue and then have the children underneath when the accordion is open. Here is how it looks if I just change to HTML LIST and group by parent. Only local images are allowed.
I can not for the life of me figure out how to get this accordion to apply to the top parent item instead of the children below. Does this make sense?

phelix’s picture

FileSize
52.06 KB
29.73 KB

Sorry for re-posting but my images didn't come through.

Current Result
I am having the exact same issue. If I change the style to either HTML List or Grid they are grouped by the parent and all the items show properly below. This is organized properly but the accordion is applying the style to the items under the parent. I am trying to get this accordion to have that affect to the parent item above in blue and then have the children underneath when the accordion is open. Here is how it looks if I just change to HTML LIST and group by parent. With HTML LIST

I can not for the life of me figure out how to get this accordion to apply to the top parent item instead of the children below. Does this make sense?

bcobin’s picture

Same issue here. Any ideas? Thanks...

Manuel Garcia’s picture

Status: Active » Needs review
Related issues: +#2178101: Multiple / embedded view accordions don't work

Ive committed a patch that might help out with what you guys are trying to do here, please see #2178101: Multiple / embedded view accordions don't work

Manuel Garcia’s picture

Status: Needs review » Fixed

Assuming this is no longer an issue due to the lack in response.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.