Hello Predator,
I appreciate your new suggestion...and I tried it...but it did not work. I'm still getting "access denied". Yes, the "access denied" is only occuring in the one part of the configuration. I have total access to everything else. But, the configuration in adminmenu/xfmod/configuration still denies access. Is it possible I also need to make a change in xfmod/admin/config/config.php?

Thanks again,
Larry

Predator,
I must say you know that of which you speak. I un-installed the other xoopsforge-2.06...installed your recommended version and BOOM...access to eveything EXCEPT...configuration in adminmenu/modules/xfmod/configuration. I still get "access denied". Otherwise...it's all working...but I obviously need to get this. I very much appreciate your help and time and I feel guilty to ask...but, any ideas? I'm thinking a database problem concerning paths and or privileges. I don't think so because in your version 99% of everthing is accessible...my other install did'nt allow ANY access. Thanks again,

Larry

"P.S. Due to the development for the http://dev.xoops.org Site the Whole stuff is in english, so the german language files are not complete"--nobody's perfect haha

Hello Predator,

"You mean the xoopsforge 2.0.6 from the XoopsForge Project? This Version is old and works only with XOOPS 1.3.x [b[not[/b] XOOPS 2.0.x"--

Actually, I have installed the one from Novell that you kindly mentioned earlier and I'm still having the "access denied" show up. Do I need to configure a path or give permissions? I thought the auto install does this itself.

Thanks for your help,
Larry

Hello Predator,
First, I thank you for the very detailed answer that you have given me. I am new here and I appreciate your time. Second, I appreciate your picking up the pieces of the 2002 xoopsforge and building on it...without your work I would have nothing to look for. Finally and most importantly, THANK YOU for answering my question!

Servus,
Larry

Dear Richard(carnuke),
I very much appreciate your response. The veil of ignorance on my part has a least been lifted a little. I realize XOOPS has growing pains, however, I feel that it is important for the project as a whole to AT THE VERY LEAST have some documentation on the modules that it itself uses. For me, the XOOPS installation was EASY with NO problems whatsoever. My problem, in particular, is with Xoopsforge and it's lack of documentation. I can understand individual module developers lacking the time to make documentation, but xoopsforge is a BIG project backed by many developers from Novell(a big company itself)that showcases Xoops. This, above all, should be well documented so everyone can see what great software it is.

I understand patience is required and those who develop XOOPS do so of their own free will without being paid for it...at least in traditional form. NOONE is more disgusted by bug-filled, illogically made proprietary crapware than I. I have been burned by it more than once and the financial pain still aches in my memory. A platform such as XOOPS can be used for many things on a large scale...limited, in many respects, by hardware only. When this happens crapware vendors cannot produce competing crapware anymore and everyone wins. However, the users need to know how to use it. I am very happy to hear that documentation is coming because XOOPS deserves it.

Thanks,
Larry

Hello everyone,
A couple of days ago I posted a question asking about Xoopsforge documentation. As of yet, I have not recieved any response and I am curious. What's the BIG SECRET with Xoopsforge documentation? Is there an ugly secret, that as a newbie here, I am unaware of or is that others simply do not know the answer? If it is the first case, please ANYONE, forget the community code of silence crap that surrounds SO MANY communities when a newbie asks a SIMPLE question and enlighten me. Documentation is pretty standard stuff for a well developed system like Xoops, particularly when a company like Novell uses the platform to create the module I am seeking info on making it compatible with Xoops2 and then re-releases back to the XOOPS community. If it is the second case, then WE have a problem. Please ANYONE, let me know that I am not alone with this question and we can at least go from there. Problems do not simply go away if we play dumb and ignore them.

Thanks,
Larry

Hello,
Just joined and I must say XOOPS is certainly a breathe of fresh air...easy installation, clean interface and a solid community. However, the module I'm interested in appears to be in documentation no-mans land. Ok here I go:

I'm running apache-2.0.47, php-4.3.3 and MySQL 4.0.18 under windows xp. I've installed the core XOOPS 2.06 successfully...it's hard not to and I thank the developers for it. Anyway...I download and install xoopsforge-2.06 from Novell Forge...once again good. All is working EXCEPT when I use the admin menu and attempt to access the xfmod to configure it....I get "access denied". Now, ordinarily I would say to myself, "self this looks like you need to give MySQL more permissions"....BUT I would like to know what it says in the documentation first. Funny thing is...I can't find it. Sure the XoopsForge site has two year old documentation for unix users on their site....and Novell Forge has little to nothing on xoopsforge(only Novell Forge documentation on linux)but I need the new documentation on the Novell Forge rebuild for xoops. By the way, my only issue is the access denied notice...nothing else...everything works. Thanks for your help and the awesome software. Live long and prosper.

Ciao,
Larry