Hi,

I'm using the plugin directory for mozilla browsers under $HOME/.mozilla/plugins so that it remains when upgrading the browsers.

The Java plugins for Firefox have recently changed, so e.g. Firefox 3.6 expects libnpjp2.so which is -> .../jdk/jre/lib/i386/libnpjp2.so, while the old ones (including Seamonkey 1.x) needs the old libjavaplugin_oji.so that is -> .../jdk/jre/plugin/i386/ns7/libjavaplugin_oji.so.

(I still need the old Seamonkey because there are some Java based apps that just fail to work with FF3.x)

This is however problematic, as if I have both java plugin links there when I start Seamonkey, it will get confused and fails to start the old java plugin.
My workaround is quite dirty: remove the new plugin link, then start Seamonkey 1.x, then put back the new plugin link and start FF 3.6.
Then they will see different Java plugins.

Is there a way for Seamonkey 1.x and FF 3.6 (...and then Seamonkey 2 too) to use different plugin directory under $HOME ?

Hi -

It sounds like the cleanest approach would be:

1. Create *two* plugin directories: one for Seamonkey, the other for FireFox 3 (and all new stuff you acquire).

2. Use your existing "$HOME/.mozilla/plugins", your existing "start program" method and your default Java JRE for Firefox.

3. Create a new shell script to start SeaMonkey.

Modify the script so that it uses your "Seamonkey" plugin directory, your old "Seamonkey" JRE and any other environment variables you need to customize.

4 Change your "start" method (for example, your desktop icon) to call your new script, instead of starting SeaMonkey directly.

'Hope that helps .. PSM

Exactly, that would be a nice solution.

So my question boils down to how to do 3. above, i.e. "Modify the script so that it uses your "Seamonkey" plugin directory, your old "Seamonkey" JRE and any other environment variables you need to customize".

Hi, again -

Google "Linux Seamonkey custom plugin folder" (for example) turns up this:

http://kb.mozillazine.org/Profile_folder_-_SeaMonkey

Again, I want to emphasize:

1. Java is probably NOT your problem

2. The key issue is how to override your SeaMonkey defaults

3. I honestly believe it's as easy as wrapping how you "invoke" Seamonkey into a small shell script (a script which overrides a few key environment variables), then "invoking" Seamonkey via the script (instead of directly).

The exact mechanics are something you're probably going to have to experiment with yourself (trial and error).

'Hope that helps .. PSM

PS:
Please post back what you find!

No luck. The plugin directory under the profile directory is not scanned.
The KB page only mentions pluginreg.dat but that's not what I need because that is rewritten I think when a new plugin is found.

So the current workaround was to install the new java plugin for FF3.6 under the FF install dir while keeping the old one for Seamonkey under ~/.mozilla/plugins.
But thanks for the help anyhow.