Symphony Extensions

Symphony CMS

Follow @symextensions for updates to the 412 extensions that we track. What is this?

What is symphonyextensions.com?

Symphony Extensions tracks Symphony CMS extensions that are hosted on Github.

How do I submit an extension?

Host your extension on Github and make sure the repository has a good README and an extension.meta.xml file. Then sign in to this site using your GitHub profile where you will see a list of your public repositories. Pick one, and add it to the site. When you make changes, just update the XML file in your repository and we do the rest.

What is an extension.meta.xml file?

It is an XML file that you add to your repository to describe your extension. You can include a name and description, developer contact details, version history, changelog, dependencies and more. Please read the documentation for a full list. You can use the lint tool to check your XML against the schema before submitting your extension to the site.

Who runs this site?

This site is now run by the community @symextensions. The site was created by nickdunn. Contact him at @nickdunn

Found a bug?

Please report it here.

1.02releasedFingerprint

Create a fingerprint of the hidden inputs for a given form.

Clone URLhttps://github.com/lewiswharf/fingerprint.git

Add as a submodulegit submodule add https://github.com/lewiswharf/fingerprint.git extensions/fingerprint --recursive

Download: .tar.gz, .zip
Links: Github, Issues, Wiki

Compatibility

2.x.x	2.1.x	2.2.x	2.3.x	2.4.x	2.5.x	2.6.x	2.7.0	2.7.1	2.7.2	2.7.3	2.7.4	2.7.5	2.7.6	2.7.7	2.7.8	2.7.9	2.7.10
No	No	No	1.02	No	No	No	No	No	No	No	No	No	No	No	No	No	No. Soon?

Symphony Version	Extension version
2.7.10	No. Soon?
2.7.9	No
2.7.8	No
2.7.7	No
2.7.6	No
2.7.5	No
2.7.4	No
2.7.3	No
2.7.2	No
2.7.1	No
2.7.0	No
2.6.x	No
2.5.x	No
2.4.x	No
2.3.x	1.02
2.2.x	No
2.1.x	No
2.x.x	No

Readme

Fingerprint

Fingerprint allows you to create a fingerprint of the hidden inputs for a given form, ensuring that users do not change the values of the hidden inputs prior to submitting the form.

Usage

Fingerprint works with Symphony section events. Custom events that do not invoke the frontend delegate EventPreSaveFilter will not work and be ignored.

Enable the extension.
Set a long and random secret under Preferences.

If the fingerprint upon form submission fails to match the fingerprint created at page creation, the filter messages array will be populated and cause the event to fail.

<filter name="fingerprint" status="failed">Fingerprint does not match.</filter>

Note: hidden input values must be generated via XSLT. Hidden inputs added or changed with JavaScript will cause the event to fail.

Example Use Cases

Fingerprint allows you to do the following things without worrying about users altering values and tampering with a form:

Calculate shopping cart prices/totals via XSLT and pass them as a hidden input to the payment processor.
Use in conjunction with the Members extension to ensure users do not change their role or attempt to edit another entry.
Use in conjunction with the Stripe extension to ensure information sent to Stripe is not altered by the user.

Version history

Requires Symphony 2.3

        - Small improvements
	        - Added `no-fingerprint` page type check to terminate fingerprint checking for page

Requires Symphony 2.3

        - Use HMAC instead of shal to create fingerprint.
	        - Changed behavior of fingerprint creation. Always create/check fingerprint, fall back to hash of secret in preferences.
	        - Cleaned up session name.

Requires Symphony 2.3

        - Initial release.

Symphony Extensions

Symphony CMS

What is symphonyextensions.com?

How do I submit an extension?

What is an extension.meta.xml file?

Who runs this site?

Found a bug?

1.02releasedFingerprint

Mark Lewislewiswharf7 extensions

Compatibility

Readme

Fingerprint

Usage

Example Use Cases

Version history

Mark Lewis lewiswharf7 extensions