Marc-André:

As a francophone you'll find more useful the following contribution by theCat:

Classes de formulaires

In fact, this site has several excellent resources for module writers and xoopsers interested in digging behind the curtains of our favorite CMS.

Cheers.

bendell:

The module will be available to all as soon as Naish's team has it ready. Please read the newsletter WOX: in this issue's interview, Naish answers your question.

Just as you, I'm waiting eagerly.

Cheers.

amok200:

This is a weird message, since the calls mean there's an attempt to retrieve the name of a column's author, and then the name of a column, but AFAIK this call can't be made but via a file...

Of course, since you've uninstalled Soapbox, the error messages make sense: the tables don't exist anymore.

As a general measure, I'd go through the database to drop any possible table there that contains the "xoops_sb" string, and then I'd delete the files in the templates_c folder.

You can also go through your XOOPS files and search for the strings "SELECT author FROM" and "SELECT columnID, name FROM". If you find them somewhere, please let me know, for of course they don't belong there.

Other than this, I can't think what to do, since this has to do with the file admin/index.php, which the module never touches...

I'll do this. I have Soapbox installed in one of my test servers. I'll delete the module using the standard procedure, and then I'll comb the database to see if there's any remnant left. If I find anything, I'll report it here so people know.

Cheers.

cmsguy:

You can. Just have in mind that when writing a custom block, you're coding in PHP. This means that instead of having variables such as <{$xoops_url}> (please notice the dollar sign is inside the curly brackets), you should use variables such as XOOPS_ROOT_PATH. For instance:

$something = XOOPS_ROOT_PATH."/modules/name/index.php?id=".$var;

Cheers.

krayc:

I'd like to keep things compatible. However, in order to satisfy some of the petitions, I might be moved to change the database. So maybe I'll have to learn how to build an update script...

Cheers.

Hemertje:

Thanks for your comments. I think the ordering articles and columns is not that hard to accomplish. I'll try to include it in the next iteration.

I regret to say I haven't looked yet at the blocks issue, so I'll need more days to do some progress in this. I've solved a fech more glitches, but I'll wait till I have a more solid module to offer the community. So for the moment it's safer to use the module WITHOUT using the blocks.

Meanwhile, I'm about 85% finished with Wordbook, a glossary module that will allow a webmaster to define if it'll work as a single-glossary module or as as multi-glossary module. Right now I'm working on the search function, then all I'll have left to do is the ask a definition thing and a lot of cleaning up.

Cheers.

An apology is in order.

The usage of group permissions has turned out to be more complex than I expected. I have successfully assigned permissions on a column basis, but I'm at a loss when defining the blocks, because they need to scan the whole repository of articles and take out of the list those articles whose column should not be seen by the present user. The logic behind my blocks is wrecked, and I'm waiting for some kind dev to enlighten my darkness...

It would be easier, perhaps, to take out the permissions stuff and just grant view rights using the system permissions, but now this has turned into a kind of challenge, and I intend to solve it.

When? As Shakespeare said: that is the question. For the moment, I don't want to wreck more functions, so my advice would be: Soapbox is quite usable as it is, but not its blocks. When you're the webmaster, or when you give all users all rights, everything is ok, but as soon as you begin to granularize rights, things break down.

Unfortunately, I don't have yet the wits to solve this in a flash of genius, so please bear with me.

To ease a bit, I'm now creating a Soapbox clone that will act as a glossary module and that won't have category rights. I hope this will make things a bit easier and could actually give me a module easier to explain in a handbook about module making.

Again, sorry for these delays. I'm learning in order to be able to teach, and it's not always easy when you have such a backlog against you...

Cheers.

foxle:

Of course it could. My test sites all run under Win XP Pro, alhtough the hosted ones are on Linux Red Hat. No problem whatsoever due to the OS.

As you can see here, XOOPS runs on a lot of environments.

Good luck and Cheers.

If you want to host in a Win environment, it might be worth to examine Zee-Way's ZPanel.

Cheers.

Vargr:

Perhaps you might try putting your external file in a clean HTML page and then calling that page in an iframe.

Cheers.