| Summary | summary block not availabe |
| Queue | Nag |
| Queue Version | HEAD |
| Type | Bug |
| State | Resolved |
| Priority | 1. Low |
| Owners | |
| Requester | xk3 (at) mompl (dot) org |
| Created | 5/30/04 (7985 days ago) |
| Due | |
| Updated | 7/24/04 (7930 days ago) |
| Assigned | |
| Resolved | 7/24/04 (7930 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
State ⇒ Resolved
State ⇒ Stalled
State ⇒ Unconfirmed
Priority ⇒ 1. Low
Type ⇒ Bug
Queue ⇒ Nag
horde start page? A little pattern matching with other modules let me
insert the following in nag/lib/api.php
$_services['blocks'] = array(
'args' => array(),
'type' => 'stringArray'
);
function _nag_blocks()
{
return array('summary' => array('name' => _("Tasks Summary")));
}
I have no idea of the horde framework internals, but it's working that way.