Heh... Great thx, and sorry for silly problem...
IMHO this should be in mod dev on wiki (And lot more)...

I just added it to the kickstart guide for module development.

What more should be on the dev wiki? It's always easier to spot useful information after problems arise, so if you can give some topics, which are not exactly problems (yet) we may be able to catch it before the problems emerge.

Previusly i have problem with modyfing database when form was submited by GET method, not POST. Use of queryF insted of query. This wasn't mentioned on kickstart.

Now I'm fighting with XoopsFormClass, and stuck on creating Select :P, but still trying to figure it out.

Anyway, IMHO whole Module Development Docs shuld have more "human" readable informations about some XOOPS API's (classes) like $xoopsDB, XoopsForm, accessing XOOPS global config and module config values (how, and what can be accesed).

Now i'm begingin working on huge module for XOOPS for my site, and i want make it proper as XOOPS module, to avoid any problems in future when mooving/reinstaling/upgrading xoops. But now instead of working on my mod, i still learning whole API's and trying what is what and how it work (or why it not working). If i stuck on something else i give know on this forum :P

Anyway, once again thanx for great and fast support on forum, but i think if someone spend some time on making good Module Development Documentation, you All (dev's) will have much more time to work on XOOPS instead replaying to basic forum questions. Think about it.

Btw. Sry for my poor english

XoopsFormSelect?

I agree that more things could be explained but it is quite difficult to estimate the level needed. In general, the dev wiki is written to be a little more accessible and commented than the phpDoc generated documentation and looking at the code itself. However, the best way to find out, how things work is by reading the code - it is not the easiest way, it is not the quickest way, but it's the most rewarding way

I have a couple of questions regarding this.
If I have a form that is currently like this:

And in my xoops-version I set up

Would the correct way to replace the var in the form be:


Also another question. Do I always have to setup xoops_version like this:

Or could I cut some options out (at the moment I'm just tring to keep it simple to see if I can understand how things work)? Like this:


Thanks

1) Quote:

It depends on the context. Is this in a .php file, output with echo? Is it in a Smarty template?

If it's in a .php file, the correct syntax would be:



You might also need preceding that.

By the way, passing a file system directory name as a form input field, and using that directory for file operations, is not really secure, unless you check that the directory name is valid before using it. But maybe you're not using it that way.

2) I'm not sure what happens if you omit the title and description.

So what would be the sugested method for using it? At the moment I'm not using smarty. Only the php echo thing. Would I have to setup iniatlly vars in the php file such as:

and then use that var in the form?

Thanks for the help.