Default Search Engines aren't Working
-
majriti last edited by
I noticed this a while back with the default Search Engine for Amazon.com; using Z just did a default Google search for whatever I was looking for. I made a custom search using A (for Amazon, but also the A key is next to Z).
Recently, the W key has stopped going to Wikipedia, and now just does a Google search. I have made a new custom search engine using Q (for query, but also the Q is next to W).
I just ran through all the preset search engines, and none of them seem to be working except for Google (which is set as my default search engine).
If it's possible, can this be fixed? Or, if the presets are not going to actually be functional anymore, is it possible to release the keys so that I can make a custom search engine using those keys how I want to?
Opera GX
Core:133.0.5932.39
System:Windows 11 64-bit
Chromium version:149.0.7827.197 -
Janijan last edited by
@majriti
I recommend resetting Opera GX's default search engines and updating the browser to the latest version, as this may restore the built-in search keywords. If the issue persists, Opera should fix the broken preset search shortcuts or allow users to reassign reserved shortcut keys for custom search engines. -
burnout426 Volunteer last edited by burnout426
Is the "Enable search engine shortcuts in address bar" setting enabled at the URL
opera://settings/search? -
Janijan last edited by
@burnout426 Yes, I checked that setting, and it is enabled. The default search engine shortcuts still don't work, while my custom shortcuts work fine.
-
majriti last edited by
Thank you for this. It had become unchecked. My custom search engines were still working fine, but the defaults weren't. Clicked the box and restarted Opera. All fixed.
-
burnout426 Volunteer last edited by
@Janijan Try unchecking it, restarting Opera, rechecking it and then restarting Opera again.
Same issue in a test standalone installation?
-
burnout426 Volunteer last edited by burnout426
@majriti said in Default Search Engines aren't Working:
It had become unchecked.
There was mentioned of this in one of the changelogs that it's purposely unchecked by default now. So, it wasn't a glitch or anything you did.
