OIOpublisher Lite & Geolocation

Published by Simon on February 4th, 2008

First off, you may or may not know that last weekend, I released OIOpublisher Lite to the public, for free. It actually conforms to the original design specifications (a text link and paid review management system), and should be worth a try out for anyone wishing to see what the plugin is like.

I know that a few people will be disappointed that banner ad management wasn’t included in the free version. I had to think really hard about whether or not to include it, but eventually decided against it. I plan on including all standalone ad management features once some of the other monetisation streams are in place, such as the DigiZine content revenue sharing concept, and the adnetwork (see the labs for more details).

Pro Version gets Geolocation:

The best just got better! After a couple of requests, I spent the weekend polishing off a (country specific) geolocation system for banner ads (including inline ads). This also sees the addition of a default ad system, that lets you add banner ads into OIOpublisher without having to make them into purchases.

At this stage, only default ads benefit from geolocation targeting, as geotargeting purchased ads would mean headaches over pricing and quantity issues. There is also no ad tracking available for default ads yet (as the tracker is built around purchased ads), but that will hopefully be resolved in a future release.

Download the new version now

PS. a mass email will go out on Monday to notify all members of the above announcements 

Leave Comment




9 Responses to “OIOpublisher Lite & Geolocation”

  1. Ben Says:
    February 8th, 2008 at 4:36 pm

    Hi Simon

    I tried sending you an email but got no confirmation message. Pressing send just took me back to the contact page.
    If you could email me at the address in this comment then that would be really good.

    feel free to delete this comment :)

    look forward to hearing from you

    Ben

  2. Simon Says:
    February 8th, 2008 at 5:44 pm

    Hi Ben,

    Sorry the contact form didn’t work for you. I’ve emailed you as requested.

  3. Neil Shearing Says:
    February 15th, 2008 at 3:44 pm

    Hi Simon,
    What are your most recent thoughts about the pros and cons of creating Wordpress plugins and the constraints of the GPL license? As a fellow Brit, I’d like to know your current thoughts.

    Thanks
    Neil.

  4. Simon Says:
    February 16th, 2008 at 9:09 am

    Hi Neil,

    GPL constraints seem murky, even within the WP community, once you bring something “commercial” to the table. At this point it seems that WP is perfectly happy to put GPL and commercial plugins side by side (they even list them in some plugin despositories).

    I’d eventually like to see plugin and theme APIs move to LGPL, to clear things up once and for all - although who knows whether that will ever happen.

  5. Neil Shearing Says:
    February 16th, 2008 at 10:31 am

    Hi Simon,

    Thanks for the reply. I’m concerned about selling a plugin only for people to redistribute under “GPL”. I guess there’s no counter to that, apart from retaining some functionality on my server.

    Neil.

  6. Simon Says:
    February 16th, 2008 at 12:03 pm

    Yes, it’s hardly an ideal situation. As you say, retaining some functionality on a central server is a potential way around it (that’s one of my tactics also). But I also consider this to be “my software” (it’s an original work). The fact it is plugging into the Wordpress platform shouldn’t really matter (and that’s where GPL comes up short for a platform like WP I feel).

    No one, other than the w*r*z community, would dream of re-distributing a premium WP theme for example, and as far as I’m concerned, the same should apply to plugins. And in practice, it does apply, because ONLY the copyright holders can enforce GPL rights - I suppose in theory the WP creators could try and do that for every premium theme and plugin out there, but that would hinder rather than help the project as a whole.

    In fact, there are even arguments to suggest that certain plugins can be exempt by definition. It depends on the interpretation of wording such as “derivative works”. If your plugin is an original work, then it isn’t covered by GPL:

    http://wordpress.org/support/topic/113358

  7. Neil Shearing Says:
    February 16th, 2008 at 12:34 pm

    Thanks for the info, Simon, much appreciated. :-)

    Neil.

  8. Simon Says:
    February 16th, 2008 at 12:44 pm

    No problem, it’s murky waters for sure, but I feel safe enough to use a commercial licence when creating something that goes far beyond what Wordpress offers in itself.

  9. Andy Beard Says:
    February 22nd, 2008 at 1:28 am

    Just ensure as much of your plugin code is contained in function libraries, and claim copyright on those.

    If LGPL can be used with commercial software, then there is no reason why you can’t use the opposite, commercial functions used within a GPL plugin interface.

Leave a Comment

Name (required)

E-mail (required)

Website (optional)