My basic goal: create a panel page for taxonomy terms from a specific vocabulary (in this case, "Sports" is the vocabulary). This page displays, among other term-related panes, one "featured" article (includes thumbnail & teaser) and the five most recent "non-featured" articles (headline only).

Here's what I did:

  1. I created a "taxonomy smartqueue" that operates on the Sports vocabulary and has a queue length of one. If I add an article to the "Featured Football Articles" queueu, it kicks out the previously-featured Football article
  2. I created a View that takes an argument of Taxonomy:term, and has a relationship to the above nodequeue, without requiring it (to allow "non-featured" nodes into the view)
  3. For the Featured article, I created a block display that filters by Nodequeue: In Queue, and selected "True", then added the appropriate fields, filters, etc.
  4. For the "non-featured" articles, I created a pane display [the reason I chose Pane and not Block is that I needed a custom "more" link, and Block was not passing it through to the Panels pane]; filtered by Nodequeue: In Queue, and selected "False", then added the appropriate fields, filters, etc.
  5. Next I enabled the "Taxonomy term template" page that ships with Panels, and added a variant called "Sport Main Page." Under "Selection Rules" I added "Term being viewed vocabulary is 'Sports'." I retained the default contexts of "Argument 1, Term being viewed," and "Argument 2, Depth"
  6. I successfully added the "Featured Article" block to a content pane
  7. When I tried to add the "Non-Featured Articles" Views pane, it was not available in the "View panes" bucket. [It was available in Views, but again, the custom "more" link that I needed from the view did not come through, which is why I wanted to get it from "View panes"]. This remained true even after I went back to the View and tried a number of different argument inputs for the "Non-Featured Articles" pane

What am I missing here?

(I left out the full history of this issue, for simplicity's sake, but it's worth mentioning: the reason I know that the custom "more" link comes through when I use the pane is that the first time I tried this, it actually worked - EXCEPT the pane was not responding to the taxonomy context. It was at that point that I discovered and started playing with the "Argument input" field in the Views pane display, and it hasn't showed up in the Panels content "View panes" bucket since then - even when I reset the "Argument input" to "No argument.")

Any insight is gratefully appreciated.

[I also posted this as a reply to another issue - please forgive the double-dipping, but I want to increase my chances of getting a useful response]

Comments

merlinofchaos’s picture

merlinofchaos commented

Can you export the view and paste it? That'll make it easier to diagnose why it is not showing up.

merlinofchaos’s picture

merlinofchaos commented

One other comment; if you had the edit content page open with changes in it before you made the view, you may need to go ahead and update the content page. The available content is cached while changes are being made. This is kind of annoying but it is a significant performance boost.

dalehgeist’s picture

dalehgeist commented
Status: Active » Closed (fixed)

Thanks for your response. Without having done anything differently, as far as I know, I am now getting a different result. Now the "Non-featured Articles" View pane is available to the Panel page, and it displays correctly. In other words, problem fixed.

I spent quite a while troubleshooting this before making my initial posting: I tried all the options for the View pane's argument input, I tried changing the view argument from "term:name" to "term:ID" and back, I cleared caches, etc.; none of which resulted in being able to see the view pane in the "Add content" UI. Then I left it alone for four days, and looked again: there it was.

(I am also 99% certain that during this process, I updated the edit content page, too.)

Thanks for your time, MOC: closed. Thanks for the terrific modules and support.

tahani’s picture

tahani commented

I had the same experience -- the views stuff suddenly and mysteriously becoming available. And I was quite sure I'd saved and reentered the panel editing page several times while trying to get the views panes to appear. After reading this, I thought I'd try clearing the cache (at the bottom of admin/settings/performance). That did it.

oteno’s picture

oteno commented

same problem - find the solution in disabling/enabling the variant

gthing’s picture

gthing commented
Category: support » bug

I had to enable the "Custom Content Panes" module, then remove the pane from my view and re-add it before it would show up.

Seems like this should be a bug - it shouldn't allow you to create a content pane in views if that module is not enabled.

djh007’s picture

djh007 commented

I had the same problem.

The Views Panes were available to other Panels, just not node templates.

After trying all kinds of stuff, from building new panes, templates, creating new Views, removing contexts etc, I found that simply SAVING the Node Template was the solution. After pressing Update and Save on the Panel page, the missing Views Panes were suddenly available. Hope this helps someone...

brad.curnow’s picture

brad.curnow commented

Just a note to anyone having similar issues who finds this page - I broke my views/panels panes access for a particular view by CLONING an existing pane in that view.

Starting a new pane seemed to fix it, so I won't be cloning panes any more :)

brad.curnow’s picture

brad.curnow commented

Turns out I had to turn off the argument in "Argument input" under Pane settings to bring them back as well.

saltednut’s picture

saltednut
she/her
Primary language English
Location Chicago
commented

I was using User: User ID as a required context under 'Argument Input' - at first I could not see the Context pane under 'Views panes' when I tried to add it.

Turning off arguments or making the argument optional enabled the Content pane in the listings but I was still unable to set logged-in user as context.

I then realized - of course: this was because No Context was available. Once I set up the proper Context for the panels variant, I was able to see the Content pane and set it up correctly.

So it would seem that if the context isn't available for a Views pane, then it won't show up on the list. Makes sense... and seems strange, but not a bug.

pinin4fjords’s picture

pinin4fjords commented

+ 1 for a save on the node template- turned out that was the cause of this problem for me.

lucaspretti’s picture

lucaspretti commented

+ 1 for a save on the node template- turned out that was the cause of this problem for me as well

joshua.boltz’s picture

joshua.boltz commented

+ 1 for the comment in #9.

hollyfox’s picture

hollyfox commented

I have had this issue since I began developing back in 2013 with panels. It seems it is a bug and many times it relates to one of the displays having issues with accessible content or something. This time, I noticed that view panes that were disabled showed up as being able to be added. So, I disabled the view pane I was adding, added it and re-enabled it. Worked like a charm. Not sure if it works every time, but it's worth a try.

candelas’s picture

candelas commented

Thanks @djh007 saving the Node Template made panes available :)