Closed (won't fix)
Project:
Internationalization
Version:
6.x-1.x-dev
Component:
Blocks
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Jun 2010 at 03:59 UTC
Updated:
10 Mar 2013 at 18:21 UTC
Jump to comment: Most recent
Comments
Comment #1
dawehnerDo the blocks have a pager, too?
If yes, set another pager element there.
This might fix the issue.
Comment #2
shellbot commentedThanks for the reply.
The blocks did not have pagers of their own. In the spirit of full investigation I set some blocks with pagers and I've discovered that these behave normally, so it's only blocks without pagers that have the problem.
Comment #3
shellbot commentedSeems I should have set this back to active to get noticed, still learning how the site works...
Comment #4
merlinofchaos commentedCan you export a view that's experiencing this problem? (Also, the simpler the better; avoiding things like CCK fields and fields provided by modules will make it easier for other people to try to reproduce the issue).
Comment #5
likewhoa commentedI ran into this issue tonight and it's happening with drupal-6.17,views-6.x-3-dev from cvs. I have created a simple view for others help reproduce. The problem is similar for me, were no blocks are generated for the view with or without a pager.
Comment #6
dawehnerWhat i did
a) imported the view
b) moved the block to a region
c) went to frontpage?page=1 block is shown
d) went to frontpage block is shown
e) went to node?page=1 block is shown
e) went to node block is shown
So i cannot reproduce the problem here. That's sad ;)
Comment #7
dawehnerUpdate status based on last comment.
There has to be a way to reproduce the bug.
Comment #8
jmseigneur commentedWe confirm having the same issue for blocks disappearing on the pages that follow the first page of multiple pages. On the first page, the blocks appear correctly. On pages with for example "?page=1", some blocks disappear.
Initially, the culprit seemed to be a filter on a CCK field whose value should be equal to 0 for appearance. When we removed that filter and left other filters "Content Negotation", "Published", the block appeared on all pages. However, that fix did not work for another block having that filter on a CCK field.
At the moment, we have noticed that if we remove "Content Negotiation" filter, all blocks appear in our case. Unfortunately, we do not have a fix to have "Content Negotiation" filter and all blocks at the same time.
Comment #9
dawehnerWhich module provides "Content Negotiation"?
Comment #10
jmseigneur commentedI think it is i18n but I'm not sure. We moved back to Views 6.x-2.11 with "Content Negotiation" filter in the disappearing blocks and it seems to work fine, all blocks appear even when there is a "?page=1". i18n has not been changed so it may be either incompatible with Views 6.x-3.x-dev (but at least it is compatible with 6.x-2.11) or the problem comes from Views 6.x-3.x-dev and not i18n.
Comment #11
dawehnerLet's move to i18n, because this seems to cause the problem at the moment. When you remove the filter it works fine.
Comment #12
WilliamB commentedI've had the same happen with drupal 7: http://drupal.org/node/1094414
Comment #13
mandreato commentedSame issue here: a view in a block disappears when navigating to a page of another view (i.e. /?page=...).
I have: views 6.x-3.x-dev + i18n 6.x-1.9 + i18nviews 6.x-3.x-dev.
Comment #14
Anonymous (not verified) commentedGoing to confirm the pager ID issue. If you have two views on a single page and both have pagers with the same ID, one will win the battle and in this case it seems like the blocks lose. In my instance, I just disabled the pager on the block because I simply forgot to disable it in the first place.
Comment #15
conniemh2 commentedI second that confirmation! I had created a block of summary links for another view display. The block summary list display was not showing up in subsequent paging of the main view display to which the summary links were pointing. Turning off paging in the block of summary links did the trick. Now the block appears on every page of the main view display and works correctly within the view display (D7.9).
Comment #16
jose reyero commentedNo follow up for years, still unconfirmed this is i18n, so closing this one.