Support

The error message reads:

500 Failed opening required '…/public_html/administrator/components/com_finder/helpers/indexer/adapter.php' (include_path='.:/opt/cpanel/ea-php84/root/usr/share/pear')

File <root>/plugins/finder/weblinks/weblinks.php Line 15

As you can see in the error message, this does not have to do with our software. It comes from the Joomla Weblinks component, namely from its Smart Search plugin.

Kindly note that Weblinks was removed from Joomla about a decade ago. It has since been made available for download as a “core-supported extension”, but the reality is that it has NOT been updated for newer versions of Joomla. Its last stable release was on September 5th, 2025 – before Joomla 6.0 shipped. As it is right now, it does not support Joomla 6 at all.

There is a beta version of Weblinks which ostensibly adds support for Joomla 6. I have not used it myself, so I cannot tell you if it will work on Joomla 6.1. I would assume it does since it was made available for download three days ago.

As to what weblinks and smart search have to do with anything: it's how Joomla works. Whenever you publish, unpublish, delete, create, or edit a record in any component which uses the Joomla core API (like Akeeba Backup does) Joomla will raise an onContent* event. This event is handled by a number of system and content plugins, including Smart Search's indexer. The latter loads all Smart Search plugins and asks them to handle the event. The problem here is that one of these plugins is incompatible with your Joomla version, hence the problem you are experiencing.

You will possibly have the same problem if you try to delete an article, category, banner, or contact in Joomla's core components. These components use the same Joomla core API and of course result in the same event being raised, therefore the same chain of event handling going down up to the point that the errant weblinks smart search plugin tries to load a file which was removed as of Joomla 6.0, causing a fatal PHP error. Joomla's core components will be less graceful in handling the error, showing you the generic Joomla error page.