Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

a custom search plugin has disappeared

  • 4 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: 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)

모든 댓글 (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 :-)