When teaching (yeah!) Drupal 7 and Views 3, we have repeatedly noticed how the 'node: published' filter doesn't show any value settings (yes/no). This does not always happen, and everything usually works well after saving the view.

I'm sad to say that I don't have any more information on this right now.

CommentFileSizeAuthor
#2 node published (missing options).png21.3 KBItangalo
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented

Perhaps a screenshot would perhaps help to understand the issue.

It's true, that such kind of issues are hard to reproduce.

Itangalo’s picture

Itangalo CreditAttribution: Itangalo commented
FileSize
node published (missing options).png21.3 KB

Screenshot attached. Trying to understand what's happening a bit more – hope to get back with information soon.

Itangalo’s picture

Itangalo CreditAttribution: Itangalo commented

Ok, I found a way to reproduce the bug:

* Create a new view (of nodes)
* Add filters Node: Published and Node: Type at the same time. Configure them, or just remove them while configuring them – doesn't matter.
* Add the Node: Published filter again. Now the options are missing.

The effect disappears when saving the view, but reappears if repeating the steps above in a previously saved view. It does not seem to appear if you add other filters two at a time, such as Node: Published and Node: Sticky.

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented

The problem is that views uses the ctools dependency system at the moment. This relies on the html id's of the fields.

Once you have done some ajax tasks this id's change, so it seems to be a problem there.
Not sure whether views or ctools is the problem.

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented

I made some fixes to the system that actually prevent the IDs from changing via ajax, and I thought these fixes went out in alpha1. It actually required fixes on both the views and ctools sides.

In CTools, I changed the dependent.js work to happen mostly in pre_render so that unrendered forms didn't muck up the dependency info. In Views, I actually unset the ajax IDs because none of it is actually helpful to Views' ajax. Will have to investigate, maybe more needs to be done.

Itangalo’s picture

Itangalo CreditAttribution: Itangalo commented

I just updated ctools to 1.x-dev, to double check, and the glitch is still there. Sorry. :-/

goldlilys’s picture

goldlilys CreditAttribution: goldlilys commented

Subscribing, installed a fresh D7 today and testing out views. This Node:published is not displaying yes/no button until I actually save the views first. Someone please fix this error. Thanks.

starsinmypockets’s picture

starsinmypockets CreditAttribution: starsinmypockets commented

Subscribing.

I'm experiencing the same behavior: no yes/no checkboxes are displaying in the node:published filter settings page.

ChristianP’s picture

ChristianP CreditAttribution: ChristianP commented

Subscribing as well. Experiencing the same problem.

yngens’s picture

yngens CreditAttribution: yngens commented

ditto. subscribing.

anon’s picture

anon
Primary language Swedish
Location Gothenburg
CreditAttribution: anon commented

I also found this, in the exact same way #3 did..

dawehner’s picture

dawehner
Primary language German
CreditAttribution: dawehner commented
Status: Active » Postponed (maintainer needs more info)

In general this should be reproduced with the latest version of both ctools and views.

knalstaaf’s picture

knalstaaf CreditAttribution: knalstaaf commented

Subscribing.

bojanz’s picture

bojanz CreditAttribution: bojanz commented

Does this happen in the new UI?
Because that code is getting merged any day now, so it makes no sense to fix a bug only present in the old UI.

zilverdistel’s picture

zilverdistel CreditAttribution: zilverdistel commented

Subscribing.

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

+

knalstaaf’s picture

knalstaaf CreditAttribution: knalstaaf commented

This issue has been fixed in views 7.x-3.x-dev, hasn't it?

zilverdistel’s picture

zilverdistel CreditAttribution: zilverdistel commented
Status: Postponed (maintainer needs more info) » Fixed

@knalstaaf: yes this seems to be fixed in the dev version.

Status: Fixed » Closed (fixed)

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

Jerome F’s picture

Jerome F CreditAttribution: Jerome F commented

We probably need a backport for Views Drupal 6.x-3.x I created a separate issue to make things clear in the issue queue : http://drupal.org/node/1118716

Lythimus’s picture

Lythimus CreditAttribution: Lythimus commented
Version: 7.x-3.0-alpha1 » 7.x-3.5
Status: Closed (fixed) » Needs work

I've had the same issue with Published and also Content Type. It is mitigated by saving. Some of my fellow employees have independently run into this, thankfully I pointed out the fix. It's a tiny bug, but I think it would save a lot of people trouble if it were fixed.

Instructions:

  1. Create a new view.
  2. Switch to display fields?
  3. Add some fields?
  4. Add a content type filter (Published o Content Type).
  5. Be directed to the settings field via AJAX popup to find there value fields are not rendering.
DamienMcKenna’s picture

DamienMcKenna
Location NH, USA
CreditAttribution: DamienMcKenna commented
Issue summary: View changes

Closed a duplicate: #2477057: Exposed filter for published not working for unpublished nodes