Thanks. I should really try and get people to test a release before I release it. Every release these days is bigger and and there is a bigger and bigger chance at a bug creeping in…

No problem – I actually noticed that it had happened in your forums! That’s why I asked you

Can’t turn on php errors on that site, but I can have a good bug hunt for you in some quiet test area over the weekend and let you know how I get on (from memory there have been a couple of things show up in the logs with this plugin, but mostly permissions stuff that aren’t your concern – like moving things around for file uploads etc!).

Thanks for sorting it so quickly – I’ll give this a good test before the next live upgrade and try to help you get things running better where possible.

Thanks for the excellent plugin btw.

@rob Actually I did experience the white screen (of doom) today after I did the second update to TDO Mini Forms. I’m still not sure of the exact cause because 0.13.7 fixes the missing function calls which are plaguing everyone it seems.

I had to delete the plugin and then upload it manually over FTP. And it worked. I hope it’s not some latent bug in TDOMF!

Rob, I’m releasing 0.13.7 as we speak to fix this. A number of people on the wordpress forums raised it as well and it manifested here on the forums (but not on my local testbed). Sorry about that.

Rob said:
Tried the auto update and our site went white; changed themes and the same was true. Deactivated and rolled back and everything was fine again – could be a conflict with one of our other plugins? Anything changed that might cause this?

No, not that I know of. I was testing with WordPress 2.8.6 and did the auto-update on my own site here and didn’t see any issues like that.

Can you check your error log for the error, it might be something trivial? (it would be great if you could turn on all PHP errors and try again and see the error message, but I’m guessing you’re running on a live site…)

Hi,

Tried the auto update and our site went white; changed themes and the same was true. Deactivated and rolled back and everything was fine again – could be a conflict with one of our other plugins? Anything changed that might cause this?