[
https://jira.codehaus.org/browse/MSKINS-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
barnaby relph updated MSKINS-88:
--------------------------------
Description:
For fluido-based sites with an in-house search engine, I'd like to be able to
specify a search element (like the existing google search element) but to
supply the action URL and field name, so that I can point the search at an
in-house server.
This seems to be the same requirement as this SO question too:
http://stackoverflow.com/questions/14373950/maven-site-search-capabilities
Happy to know if there's another way of achieving this.
Would something like this work:
##
#macro ( customSearch $top )
#set( $customsearchURL = $decoration.custom.getChild( 'fluidoSkin' ).getChild(
'customSearch' ).getChild( 'customsearchURL' ).getValue() )
#if ( $decoration.custom.getChild( 'fluidoSkin' ).getChild( 'customSearch'
).getChild( 'customsearchParamName' ) )
#set( $customsearchParamName = $decoration.custom.getChild( 'fluidoSkin'
).getChild( 'customSearch' ).getChild( 'customsearchParamName' ).getValue() )
#else
#set( $customsearchParamName = "q" )
#end
<form id="search-form" action="$customsearchURL" method="get" #if ( $top )
class="navbar-search pull-right" #end>
<input class="search-query" name="$customsearchParamName" id="query"
type="text" />
</form>
#end
was:
for fluido-based sites with an in-house search engine, I'd like to be able to
specify a search element (like the existing google search element) but to
supply the action URL and field name, so that I can point the search at an
in-house server.
This seems to be the same requirement as this SO question too:
http://stackoverflow.com/questions/14373950/maven-site-search-capabilities
Happy to know if there's another way of achieving this.
Would something like this work:
##
#macro ( customSearch $top )
#set( $customsearchURL = $decoration.custom.getChild( 'fluidoSkin' ).getChild(
'customSearch' ).getChild( 'customsearchURL' ).getValue() )
#if ( $decoration.custom.getChild( 'fluidoSkin' ).getChild( 'customSearch'
).getChild( 'customsearchParamName' ) )
#set( $customsearchParamName = $decoration.custom.getChild( 'fluidoSkin'
).getChild( 'customSearch' ).getChild( 'customsearchParamName' ).getValue() )
#else
#set( $customsearchParamName = "q" )
#end
<form id="search-form" action="$customsearchURL" method="get" #if ( $top )
class="navbar-search pull-right" #end>
<input class="search-query" name="$customsearchParamName" id="query"
type="text" />
</form>
#end
> Add a generic search form
> -------------------------
>
> Key: MSKINS-88
> URL: https://jira.codehaus.org/browse/MSKINS-88
> Project: Maven Skins
> Issue Type: New Feature
> Components: Fluido Skin
> Affects Versions: fluido-1.3.0
> Environment: ALL
> Reporter: barnaby relph
> Priority: Minor
>
> For fluido-based sites with an in-house search engine, I'd like to be able to
> specify a search element (like the existing google search element) but to
> supply the action URL and field name, so that I can point the search at an
> in-house server.
> This seems to be the same requirement as this SO question too:
> http://stackoverflow.com/questions/14373950/maven-site-search-capabilities
> Happy to know if there's another way of achieving this.
> Would something like this work:
> ##
> #macro ( customSearch $top )
> #set( $customsearchURL = $decoration.custom.getChild( 'fluidoSkin'
> ).getChild( 'customSearch' ).getChild( 'customsearchURL' ).getValue() )
> #if ( $decoration.custom.getChild( 'fluidoSkin' ).getChild( 'customSearch'
> ).getChild( 'customsearchParamName' ) )
> #set( $customsearchParamName = $decoration.custom.getChild( 'fluidoSkin'
> ).getChild( 'customSearch' ).getChild( 'customsearchParamName' ).getValue() )
> #else
> #set( $customsearchParamName = "q" )
> #end
> <form id="search-form" action="$customsearchURL" method="get" #if ( $top )
> class="navbar-search pull-right" #end>
> <input class="search-query" name="$customsearchParamName" id="query"
> type="text" />
> </form>
> #end
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
