|resources:||Home Mailing List Source Code Bugs Documentation|
- Feb 18, 2013
Version 2.1.3, made the creation of local mozplugger.so instances for emulation of different plugins more robust during mozplugger-update (note 2.1.2 improvements did not work on freebsd).
- Feb 12, 2013
Version 2.1.2, added code to respect the env vars XDG_CACHE_HOME and XDG_CONFIG_HOME.
- Jan 20, 2013
Version 2.1.1, made the getting of HOME directory more robust, improved the way mozplugger-update is called automatically when mozplugger detects its out of step with mozpluggerrc.
- Dec 18, 2012
Version 2.1.0, some combinations of browser, applications and window managers do not work nicely with the swallow flag, it is therefore recommended to avoid using the swallow flag and use the links flag instead for those troublesome combinations. mozplugger has been update to extend the links flag to cover these cases.
- Dec 09, 2012
Version 2.0.2, mozplugger now has the ability to provide several plugins with different names. This is so that Java script that required a particular plugin by name and version will work as expected. Also now caches a processed version of mozpluggerc which can be updated by running mozplugger-update.
- Jul 15, 2012
Version 1.14.6, last version where mozplugger does NOT preprocess mozpluggerrc with mozplugger-update NOR support multiple plugins with different names.
MozPlugger is maintained by Louis Bavoil and Peter Leese. Louis Bavoil started MozPlugger as a branch out of Plugger 4.0 in February 2003. For an introduction to plugger see http://fredrik.hubbe.net/plugger.html. Peter Leese joined the development team in November 2007.
The goal of the project is to provide a minimalist, clean and stable general purpose Mozilla plugin module that allows the user to embed and launch their favourite application to handle the various different types of media found on the Internet.
- Some combinations of browser, application and window manager do not work nicely with the swallow flag (this cannot be fixed in mozplugger), it is therefore recommended to avoid using the swallow flag and use the links flag instead for those troublesome combinations. If this is not diserable one can try passing the "needs_xembed" flag to the browser via mozplugger by setting it in mozpluggerrc, but there is no guarantee that this will work.
- One may need to run mozplugger-update after changing mozpluggerc or after installing or uninstalling applications. See this bug report for more information.
- To add more helpers, edit /etc/mozpluggerrc. See man page for details
- Mozplugger requires m4 to parse its configuration file.
- When running the browser behind a non-transparent http proxy OR when accessing a web-site that requires authentication you may find that the commands in the mozpluggerrc file that use the stream flag do not work. This is because authentication details required are not passed to the application. The solution is to either remove the stream flag OR to add in the additional proxy or authenticated related parameters in the command line. The detail of the parameters to pass are specific to the application in question. See this bug report for more information.
- The default "./configure" behaviour is to look for the existance of likely directories the plugin should be placed (e.g. /usr/lib/mozilla/plugins), see configure.ac for the full list of directories checked. On some systems this may not be the correct directory (i.e. the plugin not detected by browser). If this is the case, you need define env variable PLUGINDIR when running configure i.e. "./configure PLUGINDIR=plugin_dir_on_my_system" see bug report
Version 2.1.3 (Feb 18 2013):
Version 2.1.2 (Feb 12 2013): Source
Version 2.1.1 (Jan 20 2013): Source
Version 2.1.0 (Dec 18 2012): Source
Version 2.0.2 (Dec 09 2012): Source
Version 1.14.6 (Jul 15 2012): Source
MozPlugger is now included in Mandriva Linux, Fedora Linux, Debian, Gentoo, and other Linux distributions.