Closed Bug 233533 Opened 18 years ago Closed 5 years ago
flash communication (scripting - fscommand) fails after upgrading to a new seporate mozilla version (or Fire
> or if Mozilla is actually getting the plugin from another directory That's what's going on, as far a I recall.... we search for plugins in various places. But the xpt needs to be explicitly placed in components.
Is it possible to get Mozilla to also search for the xpt, or don't search at all if the flash player is not installed? This problem had me scratching my head for weeks. I couldn't figure out why it would work sometimes on some machines but not on others. Even after I redownloaded and ran the Flash setup file, it still would not work. It would be great if this could be solved in future versions, so that unsuspecting users and testers are never baffled again. :-)
You can see the plugin path if you enable : user_pref("plugin.expose_full_path", true); with an entry in teh user.js or via about:config
Assignee: general → peterlubczynski-bugs
Component: Browser-General → Plug-ins
confirm this. I am not sure how big of an issue for "normal" people this would be though. Seems to me that if we are searching for the plugin we should search for the xpt as well.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Was there any word on this? "Normal" users might start running into this problem if they start switching from Netscape, or Mozilla proper to Mozilla FireFox...
I just wanted to mention this problem before 1.0 is reached since I've run into the problem again. Any user that downloads FireFox 1.0 is going to have this problem if they are switching from another version of Mozilla or Netscape, so it might be worth some consideration before 1.0 is reached. How hard would it be to fix this anyway? Isn't it just a matter of searching for the xpt file as well as for the plugin? If it's easy, there is no reason this should not be done for 1.0 .
Is bug 255808 a possible dupe of this bug? BTW, any chance of getting this in Firefox 1.0? Now that Firefox is competeing with Mozilla Suite and Netscape, you may get more users running into this problem..
jst, can you have a look?
Assignee: peterlubczynski-bugs → jst
Bugs 277319, 210387 and maybe 248599 are possible duplicates of this bug.
Just as you predicted I ran into this bug when I switched from using netscape to using firefox. I did not have any warning the Flash wasn't working completely. I posted the bug 277319. Users and developers will have no idea why some Flash sites work and some won't. What it sounds like needs to be done is when searching for the flash plugin also search for the flashplayer.xpt file. If both are NOT found then deny loading flash and present the user with the Install Plugin messsage.
dupe of bug 219471 ?
I'd say that bug 219471 is either a dupe of this bug, or depends on this bug.
Is there any chance that this will be fixed for 1.1?
This seems to have been fixed with Flash player 8 (beta). If you install a new mozilla app in a seporate location, it will find and use Flash Player 8, will not copy the flashplayer.xpt file, but fscommand and flash scripting both work anyway. I guess Macromedia fixed this on their end :-)
Yet another bug like this one has been found - bug 233533
I just updated bug 284057 (I probably meant to reference this bug in Comment #15), but I'll reiterate here for convenience. Unless there is some warning about using external support files (like flashplayer.xpt) in the plugin development docs, then this is a bug in the way that Mozilla searches for and copies installed plugins from other installed browsers - when Mozilla copies the plugins, it does not copy all possible support files. The fixes are: 1. Find some way to copy the external support files (maybe it isn't possible). 2. Don't search and copy plugins at all, if you can't be sure you are getting everything (which means users will have to manually install, or be prompted by Mozilla, and as a bonus, will get the most recent version of whatever plugin). 3. Add bright red blinking text to various places in the plugin development docs that warn plugin developers that their plugins may not function properly if they distribute and use external support files with their plugins. This bug was originally about missing functionality in Flash Player. That missing functionality has been fixed by Adobe (then Macromedia) with Flash Player 8+. The above describes the more general problem that this bug may have dug up, but this bug may still be valid specifically as related to Flash on platforms where Flash Player 7 is the latest version (some PPC Linux versions maybe?).
Closing out old bugs. Plugin .xpt hasn't been needed/used in ages.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.