Symphony – Extensions

Edit Plus

Sat, 11 May 2013 10:00:00 +1000

Code editor with syntax highlighting

By Petertron

Edit Plus is a code editor for XSLT, CSS and JS. The current version includes syntax highlighting for XSLT.

Tabnavigation

Fri, 26 Apr 2013 09:00:00 +1000

Extension that provides back-end tabs for Symphony CMS

By mgussekloo

This extension for Symphony CMS enables tabs in the main menu in the backend. Useful for simplifying complex content structures.

Markdown Live

Wed, 24 Apr 2013 10:00:00 +1000

Quickly preview Markdown textarea fields

By gwilson

Adds a button beneath Markdown text area fields that opens a quick preview of the formatted text. Works with Markdown, Markdown Extra and Markdown Extra with Smartypants fields. Supports multiple Markdown fields on one page.

Multilingual

Tue, 09 Apr 2013 09:00:00 +1000

Manipulates datasources for multilingual filtering and output.

By jensscherbl

See symphonyextensions.com for details.

Symphony Checkout

Mon, 11 Mar 2013 10:00:00 +1000

Payment Gateways and Transactions

By davjand

Symphony Checkout is an extension that aims to bring more robust payment functionality to symphony. Inspired by paypal payments and PGI loader, Symphony Checkout provides a Transaction field that can be used to store the relevent data to process a transaction. A 'Transaction' field goes into a section whoes entries represent a payment. The field can then map in data from the other fields in the entry (such as names, addresses, emails etc) in order to pass the relevent data to a payment processor. The field can then post the data to the payment processor via an event and then reconcile the transaction into the field. Currently only sagepay server integration is supported but a test payment gateway class is provided which can be extended for any other payment gateway. NB: Currently the price field is grabbed from the section which means that it has to be pre populated. For use on a 'basket' based ecommerce website, your basket extension needs to save the data into the section. There are obviously security issues here that need to be resolved but this extension currently doesn't cater for that. I have a cart extension (davjand/symphony_cart) that could potentially be integrated in the future. Read more on github

Database Integration Manager

Fri, 08 Mar 2013 10:00:00 +1000

Database Deployment

By davjand

Symphony's database structure doesn't currently lend its self to a continuous integration workflow. There are ways to do it as evidenced by some other great extensions but from bitter experience, it is very easy to accidentally corrupt your database. And this is just for simple workflows with one developer, it gets even more complicated with several developers in which if queries are executed in the wrong order, you get some horrible database issues. How it works DIM provides a method of locking the database structure when a user is making changes. Once the changes are completed, no further users can edit the database structure until they are running the latest version. Workflow is something like as follows: Example Workflow DIM is setup and configured on the staging server (server mode) DIM is setup and configured on the local install (client mode) Authentication details are setup on the server and local installs (multi-user support) The database structure is completely locked now. No pages, events or sections can be edited. NB: Database entries can still be created/edited/deleted etc. The local user requests a database checkout which is recorded on the staging server At this point the user can make changes to their local symphony install. If another user tries to checkout then this will be denied The local user adds a section and checks in the database, creating a new version. At this point the new version is logged on the staging server but not complete as the version only exists locally. The version file must be uploaded to the staging server (My workflow uses GIT to do this). Once the staging server has been updated to the latest version, then (4) can happen again. See Github for complete readme

Filemanager

Thu, 21 Feb 2013 08:00:00 +1000

Select, upload, move and delete files.

By iwyg

Filemanager Dependencies If you are looking for a 2.2.x compatible version, please checkout the release.2.2.x branch. Filemanager has two hard dependencies Require js for Symphony CMS Backbone js for Symphony CMS so if you want to use filemanager, please install these extensions first. (It is not necessary to install Backbone.js since it only provides the javascript source for backbone.js and underscore.js. Placing sym_backbonejs extension in your extensions directory without actually installing it shlould work fine). Notes on Multiple field instances As a major change, version 1.0.0 now allows you to have multiple filemager instances per section. Filemanager keeps its files and folders in sync, though it's beste practice not to share the same directories between different filemanager fields. Pitfalls This mainly refers to developers who are testing on windows/mampp environments In case you dont't have PECL extension finfo_open installed and the deprecated mime_content_type is not available on your system, the file mimetype checking will fallback to application/octet-stream. If you want to use the fileupload feature in this case, include application/octet-stream in your allowed mimetype settings. This results in all files getting validated on the serverside, though clientside validation will work as expected (depending on the browser. e.g. IE will not). Configuration Preferences Default MIME types: define the default MIME types which should be allowed for uploading. This will be overriddin if you set default MIME types on the fields setting. ignore files: define which files shoud be ignored in the directory listing by default. Don't put in here different regular expressions but regexp fragments, e.g. if you want to ignore all files with .jpg and .gif extensions, write .jpe?g$ .gif$ which becomes a regular expression that looks like /(.jpe?g$|.gif$)/i. You can extend this per field in the fields' setting panel. Field Settings Directory options: Set the rootdirectory within workspace and select which directories should be excluded. You can also choose to allow moving, removing and/or creating directories. Uncheck Show filesearch if you don't need fielsearch on this field (since 1.0.5). Allow fileupload: Check this, if you want to allow uploading files. After you save your current section, more options will become available, as they are: Unique Filenames: check this, if you want to have unique filenames Allowed MIME types: define the MIME types that should be allowed for uploading. This will override the defaults set in preferences for this field. File options: Extend the default fileextensions that should be ignored (see Preferences) and set if you want to allow moving files to another location and/or allow deleting files. Select options: Limit the amount of files that can be selected per entry. 0 equals unlimited, -1 prevents selecting files. You may allow re-ordering selected files and choose a displaymode (compact and preview). The Field Selections The Selection field is the actual field (the one which will hold all data). Selecting a file is easy: just click on a file title in the Filebrowser panel to select a file and click the remove button (or a selected file title once again) to remove it form the selection. Since version 1.0.4 holding down shift allows you to select multiple files at once. display mode compact display mode preview Uploads You can add or remove a upload section for each directory within your selected rootdirectory (given your configuration allows fileuploads). Uploaded files will show up in the filebrowser as soon as they are validated. Filebrowser This is the heart of the Filemanager field. Depending on your configuration, you can move and delete files and directories, create new directories or upload files from your local harddrive. Search for files Results are shown while you are typing. You can add searchresults directly to your selection by clicking on the a result node. Meta View Each fileview also has a meta view panel. Click on a files' infobutton to display additional file information such as file size, file type and a file preview (if available). Changelog 1.0.8, 2013-02-21 bugfix: legacy method call validate uploaded file against all error codes 1.0.7, 2012-08-08 bugfix: opera fileupload bugfix: retain selection order 1.0.6, 2012-06-20 bugfixes 1.0.5, 2012-06-04 better handling when file selection is deactivated. searchview is now optional (but activated by default). 1.0.4, 2012-05-25 Fixed a bug with uploads on multiple instances. you may now select and unselect multiple files at once 1.0.3, 2012-05-15 Fixed a bug with file selection limit. Selecting files can now be deactivated (e.g. to use it as a standanlone filemanager) updated lang.de 1.0.2, 2012-05-10 Symphony 2.3 1.0.1, 2012-05-09 minor css fix 1.0.0, 2012-04-25 filemanager field can now hav multiple instances added filesearch view selections can now be reordered selection view can now be displayed in two different modes (preview and compact) design changes beta 1.3.2, 2012-04-19 fixed a bug, were files selection would save if there a whitespace character in the files' name beta 1.3.1, 2012-04-18 success message in file deletion now works as expected fixed an error where the upload progress indicator wouldn't complete animation beta 1.3, 2012-04-17 fixed an error when a directory wasn't accessible (dev 1.4.3) improved error handling (dev 1.4.3) replaced some method calls for compatibility reasons (dev 1.4.3) File ignoring now works as expected (dev 1.4.2) added support for multiplatform installations (pathhandling etc.) (dev 1.4) False error handling for failed uploads (dev 1.4) There was an error while creating new directories. New directories were always created in the workspace root folder (dev 1.4) file upload for legacy browser (iframe-transport mode) (dev 1.3) Metaviews now retain their states when a directory node gets updated (dev 1.3) Fixed some possible pitfalls in case PECL extension finfo_open is not available (dev 1.3) Fixed some possible putfalls in case of a broken default file ignore regexp fragment (dev 1.3) beta 1.2, 2012-04-12 fixed broken default file-ignore RegExp added update method that will handle broken default regexp form previous verions Filebrowser: Folders now auto open and close when dragging over them beta 1.1, 2012-04-11 fixed directory update behaviour deprecated field setting that would cause an error beta 1, 2012-04-11 initial release

APIPage

Fri, 08 Feb 2013 08:00:00 +1000

api, frontend

By iwyg

Synopsis Easily generate api pages with Symphony CMS. Dependencies php >= 5.3.6 all other dependencies should already be met by Symphony CMS Usage Install as usual. set default format and format url parameter in System/Preferences set pagetype to API (do not set any pagetype other then API when using the content type mappings extension) set your template's output format to xml, e.g.: do your data transformation as you would usually do. FAQ Q: why no php 5.2? A: Brace yourself, php 5.5 is comming. Q: I can do all this using a xml to json stylesheet. So why using this extension? A: Sure you can. The downside of doing so is, that all these stylesheets are a bit restricted and perform expensive string operations. The extensions XMLtoJSON parser uses the php C extension SimpleXML, which is much faster. It's reliable and it's tested. TODOS make XMLtoJSON parser exchangable add more output formats like yml, python, etc.

Fingerprint

Thu, 07 Feb 2013 15:00:00 +1000

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

By Lewis

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.

Sections event

Tue, 29 Jan 2013 08:00:00 +1000

Handles forms for multiple sections at once

By vladG

This extension bundles an event and corresponding form controls for easier & integrated control of your frontend forms in one place. If you ever had to submit data from Frontend to more than 1 section and those sections are linked together through a SBL/SBL+ field, you had to customize your event. Using this approach, those relations are handled on-the-fly and no more customizations are required. Features: One event to rule them all. It takes the form data and dispatches the processing for all sections where it should be. It also takes care of linking the entries to each other. Up to date Form controls. More complex fields have arisen lately. @nickdunn's Form Controls have fallen behind. The Section Form Controls offer updated and flexible utilities to help with the new fields and challenges. Built in multiple entries support. Multiple entries are now supported by default without needing to apply another filter. Using Section Form Controls, refactoring the XSLT code to support multiple entries at once becomes a breeze.

Admin CSS Override: @media Print Edition

Fri, 25 Jan 2013 15:00:00 +1000

Great for making PDFs of invoices etc.

By wjnielsen

This extension allows overriding Symphony's Admin CSS PRINT styles by additional CSS rules. It simply appends a custom stylesheet to the head of admin pages. This is probably the simplest extension ever - at least as simple as Admin CSS Override!

Dynamic Text Group

Fri, 18 Jan 2013 15:00:00 +1000

Dynamically add a text field or text field groups to a section entry

By brockpetrie

This field provides a method to dynamically add groups of text fields and text-representable fields (including radio, checkbox and dropdown inputs) to an entry. An example of its use would be for creating tracklists in a section for record albums. This extension would allow you to create as many track entries in each album entry as needed. Usage Add the dynamictextgroup folder to your Extensions directory Enable the extension from the Extensions page Add the Dynamic Text Group field to your section, then save your section to enable the Field Editor Go nuts Field Editor The Field Editor allows for easy manipulation and customization of each field's instance. When adding a new subfield, the label MUST be unique or it'll crash and burn. This is because it names the SQL columns based on your input, and SQL column names must be unique. v3.0 now uses Select2 as its select box mechanism. This means that dynamic values in your select list are now possible, though you'll have to get your hands pretty dirty by creating an instantiation function in assets/dynamictextgroup.publish.js (instantiating it with a unique classname), and then entering that classname (without the leading .) in the Custom Override field within the Select Box field's options dropdown. This will attach your unique class to the select element, allowing for your jQuery instantiation plugin to find it and do its magic. I've included an example that dynamically pulls movies from Rotten Tomatoes to give you a starting point; just enter 'rottentomatoes-example' in the Custom Override option (please don't abuse my API key, I included it as a kindness; go register for your own if you want to actually use it, it takes like 20 seconds). In the distant future I'd like to make implementing these custom selects more user-friendly, but the potential use cases are so varied that it's scary and daunting. Anyway, with a bit of tinkering, it shouldn't be too hard for you to set this up to pull dynamic data from your Symphony site via the APIPage plugin. Change log Version 3.0 beta 1 Symphony 2.3 compatibility. Switched Select Box mechanism to use Select2, so it's now Select Box on steroids. Dynamic select values and more! Just a heads up: I'm planning on renaming this extension to Dynamic Field Groups at some point in the future, so brace yourselves. Version 2.0 See v2.0 Version 1.0 Initial release. See v1.0

Static Asset Versioning

Thu, 17 Jan 2013 08:00:00 +1000

Provides hashes for static assets

By creativedutchmen

This extension will provide a sha1 hash of your static assets in the XML. In a way it is similar to the Asset Compiler extension, except that it does not alter your output, so it can also be used with require.js or script.js. As a sample, this is the output when the folders workspace/js and workspace/css are selected, and Twitter's bootstrap is used (css is concatenated):

77d68d889

1a3ac2a00

9cfbeb5d6

a8f204c81

265e52c5f

320469b1c

2664c0490

e12c769aa

99aee04c5

bd739439a

8b3264cc1

b9809fcb0

aa978472d

01f6c6fab

c01d4b6d4

acdac461d

6788645c4

ec9b205bd

25429fa03

20ecf0567 53b2ef39e This extension does not compile, minify, concatenate or do anything else with your assets, it will just provide you with enough information to ensure your visitors always see the latest stylesheets or scripts, even if you have an agressive cache in place.

Language: German

Mon, 07 Jan 2013 09:00:00 +1000

German translation for Symphony

By Nils

Deutsche Übersetzung für Symphony.

Anti Brute Force

Tue, 18 Dec 2012 15:00:00 +1000

Secure your backend login page against brute force attacks

By Nitriques

Prevents people and software to brute force your authors accounts. SPECS After x failed attempt, the IP address will be banned for y min;x and y are settings in the preferences page Features colored list: Black list, Grey list, White list. Features a unban via email capabilities; Must be enabled in the preferences page Backend content page for managing blocked IPs and colored lists A Facade/Singleton class -ABF- for developers to leverage antibruteforce capabilities (ex.: email reports or use with the member extension) Please read the README.md file on github for full information and for issues

Improved Entry Editor

Thu, 13 Dec 2012 09:00:00 +1000

Enable in-place fields re-ordering and collapsing.

By eKoeS

See the README or the symphonyextensions.com entry for details.

Asset Compiler

Tue, 27 Nov 2012 09:00:00 +1000

Concatenate & minify Javascript & CSS assets

By firegoby

Asset Compiler Symphony CMS extension to concatenate & minify Javascript & CSS assets and update Symphony's output with the newly compiled, SHA1-tagged, filename. Version: 1.4 Date: 5th February 2013 Requirements: Symphony 2.3 Author: Chris Batchelor Synopsis Asset Compiler scans an XSLT Template (master.xsl by default) for CSS and Javascript assets with an attribute of data-compile='true'. These assets are concatenated (in-order) into a single, minified file and tagged with a unique hash (to ensure fresh caching). Symphony's HTML output is updated, removing any data-compile='true' assets and replacing them with the single, minified file (just before closing for CSS and just before closing for Javascripts). There are also a checkbox On/Off switches to control whether to serve the compiled assets. Javascript compilation is via an CURL API call to Google's Closure Compiler. Installation Extract files into extension/asset-compiler directory Enable extension in System > Extensions Add a data-compile='true' attribute to any or