Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

a custom search plugin has disappeared

  • 4 odgovora
  • 1 ima ovaj problem
  • 1 prikaz
  • Posljednji odgovor od 25x8

more options

Hello! I have some search plugins created myself as xml files, for cases where "add to search bar" function cannot be used (no search field for example). One day, one of those plugins had just disappeared from search engines list. I've double checked syntax, tried to rename the file, restored defaults with "manage search engines" - nothing helps: FF just ignores this particular file on reboot. What could be a problem? Thanks! (printer section removed from config info, because of 30000 letters limit)

Hello! I have some search plugins created myself as xml files, for cases where "add to search bar" function cannot be used (no search field for example). One day, one of those plugins had just disappeared from search engines list. I've double checked syntax, tried to rename the file, restored defaults with "manage search engines" - nothing helps: FF just ignores this particular file on reboot. What could be a problem? Thanks! (printer section removed from config info, because of 30000 letters limit)

Svi odgovori (4)

more options

Try to delete search.sqlite and search.json in the Firefox Profile Folder.

more options

Hi cor-el, thanks for reply! Just tried. Unfortunately, that didn't solve the problem... Put original search.xxx files back to profile.

more options

bump? any idea?

more options

OK, it seems just fixed it! For this specific searchplugin, I had to move all the params into separate statements, I mean:

<os:Url type="text/html" method="GET" template="script.php?param1=value1&param2=whatever{searchTerms}">
into 

<os:Url type="text/html" method="GET" template="script.php">

 <os:Param name="param1" value="value1"/>
 <os:Param name="param2" value="whatever{searchTerms}"/>

</os:Url>

Then I removed search.json only and it works now. The weird thing is, all my other custom searchplugins remain untouched (in "old syntax") and still work. Looks like they change something in plugins-checking engine we will never know :-)