Make search sources more robust when processing of a source feed fails
Reported by Walter McGinnis | November 18th, 2010 @ 02:51 PM
Right now if a search source has an error processing results, it can cause the calling application to have a total page failure. I.e. something is malformed in a feed result raises an error in external search sources code and the calling application throws a 500 page to the user.
It would be better if there were two levels of error catching:
-
if the total feed fails, return a (configurable) "Service currently unavailable" as a single entry
-
if an individual entry fails to be processed, return a (configurable) "entry unavailable" for that entry
In both instances, the raised error should be logged.
Cheers,
Walter
Comments and changes to this ticket
-
Lurhany67 October 17th, 2025 @ 05:18 PM
When optimizing search performance, it is important to make search sources more robust especially when a source feed fails during processing. Ensuring backup solutions and smart indexing can enhance data stability and improve user access speed. Incorporating engaging experiences such as the game drift boss can also keep users active on the platform while the system refreshes or updates content efficiently for better SEO results.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Display results from external search sources edit
Walter McGinnis