Hello to all,
This is my first issue report, so sorry if I'm being scholastic...
Steps I followed:
1. created a view and tested
2. gone to /admin/content/node-type/myNodeType >>> related content configuration >>> settings and filled the form as follows
Length of node table: 10
Related content in teasers: exclude
Where to display: end
What to display: Teasers
How to display: Grouped by view
3. Gone to node page >> tab related content and checked some of the related nodes
Expected Results:
I expected the related content listed at the end of the node
Actual Results:
the list is always on top.
If I check where to display either "not at all" or "beginning" the behaviour is correct, the list disappear or stay on top
Did I miss something? Is there a way to solve this?
Thank you in advance
Simone (Italy)
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | Screenshot.png | 251.74 KB | peter-boeren |
| #1 | Screenshot.png | 114.77 KB | peter-boeren |
| #1 | Screenshot-1.png | 130.09 KB | peter-boeren |
| #1 | Screenshot-2.png | 148.47 KB | peter-boeren |
Comments
Comment #1
peter-boeren commentedHi Simone,
I have tried to reproduce you bug but I was unable. I have created the same set up as described in you post. I have added a few screenshots to show you what I see.
screenshot: editing of the node type page
screenshot 1: show the node with the local task 'related content'
screenshot 2: node view showing the related content at the end.
First recheck you settings to make absolutely sure. If you are then the next step is to debug. The magic of 'beginning - end' happens in the function function _relatedcontent_node_view(&$node, $teaser, $page) { This can be found in the file relatedcontent.module
if you print the variable $output_placing you can see which case will be used. Compare this value with you settings. All settings are saved in the variable table.
I hope this helps.
Comment #2
midmood commentedHi, thanks for your time.
Yes: setting are ok, more than double check
I'd be glad to help debugging but... I'm more a configurator than a coder, so I'm not able (practically) doing this.
If this feedback is important to you to debug the module, I'm helping happily, but I'm sorry to ask you sort of a workflow.
Have a nice day
Simone (Italy)
Comment #3
peter-boeren commentedOkay, well it is quit easy. Open the file 'relatedcontent.module' in an editor (http://en.wikipedia.org/wiki/List_of_PHP_editors)
Search for line 350 which should start with "function _relatedcontent_node_view(&$node, $teaser, $page) {". Below is the function and add the print-statement ("print $output_placing;") in the code to debug the settings. After saving the new code, you should visit a node with related content. On top of the page the output of the print statement will appear. It should say 'beginning' of 'end'. Compare this to your settings.
Comment #4
midmood commentedok, all done:
the
functionprint statement return "end", but the selecteed list of related content is at te beginningI checked the settings again in the content type. It's on "end" as well.
Comment #5
peter-boeren commentedInteresting,
do you have a clean install like me of is the a website with a lot of other active modules? It is possible for other modules/themes to alter the way content is show.
1) choose an other template: Choose garland, bluemarine or something other very basic. If the problem persists than it is not theme related.
2) If you have a lot of active modules try a clean install. If the problem doesn't occur anymore then one of the active modules is interacting.
kind regards
Peter
Comment #6
midmood commentedcase 1 >> garland >> same behaviour (so, no interactions with genesis theme)
case 2 >> garland & disabling the only module hich actively impact on the content type (addthis.nodule) >> same behaviour
Anyway, this troubleshooting was *very* useful, even for future problems, I feel the step forward :-)
And, with the "step forward hat" on, i truly believe it's a module interaction issues. The site we're talking about is a test one. I installed and uninstalled many times many modules.
I think it's impossible to go back to the root of the problem, do you?
Thank you very much, Peter
Simone
Comment #7
peter-boeren commentedIf it is a test website you might send me a dump of the database and the website. Then I can reproduce it on my local machine. A solution to your problem may prevent more issue posts for me. ;)
Peter
Comment #8
peter-boeren commentedComment #9
peter-boeren commentedThe problem is that with CCK you are able to alter the weights of elements. This can be seen at $node->content['#pre_render']. There the function 'content_alter_extra_weights' is called. So to make your website work the relatedcontent should be aware of the fact that CCK can be installed. This is shown in the code below. This code will soon finds it way into the related content package. Attached is also a screenshot where the relatedcontent is lower than the body as it supposed to be.
Comment #10
midmood commentedThank you very much.
I'm adding your code and looking forward for the corrected version.
Simone