I am using the Events module for just a basic calendar. I do not have it linked to any particular nodes or types of events. Just using it to display events. I have cleaned up the CSS so that it displays better, for my purposes:
http://gates-chili-high.org/event/2006/07/15/month/all/all/1

I have tried to remove the first link (highlighted in yellow) noted by (event), since it seems to take me nowhere but back to the calendar (with no further info on the event). Which makes it redundant. When I removed the code that displays this, I literally 

crashed my drupal and got this error message on every access:
Cannot modify header information - headers already sent by (output started at /home/sharon/public_html/gates-chili-high/modules/event/event.theme:1) in /home/sharon/public_html/gates-chili-high/includes/common.inc on line 139.

The code I tried to remove is multiple occurences of this code in events.theme:

if ((event_get_types('all') + event_get_types('solo')) > 1) {
    $output .= '<div class="type">'. l('('. $node->event_node_title .')', 'event/'.gmdate('Y/m/d', $node->event_start).'/day/'.$node->type, array('title' => t('limit view *to events of this type'))).'</div>'."\n";
  }

Can someone tell me if there is a way for me to safely remove this display?

Comments

eveltman’s picture

eveltman commented
Title: Redundant Links » Redundant Links for filtering by node type
Status: Active » Needs review

I think the filter links for node type are currently always displayed, due to a bug.
In event.theme, event_get_types() is treated as a function that returns a single numeric value,
but it really returns an array. If event_get_types(....) is surrounded by a count(...), then it works fine.

Then the filter links are only shown if there are multiple content types available for display in the calender.

simon georges’s picture

simon georges commented
Status: Needs review » Closed (won't fix)

This version of Event is not supported anymore. The issue is closed for this reason.

Please upgrade to a supported version and feel free to reopen the issue on the new version if applicable.