I honestly can't say that this isn't just my website acting weird, but I hadn't noticed this problem before installing the twitter module, and it only effects the twitter block. Whenever I view a regular page, the block is there telling me about my tweets. If I go to any page that was created in views, the blocks disappear. I am the superuser and I have not specified that the block should only display on certain pages. Any ideas?
Comments
Comment #1
davidneedhamI put the wrong version.
Comment #2
davidneedhamIf it matters, it should be noted that I went into the view and added a second block with different settings so that I could have a "what I'm doing..." block that only displayed the most current tweet.
This bug effects both blocks in this view, but no other block views that I'm using.
Comment #3
davidneedhamI just noticed that the blocks will not appear if I'm on any admin page as well.
Comment #4
davidneedhamI fixed my problem by setting the uid argument fixed at 1 rather than uid by url. That will work fine for me since I'm the only user, but it's still a very strange bug. I'm still curious about what the problem was, but feel free to ignore this eaton. :-)
Comment #5
brei9000 commentedThis fixed my issue also. A very strange bug indeed.
Comment #6
davidneedhamI've had ppl email me directly for more help with this issue since I was able to fix it for myself, so I'm changing this back to normal priority. I wish I knew more about programming for views or module dev so I could help.
For everyone who needs help until this bug gets worked out, here's a detailed explanation of what I did to work around it. Note that this will only work if there is only one person utilizing the Twitter module.
I hope that helps!
Comment #7
jaydub commentedThe default block should not display on -any- page where the uid in question is not in the path as the view expects as uid argument and the default argument is 'User ID from URL'.
There should be 2 blocks setup by default. One for the tweets of the logged in user. That block could appear on any page since the uid of the logged in user is always available. The default argument in this case would be 'User ID from logged in user'.
The other block would be dependent on getting the uid from the context delivered in the URL as in the current case.
As noted above, there is also the option of setting a hard-coded default uid as an argument.
Since the current behavior is as configured this isn't really a bug per se so setting this to a feature request.
Comment #8
jaydub commentedSee related: #343007: Default block for tweets only works on profile page
Comment #9
davidneedhamSee above post.
Comment #10
petrolone commentedHello,
I tried these fixes and still couldn't get the block itself to show up. When I updated I got the message :" This display has no path." Did I miss something?
Comment #11
linkcreative commentedThis helped immensely, thanks unrealnighthawk.
Comment #12
Kutakizukari commented@davidneedham http://drupal.org/node/360840#comment-1215936
That fixed it thanks.
Comment #13
ben_m commentedTHANKS! - i'd never have found that - was stuck with a twitter block only appearing on certain pages - oddly enough it showed on certain pages of one content type but not others of the same type -
@davidneedham http://drupal.org/node/360840#comment-1215936 fixed it!
Comment #14
sagar ramgade commentedHi,
I wanted to show tweets of the logged in user, edited uid argument in the tweets view and selected "User ID from logged in user", which works for me.
Regards
Sagar