|
|
8812.
|
|
|
Enter the ID or IDs (comma-separated) of the %s entries to re-queue. Leave blank to re-queue all.
|
| Context: |
|
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php requeueinputfieldarialabel
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php requeueinputfieldarialabel
|
|
|
8813.
|
|
|
Re-queue all %s entries or the selected IDs for this type
|
| Context: |
|
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php requeuebuttonarialabel
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php requeuebuttonarialabel
|
|
|
8814.
|
|
|
<p>The following table shows the number of records indexed by Elasticsearch and those waiting in the queue. Records are sent to the Elasticsearch index each time the search plugin's cron task runs, typically every 5 minutes.</p> 
<p>You can re-queue records of individual types to avoid having to reset the entire index. If you want to re-queue only one record, enter its ID. To re-queue multiple records, separate their IDs by comma. Don't enter any IDs if all records of a type shall be re-queued.</p>
<p>Click the button "Reset index" at the bottom to reset the entire index, deleting all records and re-queuing them. This may take a while on large sites. |
| Context: |
|
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php resetdescription
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php resetdescription
|
|
|
8815.
|
|
|
Reset index
|
| Context: |
|
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php resetalltypes
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/elasticsearch7/lang/en.utf8/search.elasticsearch7.php resetalltypes
|
|
|
8816.
|
|
|
<!-- @license https://www.gnu.org/licenses/gpl-3.0.html GNU GPL version 3 or later -->
<!-- @copyright For copyright information on Mahara, please see the README file distributed with this software. -->
<h1>Exact people searches</h1>
<p>If your site has a lot of people and uses a PostgreSQL database,
people searches will be faster with exact people searching enabled.
The setting will still work with MySQL databases, but is unlikely
to significantly increase search performance.</p>
<p>However, partial matches on profile fields will not return results,
so if for example you have a person called "Nigel", then typing "Nige"
into the search box will not find that person.</p>
|
| Context: |
|
search/internal/lang/en.utf8/help/forms/pluginconfig.exactusersearch.html
|
|
|
represents a line break.
Start a new line in the equivalent position in the translation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/internal/lang/en.utf8/help/forms/pluginconfig.exactusersearch.html
|
|
|
8817.
|
|
|
Internal
|
| Context: |
|
search/internal/lang/en.utf8/search.internal.php pluginname
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/internal/lang/en.utf8/search.internal.php pluginname
|
|
|
8818.
|
|
|
Exact people searches
|
| Context: |
|
search/internal/lang/en.utf8/search.internal.php exactusersearch
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/internal/lang/en.utf8/search.internal.php exactusersearch
|
|
|
8819.
|
|
|
Results from the "Search for people" box and "People" page are only returned for people whose profile fields match entire search terms.
|
| Context: |
|
search/internal/lang/en.utf8/search.internal.php exactusersearchdescription4
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
search/internal/lang/en.utf8/search.internal.php exactusersearchdescription4
|
