The last couple of days have been busy ones for adding functionality and developing new Payment Methods for the Concrete5 eCommerce add-on. eWay (Australia) v 0.5 [Updated] This release now supports the “shared” payment methods, using eWay hosted forms for collection of credit card details, removing the need for the site running eCommerce to collect [...]
Archive for the ‘Programming’ Category
eWay Payment Plugin for Concrete5 eCommerce
July 5th, 2010
No Comments
Annoucing support for eWay® Payment processing support for the eCommerce extension to the Concrete5 CMS. Version 0.2 supports the following features: Live / Test transaction modes All “Hosted” Payment methods: Real Time Real Time CVN Geo-IP Anti-Fraud Support for “Shared” payment processing facilities from eWay are in development and will be available shortly. The eWay® [...]
Concrete to the rescue
May 18th, 2010
1 Comment
The second in my series of articles exploring some of the tools that really excite me or make my life as a web developer easier. In this article we explore a fantastic content management system, Concrete5 which I first used in a project last November and now once again am using to power a project for a new client.
jQuery Tip: Radio Button Deselection
November 25th, 2009
1 Comment
As a web developer I sometimes get things thrown at us that for whatever reason it makes sense for the behaviour of something to be changed. Normally I push back in these situations waving the big User Experience stick at people, but sometimes the request actually makes sense.
Recently while working on a survey page for a client that was entirely radio button driven I was asked for the ability to allow a user to de-select a radio button – I assumed it would be a pretty easy task, but was wrong. The answers Google returned for me mostly said “radio buttons should always have a value, they aren’t designed for de-selection.”
The problem with this particular set of buttons was it was the weighting in the survey the user assigned to the ‘Other’ field. If the user selected a radio button they were then forced to have to enter their own text with no way of deciding the no longer wanted to enter an optional “other” item. This was also the only optional field in the entire survey. The other problem was purely aesthetic with a “no selection” selection not working with the design. It was decided a second click on the radio button would de-select the selection.
I thought it would be easy – I’ll just cancel the onClick event on that object. Unfortunately Firefox didn’t like that idea. It seems that when the onClick event is fired, the radio button is already selected, so retrieving the previous selection’s value didn’t work. The way I dealt with this was a two-pronged approach using both the mouseDown and click events.
Zend Amazon S3 conflicting with Twitter
September 8th, 2009
No Comments
I’ve recently been working on the backend for a project which revealed a conflict between Zend_Service_Amazon_S3 and Zend_Service_Twitter.
