The missing feature status update (sticky thread, closed for discussion) is here:
http://www.vbulletin.com/forum/forum...feature-status
It was started in September 2012 which is probably about when I upgraded my vB4 licence to vB5 - it's so long ago I can't remember now. This was last updated by Wayne on 1st October. When we upgraded from vB3 to vB4 it was full of bugs but we learned to live with it and use it. That meant putting a lot of effort into the CMS and initially into the calendars to get them going. The CMS still takes some effort but we have a regular stream of content; but the calendar just self-populates, it's now no effort at all. We still use 4.2.2 and there's not much we can do with vB5 without both CMS and calendar, without damaging the site.
The latest alpha release of vB5 contains the CMS replacement and when I saw that I thought, "...finally, 18 months on I might be able to use the thing." I'm not expecting perfection from vB5, in fact I'd go so far as to say I'm expecting it to have bugs in it. But at least if you know where most of them are you can usually manage it.
I can't help but feel a little disappointed though that son-of-CMS has finally turned up....but with no calendar...
That statement in the missing feature status update on 1st October which as of today still says "Major feature...future release" reads as very ominous....it's been a year and a half for the alpha version of the CMS replacement to turn up in a "future release."
http://www.vbulletin.com/forum/forum...feature-status
It was started in September 2012 which is probably about when I upgraded my vB4 licence to vB5 - it's so long ago I can't remember now. This was last updated by Wayne on 1st October. When we upgraded from vB3 to vB4 it was full of bugs but we learned to live with it and use it. That meant putting a lot of effort into the CMS and initially into the calendars to get them going. The CMS still takes some effort but we have a regular stream of content; but the calendar just self-populates, it's now no effort at all. We still use 4.2.2 and there's not much we can do with vB5 without both CMS and calendar, without damaging the site.
The latest alpha release of vB5 contains the CMS replacement and when I saw that I thought, "...finally, 18 months on I might be able to use the thing." I'm not expecting perfection from vB5, in fact I'd go so far as to say I'm expecting it to have bugs in it. But at least if you know where most of them are you can usually manage it.
I can't help but feel a little disappointed though that son-of-CMS has finally turned up....but with no calendar...
That statement in the missing feature status update on 1st October which as of today still says "Major feature...future release" reads as very ominous....it's been a year and a half for the alpha version of the CMS replacement to turn up in a "future release."
Comment