- Issue created by @vipin.mittal18
- First commit to issue fork.
- Status changed to Needs review
7 months ago 10:10am 3 July 2024 - Status changed to Needs work
7 months ago 10:13am 3 July 2024 - Status changed to Needs review
7 months ago 10:40am 3 July 2024 - Issue was unassigned.
- 🇮🇳India vipin.mittal18 Greater Noida
Attached patch till these changes included in next version release.
- First commit to issue fork.
-
japerry →
committed 14e10fb7 on 3.1.x authored by
vipin.mittal18 →
Issue #3457490: Solr Flood Control message appears publically
-
japerry →
committed 14e10fb7 on 3.1.x authored by
vipin.mittal18 →
- Status changed to Fixed
4 months ago 2:26am 18 September 2024 - 🇮🇳India deepakkm
Hello @japerry - Are there any reasons why credit is not given for this issue, considering that the merged commit was made by me?
- 🇺🇸United States nmillin
**Note** Hopefully this helps a future dev.
I like that the message isn't being displayed anymore. Now an error message of "An error occurred while searching, try again later." will show for me. This is coming from SearchApiSolrBackend.php (for me at least).
This message can be overridden by something like:
/** * Implements hook_preprocess_HOOK(). */ function mymodule_preprocess_status_messages(&$variables) { // Normal error message from SearchApiSolrBackend.php. Could be better. if (isset($variables['message_list']['error'])) { $status_messages = $variables['message_list']['error']; foreach ($status_messages as $delta => $message) { if (strpos((string) $message, 'An error occurred while searching, try again later.') !== FALSE) { $variables['message_list']['error'][$delta] = "Search had a bad time. Call the help desk for assistance."; } } } }
Automatically closed - issue fixed for 2 weeks with no activity.