REALNAME module stops panel override from working

I have seen a similar complaint before and it was a Panels bug. I do not have Panels installed, and the only site I maintain that has Panels 2 does not use RealName.

No, certainly you are not the only one. I have other modules where the way Panels works interferes with their function.

In typical Earl fashion, he gives no details on how to "cooperate." Personally, I think properly using a theme function (and a core one at that) is cooperating.

Is there any followup to the last comment Earl posted here http://drupal.org/node/441874

It appears he is requesting more code information from you.

These are both great modules and it would be a real stinker not to be able to use them both.

Thanks for your efforts and contributions to the drupal community!

I've wrote simple patch.
http://drupal.org/files/realname_ctools.patch

I am just learning PHP and Drupal...

This link just seems to go to the drupal home page...where is the patch?

Try this link:

Thanks mrjavum...I haven't checked the realname search functionality but everything else seems to be working with this patch. Just remember to check your permissions.

Is this patch going to be included in the dev release or it needs further evaluation?

The new patch with more correct version detection of installed ctools.

cool, patch works now. I have been wondering why panels was not taking over the user page !
thanks

I can confirm this patch works - now Panels user view override works and user names are still being converted to real names.

Yes the patch works great!
Please accept it.

mrjavum - please.... can you make a patch for 5.x?

There is now an easier way to take over the fallback than this. Here is code from nodecomment.module designed to do exactly this:

First, it doesn't take over the menu if it knows ctools will:

function nodecomment_menu_alter(&$items) {
  // Override the node view handler for our purpose.
  if (!module_exists('delegator') && !module_exists('page_manager') && $items['node/%node']['page callback'] == 'node_page_view') {
    $items['node/%node']['page callback'] = 'nodecomment_node_view';
  }

Second, it tells page manager it can handle the default case:

/**
 * Ask Delegator to use our version of the node page view instead of
 * Drupal's when falling back.
 */
function nodecomment_delegator_override($type) {
  // Continue to support the older delegator module by passing thru
  // to the newer function:
  return nodecomment_page_manager_override($type);
}

/**
 * Ask Page Manager to use our version of the node page view instead of
 * Drupal's when falling back.
 */
function nodecomment_page_manager_override($type) {
  if ($type == 'node_view') {
    return 'nodecomment_node_view';
  }
}

This works with both the older delegator AND page manager so you don't need a gap in functionality.

It doesn't work with the RC1 releases either...page just goes white. Can anyone revise the patch to include the code that merlin posted?

I am willing to pay a bounty to have this issue fixed. Whatever method is used to fix this issue I would like added to respective module's future releases. Contact me directly or reply if interested. I'm ready to pay as soon as tomorrow (Aug. 6th 2009) I need this ASAP.

Thanks!

The last patch by @mrjavum worked before ctools beta4, which switched to the page_manager module and removed the delegator module. So here is a new patch that should allow it to work with either delegator or page_manger.

regarding merlinofchaos's comment from #21, the proper rewrite of this patch is attached to this message, im using it without any issues till now on a live site
applies against 6.x-1.2 with from within the realname module's directory (-p0)

this should be included into realname, anything against this?

@abaddonsun - The patch works for me too - I started using Realname 6.x-1.x-dev and ctools 6.x-1.0-rc1. After I knew this worked I "upgraded" to Realname 6.x-1.2 and ctools 6.x-1.0 and this also worked. Thank you!

I applied the patch in #25 and it works as expected. My vote to add this t the next release.

subscribe

Please commit the patch in #25. This is the second time I stumbled over this.

It is not marked RTBC.

Patch from #25 worked for us. Thanks!

Hey Nancy, I'm not sure who would be the best person to mark an issue RTBC but I thought it was the module maintainer. The patch seems to work for everyone without problems. I still have it running on several installs without problems. I'm marking it RTBC now, please don't yell at me if I wasn't supposed to :-)

Anja

The correct person would be the second or third person who thoroughly tested and approved it. That means you are an appropriate person. I will try to remember to commit it in the morning.

Well, I was going to commit this as part of #579040: Some bugfixes, but someone now says that there is an issue that is outstanding against that patch.

Fixed by #579040: Some bugfixes.

Included in 6.x-1.3