Closed Bug 1063083 Opened 10 years ago Closed 9 years ago

Cannot install search engines in SM 2.29 Beta 2 (regression)

Categories

(SeaMonkey :: Search, defect)

SeaMonkey 2.29 Branch
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: michal-ok, Unassigned)

References

()

Details

(Whiteboard: [DUPME Bug 1051862])

It's not possible to add a search engine from AMO at https://addons.mozilla.org/en-US/seamonkey/search/?atype=4 or third-party sites.

After pressing the 'Add to Seamonkey' button at AMO I get alert "Sorry, you need a Mozilla based browser like Firefox to install a search plugin.".

When trying to install a search engine from http://mycroftproject.com/ebay-search-plugins.html SM says "Your browser does not support OpenSearch search plugins.".

Spoofing UA to SM 2.26 doesn't help in this case.

The search engines should install normally like in SeaMonkey 2.26.1.

However, it's possible to install search engines manually by downloading the xml file from AMO and placing it in "searchplugins" folder in the profile folder and after restarting they seem to work fine.
Summary: Cannot install search engines (regression) → Cannot install search engines in SM 2.29 Beta 2 (regression)
I can confirm this with  Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 SeaMonkey/2.29a1
Component: General → Search
See Bug 1051862 Can't add e.g. Mycroft search engines (Fix fallout from bug 983920)
status-seamonkey2.26: 	unaffected
status-seamonkey2.27: 	unaffected
status-seamonkey2.28: 	affected
status-seamonkey2.29: 	fixed
status-seamonkey2.30: 	fixed
status-seamonkey2.31: 	fixed
Whiteboard: [DUPME Bug 1051862]
Thanks for the info. But it looks like it's only half-DUPME because the other bug 1055371 - concerning installation from AMO - sits there unresolved.
Bug 1055371 is not marked as resolved but the problem seems resolved in the latest 2.29 candidate build. Installation from AMO works for me.
(In reply to lemon_juice from comment #4)
> Bug 1055371 is not marked as resolved but the problem seems resolved in the
> latest 2.29 candidate build. Installation from AMO works for me.
Possibly fixed in Bug 1055371. Closing as WORKSFORME. Thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.