Extending $LinkingMode to handle controller actions

As some of you might have noticed, as soon as you step outside of the standard SiteTree structure you're pretty much on your own. Today I had to make a menu that mixed normal SiteTree pages and controller actions.

I wanted to be able to use LinkingMode to check if this is the currently viewed page and unfortunately the standard function does not take controller actions into account.

The Snippet
public function LinkingMode($action = null) { $controllerAction = Director::urlParam('Action'); if (is_null($controllerAction) && is_null($action)) return parent::LinkingMode(); if ($action == $controllerAction) return 'current'; else return $this->LinkOrSection(); }

What it does

First of all we give the LinkingMode an optional parameter called $action which is set to null by default. Director::urlParam('Action') will return null if you are on the default or index action so if urlParam is null and no action has been given we simply return the results from the original LinkingMode function.

However if an action is entered into the function it checks whether this action matches the urlParam. If it does it returns current, otherwise we return the results from the LinkOrSection function. This means that the controller which the action resides in will get the class section if it's in the same menu as the action.

Use Case

Below is an example of how to use the snippet in your templates. The Link function accepts an optional action parameter which will return the appropriate url for a controller action. As you can see, the new LinkingMode function works the same way. Note that if you're outputting a normal menu no parameter should be passed.
<% control Menu(1) %> <a href="$Link" mce_href="$Link" class="$LinkingMode">$MenuTitle</a> <% end_control %> <a href="$Link(blog)" mce_href="$Link(blog)" class="$LinkingMode(blog)">Blog</a>

Put the new LinkingMode function in your base Page class and you are good to go.

About the Author