Error when using custom search with quick launch feature

[Juxsta]

Description

I'm using custom search with the quick launch feature and when performing the search via quick launch a new tab opens with the following error

Application error: a client-side exception has occurred (see the browser console for more information).
The relevant console and server logs report undefined errors. I am able to perform the custom search fine when not using the quick launch feature and instead using the widget directly.

homepage version

v0.9.2 (af16956, Jun 5, 2024)

Installation method

Docker

Configuration

- search:
    provider: [google, custom]
    url: https://www.perplexity.ai/search?q=
    target: _blank
    suggestionUrl: https://ac.ecosia.org/autocomplete?type=list&q=
    showSearchSuggestions: true # Optional

Container Logs

[2024-06-27T20:01:41.316Z] error: undefined

Browser Logs

TypeError: Cannot read properties of null (reading 'classList')
at l (_app-b877b7641e51de94.js:1:16848)
at _app-b877b7641e51de94.js:1:16976
at ri (framework-95233f837b560043.js:1:93734)
at Ss (framework-95233f837b560043.js:1:113961)
at framework-95233f837b560043.js:1:110551
at S (framework-95233f837b560043.js:1:138480)
at MessagePort.T (framework-95233f837b560043.js:1:139014)

Troubleshooting

N/A

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided, it seems that there is a client-side exception occurring when using the Quick Launch feature with a custom search provider. The error message from the browser logs indicates that there is an attempt to access a property of null, which suggests that an element expected in the DOM is not present or not accessible at the time the script is running.

Given that the error does not occur when using the widget directly, it's possible that the Quick Launch feature may not be handling the custom search provider configuration correctly, or there may be a bug in the Quick Launch script that is triggered under certain conditions.

To troubleshoot this issue, you can try the following steps:

1. Verify that the custom search provider configuration is correct and follows the documentation for setting up custom searches with Quick Launch. Ensure that the url and suggestionUrl are properly formatted and accessible.

2. Check if there are any known issues or updates related to the Quick Launch feature by reviewing the Homepage repository on GitHub, specifically the issues and discussions sections.

3. If the issue persists, consider opening a new issue on the Homepage GitHub repository with the details of the error, including the configuration, container logs, and browser logs. This will allow the developers to investigate the problem further.

4. As a temporary workaround, you may disable the Quick Launch feature for the custom search provider and continue using the search widget directly until the issue is resolved.

Since the error message indicates a problem with accessing a DOM element's classList, it's also possible that there is a conflict with custom CSS or JavaScript that may be affecting the Quick Launch feature. If you have added any custom CSS or JS, review those changes to ensure they are not interfering with the Quick Launch functionality.

Lastly, ensure that you are using the latest version of Homepage, as the issue may have been addressed in a newer release.

This comment was generated by Glime.

[shamoon]

You should double-check the docs, see the example https://gethomepage.dev/latest/configs/settings/#__codelineno-33-1:5 and above that:

For custom providers the suggestionUrl needs to be set in order for this to work.

[Juxsta]

I have a suggestionUrl set and it works within the widget. It only fails when using quick launch

[shamoon]

Post your config

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.