If we haven't said so before, a big THANK YOU to all the buyers of the CPO Source Code. Your purchases are lighting the fire under our pants to keep improving CreativePro Office daily.
There are source code patches available to amend some of the bugs that our much appreciated bug testers have found.
The link is here:
http://creativeprooffice.com/site/patches
We are currently working on CreativePro Office 2.0 that we hope will be available by the end of March and possibly earlier. We are excited about this release as it will be the "new improved" version with more features that users have been requesting and numerous bug fixes.
We have been hearing from people who are starting out with Creative Pro Office and are receiving activation errors upon signing up. We are taking a closer look at this and wanted folks to know that we are aware of the situation. It is easy to rectify, if you let us know we can manually activate the account, but this isn't a permanent fix. If you get an activation error, do let us know, it is fast for us to activate your account manually and can get back to you relatively quickly.
In other news, we are aware that CPO is running extremely slowly for us, and have gotten word from other users that its slow going for them as well. Since we have increased our base of users so much since we initiated our current hosting situation, we recognize that the time has come to give a boost to our bandwidth so CPO can run more smoothly. We can do this thanks to those who have purchased the source code.
Jeff continues to busily rewrite the code base to so that we can provide a feature rich and stable product for users. For those of you submitting bugs and feature requests, we owe a debt of gratitude, keep 'em coming because you are what is driving the improvements and growth to Creative Pro!
I’ll admit it…I’m embarrassed that my first blog post in over 6 months is to explain a site outage. I throw myself on the mercy of the court, beg your forgiveness and vow to do better. Now, on to our feature presentation.
So, What Happened?
As many of you no doubt noticed, CPO went offline yesterday somewhere between 12:00 and 1:00 pm PST. It came back to life this morning around 4:30 am. First, I wish to apologize to all loyal CPO users for this inconvenience. I know how earth shattering it can be to rely upon a web service and then one day find out it’s GONE! So, I’m very sorry this outage occurred and I will explore ways to keep this from happening in the future.
Most of you will know this already but I’ll say it anyhow…No data was lost – none, zero, zilch. The database is intact and functioning fine. One of my other web properties, StuffSafe.com , was picked up by Lifehacker on Tuesday afternoon and traffic has spiked through the roof since then. I’m working with my hosting company to determine the exact cause of the outage but my suspicion is that there were just too many simultaneous authentication requests to the database server attached to my cheap-ass hosting account.
“Wait!”, you say. “What does StuffSafe have to do with a CPO outage?”
Well, both sites (and a few others) are hosted on the same account so the traffic spike to StuffSafe brought down everything. (Gasp from the audience and then…pin drop silence.)
“Hmmm, not very good infrastructure planning is it, Jeff.”
Yes, you would be right about that – given unlimited resources or at least a profitable business model, neither of which CPO has right now. What CPO does have in the way of resources is time and the good will of its users, but not cash.
“Ok, enough excuses. How will you keep this from happening in the future?”
I have one idea. Move StuffSafe.com to its own cheap-ass hosting account and if it spikes again, at least it won’t bring down everything else. But consider this, StuffSafe has averaged less than 500 page views per day for almost 2 years. CPO averages about 5,000 page views per day. My other 3 sites combined barely even register since I’m not actively promoting them right now. On a typical day, my hosting account deals with around 5,500 page views which is not taxing in the least.
Short of offloading a couple of sites to other hosting accounts, I’m not sure what else can be done at this point. I’m open to suggestions if some of you have dealt with this problem before – specifically, large traffic spikes on cheap hosting accounts coupled with the inability to afford a more robust infrastructure.
Again, I apologize for the downtime and the heart failure. Thanks for reading.
Jeff
First, allow me to apologize for the long delay between posts. I've been trying to be responsive to the forum posts that have been coming in while also picking away at some new features.
Anyway, the whole point of this post is to simply say that invoice editing now works as it should. A bug that prevented an accurate invoice total while editing an invoice has been haunting CPO for the past 2 weeks. I believe this problem has been fixed but, of course don't hesitate to let me know if you experience problems.
I appreciate everyone's patience as this problem was sorted out.
Thanks for reading.
CPO user SebyM was kind enough to alert me to some pretty significant problems with the invoice editing features. Here's what's happening...
I've looked into this bug today and found that it's a bit of a monster. There is so much code involved and not all of it is really clean. So, my thought right now is that this will take me through the weekend to fix properly. Until next week, don't plan on doing any serious edits to invoices or you may wind up having to delete them and start over.
Ok, now that the confession is out of the way, I'd like to express a tremendous amount of appreciation to a few bug watchers. Yanick Rochon, Maurer Sebastian and Greg Manset - you guys are terrific! Thanks a million for sticking with CPO and taking time out of your busy day to help me identify problems and suggest great improvements.
CPO has grown much faster than I ever could have imagined and, right now, I'm scrambling a bit to keep up. It's a pleasure to have some users who will graciously point out problems without just giving up and leaving.
Thanks so much, guys. I hope I can do something nice for you one of these days soon.
Thanks for reading.
Jeff
So I've had a couple of questions recently concerning IE support on CreativePro Office. Currently, the layout breaks in IE 6 and 7 and there are some JavaScript issues with IE as well - surprise, surprise! And CreativePro Office hasn't even been tested on Safari yet.
Yes, I do intend to support both Safari and IE (6 and 7) in the near future. So, what's the holdup? Well first of all, CPO is in beta (some might even say alpha) release which means things are changing and changing daily. Also, when building any web app, I prefer to work exclusively in Firefox as do most folks. Once the layout and JavaScript behaviors are nailed down in FF and I'm happy, then I know how things are supposed to work. I've found that testing in multiple browsers as I develop is a massive waste of time because the testing scenario usually goes something like this:
So until users are satisfied with a stable release of CPO, plan on using CreativePro Office with Firefox on a Mac or PC. I'm sorry if this presents an inconvenience and look for enhanced browser support some time in May of 2007.
Thanks for reading.
Jeff
OK, here we go. The CreativePro Office beta officially launches today - no more putting it off. I missed my original launch date by 2 months but a lot of good stuff has happened in that time...