Hi,

After upgrading to 7.x-3.0 some of the views diapered. Views module is 3.1.
It looks like all the views have in common the fact that there are term views expecting a term id.

There are no errors in the logs, just the views that don't appear.

Thanks,
Alina

Comments

Letharion’s picture

Letharion commented
Category: bug » support
Priority: Critical » Minor
Status: Active » Postponed (maintainer needs more info)

I suggest you start by reading the text that is displayed over the new issue form.

alinag’s picture

alinag commented

I did not provide more because it is as vague for me as it is for me.
I just did an upgrade to Panels because it was mentioned as security upgrade(the only upgrade) and some views, not all, are not displayed, although everything is ok in the administration page.

I tried to go back to previous version 3.0-alpha-3 which was working, but the same result, the views are still not displayed. I also tried the dev branch, still same result.

I just hope that somebody with more experience with Panels will have the same problem and report more.
It might be the same as this.
http://drupal.org/node/1390160

merlinofchaos’s picture

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

If you have views which are content panes that are expecting a term id, and you've set that argument to be filled 'From context' then you need to ensure that there is, in fact, a 'term' context available to fulfill that or the view will not appear.

None of this is in Panels at all, that's all views_content.module in CTools.

Letharion’s picture

Letharion commented

@alinag Regarding the text on the "front page", I mainly meant the last paragraph, which links to two issues, which this is likely a duplicate of. :)

alinag’s picture

alinag commented

I'm a low level programmer so this was the easiest way for me :). I looked through the db queries and found the guilty one. When it is creating the view the query is setting the node type as the id of the taxonomy, instead of the type.

SELECT node.title AS node_title, node.nid AS nid, 'node' AS field_data_body_node_entity_type
FROM
node node
WHERE (( (node.status = '1') AND (node.nid IN (SELECT tn.nid AS nid
FROM
taxonomy_index tn
LEFT OUTER JOIN taxonomy_term_hierarchy th ON th.tid = tn.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th1 ON th.parent = th1.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th2 ON th1.parent = th2.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th3 ON th2.parent = th3.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th4 ON th3.parent = th4.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th5 ON th4.parent = th5.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th6 ON th5.parent = th6.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th7 ON th6.parent = th7.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th8 ON th7.parent = th8.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th9 ON th8.parent = th9.tid
LEFT OUTER JOIN taxonomy_term_hierarchy th10 ON th9.parent = th10.tid
WHERE ( (tn.tid = '1906') OR (th1.tid = '1906') OR (th2.tid = '1906') OR (th3.tid = '1906') OR (th4.tid = '1906') OR (th5.tid = '1906') OR
(th6.tid = '1906') OR (th7.tid = '1906') OR (th8.tid = '1906') OR (th9.tid = '1906') OR (th10.tid = '1906') ))) )AND(( (node.type IN ('1906')) )))
ORDER BY node_title ASC
LIMIT 50 OFFSET 0

Notice (node.type IN ('1906')). If I change this to "cuvant" (the actual type, also used in the previous query for counting) the query is ok.
I search Views issues db and found this http://drupal.org/node/1408976. Downgrading to Views 7.x-3.0 solved the problem. But I don't understand why the update of Panels trigged this bug and not the update of Views. I will pass this to Views.

Thanks,
Alina

Letharion’s picture

Letharion commented

Nice, I'm glad you worked it out. :)

goldlilys’s picture

goldlilys commented

Is there a committed fix to this because I have the latest 7.x-3.0 and none of the views with context id is showing up?

goldlilys’s picture

goldlilys commented
Status: Fixed » Active
merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (won't fix)

The query generation has nothing to do with Panels. That would have to be fixed in the Views queue. THere is a referenced issue, try there.

goldlilys’s picture

goldlilys commented
Status: Closed (won't fix) » Active

Ok the mentioned fix is to downgrade to views-7.x-3.0 . But this really needs to be fixed with panels too somehow.

merlinofchaos’s picture

merlinofchaos commented
Status: Active » Closed (won't fix)

You have contributed exactly 2 sentences to this issue.

It is not to re-open this issue in direct contradiction of something I have not said without a pretty good reason.

It's possible:

1) You actually have a different issue
2) You don't know what you're talking about
3) You didn't actually click through.

alinag has posted a fair bit of diagnosis, and the problem he reported is fixed. Clearly there is something in Views 3.1 that broke and that has to be dealt with in Views.

If you, in fact, have a different problem, you need to provide an actual problem report. Not just one sentence, and a rather haughtily worded one at that.

Please go reread comments #3 and #5. If you have more information, provide it. If you are unable to provide more information, we cannot magically fix it.

goldlilys’s picture

goldlilys commented

Sorry about sounding haughty ... the thing is I did check #5 and even when I did downgrade views to 3.0, none of the views for panels with context id are showing.

Got frustrated about exporting a feature from local to dev only to find out that after exporting, nothing shows up on dev no matter how many times I override the feature and cleared the caches. And thought that oohh updating modules will probably do the trick on local first, but noooo, that only made all the views on panel pages disappear even though the views and contexts are set up correctly because it was working before I tried exporting to dev and updated the views and panel modules. And the freaking task was planned to be done yesterday but goodness Murphy's Law strikes again!!

merlinofchaos’s picture

merlinofchaos commented

Did you check #3? The biggest culprit of this is your 'From context' being set to a context you do not actually have. This could be a little messed up because the changeover to entities has caused some inconsistencies in the data that we've tried to correct for but sometimes stuff slips through. So I would doublecheck that first of all.

alinag’s picture

alinag commented

I've installed today a new Drupal site with the latest Panels and Views and created a view on a taxonomy term and it is working perfectly. This is strange, some inconsistency created during the upgrade, in my case of Panels and in other cases of Views. And probably very difficult to debug.

BTW :) I'm a girl.

Alina