Compatibility with Janrain engage [#1696428]

Comment #1

bodyblueprinter CreditAttribution: bodyblueprinter commented 23 July 2012 at 03:27

I kept digging into this and I think that the button is trying to be put into the dropdown menu for subscribing to posts. It shows up mis-labled (shareShare on:) and then links to a page not found error. I really have no idea how to fix this, but I think this is where it is trying show up. I compared dropdown menus on the Commons Community site and there is not a "shareShare on:" option in the dropdown.

Log in or register to post comments

Comment #2

bodyblueprinter CreditAttribution: bodyblueprinter commented 30 July 2012 at 20:55

Here is what seems like is happening.....before all of the subscription links (located on content pages between content and comments) were moved the Janrain share button lived where the comment button now lives. It appears as though now it is scooped up with all of the subscriptions and pushed into the dropdown menu.

I really need some help on this as users can no longer share on 3rd party. It appears as this will all change in 3x, but I have a production site that is now ineffective until I can find a way to reach this button. I really appreciate all the dedication that is being given to the 3x project, but I am hoping someone can at least point me to where I need to look to fix this. Most of the Drupal people I have talked to are not familiar with Commons.

Thank you.

Log in or register to post comments

Comment #3

bodyblueprinter CreditAttribution: bodyblueprinter commented 31 July 2012 at 22:15

Here is what seems like is happening.....before all of the subscription links (located on content pages between content and comments) were moved the Janrain share button lived where the comment button now lives. It appears as though now it is scooped up with all of the subscriptions and pushed into the dropdown menu.

I really need some help on this as users can no longer share on 3rd party. It appears as this will all change in 3x, but I have a production site that is now ineffective until I can find a way to reach this button. I really appreciate all the dedication that is being given to the 3x project, but I am hoping someone can at least point me to where I need to look to fix this. Most of the Drupal people I have talked to are not familiar with Commons.

Thank you.

Log in or register to post comments

Comment #4

bodyblueprinter CreditAttribution: bodyblueprinter commented 13 August 2012 at 15:46

I am wondering if 6x issues are just off the map right now..........I have no clue how I can fix this Janrain issue. I uninstalled and reinstalled and it is definitely being broken by the Commons 6x 2.5 and later versions. The HTML is

Log in or register to post comments

Comment #5

bodyblueprinter CreditAttribution: bodyblueprinter commented 16 August 2012 at 21:07

Category:

bug

» support

Maybe I should not have put this as a bug report?

Log in or register to post comments

Comment #6

bodyblueprinter CreditAttribution: bodyblueprinter commented 4 September 2012 at 19:46

I traced it to Tidy Nodes.....the module scoops up all links and puts them into a drop down. I do not know PHP, is there anyone available to write an exception for the Janrain link?

Log in or register to post comments

Comment #7

lightsurge CreditAttribution: lightsurge commented 5 September 2012 at 12:55

You could target the preprocess_node function in tidy_node_links.module, this might work (untested):

function tidy_node_links_preprocess_node(&$variables) {
  if (isset($variables['node']->links))  {
    $links = $variables['node']->links;
    foreach ($links as $key => $link) {
      //if class of link starts with rpx (janrain), theme normally
      if (strpos($key, 'rpx') === 0) {
        $normal_links[] = $link;
        unset($links[$key]);
      }
    }
    $variables['links'] = isset($normal_links) ? theme('links', $normal_links, array('class' => 'links inline')) : '';
    if (count($links)) {
      $variables['links'] .= theme('tidy_node_links', $links, $variables['node']);
    }
  }
}

You could avoid hacking the code by putting this in a custom module with a greater weight than tidy_node_links.

There might be a better way through a hook in tidy node links (like the comments button gets separated).

Edit: edited to not to affect $variables['node']->links