Manual:Extension/BlueSpiceUniversalExport/Customization and Reference:BlueSpiceExtendedSearch: Difference between pages

(Difference between pages)
No edit summary
Tag: 2017 source edit
 
No edit summary
 
Line 1: Line 1:
{{DISPLAYTITLE:PDF Customization (Cloud only)}}
{{BSExtensionInfo
The standard PDF template in BlueSpice Cloud can be adjusted directly in the wiki.  
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro, BlueSpice free, BlueSpice Farm, BlueSpice Cloud
|compatible=BlueSpice
|category=Search and Navigation
|license=GPL v3 only
|features='''ExtendedSearch''' replaces the default MediaWiki search engine. It is based on ElasticSearch engine, and provides many improvements over the standard MediaWiki search both in terms of quality of indexed content and user interface.  


{{Messagebox|boxtype=important|icon=|Note text=In non-cloud editions, the PDF template has to be adjusted on the server.|bgcolor=}}
*Search titles.
*Search the full content.
*Search uploaded or linked files (Office documents and PDFs).
*Search image data.
*Search-as-you-type and auto-complete.
*Ignore upper and lower case (case-insensitive).
*Search with the operators AND, OR, NOT.
*Search with wildcards.
*Search for phrases.
*Fuzzy search.
*Search for sentence fragments.


==Header and footer==
Some aspects of this extension can be configured on [[Special:BlueSpiceConfigManager]], under section "ExtendedSearch". Here wiki administrators can configure:
By default, the PDF template  contains 3 sections for the header and 3 sections for the footer.
<br />
[[File:Manual:PDF-header-footer-standard.png|alt=Standard PDF template|center|thumb|848x848px|Standard PDF template]]
Both the content and the number of columns in the header and footer area can be edited in the following files.


*MediaWiki:UniversalExport/PDF/Default/Header.html
*external file paths
*MediaWiki:UniversalExport/PDF/Default/Footer.html
*layout of the autocomplete box
*MediaWiki: UniversalExport/PDF/Default/Styles.less (optionales externes Stylesheet)
*language filter
*exclude patterns


===Available parameters===
==Boosting (server configuration)==
The following content can be added to each section in the header or footer:
For boosting by match percent, the following settings are available in the extension itself:<syntaxhighlight lang="json">
{| class="wikitable" style="width:100%;"
"ESRecentBoostFactor": {
|+
"description": "Value must be between 0 and 1. If set to 1, very recent pages will almost double their score",
!Parameter
"public": false,
!Description
"value": "0.5"
|-
},
|logo
"ESMatchPercentBoostFactor": {
|current wiki logo
"description": "How much to boost the result based on the percent of its title taken up by the search term. Set to 0 to disable",
|-
"public": false,
|title
"value": "0.5"
|title of the page. In books, this is the title of the book page.
},
|-
"ESMatchPercentTitleField": {
|subtitle
"description": "Field on which to base the match percent boosting. If empty, default title field of the source will be used",
|prints the subtitle of a book if a subtitle was created in the book meta data
"public": false,
|-
"value": ""
|currentpagenumber
|number of the current page
|-
|totalpagescount
|total number of pages
|-
|url
|URL of the wiki page
|-
|user
|username of user who printed the page
|-
|exportdate
|date of PDF-creation
|-
|exporttime
|time of PDF-creation
|}
Each parameter is added to the header or footer enclosed in three curly brackets, for example: <code><nowiki>{{{logo}}}</nowiki></code>.
 
In addition, you can simply type in regular text in each section.
 
===Header===
The header contains a wiki table with three columns. The default content for the first column is the logo of the wiki and the last column shows the page title. The middle column is empty.
 
To make changes to the header, open the page ''MediaWiki:UniversalExport/PDF/Default/Header.html'' in edit mode. <br />
 
[[File:Manual:PDF-header-table.png|alt=Header table|center|thumb|450x450px|Header table]]
 
====Using custom text====
If you do not want to show the logo, but display custom text, you can simply delete the existing placeholders and replace them with your text. Be aware that this header will be used for all PDFs on your wiki, including books.
 
Any of the columns can be left blank.<syntaxhighlight lang="text">
{|
| Text in left column || Text in middle column || Text in right column
|}
</syntaxhighlight>
 
====Removing the middle column====
By default, the 3 columns each use 1/3 of the header width. If you need more room for the left or right column, you can remove the middle column. The remaining 2 columns than each get 1/2 of the header width.<syntaxhighlight>
{|
|The left column now uses 50% of the header width. || Text in the right column
|}
</syntaxhighlight>
[[File:Manual:PDF-header-2col.png|alt=2 columns in the PDF header|center|thumb|650x650px|2 columns in the PDF header]]
<br />
 
====<span class="mw-headline" id="Abstand_vor_und_nach_der_Kopfzeile_anpassen">Adding a margin before and after the header</span>====
The margin before and after the header can be adjusted by changing the beginning of the table  <code>{|</code>  to include a  style declaration:
{| style=”margin-top:20px; margin-bottom:20px;"
 
===Footer===
The footer can be customized just like the header.
 
By default, the footer shows the creation date of the pdf, a BlueSpice disclaimer, and the page number with number of total pages.<syntaxhighlight lang="text">
{|
| {{{exportdate}}} || {{int:universal-export-pdf-default-disclaimer}} ||
{{{currentpagenumber}}} / {{{totalpagescount}}}
|}
</syntaxhighlight>To make changes to the footer, open the page ''MediaWiki:UniversalExport/PDF/Default/Footer.html'' in edit mode.
For example, you could replace the BlueSpice disclaimer in the middle column with the username of the user who printed the pdf.<syntaxhighlight>
{|
| {{{exportdate}}} || {{{user}}} || {{{currentpagenumber}}} / {{{totalpagescount}}}
|}
</syntaxhighlight>
[[File:Manual:PDF-footer-custom.png|alt=PDF footer showing username|center|thumb|650x650px|PDF footer showing username ]]
<br />
 
===Header and footer background color===
If you want to use a background-color for the header and footer, you can copy the following style declaration at the end of the page ''MediaWiki: UniversalExport/PDF/Default/Styles.less'':<syntaxhighlight lang="css">
#runningheaderfix, #runningfooterfix {
background-color: #eee;
}
#runningheaderfix > table {
border-bottom: none !important;
}
#runningfooterfix > table {
border-top: none !important;
}
}
</syntaxhighlight><br />
==Book cover==
When you print a book to PDF, the book has a basic cover page.
By default, the cover page contains the logo, book title, and a placeholder for the subtitle. If you did not create a subtitle for your book, no subtitle is shown.
<br />
[[File:Manual:PDF-cover-default.png|alt=PDF book default cover|center|thumb|424x424px|PDF book default cover]]
<br />
===Using a cover image===
To customize the cover page for books, you will edit the page ''MediaWiki:UniversalExport/PDF/Default/Cover page.html'' .
The example shown below contains the following elements:
*Logo
*Background image
*Title
*Subtitle
[[File:Manual:PDF-cover-withbackground-EN.png|alt=Customized book cover|center|thumb|420x420px|Customized book cover]]
This cover page was created with the following source code. You can simply overwrite the existing content:<syntaxhighlight lang="text" line="1">
{| style="width: 100%; text-align: right;"
|{{{logo}}}
|}
<div style="font-size: 18pt; font-weight:bold; margin-top:5cm; color:#333333">{{{title}}}</div>
<div style="font-size: 14pt; margin-top:11.5cm; color:#333333">{{{subtitle}}}</div>
</syntaxhighlight>
*Lines 1-3: A table with the wiki logo.
*Line 4: Title - here you can define, for example, the font size and font weight, the margin to the top of the page and the font color.
*Line 5:  Subtitle - same as the title. The property ''margin-top'' sets the distance between title and subtitle.
====Defining <span class="mw-headline" id="Untertitel_und_Hintergrundbild_festlegen">the background image and the subtitle</span>====
The subtitle and background image are set in the book's metadata.
#Go to the book manager.
#Select the book for which you want to customize the cover page. This should be an image with the '''full page dimensions''' (e.g., DIN A4 or letter size) since it will be shown as a background image.
#On the book editing page, click the wrench. This opens the metadata dialog.<br />[[File:Manual:PDF-cover-metadata-EN.png|alt=Meta data|center|thumb|450x450px|Meta data]]<br />
#Select ''Bookshelf image'' from the drop-down menu (1) and click ''Add'' (2). In the right column, enter the name of the picture that you want to use for the background. The picture must be uploaded t  o the wiki. If your picture has a namespace prefix, this must be included in the image name.
#Select ''Subtitle'' from the drop-down menu (1) and click Add (2). Entehe desired subtitle accordingly in the right column.
#Click ''Done''.
#Finally, click S''ave'' at the end of the book editing page.
Now test the layout by printing the book as a PDF using the book management. To make the necessary changes (e.g. spacing between title and subtitle), change the settings accordingly on the ''MediaWiki:UniversalExport/PDF/Default/Cover page.html'' or in the metadata.
{{Messagebox|boxtype=note|Note text=You can define a separate background image for each book using the book's the metadata. However, the picture should always be placed in the same position, since all books share the ''Cover page.html''. The alignment of the text elements is shared between all cover pages.}}
====Using background colors====
If you do not have a background image for your book covers or if you don't want to use one, you can also work with colors to customize the cover page.
Here are some examples and the needed source text for the page  ''MediaWiki:UniversalExport/PDF/Default/Cover page.html''.  To use them, simply overwrite the existing content in that page.
<gallery widths="220" heights="300" perrow="34">
File:Manual:Cover-bgcolor-stripe-EN.png|Cover page 1
File:Manual:Cover-bgcolor-topbottom-EN.png|Cover page 2
File:Manual:Cover-bgcolor-middle-withtext-EN.png|Cover page 3
</gallery>
'''Cover page 1'''<syntaxhighlight lang="text">
<!-- Logo -->
{| style="width: 100%; text-align: right;"
|{{{logo}}}
|}
<!-- Color block -->
<div style="position:absolute; height:2cm; width:1.8cm; background-color:#3a3b3c;
margin:4cm 0 0 -2cm">
</div>
<div style="position:absolute; height:2cm; width:24cm; background-color:#3366cc;
margin:4cm 0 0 0cm;">
</div>
<!-- Title -->
<div style="font-size:28pt;font-weight:bold;margin:8.5cm 0 1cm 0;color:#333333;">{{{title}}}
</div>
<!-- Subtitle -->
<div style="font-size:16pt; color:#555555">{{{subtitle}}}
</div>
</syntaxhighlight>
</syntaxhighlight>




===System-wide boosting===
By default, BlueSpice influences the score, after the results have been retrieved, in the following ways:


'''Cover page 2'''<syntaxhighlight lang="text">
*'''Creation date / last edit:''' All things equal, more recently edited pages will rank higher. The amount of influence can be adjusted with '$bsgESRecentBoostFactor' (default 0.5). The value for this can be a number between 0 and 1. 0 means that recency of the page does not change the score and 1 means that very recent changes might get their score doubled.
<div id="coverpage" style="height:29.7cm; width:21cm; margin:-1cm 0 0 -1.5cm;background: #cdcdcd; overflow:hidden;">
*'''Percent of the page title taken up by the search term: ''' An additional score boost is assigned to results that match a larger part of the title. E.g., if the search term is “foo”, a page called “Foo Bar” will have a good match percentage (50%), since the search term takes 50% of the full page name. The page “Foo quick brown fox jumps” will have a lower percentage boost, because the search term takes up only a small percentage of the whole title. This is controlled by '$bsgESMatchPercentBoostFactor' (default 0.5). Same as for the previous setting, a value of 0 will effectively disable this kind of boosting, while 1 would double the score for exact matches (In our example, page “Foo Bar” would get 50% added to its original score).
<div style="min-height:10cm; background:white; margin:2cm 0 0 0; padding:1cm">
*'''Wikipages''' will always be boosted a bit more than other results types (repofile, socialentity, …)
<!-- Logo -->
*Inside the “wikipage” type, pages in '''content namespaces''' and especially pages is '''NS_MAIN''' will be boosted additionally. Talk pages will receive no boost.
{| style="width: 100%; text-align: right;"|
|{{{logo}}}
|}
<!-- Titelblock -->
<div style="font-size: 32pt; font-weight:bold; padding:0 1cm; margin:4.5cm 0 0.5cm 0;color:#333333; background:white">{{{title}}}</div>
<div style="font-size: 24pt; margin-top:0; padding:0 1cm; color:#555555;">{{{subtitle}}}
</div>
</div>
</syntaxhighlight>


Additional configuration is possible for:
*'''ESMatchPercentTitleField:''' Field on which the match analysis is performed. Defaults to nothing, so whatever the search lookup sets. It can be set to "prefixed_text" to calculate match percent on the title with namespace prefix, for example, or to something like "basename" to calculate the match percent only on the page name, without the namespace prefix.




'''Cover page 3'''<syntaxhighlight lang="text">
===User-related boosting===
<!-- Logo -->
{| style="width: 100%; text-align: right;"
|{{{logo}}}
|}
<!-- Title block with background color -->
<div style="background-color:#c6752d; margin:4.5cm -2cm 0 -2cm; padding:2cm 2cm 3cm 2cm;">
<div style="font-size: 24pt; font-weight:bold;  margin-bottom:0.5cm; color:#ffffff;">{{{title}}}
</div>
<!-- Subtitle block -->
<div style="font-size: 18pt; margin-top:0.5cm; color:#efefef">{{{subtitle}}}
</div>
</div>
</syntaxhighlight>
 
==Tags==
===Landscape printing ===
To print a PDF page in landscape format, the following tag can be inserted in the wiki page in source editing mode at any position:
<nowiki><bs:ueparams template="BlueSpiceCloudLandscape" /></nowiki>
To make it easier for the user to add this tag with the visual editor, this tag can be added to a wikitext-template, for example, <code style="box-sizing: inherit; font-family: monospace, Courier; font-size: 13.5px; padding: 1px 4px; color: black; background-color: rgb(249, 249, 249); border-radius: 2px; border: 1px solid rgb(221, 221, 221);"><nowiki>{{LandscapeFormatExport}}</nowiki></code>. The element can be inserted anywhere on the page.


{{Messagebox|boxtype=note|Note text=This tag only works for the PDF single page export.}}
Users can adjust how pages are ranked individually. Such adjustements will only be applied for search queries made by that user and do not affect global search ranking.


<br />
*'''Preferred namespace:''' On the page ''Special:Preferences'' (tab "Extended search"), a user can prioritize namespacea, so that pages in those namespaces will be ranked a bit higher.
{{Box Links-en|Topic1=[[Administration_and_safety#Cloud_administration|Cloud administration]]}}
*'''Favourite results''': In the list of search results, each result has a little "star"-button in the top right corner. Clicking this marks a result as “favorite” for the user who clicked it. This means that this particular result will be boosted more than other results.
}}
{{wcagCheck
|wcagStatus=2-testing complete
|wcagCheckedfor=Web
|wcagTestdate=2022-08-08
|wcagLevel=AA
|wcagSupport=partially supports
|wcagComments=*filter pills, buttons: don't indicate focus, so they cannot easily be opened with keyboard although technically it would already work.
*all buttons announce “blank” and cannot be distinguished.


<br />
erm:[https://support.hallowelt.com/issues/29483 29483]
[[Category:BlueSpice Cloud]]
|extensionType=core
[[en:{{FULLPAGENAME}}]]
|extensionFocus=reader
[[de:Handbuch:Erweiterung/BlueSpiceUniversalExport/Anpassung]]
}}

Revision as of 16:51, 14 December 2022

Extension: BlueSpiceExtendedSearch

all extensions

Overview
Description:

Elasticsearch search backend

State: stable Dependency: BlueSpice
Developer: HalloWelt License: GPL-3.0-only
Type: BlueSpice Category: Search and Navigation
Edition: BlueSpice pro, BlueSpice free, BlueSpice Farm, BlueSpice Cloud Version: 4.1+

Features

ExtendedSearch replaces the default MediaWiki search engine. It is based on ElasticSearch engine, and provides many improvements over the standard MediaWiki search both in terms of quality of indexed content and user interface.

  • Search titles.
  • Search the full content.
  • Search uploaded or linked files (Office documents and PDFs).
  • Search image data.
  • Search-as-you-type and auto-complete.
  • Ignore upper and lower case (case-insensitive).
  • Search with the operators AND, OR, NOT.
  • Search with wildcards.
  • Search for phrases.
  • Fuzzy search.
  • Search for sentence fragments.

Some aspects of this extension can be configured on Special:BlueSpiceConfigManager, under section "ExtendedSearch". Here wiki administrators can configure:

  • external file paths
  • layout of the autocomplete box
  • language filter
  • exclude patterns

Boosting (server configuration)

For boosting by match percent, the following settings are available in the extension itself:
"ESRecentBoostFactor": {
"description": "Value must be between 0 and 1. If set to 1, very recent pages will almost double their score",
"public": false,
"value": "0.5"
},
"ESMatchPercentBoostFactor": {
"description": "How much to boost the result based on the percent of its title taken up by the search term. Set to 0 to disable",
"public": false,
"value": "0.5"
},
"ESMatchPercentTitleField": {
"description": "Field on which to base the match percent boosting. If empty, default title field of the source will be used",
"public": false,
"value": ""
}


System-wide boosting

By default, BlueSpice influences the score, after the results have been retrieved, in the following ways:

  • Creation date / last edit: All things equal, more recently edited pages will rank higher. The amount of influence can be adjusted with '$bsgESRecentBoostFactor' (default 0.5). The value for this can be a number between 0 and 1. 0 means that recency of the page does not change the score and 1 means that very recent changes might get their score doubled.
  • Percent of the page title taken up by the search term: An additional score boost is assigned to results that match a larger part of the title. E.g., if the search term is “foo”, a page called “Foo Bar” will have a good match percentage (50%), since the search term takes 50% of the full page name. The page “Foo quick brown fox jumps” will have a lower percentage boost, because the search term takes up only a small percentage of the whole title. This is controlled by '$bsgESMatchPercentBoostFactor' (default 0.5). Same as for the previous setting, a value of 0 will effectively disable this kind of boosting, while 1 would double the score for exact matches (In our example, page “Foo Bar” would get 50% added to its original score).
  • Wikipages will always be boosted a bit more than other results types (repofile, socialentity, …)
  • Inside the “wikipage” type, pages in content namespaces and especially pages is NS_MAIN will be boosted additionally. Talk pages will receive no boost.

Additional configuration is possible for:

  • ESMatchPercentTitleField: Field on which the match analysis is performed. Defaults to nothing, so whatever the search lookup sets. It can be set to "prefixed_text" to calculate match percent on the title with namespace prefix, for example, or to something like "basename" to calculate the match percent only on the page name, without the namespace prefix.


User-related boosting

Users can adjust how pages are ranked individually. Such adjustements will only be applied for search queries made by that user and do not affect global search ranking.

  • Preferred namespace: On the page Special:Preferences (tab "Extended search"), a user can prioritize namespacea, so that pages in those namespaces will be ranked a bit higher.
  • Favourite results: In the list of search results, each result has a little "star"-button in the top right corner. Clicking this marks a result as “favorite” for the user who clicked it. This means that this particular result will be boosted more than other results.

Technical Information

This information applies to BlueSpice 4. Technical details for BlueSpice Cloud can differ in some cases.

Requirements

  • MediaWiki: 1.37.0
  • BlueSpiceFoundation: 4.1

Integrates into

  • BlueSpiceArticleInfo
  • BlueSpiceExtendedSearch
  • BlueSpiceExtendedStatistics
  • BlueSpicePrivacy
  • BlueSpiceSimpleFarmer
  • BlueSpiceTagCloud
  • BlueSpiceVisualEditorConnector
  • ContentDroplets
  • VisualEditor

Special pages

  • BSSearchAdmin
  • BSSearchCenter

Permissions

Name Description Role
extendedsearch-search-externalfile Search for external files accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager
extendedsearch-search-repofile Search for files accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager
extendedsearch-search-specialpage Search for special pages accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager
extendedsearch-search-wikipage Search for pages accountmanager, admin, author, bot, commenter, editor, maintenanceadmin, reader, reviewer, structuremanager

Configuration

Name Value
ESAllowIndexingDocumentsWithoutContent true
ESAutoRecognizeSubpages true
ESAutoSetLangFilter false
ESBackendClass '\\BS\\ExtendedSearch\\Backend'
ESBackendHost '127.0.0.1'
ESBackendPassword ''
ESBackendPort '9200'
ESBackendTransport 'https'
ESBackendUsername ''
ESCompactAutocomplete true
ESDefaultSearchOperator 'AND'
ESEnableSearchHistoryTracking true
ESEnableTypeFilter true
ESExternalFilePaths array ( )
ESIndexPrefix ''
ESLookupModifierRegExPatterns array ( 0 => '[0-9]{2}\\-[0-9]{2}\\-[0-9]{4}', 1 => '[0-9]{4}\\-[0-9]{2}\\-[0-9]{2}', 2 => '[0-9]{2}\\-[0-9]{4}\\-[0-9]{2}', 3 => '[0-9]{2}\\/[0-9]{2}\\/[0-9]{4}', 4 => '[0-9]{4}\\/[0-9]{2}\\/[0-9]{2}', 5 => '[0-9]{2}\\/[0-9]{4}\\/[0-9]{2}', 6 => '[0-9]{2}\\.[0-9]{2}\\.[0-9]{4}', 7 => '[0-9]{4}\\.[0-9]{2}\\.[0-9]{2}', 8 => '[0-9]{2}\\.[0-9]{4}\\.[0-9]{2}', 9 => '[0-9]{2}\\\\[0-9]{2}\\\\[0-9]{4}', 10 => '[0-9]{4}\\\\[0-9]{2}\\\\[0-9]{2}', 11 => '[0-9]{2}\\\\[0-9]{4}\\\\[0-9]{2}', 12 => '[0-9]{1}\\-[0-9]{2}\\-[0-9]{4}', 13 => '[0-9]{4}\\-[0-9]{2}\\-[0-9]{1}', 14 => '[0-9]{1}\\-[0-9]{4}\\-[0-9]{2}', 15 => '[0-9]{4}\\-[0-9]{1}\\-[0-9]{2}', 16 => '[0-9]{2}\\-[0-9]{4}\\-[0-9]{1}', 17 => '[0-9]{2}\\-[0-9]{1}\\-[0-9]{4}', 18 => '[0-9]{1}\\/[0-9]{2}\\/[0-9]{4}', 19 => '[0-9]{4}\\/[0-9]{2}\\/[0-9]{1}', 20 => '[0-9]{1}\\/[0-9]{4}\\/[0-9]{2}', 21 => '[0-9]{4}\\/[0-9]{1}\\/[0-9]{2}', 22 => '[0-9]{2}\\/[0-9]{4}\\/[0-9]{1}', 23 => '[0-9]{2}\\/[0-9]{1}\\/[0-9]{4}', 24 => '[0-9]{1}\\.[0-9]{2}\\.[0-9]{4}', 25 => '[0-9]{4}\\.[0-9]{2}\\.[0-9]{1}', 26 => '[0-9]{1}\\.[0-9]{4}\\.[0-9]{2}', 27 => '[0-9]{4}\\.[0-9]{1}\\.[0-9]{2}', 28 => '[0-9]{2}\\.[0-9]{4}\\.[0-9]{1}', 29 => '[0-9]{2}\\.[0-9]{1}\\.[0-9]{4}', 30 => '[0-9]{1}\\\\[0-9]{2}\\\\[0-9]{4}', 31 => '[0-9]{4}\\\\[0-9]{2}\\\\[0-9]{1}', 32 => '[0-9]{1}\\\\[0-9]{4}\\\\[0-9]{2}', 33 => '[0-9]{4}\\\\[0-9]{1}\\\\[0-9]{2}', 34 => '[0-9]{2}\\\\[0-9]{4}\\\\[0-9]{1}', 35 => '[0-9]{2}\\\\[0-9]{1}\\\\[0-9]{4}', 36 => '[0-9]{2}\\-[0-9]{2}\\-[0-9]{2}', 37 => '[0-9]{2}\\/[0-9]{2}\\/[0-9]{2}', 38 => '[0-9]{2}\\.[0-9]{2}\\.[0-9]{2}', 39 => '[0-9]{2}\\\\[0-9]{2}\\\\[0-9]{2}', 40 => '[0-9]{1}\\-[0-9]{1}\\-[0-9]{4}', 41 => '[0-9]{4}\\-[0-9]{1}\\-[0-9]{1}', 42 => '[0-9]{1}\\-[0-9]{4}\\-[0-9]{1}', 43 => '[0-9]{1}\\/[0-9]{1}\\/[0-9]{4}', 44 => '[0-9]{4}\\/[0-9]{1}\\/[0-9]{1}', 45 => '[0-9]{1}\\/[0-9]{4}\\/[0-9]{1}', 46 => '[0-9]{1}\\.[0-9]{1}\\.[0-9]{4}', 47 => '[0-9]{4}\\.[0-9]{1}\\.[0-9]{1}', 48 => '[0-9]{1}\\.[0-9]{4}\\.[0-9]{1}', 49 => '[0-9]{1}\\\\[0-9]{1}\\\\[0-9]{4}', 50 => '[0-9]{4}\\\\[0-9]{1}\\\\[0-9]{1}', 51 => '[0-9]{1}\\\\[0-9]{4}\\\\[0-9]{1}', 52 => '[0-9]{1}\\-[0-9]{1}\\-[0-9]{2}', 53 => '[0-9]{2}\\-[0-9]{1}\\-[0-9]{1}', 54 => '[0-9]{1}\\-[0-9]{2}\\-[0-9]{1}', 55 => '[0-9]{1}\\/[0-9]{1}\\/[0-9]{2}', 56 => '[0-9]{2}\\/[0-9]{1}\\/[0-9]{1}', 57 => '[0-9]{1}\\/[0-9]{2}\\/[0-9]{1}', 58 => '[0-9]{1}\\.[0-9]{1}\\.[0-9]{2}', 59 => '[0-9]{2}\\.[0-9]{1}\\.[0-9]{1}', 60 => '[0-9]{1}\\.[0-9]{2}\\.[0-9]{1}', 61 => '[0-9]{1}\\\\[0-9]{1}\\\\[0-9]{2}', 62 => '[0-9]{2}\\\\[0-9]{1}\\\\[0-9]{1}', 63 => '[0-9]{1}\\\\[0-9]{2}\\\\[0-9]{1}', 64 => '[0-9]{2}\\-[0-9]{4}', 65 => '[0-9]{2}\\/[0-9]{4}', 66 => '[0-9]{2}\\.[0-9]{4}', 67 => '[0-9]{2}\\\\[0-9]{4}', 68 => '[0-9]{4}\\-[0-9]{2}', 69 => '[0-9]{4}\\/[0-9]{2}', 70 => '[0-9]{4}\\.[0-9]{2}', 71 => '[0-9]{4}\\\\[0-9]{2}', 72 => '[0-9]{2}\\-[0-9]{2}', 73 => '[0-9]{2}\\/[0-9]{2}', 74 => '[0-9]{2}\\.[0-9]{2}', 75 => '[0-9]{2}\\\\[0-9]{2}', )
ESMatchPercentBoostFactor '0.5'
ESMatchPercentTitleField ''
ESOfferOperatorSuggestion true
ESRecentBoostFactor '0.5'
ESSearchCenterDefaultFilters array ( 0 => 'namespace_text', 1 => 'categories', )
ESSearchInRawWikitext true
ESSharedUploadsIndexPrefix false
ESSourceConfig array ( 'wikipage' => array ( 'skip_namespaces' => array ( 0 => 8, 1 => 9, ), ), 'repofile' => array ( 'extension_blacklist' => array ( 0 => 'mp4', ), 'max_size' => 20000000, ), 'externalfile' => array ( 'extension_blacklist' => array ( 0 => 'mp4', ), 'max_size' => 20000000, ), )
ESSubpageMasterFilterPatterns array ( )
ESSubpageMasterFilterUseRootOnly true
ESUseSharedUploads false
ESWildcardingOperators array ( 0 => '+', 1 => '|', 2 => '*', 3 => '(', 4 => ')', 5 => '~', )
ESWildcardingSeparators array ( 0 => ',', 1 => '.', 2 => ';', 3 => '-', 4 => '_', )
ExtendedSearchExternalFilePathsExcludes array ( )
TagSearchSearchFieldTemplatePath '/resources/templates'

API Modules

  • bs-extendedsearch-autocomplete
  • bs-extendedsearch-query
  • bs-extendedsearch-resultrelevance
  • bs-extendedsearch-stats
  • bs-extendedsearch-triggerupdate
  • bs-extendedsearch-type-store

Hooks

Accessibility

Test status: 2-testing complete
Checked for: Web
Last test date: 2022-08-08
WCAG level: AA
WCAG support: partially supports (workaround: )
Comments:
  • filter pills, buttons: don't indicate focus, so they cannot easily be opened with keyboard although technically it would already work.
  • all buttons announce “blank” and cannot be distinguished.

erm:29483

Extension type: core
Extension focus: reader




To submit feedback about this documentation, visit our community forum.

Discussions