Improve Panels integration

What kind of field are you trying to use [node:title]? A field on that node? A block?

Also try using 7.x-1.x-dev.

I think at one point that Panels in its code used unset($node->title) which of course means that the node title is then unavailable to anything that wants to use it after that happens. But I think this might have been fixed in the latest version of Panels/CTools.

Does the Panel configuration use "Node content", or "Node body" in the variant? Using individual fields is a common integration problem with other modules that depend on Core's node_build_content call.

Please try the latest version: 7.x-1.x-dev. I think #1438810: expand token guessing to views fixed this issue. If not, re-open this.

I am using the latest version: 7.x-1.x-dev but I can't use any node related token in a panel pane. is there any other thing I should take into account?

Attached patch adds support for panels node view pages by adding

      case 'page_manager_node_view_page':
        $node = $caller['args'][0];
        $data['node'] = $node;
        break;

I've tested this with the fieldable_panel_panes and tokens.

• %node:title : does not work. I expected this somehow to workas we are in a panels context.
• [node:title] : works
• [site:name] : works already
• [node:body] : works
• [user:name] : will be another patch :)

XRef #1768550: Use context keywords in fieldable panels

See #1775160: Add $user to the available tokens for ie [user:name]

How exactly are you using tokens in a panel panes/content? I need specifically what use cases and where to reproduce.

I'm not sure whether my solution is that good anymore. My current use case was solved by creating a mini panel to have a reusable widget for my title.

But this issue summary and comment #3 suggested panels + tokens was in err so I ended up in trying to get my panels node view title into a reusable solution by using fieldable_panels_panes. That suggested to use token_filter to display context tokens #1768550: Use context keywords in fieldable panels.

But when using fieldable_panels_panes which is an entity I cannot display anything from the current node as token_filter does not know it or did I miss again the available global tokens?

In #1768550-9: Use context keywords in fieldable panels I asked for whether panels contexts should be available for token module.

Steps to reproduc are:

- install fieldable_panels_panes

drush dl fieldable_panels_panes token_filter
drush en fieldable_panels_panes token_filter page_manager

- visit http://drupal.d7/admin/structure/fieldable-panels-panes
- Add a new Panel pane
- Save and manage fields
-- Add a text field with input filter enabled

- visit http://drupal.d7/admin/structure/fieldable-panels-panes/view/1/edit
-- add tokens [current-user:name] [site:name] [node:title] [current-node:title] to text field

- visit http://drupal.d7/admin/config/content/formats/full_html
-- enable 'Replace tokens'

- visit http://drupal.d7/admin/structure/panels and enable node template
-- add a variant
-- add the fieldable-panels-pane to the panels content.

- visit a node
-- The tokens are partly replaced.
-- I expected the node related tokens being replaced too.

(did this help)

I applied the patch from #10 and I have to say it is awesome, and should be committed. So simple, and exactly what I needed.

I have applied this patch (#10) as well and it closes a huge gap in panels enabling new development scenarios. What still needs to be done to get this patch committed and included in a stable release? I'm happy to help, so feel free to give me a ping.

I don't think this would work if you had more than one node context being used in your Panel, as this would *only* work for the first node. I'm wary of adding this due to the fact that based on the description, you *should* be able to use %node:title natively in Panels. But if Panels/Page Manager doesn't have that solved correctly, I'm not sure how we reliably can.

I think I'll wait to see how #2075663: Improve context logic for filter processing. goes and whether it fixes this issue.

+1 for that patch. It works for me, but agreed this could be tricky if there are more nodes. The context comes over from the path argument though, so I'm not sure that would be an issue.

No activity for many years and Drupal 7 is now out of support. Marking out of date.