I’ve released OIO v2.28 in order to address a compatibility issue with WordPress 3.0.
The issue only affects users running WordPress’ new “multi-site” mode (the replacement for WPMU), which may result in “page not found” errors when loading OIO’s javascript or click tracking features. If you have noticed any such problems after activating multi-site mode, it is recommended that you upgrade to the latest code.
A full changelog is available here.
As always, please remember to back-up your database before upgrading.
A new OIO payment module is now available for download – either separately or via the main download link – using the AlertPay.com payment processor.
The module will allow you to manage all one-off / subscription purchases with AlertPay automatically (in the same way that the existing PayPal module does). If you have any problems with it, let me know on the forum and I’ll help you out.
Cause: a 3rd party web service (used to grab the location of a user) has been inaccessible lately, causing OIO to hang when running.
Solution: upgrade to v2.26. The standard upgrade procedure is to simply upload the new files over the top of the old ones. A step-by-step upgrade tutorial is also available here.
What it does: this update will stop OIO from hanging if 3rd party web services are inaccessible. It also adds the ability to turn off geo-targeting completely.
Please report any issues in the forum. As always, a full changelog is available by clicking here.
————-
Customised Installs: for those users who have template customisations, you shouldn’t need to over-write any of the templates. At the very least, you will need to overwrite the following files:
* the entire “admin” directory
* the entire “modules/demographics” directory
* the functions.php, install.php, upgrade.php files in the “include” directory
* all php files in the main OIO directory (eg. oiopub-direct/admin.php)
If you encounter any problems with updating the minimum number of files, you should try over-writing all files (in case you have an older install that requires a complete upgrade). You can leave the “templates” directory until last, since it is the least likely to require updating.
After a couple of months of being unable to work on the new version of OIO, I’m glad to say I’m now able to get back to it.
I’m currently in the process of building a library of re-usable components that will deal with most of the laborious tasks automatically (the backbone of the opensource framework upon which OIO will be built). I did at one point consider using an existing library (Zend Framework, Kohana etc), but as many have found before me it’s not quite the same as doing it yourself.
As a quick example, I’ve most recently been working on an email component, in order to handle different protocols (SMTP, POP3, IMAP) and send / receive mail in any language automatically. Each component can be used independently of others, so as to make them usable in any development situation, but is kept as lightweight as possible.
Once I’ve constructed the final few generic components, I’ll be able to use them to develop the first prototype of OIO v3. As I mentioned previously, I won’t give any timeframes until I can tell you something accurate; otherwise it’s just a guess on my part.
Every so often I get requests for little additions for OIO. I’ve therefore just released a small plugin that tackles a few such requests in one go. They are not meant to be full blown features, but helpers for certain issues – such as integrating OIO with WPMU.
The main features are:
1.) Integrate a standalone installation of OIO with any WordPress / WPMU blog (if you’ve got OIO installed as a WordPress plugin, you can ignore this feature).
2.) Type a placeholder such as [% oiopub-banner-1-left %] into any of your WordPress posts and it will automatically be converted into an OIO ad zone. The example would output banner zone 1 on the left of your post.
3.) Put an ad zone into your RSS feed.
For more information and to download the “addons” plugin, click here.
