Blocks do not appear ...

Liliplanet - January 14, 2009 - 11:10
Project:Relevant Content
Version:6.x-1.4
Component:Code
Category:support request
Priority:normal
Assigned:Unassigned
Status:postponed (maintainer needs more info)
Description

Hi,

The strangest thing .. this is a vanilla install on my production site and the blocks do not show when all was perfect before on the test site. Just so love this module :)

Could it be that in automated url-aliases I have for node-paths ..

[field_newscategory-term]/[title-raw]

I've tried by path the newscategory term (i.e. 'production/*'), but did not do it either. All permissions are correct.

Perhaps any pointers on what I'm missing here please?

Look so forward to hearing from you.
Lilian

#1

nicholasThompson - January 14, 2009 - 11:31
Component:Documentation» Code
Status:active» postponed (maintainer needs more info)

Hmmm..

There are a number of places the module could be falling over. To start with, you could try chucking in some debugging into the module code. Find this section in the function relevant_content_block:

<?php
     
//Get the terms for the current page using a little reusable wrapper function
     
$terms = relevant_content_get_page_terms();

     
//If there are no terms, not a lot of point in continuing
     
if (empty($terms)) {
        return;
      }
?>

and change it to

<?php
     
//Get the terms for the current page using a little reusable wrapper function
     
$terms = relevant_content_get_page_terms();

echo
"Node Terms are...";
print_r($terms);

     
//If there are no terms, not a lot of point in continuing
     
if (empty($terms)) {
        return;
      }
?>

This should print out the text "Node terms are..." followed by an array of the current node's terms at the top of the page. If nothing at all comes up then the block isn't being viewed. If just the text comes up then your node doesn't have any taxonomy available. If the whole shebang comes up then we're good to move on.

The other problem could be to do with the terms getting excluded due to vocabulary filtering. Try putting in a little more debugging code...

<?php
     
//Again - if there are no terms, no need to continue!
     
if (empty($terms)) {
        return;
      }

     
//Create a node exclusion list - this will exclude the currently viewed node - if applicable.
?>

change that to this:
<?php
     
//Again - if there are no terms, no need to continue!
     
if (empty($terms)) {
        return;
      }
echo
"We still have terms!!";

     
//Create a node exclusion list - this will exclude the currently viewed node - if applicable.
?>

Please post back with the results :-)

#2

Liliplanet - January 14, 2009 - 13:21

Thank you so much for your super-fast reply.

Followed instructions and have the following and not much to report actually. On the top of the page just shows:

'Node Terms are...Array ( )'

If you don't mind, have contacted you directly :)

#3

vevhlos - April 10, 2009 - 21:46

I have the same problem with Liliplanet, though i see you continued your troubleshouting in private. I see that liliplanets webpage no longer suffers from the problem, so could you please make the solution public, if there is one ofcourse. I use postgresql if it helps. thanks

#4

wexy - May 18, 2009 - 12:41

Check if you are using Node Breadcrumb module, after turning this off the Relevant content module appeared, now I have another problem... breadcrumbs are not the way I wont them anymore.

#5

drecute - July 19, 2009 - 08:17

@wexy my node breadcrumb module is disabled by default, but I still can't view the rc block as well.

Also, the rc_cck module is throwing errors as well. When it throws this error, the cck field won't show up on the node creation page. The error says "invalid argument supplied for foreach() in relevant_content_cck.module on line 226".

As promising as this module would have been, these errors are does not make worth the effort.

Please, help fix with a patch.

Thanks.

#6

drecute - July 19, 2009 - 08:18

@Liliplanet Please, make the solution public. Thank you.

#7

Liliplanet - July 19, 2009 - 09:17

Hi,

If I remember correctly, I did not do anything to fix it. Just re-installed on a clean site and it worked. It's possible that it was in conflict with another module, but honestly have no idea which. Sorry ..

 
 

Drupal is a registered trademark of Dries Buytaert.