Ok, I wrote this last night but I believe it still applies... I hope this ends well
ricland, please take no offense in this and please please please try not to offend all these hardworking XOOPS dudes. It isn't that hard, you know?

---------------

Hi there, ric.

Can you please be a bit more polite? You bring many important points up, but you screw up big time bullying and barking like this . It's easy to imagine scenarios in which you are either very happy or very angry with XOOPS docs this time next year and nobody cares to read or reply to your posts due to your delivery.

Now, lemme try to give you some directions on how to get this work done (and hopefully a better understanding of what goes on here and in OSS in general)

First off, you can simply get the relevant material you need from the forums, from comments inside .php files, modules' readme files, the wiki (I've just tried to fit all the wiki based info in one big page... not very successful, but makes it easier for you anyway), mailing lists, published document(s), other information sources such as the All about XOOPS link over there. If you'd rather have this compiled, either wait for someone with enough free time to do so to volunteer or add a couple of days to your Tutorial/Manual schedule and compile it yourself.

Then you can focus on writing. You should try write material that's useful for all XOOPS's users, from UbberGeeks to AOLers and from first timers to XOOPS hackers. That is, it should ideally be a good introduction, reference, tutorial and whatnot. It's up to you to decide whether a "What is a CMS?" and/or a "Extending objects" section would fit in your doc, but rest assured that literally thousands of users will read it and some dozens will give you feedback. And a couple of people will come to you with a "Hey, I always thought you'd have to be from government to have such a chimp-like writing talent" or "Can you tell me where you live so that I can beat your dog because you said something wrong about Smarty?" attitude

One of the many factors that makes writing documentation harder: would you rather have a very well documented half-baked CMS (== lots of time to compile information scattered all around) or a secure, fast and reliable system that has a somewhat chaotic but greatly (and quickly) improving documentation? It's wonderful that some people can focus on documentation, some other (like myself) on translations, and some other on coding.

Hi there krobi

I've tried to cover a way to workaround these size limits at the wiki, under ChangingFieldSizes, you can also check the "How do i change the maximum signature length??" thread.

I don't have the time to check the html thing right now, but I'd take a look at how the sig contents are parsed (both when going in and out of the DB). But it must be said that allowing html in sigs can cause HUGE lots of problems

Hmmm gotta check wheter wakka has max page size limits, cuz it's cropping the big fat humongous page's end.

Would it be ok to copy and paste other pages contents to a big, fat, one page wiki? If so, check this first attempt at an OnePageWiki for XOOPS. If not, well... sorry

Have you double checked whether all needed files were uploaded? (I've missed this many times myself)

Have you tried updating the System module? How about going to preferences and updating general modules' cache so that your cache is cleaned?

Do you still have other unistalled modules up there that have available install icons?

Oh, now I understand it
Well, having a XOOPS running offline and then adding those users to your online site would be easy, IMHO. You'd have to create a dump of your offline users table and then add it to your working DB (obviously you'd have to take good care of your SQL, uids must be unique, etc.). Then you'd never know those passwords

Hi there
I'm not sure I understand what you want either, but these links might have something for you:
http://freshmeat.net/projects/phpmyconferences/
http://freshmeat.net/projects/paperdb/
http://freshmeat.net/projects/meetingroombookingsystem/

try "xcgallery"

That's great, thanks a lot!
I guess someday I'll follow this way to include personal greetings, like "Welcome <{$xoops_username}>, you worthless freak"

Just a quick tip, in /xoopsheadline/templates/block/xoopsheadline_block_rss.html
change
to

and you'll get a lot less XHTML errors in your main page.

The other source of Headlines related errors would be non-XHTML compliant tags embedded in RSS feeds, a tag sanitizer could solve this.