The release of the latest version (v2.1) has gone well, and it seems that users are enjoying the new features and look.
Even though we had a beta period, a couple of bugs made their way into the official release. It’s always stuck me that the first official release is the time when most of the bugs are actually found, rather than any beta periods!
Just in case any more are reported, we’ll wait until this weekend to officially release the updated version, including all known bug fixes. In the mean time, if you have experienced any of the issues below, re-downloading the current release will also fix them:
- mis-alignment when .5 appears in the margins of the ad output
- asked to enter a “valid pricing option” on the post / custom purchase form
- unable to save html code in the admin purchase editor when using file uploading
Fixes to all these bugs are already included in the download. A bug tracker has also been added to the support forum.
The first official release of v2.1 is now available for download. The changelog from the previous stable version can be found below:
v2.10.b1 (beta release)
- new beta program established
- removal of excess componenets (socialposts & viralblogads modules)
- improved ad expiration process
v2.10.b2 (beta release)
- added several new payment options (google checkout, 2checkout.com, authorize.net)
- fixed multiple error notices occurring in php E_STRICT mode
- added “forgotten password” routine in standalone mode
v2.10.b3 (beta release)
- add support for swf (flash) banners
- link exchange option for banner / text ad zones
- various small fixes & enhancements to purchase templates
- added uploading capabilities to admin editor
Installation Options: web installer | manual download
Firstly, a quick note with regards to the previous entry on the OIO affiliate program. I’m now happy with it, and user feedback has been positive, so I’ll be starting work on integrating it over the weekend.
I also had an email the other day from someone requesting a refund. They cited a couple of reasons (it didn’t quite match what they wanted it to do), but the one that stuck out most in my mind was that the admin panel was a bit clunky.
Quite simply, there are too many clicks involved to get to where you want to be.
I’d discussed the possibility of re-designing the admin panel with Hyder from Weborithm previously, and the email prompted me to push on with it. We’re working on a first design draft at the moment, and whilst I don’t think it will be a particularly quick project (lots of usability and organisation elements to get through), it should be well worth the effort.
Once we have something in place, I’ll be sending out an email to the focus group (I haven’t actually sent them anything since setting it up!) to get user feedback on it. If you haven’t signed up to the group already, and would like to give your feedback, simply login to your account and click on the “edit profile” link. You’ll see an option to join the focus group from there.
It’s been one of the (few) criticisms of OIO recently; the lack of documentation. Whilst there is help provided within the application itself, it doesn’t cover everything, and so updated help docs has been on my list for sometime.
Instead of a full-blown documentation library, I’ve instead opted to write a series of tutorials, which you can find in the support forum. This also means that if you make a search in the forum, you’re more likely to find a solution.
You can also request new tutorials, which I’ll then write up and put with the others.
These new options are now available in the latest beta release.
I’ve been a bit delayed in getting the next beta release out, but was able to spare a bit of time this evening to work on a few payment modules that have been requested. They have not been released yet as all need testing, but I hope to package them with the next beta release.
The payment methods being tested are:
2Checkout and Authorize.net are both relatively straight forward, and will work much in the same way as the PayPal module (with automatic payment notifications to update the database). However, nethier method will support subscription payments initially, as both require an SSL certificate to utilise the features required for recurring billing.
It also looks as though Google Checkout requires an SSL certificate to receive any automatic payment notifications to the database (although I’m still checking on that fact), so it will most likely be a manual option to start with, where the user will get notified by email of a payment, and then enter the admin area to mark it as paid.
