Opened 12 years ago

Closed 12 years ago

#158 closed enhancement (fixed)

Patch - Add layer specific header and footer to query.php

Reported by: andersd Owned by:
Priority: major Milestone: 2.6.1
Component: GeoMOOSE/PHP Version: 2.6
Keywords: Cc:

Description

Add layer specific header and footer to query.php

query.php does not support a layer specific header and footer like the select.php service. This causes a number of issues when customizing layers for specific searches.

The following code fixes this issue. It should be inserted after about line 295 in query.php

if($queryLayer->getMetadata('itemquery_header')) {

$queryLayer->set('header', $queryLayer->getMetadata('itemquery_header'));

}

if($queryLayer->getMetadata('itemquery_footer')) {

$queryLayer->set('footer', $queryLayer->getMetadata('itemquery_footer'));

}

References in the mapfile metadata would look like the following:

'itemquery_header' 'templates/search_header.html'
'itemquery_footer' 'templates/searcg_footer.html'

When this is done the config (settings.ini) header will display first followed by the layer header andthe layer footer will display first followed by the config footer

Change History (7)

comment:1 by theduckylittle, 12 years ago

Milestone: 2.62.6.1

comment:2 by EliL, 12 years ago

Milestone: 2.6.12.6b

testing milestone deletion stuff. Ignore the next few changes on this ticket.

comment:3 by EliL, 12 years ago

Resolution: fixed
Status: newclosed

comment:4 by EliL, 12 years ago

Milestone: 2.6b

Milestone 2.6b deleted

comment:5 by EliL, 12 years ago

Resolution: fixed
Status: closedreopened

Deleting Milestones from trac removes them from closed tickets so we can't remove outdated milestones unless we don't mind having them removed from closed tickets.

comment:6 by EliL, 12 years ago

Milestone: 2.6.1

comment:7 by theduckylittle, 12 years ago

Resolution: fixed
Status: reopenedclosed

r929

This is getting forced to "fix" because of an issue with "reopen" status tickets ... really this should be testing. Sorry if there's a bug, file a follow up ticket and reference this one.

Note: See TracTickets for help on using tickets.