PFS - Revision history

Mnoorenberghe: /* Script Variables */ add link to http://viewvc.svn.mozilla.org/vc/addons/trunk/site/app/webroot/services/pfs.php

2012-02-10T23:13:43Z

Script Variables: add link to http://viewvc.svn.mozilla.org/vc/addons/trunk/site/app/webroot/services/pfs.php

← Older revision		Revision as of 23:13, 10 February 2012
Line 46:		Line 46:
	= Script Variables =		= Script Variables =

	In the service itself, there are variables that need to be defined in order to add a new plugin. These are:		In the [http://viewvc.svn.mozilla.org/vc/addons/trunk/site/app/webroot/services/pfs.php service itself], there are variables that need to be defined in order to add a new plugin. These are:
	$name = ' '; // Name of the plugin, used in UI.		$name = ' '; // Name of the plugin, used in UI.
	$guid = '-1'; // GUID to uniquely identify this plugin.		$guid = '-1'; // GUID to uniquely identify this plugin.

Morgamic at 17:48, 25 February 2009

2009-02-25T17:48:03Z

← Older revision		Revision as of 17:48, 25 February 2009
Line 1:		Line 1:
	PFS stands for the Plugin Finder Service and is used to serve up RDF files that describe plugins for a given mime-type and client.		PFS stands for the Plugin Finder Service and is used to serve up RDF files that describe plugins for a given mime-type and client.

	A new feature in Firefox 3 is [[PFS:Blocklisting\|Plugin Blocklisting]].		A new feature in Firefox 3 is [[PFS:Blocklisting\|Plugin Blocklisting]]. If you're looking for the next generation of PFS, see the [[PFS2]] page.

	= URL Format =		= URL Format =

Morgamic: /* Testing PFS */

2008-10-14T18:35:28Z

Testing PFS

← Older revision		Revision as of 18:35, 14 October 2008
Line 82:		Line 82:
	Change your server to:		Change your server to:
	http://yourserver.com/services/pfs.php(then the rest of the junk from the default)		http://yourserver.com/services/pfs.php(then the rest of the junk from the default)

			If we're testing on preview:
			https://preview.addons.mozilla.org/services/pfs.php(then the rest of the junk from the default)
	# Open a page with an embedded object with a mime-type that corresponds to the plugin you want to test.		# Open a page with an embedded object with a mime-type that corresponds to the plugin you want to test.
	# Note: you can always use LiveHTTPHeaders or TamperData to see what URL your client is actually hitting. Going to the URL directly will let you view the PFS RDF for errors.		# Note: you can always use LiveHTTPHeaders or TamperData to see what URL your client is actually hitting. Going to the URL directly will let you view the PFS RDF for errors.

Morgamic at 17:54, 21 April 2008

2008-04-21T17:54:30Z

← Older revision		Revision as of 17:54, 21 April 2008
Line 74:		Line 74:
	* Operating systems (in UA string) that should be given WMP 11.		* Operating systems (in UA string) that should be given WMP 11.
	* Versions of Firefox that are compatible (if not all)?		* Versions of Firefox that are compatible (if not all)?

			= Testing PFS =
			if you want to test PFS, here are the steps to do so:
			# update pfs.datasource.url to point to your instance of PFS. The default is:
			https://pfs.mozilla.org/plugins/PluginFinderService.php?mimetype=%PLUGIN_MIMETYPE%&appID=%APP_ID%&appVersion=%APP_VERSION%&clientOS=%CLIENT_OS%&chromeLocale=%CHROME_LOCALE%

			Change your server to:
			http://yourserver.com/services/pfs.php(then the rest of the junk from the default)
			# Open a page with an embedded object with a mime-type that corresponds to the plugin you want to test.
			# Note: you can always use LiveHTTPHeaders or TamperData to see what URL your client is actually hitting. Going to the URL directly will let you view the PFS RDF for errors.

Morgamic: /* Script Variables */

2008-04-03T23:32:34Z

Script Variables

← Older revision		Revision as of 23:32, 3 April 2008
Line 47:		Line 47:

	In the service itself, there are variables that need to be defined in order to add a new plugin. These are:		In the service itself, there are variables that need to be defined in order to add a new plugin. These are:
	$name = ''; // Name of the plugin, used in UI.		$name = ' '; // Name of the plugin, used in UI.
	$guid = '-1'; // GUID to uniquely identify this plugin.		$guid = '-1'; // GUID to uniquely identify this plugin.
	$version = ''; // Version string.		$version = ' '; // Version string.
	$iconUrl = ''; // URL of the icon for this plugin, used in UI.		$iconUrl = ' '; // URL of the icon for this plugin, used in UI.
	$installerLocation = ''; // Location of the external binary installer, should be SSL or rely on installerHash.		$installerLocation = ' '; // Location of the external binary installer, should be SSL or rely on installerHash.
	$installerHash = ''; // Installer hash value, used to verify installer.		$installerHash = ' '; // Installer hash value, used to verify installer.
	$XPILocation = ''; // Location of the XPI the browser should install.		$XPILocation = ' '; // Location of the XPI the browser should install.
	$installerShowsUI = 'true'; // Does the installer show a UI? If no, chrome is used.		$installerShowsUI = 'true'; // Does the installer show a UI? If no, chrome is used.
	$manualInstallationURL = ''; // URL to go to if auto-install fails.		$manualInstallationURL = ' '; // URL to go to if auto-install fails.
	$licenseURL = ''; // License information, if needed.		$licenseURL = ' '; // License information, if needed.
	$needsRestart = 'false'; // Does it require a browser restart?		$needsRestart = 'false'; // Does it require a browser restart?

Morgamic at 23:31, 3 April 2008

2008-04-03T23:31:46Z

← Older revision		Revision as of 23:31, 3 April 2008
Line 51:		Line 51:
	$version = ''; // Version string.		$version = ''; // Version string.
	$iconUrl = ''; // URL of the icon for this plugin, used in UI.		$iconUrl = ''; // URL of the icon for this plugin, used in UI.
			$installerLocation = ''; // Location of the external binary installer, should be SSL or rely on installerHash.
			$installerHash = ''; // Installer hash value, used to verify installer.
	$XPILocation = ''; // Location of the XPI the browser should install.		$XPILocation = ''; // Location of the XPI the browser should install.
	$installerShowsUI = 'true'; // Does the installer show a UI? If no, chrome is used.		$installerShowsUI = 'true'; // Does the installer show a UI? If no, chrome is used.

Bhashem at 00:32, 24 January 2008

2008-01-24T00:32:00Z

← Older revision		Revision as of 00:32, 24 January 2008
Line 1:		Line 1:
	PFS stands for the Plugin Finder Service and is used to serve up RDF files that describe plugins for a given mime-type and client.		PFS stands for the Plugin Finder Service and is used to serve up RDF files that describe plugins for a given mime-type and client.

			A new feature in Firefox 3 is [[PFS:Blocklisting\|Plugin Blocklisting]].

	= URL Format =		= URL Format =

Morgamic: /* New Plugin Checklist */

2007-03-27T01:06:56Z

New Plugin Checklist

← Older revision		Revision as of 01:06, 27 March 2007
Line 69:		Line 69:
	* Mime types it needs to be associated with.		* Mime types it needs to be associated with.
	* Operating systems (in UA string) that should be given WMP 11.		* Operating systems (in UA string) that should be given WMP 11.
			* Versions of Firefox that are compatible (if not all)?

Morgamic: /* New Plugin Checklist */

2007-03-27T01:06:22Z

New Plugin Checklist

← Older revision		Revision as of 01:06, 27 March 2007
Line 67:		Line 67:
	* License URL		* License URL
	* Does it require a browser restart post-installation?		* Does it require a browser restart post-installation?
			* Mime types it needs to be associated with.
			* Operating systems (in UA string) that should be given WMP 11.

Morgamic at 01:05, 27 March 2007

2007-03-27T01:05:31Z

← Older revision		Revision as of 01:05, 27 March 2007
Line 1:		Line 1:
	PFS stands for the Plugin Finder Service and is used to serve up RDF files that describe plugins for a given mime-type and client.		PFS stands for the Plugin Finder Service and is used to serve up RDF files that describe plugins for a given mime-type and client.

			= URL Format =

	The client requests the RDF at pfs.datasource.url:		The client requests the RDF at pfs.datasource.url:
Line 6:		Line 8:
	An example of the Flash RDF:		An example of the Flash RDF:
	https://pfs.mozilla.org/plugins/PluginFinderService.php?mimetype=application/x-shockwave-flash&appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=2007032403&clientOS=Windowsxp&chromeLocale=en-US		https://pfs.mozilla.org/plugins/PluginFinderService.php?mimetype=application/x-shockwave-flash&appID={ec8030f7-c20a-464f-9b0e-13a3a9e97384}&appVersion=2007032403&clientOS=Windowsxp&chromeLocale=en-US

			= RDF Format =

	The RDF format looks like this:		The RDF format looks like this:
Line 37:		Line 41:

	</RDF:RDF>		</RDF:RDF>

			= Script Variables =

	In the service itself, there are variables that need to be defined in order to add a new plugin. These are:		In the service itself, there are variables that need to be defined in order to add a new plugin. These are:
Line 48:		Line 54:
	$licenseURL = ''; // License information, if needed.		$licenseURL = ''; // License information, if needed.
	$needsRestart = 'false'; // Does it require a browser restart?		$needsRestart = 'false'; // Does it require a browser restart?

			= New Plugin Checklist =

	If you are thinking of listing a new add-on on PFS, you'll need the above info. Here is an easier to copy/paste list:		If you are thinking of listing a new add-on on PFS, you'll need the above info. Here is an easier to copy/paste list: