Well, what do I do? Do I go with one side of my divided opinion and go down the purely administrative point of view that it seems to have lost functionality from 3.X, it’s riddled with more bugs than it can justify being GOLD and the fact that on the face of it there is almost nothing new admin-wise that makes the job easier or do I go with my creative side and praise the new templates in CSS that allow you to customise truly to your heart’s content, the new CMS which allows you to customise widgets to your own needs and a better layout for social groups, blogs and various other aspects.
I’ll do both, starting with the former.
Why did they opt for the strictest of deadlines to get it finished. There was a month or so between Beta 4 and the near final product. It could be down to a very rapid development team, but then that doesn’t explain the volume of bugs that are being reported over at vBulletin.com in regards to trivial things that should have been spotted, or dealt with sooner.
Why did they not adopt the Valve stance and release it when it was ready. I, and I’m sure the many other vBulletin users out there would have been more than happy to sit on it for a few more months and get a highly polished product. Instead we have what is essentially a rehashed front end with nothing done to the back. It’s the same old control panel with its unintuitive open/close boxes and endless lists. Sure, it works but why is there no additions to it – it’s essentially unchanged since 3.x. Take a look at Mybb’s control panel, a free software might I add:

Just look at how much less clutter there is. The main admin menu at the top neatly divides the sections into exactly what you need followed by a sidebar with just the options from that section and if need be a tabular interface to switch between the various smaller functions.
It’s such a nicer experience going into it to change a setting than fishing around. Granted I know what I am doing now and can navigate with relative ease, but when I was new it was a constant foray of googling and searching on vBulletin.com to find the option I knew must exist, but was hidden in a torrent of lists and check boxes.
Another issue with the vB4 ACP is the random necessity of keeping functions from the old Style Manager (primarily Main CSS) when everything has been converted to the new Stylevars. I was quite confused upon first viewing why the styles would not change despite my constant changing until I found the newly updated stylevars section.
If the old themes no longer work then there is no point keeping the places in the ACP that they were used for. It’s confusing, needless and you haven’t a hope in hell of converting an old style to a new one with expending more effort than it would be to recreate it in vB4 form.
To summarise my rant there, it would seem that the main issues are that they have given 3.x a facelift while doing very little back-end to aid in administration, moderation and user interaction. Playstuff requires very little of these things on a day to day basis, but another forum I work on does and I do not envy the stream of bugs and complaints that will no doubt come in.
However, I’m not entirely upset about vBulletin 4.0. I always found the previous version to be pretty inflexible due to the tabular setup. You can change everything around it but if you removed the tables it got messy. The furthest I went in customisation was a new header and changing various style elements of the tables which gave Playstuff a very nice clean skin, perfect for our needs.
With 4.0 I am free to completely change the style of any particular template I wish and infact I had to when commissioned to recreate a 3.x skin on 4. Although it is impossible to completely re-create the original in Semantic XHTML it is possible to mimic such.
VB3.8:

4.0:

It’s this freer creative aspect that I enjoy. It’s just a shame that it is marred by the onslaught of niggles and issues that arise – even with the default theme. This isn’t always the Developer’s fault. Getting something as complicated as this to look near enough identical on all browsers (by that I don’t mean IE6) is no mean feat, and no doubt that will be a new post somewhere in the near future about the troubles had in different browsers.
I am also particularly interested in the new Content Management System (CMS) developed for the Suite. Playstuff in it’s nature is creative, and that is something that drives me and the other senior administrators to continually push forward out of our own free time and wallets. The CMS seems to fit into this creative trend by allowing us to showcase the best and brightest of our content to the visiting ‘masses’ – something that is hard to do on a forum as most of the content is locked away at least 3 clicks minimum away. When you’re a member these 3 clicks are nothing but to someone new enticing those clicks is a milestone each respectively. We’ve adopted, rare given our perspective on communities, a team defined as the Content Writers. We could give writing permission to everyone but this is not ideal. No matter how good the intention, a CMS clogged full of the little things defeats the point of a clearly defined showcase.
Back end it suffers from a clear case of ‘fit it into what we already have’ which isn’t going to fly considering what already exists was not designed for this. The CMS is squeezed into one of those awful flip-like boxes the rest of the options are hidden in and it’s very apparent that it has been shoved in there. The ACP style seems ill-fitting to the elements of the CMS and compared to the in-line editor it is down right awful. Fair enough it is the first version but it relays back to my point that the Admin CP should have been of a higher priority than it was at the cost of a couple of months.

To conclude this, front end vBulletin 4 is revamped and I dare say slightly improved – and certainly will be in the future given that all 4.0 seems to be is getting the new templates to act as the old tabular form did. However back end is a far greater disapointment, it seems useful functionality has taken a back seat over the design – form over function as it were – and it really shows.
The CMS shows promise and is already proving useful to our community. But like everything front-end it looks good, back end appears to be half finished and for a selling point advertised and now even further in competition with Invision Powered it will be interesting to see the improvements in the coming months.
I look forward to vB 4.1 in the sense that it might bring a host of new features and bug fixes, but also with a sense of dread that the templates in every skin I maintain will no doubt be changed again and require another 3 weeks of my time to salvage. Along with every other designer, and addon developer who will need to continually adjust to the changing code and design.
