Purchase OIOpublisher now for just $47.

Take control of your ad space.

Click here to purchase

Subscribe   OIOpub Blog » Development » Article: 2.0 Release, Bug Tracker

2.0 Release, Bug Tracker

Filed under: Development

Firstly, welcome to the all new OIOpublisher 2.0!

It’s never easy launching a new product, or an enhanced version of an existing one (especially when expectations are high). However much you prepare, not everything will be perfect, and this launch is no exception…

That’s why I’m going to keep a bug list on the blog for OIOpublisher 2.0 users to reference. If you’ve found a bug and see it listed below, you’ll know it’s being dealt with. And if it’s not on the list, report away!

Bugs Found:

Payments of 1,000 or over (any currency) not saving correctly – fixed (30/09/08)
Multiple default ads not showing when using “fill in the gaps” mode – fixed (01/10/08)
Several minor fixes, including the admin purchase editor and auto upgrades – fixed (08/10/08)
Issues with cache deletion and saving html fields – fixed (11/10/08)
Cron job fix (now you can reset all cron jobs manually at any time) – fixed (14/10/08)

Latest version now: 2.07

4 Comments so far

Hugo Santos | September 30, 2008

i have updated the plugin, but the ads used to fill the blank spaces don’t fill them. I have 3 slots empty and they should have been filled. actually only one is filled by the default ads…


Lodewijk | October 1, 2008

First of all, the new site looks great!

I’m going to upgrade my lowest traffic blog (linked above) and see how it all works. As soon as everything is working smoothly, I’ll update my OIO tutorial.


Lodewijk | October 2, 2008

I experienced the same thing as Hugo, but you’ve got that one fixed now.

I updated from 1.61 to 2.02 and also had all my default ads removed. The variable for the number of default ads still showed the correct number (6), but the ads themselves where gone (and the 6 forms to define them too).

But it was pretty easy to fill them again :)


Simon | October 2, 2008

Yep, that one *should* be gone now. Still bug fixing, but I’m hoping that by the end of the week, everything should be completely stable.


Leave a Comment

Name: (required)

Email: (required)

Website:

Comments