Closed (fixed)
Project:
OpenChurch
Version:
8.x-2.0-rc1
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2016 at 02:37 UTC
Updated:
19 Jun 2017 at 02:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
drupalninja99 commentedIn retrospect I should have probably just used fields as my row display so that I could use the group by field. I might have to refactor the view to do that. The problem is that I am supposed to sort by the staff type term weight but that is not working properly.
Comment #3
cyberhiker commentedI went into the taxonomy for the staff type and edited the weights. It seemed to take a couple of edits before the changes took. Once that was done the Staff Directory now sorts correctly - the sort criteria reads as:
(field_staff_type: Taxonomy term) Taxonomy term: Weight (asc)
Content: Title (asc)
Comment #4
LaconiaSDA commentedI'm not sure if what we're talking about here is the same issue I'm experiencing or not. When I enter staff members, and several are entered as the same "Staff Type", (i.e. "Administrative Staff"), for some reason, it will put a couple of them together under one heading, and then go to a different heading, and then it'll do another one or two... (see attachment). I'm not understanding why it won't just put all of the "Administrative Staff" together. Am I doing something wrong? Is there a bug here? Please advise how to proceed.
Comment #5
JonM commentedI installed Entityqueue to allow me to do a custom sort order for the staff and vestry directory. Change the sort order in the view to Entityqueue content queue position and customize the order to your heart's content. I also created a queue for the homepage rotator to make managing those photos easier.
Comment #6
LaconiaSDA commentedI went in to change the view, as JonM suggests, when I realized what the issue is. I'm not sure why, based on what I'm seeing of the view, but what it is doing, is it is simply alphabetizing by name. So if I have Albert Jones, Susan Adams and Kevin Walker as one category, and Donald Smith, Edward Wilson and Ellen James as another, it is simply taking this and displaying it as
Albert Jones
Donald Smith
Edward Wilson
Ellen James
Kevin Walker
Susan Adams
and then it breaks them out showing their category, which is why I've got such an odd breakup of Administrative Staff.
The view shows it should be sorting by "(field_staff_type: Taxonomy term) Taxonomy term: Weight (asc)", and then by "Content: Title (asc)" however clearly it is just sorting by name.
Comment #7
LaconiaSDA commentedI also don't get why in some instances it will take a couple of names and put them together under the "Administrative Staff" heading, and in other cases, it just lists one name, then repeats the "Administrative Staff" heading and one name, then again repeats the heading and one name, etc.
Comment #8
JonM commentedMy issue was based on how I set up my rector's taxonomy, who is technically part of the Vestry, it would list a heading for Vestry, then Rector, then Vestry again. By making a new entityqueue (like nodequeues from pre drupal 8), I put him first, then the vestry hand sorted into last name order after that. So if you have multiples of staff with taxonomy titles, like secretary or whatever, it likes to repeat things in the sql depending on those titles. I didn't feel like fixing underlying code by adding last names to sort on, or changing how it grouped when the entityqueue fixed it and wouldn't be broken on updates if the code wasn't accepted.
So if you have installed entityqueue, go to structure, entityqueue, create one for your staff, add them to the queue and sort as desired, then as I said, in Sort Position, click Add, change type to entityqueue, add the content queue position item and choose ascending or descending.
Comment #9
LaconiaSDA commentedI'll give that a try, Jon. Thanks!
Comment #10
Virginian commentedWhen I entered my staff, I noticed that if the same staff person has more than one position, it would break them up like this as well. Only the first position was displayed, and twice (or more). I got around it by entering the person more than one time, once for each position. Since our Staff members do not correlate with our "Users", nothing was affected by having duplicates.
I gave up on preserving Views to allow for easy updates, so I could move on with production. There were just too many changes needed to function adequately for our needs.
The results of my Staff Directory are here.
Comment #11
drupalninja99 commentedThe plan here is to refactor the View to use fields but still render the teaser as a field. Some *modest* refactoring and I should be able to get this working. The issue will be updating existing installs.
Comment #13
drupalninja99 commentedThis is fixed now with the last commit. I had to make a few changes to the view and Twig template.