4
Quote:
tonyo wrote:
I just assumed (as any reasonable person might) that I was being offered the latest version of the community packs with the latest version of Xoops.
[A group chuckle goes here]
Yes, that would seem reasonable, but welcome to the confusing world of Xoops.
1. There is a fork of XOOPS that is supposedly abandoned. I say "supposedly" because there are still many people using that fork that need to be supported and because there is a recent update to it that takes care of some security issues This is good on the one hand, but makes it seem all the more a viable and recent release on the other hand. So, here is confusing XOOPS rule #1: the abandoned fork has more recent release numbers. So, 2.2x is the bad fork while 2.0x is the good fork. So, for starters make sure you are using 2.0.17 or 2.0.17.1 or 2.0.18.
2. The original forum of choice for XOOPS was Newbb. The forum of choice is now CBB. However, CBB must go into a module directory calle "newbb" on your host server. So, the module directory is called newbb but that is no longer what you are running. CBB 3.08 is probably is one you want, even though there is a recent 4.0 that is a bit problematice. By the way, don't forget all the other files you have to upload to make CBB work. Those files take up maybe around 4 times more space than the CBB module itself. Make sense?
All of us who have stuck around through the years understand these quirks. We do NOT, however, understand how any new user is EVER supposed to "get" XOOPS under the present circumstances. It must be frustrating as hell. We talk to excess about how all this is supposed to be fixed so that we no longer drive away potential users, but the talk goes on.
A final word: XOOPS is worth the trouble if you can just tough it out through the learning curve.