I must admit to being a big fan of XOOPS for a long time but recently I've been drawn away by Drupal.

The reason?

I HATE, HATE, HATE complex templating engines (such as Smarty) that rival programming languages in their own right! PHP itself started out as a templeting engine for HTML pages ... now we have templating engines built upon templating engines. Ridiculous.

Anyway, Drupal's theming system at least gives its users the option of standard PHP templates OR a number of other systems. XOOPS is too interwoven and dependent on Smarty.

XOOPS has more cool modules but Drupal seems to be easier to develop modules for.

Other promising projects are Xaraya and eZ Publish, but they too suffer from ridiculously complex templating systems.

I only say these things because I love XOOPS and think it could be improved by eliminating its reliance on Smarty.

Just my 2c.

Probably a stupid question but is there any way to have per project permissions. I want to have something similar to phpCollab where clients log in, can see only their projects, and tasks can be assigned to them.

Is this possible?

I can only seem to set it up in such a way that clients log in and see ALL projects, regardless of whether they have anything to do with them or not.

Regards,
Brian Hay.

I had this exact problem, even on the xoops.org forums (and also registering as a new member).

I emailed Onokazu and he(she?) correctly identified the problem as "my browser not sending out HTTP_REFERER ... because I am using firewall software" (ZoneAlarm in my case).

As soon as I deactivated ZoneAlarm I could post to the forums.

Regards,
Brian Hay.

Quote:

You're a legend!! Thank you very much.

I should have known that the XOOPS developers would have thought of this.

Regards,
Brian Hay.

From a usability point of view it erks me that restricted menu functions in XOOPS are displayed to users who don't have access rights to them. For example, the "submit news" function is displayed even if you're an unregistered guest. It makes people think they CAN submit news when in fact they can't, without first registering and logging in.

Likewise, displaying blocks that are empty. For example, news articles that have NO comments still display the comments block with sorting fields and table headers. This is redundant and just doesn't make sense to me.

Is there any way to deactivate restricted and unused items?

If not, I think this feature would be important for webmasters who want to use XOOPS for corporate websites/intranets (rather than just community portal sites), that is, they want to display a clean, uncluttered corporate interface to casual visitors (potential customers) yet expose selected staff to the necessary admin functions.

Regards,
Brian Hay.