After creating a block and enabling it in a theme, the node page no longer displays the content but only the teaser. Disabling the block cures the problem.
Changing the block settings or upgrading to the dev version (2011-Nov-24) does not cure this issue.
Am I making a configuration mistake, or is this a bug?
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | FeaturedContentBlock-235623.png | 279.87 KB | offerman |
| #6 | sources.tgz | 466.5 KB | offerman |
| #2 | FeaturedContentBlock1.tgz | 652.31 KB | offerman |
Comments
Comment #1
kristen polPlease provide a screenshot of your configuration settings so I can take a look.
Thanks,
Kristen
Comment #2
offerman commentedTnx! Attached the screenshots of the configuration.
What happens is that the block (configured to be in the second sidebar of the Bartik theme) is not displayed at all.
The main content of the node shows no longer the full content but only the teaser (without a "Read more" link).
Disabling the "Read more" link in the Featured Content block configuration does not change anything.
Then I moved the block from the sidebar to the main content. Now the block is displayed (currently empty since there is no related content) but the main node content still shows only the teaser.
After disabling the block entirely the full node content is there again... :-|
Comment #3
kristen polIt sounds like it may be some incomplete divs or something in the html... is it possible to make the page publicly accessible so I can use firebug or view source on it?
Kristen
Comment #4
kristen polBtw, screengrab is a great free program for grabbing the entire web page in a screenshot...
Kristen
Comment #5
kristen polI have a suspicion that there is something wrong in your teasers or that the FC code is not handling the teasers properly. Can you try switching the FC block to just using the titles instead of teasers and see if the block comes up? I suspect it will. If so, then switch back to the teaser view and send me the HTML source so I can see what text is in there. If there is sensitive info, you can email me it directly if you prefer. Otherwise, just attach it to a comment.
You can also try using the full node... I suspect that may work as well. My assumption is that the teasers have some unclosed div tags that is making your site wonky. The question is whether it is in the node data itself or is the result of the FC code grabbing or formatting something incorrectly.
Thanks,
Kristen
Comment #6
offerman commentedTnx for all your suggestions. Spend some time today trying to pinpoint the problem. Hope this helps... :-)
The problem with the node content reduced to the teaser appears only when selecting Search Results Content.
There is no problem in the HTML code, it checked out all right, and the source (attached) shows that the actual teaser is displayed.
Here's the page I've been using: http://techamatic.com/review/review-xfx-ati-radeon-hd-6950
That's one.
Then switching from Titles only to Teasers to display in the block results in a WSOD with this error message: PHP Fatal error: Cannot use string offset as an array in .../drupal-7.10/sites/all/modules/service_links/service_links.module on line 669
Disabling the Service Links modules doesn't solve the node/teaser problem.
And then a question comes up: if I disable "include node being viewed", making the number of results zero, the RSS link disappears. Shouldn't that one stay?
And if I set "Include this node" shouldn't that page be displayed in the Read more page too?
Can't reproduce the page where the block completely disappears at this moment, but this should give us enough to work on for now :-)
BTW: another thing: when setting Manually Selected Content, the blocks always comes up empty.
Comment #7
kristen pol1) The "search results" is a new feature so there could be something wrong in there.
2) I don't think I've used the services_links module. Weird that it would be having a WSOD as a result of a FC block.. ?? You said that turning off the services link module didn't fix the block but did it still show a WSOD or not? The error at least must have been different since the original error couldn't come up with the module disabled.
3) The "include node being viewed" option means that *if* the node is in the results set then it can show up in the block. It doesn't mean that if you remove that option then the results will be empty though maybe I'm not understanding your issue. The RSS feed icon only makes sense if there are results because the feed is based directly on those results.
4) As for your item:
"And if I set "Include this node" shouldn't that page be displayed in the Read more page too?"
Yes, it should. Is this reproducible that the node is *not* showing up when that option is checked?
5) As for the last item, regarding the manual content, you need to make sure to enter the content to show in the correct format. What content did you put in?
We will need to sort out which of the above are bugs and put them into their own issues. If you can refer to each item with the numbering above (and new numbers for new items), then we can keep figuring these out.
Thanks,
Kristen
Comment #8
offerman commentedOn #2: created a new issue for the Service links module: http://drupal.org/node/1372264
Concerning your question: no error: just back to the situation described in #1 where the teaser is displayed instead of the node.
Comment #9
offerman commentedOn #5: Even a simple path like / should work, right? I tried other paths like /contact and contact as well.
Block keeps displaying the message nothing found.
Screengrab of configuration attached.
Comment #10
offerman commentedOn #3: Maybe I misunderstand this feature. Isn't the content of the block like a query being executed? So subscribing to the RSS feed could always be an option, even if the block is currently empty, since there might be related content in the future?
Comment #11
kristen polRegarding #5, the paths must be for *node* urls only. I think the text below the form field explains the format. e.g. something like:
node/123
some-alias-to-a-node
As for #3, that is a good point... the content may change... perhaps this could be configurable... need to think about it.
For #2, thanks for adding the issue... not sure where the problem really lies as far as the WSOD but maybe they do need to fix something on their end.
Thanks for helping sort this out... once we have some more understanding of all of these we can create separate feature requests, support requests, and/or bug issues depending on what is needed.
Kristen
Comment #12
offerman commentedHopefully we can solve these issues. The site I'm working on has gone live one week ago, so while we are working on the traffic, I'm still able to play around a bit :-)
On issue #3: since RSS is a tool to keep informed on an updated stream of items, I think it could make sense for the Filtered and Search Query content in combination with the Sort by Date Created filter for example.
What is the use of a separate RSS feed if it contains only five items and is never / hardly ever updated?
On issue #5: you are right: I entered the wrong pages, was just going through it quickly when isolating problem #1. So we can forget this one, as I just checked it is working fine here.
Back to issue #1, the one this was all about :-) I cannot reproduce the case where the Featured Content block completely disappears, as described in comments #2. As said, displaying the block in the second sidebar makes the main content of the node displayed as a teaser. Moving the Featured Content block to the main content region gives the same result. Switching from Search Result Content to Manually-Selected Content without changing anything else makes the node being displayed in its fullest glory.
Do you need anything else to be able to work on this one?
Comment #13
kristen polFor issue #3, I opened a feature request and have fixed it (in dev):
http://drupal.org/node/1383960
For issue #1, it definitely appears that a div tag is incomplete or something like that if you are seeing different results depending on where you put the block. Please try using a different theme and see if you get the same behavior. Otherwise, if you can create a test page where I can look at the page with the weird behavior, perhaps I can track it down.
I think #1 is the only outstanding issue. Please confirm.
Thanks,
Kristen
Comment #14
kristen polComment #15
kristen polClosed since no further information was provided.
Comment #16
kristen polunassigning old issues