If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

browser.search.defaultengine does not interprete "[ProfD]"

RESOLVED EXPIRED

Status

SeaMonkey
Preferences
RESOLVED EXPIRED
12 years ago
12 years ago

People

(Reporter: Lars Plessmann, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

12 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050511

I want to use Mozilla with the same profile under Windows an Linux.

the setting: browser.search.defaultengin saves the searchengine plugin.
The problem is, that windows and linux do have another path layout.
So C:\applications\mozilla cannot be found under Linux!

In this case, I copied the google.src and google.gif 2 levels over my profile
directory. In addition to that I modified the value of the setting
browser.search.defaultengin to: "engine://[ProfD]../../google.src"

But it does not work! Why? It works for email signatures, that I attatch in both
OS, too.
Is the parameter "[ProfD]" in the value not interpreted in this tag?? 

Its nasty, to change the searchengine plugin by changing the OS from Win to
Linux or in reverse.

Would be great, if that would be fixed!
Maybe you can change this to a relative path?

Reproducible: Always

Actual Results:  
I cannot use the search plugin in Linux when I set it up in Windows and reverse.
I have to reconfigure that first, when I switch the OS.

Expected Results:  
I want to use the search plugin without changing the configuration!

engine value should use a relative path in addition to the absoulute path or
interprete the "[ProfD]" parameter as a directory.

Comment 1

12 years ago
I believe the latest patch in bug 123315 enables this
Depends on: 123315
Version: unspecified → Trunk
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.