We've stated elsewhere that the bug tracker is not our sole source for working through bugs. In the case of IPS4, most of the bugs reported and fixed are filtering primarily through the support system. The public tracker will be getting more attention, hopefully beginning next week. Much of this will simply be going through the tracker and marking what has already been fixed (which is a significant amount) as fixed. Our primary concern is working with customer impacting issues and these surface mostly through support escalations. The rest will be dealt with using the normal bug reporting process. From a client perspective, you shouldn't be overly concerned with the number of bugs publicly facing in the bug tracker -- many are duplicates, many are fixed and many are low-impact to be addressed. If you are having an immediate site impacting issue, please support a ticket. If you've discovered a normal bug that's not already reported, please use the bug tracker. Thanks.
I'm sorry for the confusion -- perhaps we should have clarified that this is a short-term approach. Naturally, as SOP, we don't expect you to upgrade on a whim to determine if a bug is fixed if the upgrade is going to otherwise be disruptive. In the short-term, we are working a bit differently for the beginning stages of IPS4. Because of the sheer volume of support requests, we are fixing the majority of bugs via the ticket system. Eventually, the bug tracker will be a better live indication of what's happening. Right now, our primary concern is to keep things moving - which I'm sure you can agree that we're doing relatively well. With the hundreds of requests we're fielding every day, it's just not feasible (at this very moment) to cross-reference every bug report against every ticket which again, is where most bugs are being resolved currently. We'll be shifting focus as things continue to stabilize and the bug tracker will regain better organization. In the meantime, thanks for your patience.
It's been this way for nearly a decade. If you don't renew, you're no longer considered an active client. It doesn't inhibit your ability to post feedback, bugs, etc. You're just not recognized as a client and lose access to the client lounge because... well, you're not an active client.
We have upgraded this site to 4.0.5 which rebuilds all posts, etc. -- so the background processes are still running, which is the cause for the slowdown. The other error will need to be investigated by the developers.
Feedback from development: BugBugFeature suggestion - shouldn't be an issue to do.BugYou can, through permissions, make it so people cannot upload images (thereby making it album only) and you can also turn off the ability to create albums (thereby making it image only). If this doesn't behave as expected, it would be a bug -- please file a bug report.As discussed, we agree and this will be revised - no ETA at this time.