Debaser is the module that databases all of the content for my home video server.

Multiple players? Who needs em. Just get VideoLan Client and slap the client plugin html code in a debaser 'player' and you have it. Handles all video/audio types with no need to keep track of any codecs. I even have debaser indexing my pdf collection as well launching Acrobat as a 'player' when a pdf is clicked on. VLC would handle that TV streaming too.

Desbaser is the best indexing module for media because of one major feature, BATCHLOAD! With that one ability you can really automate a looooot of tasks with linux bash scripting on the backend. Putting 3000 playlists in one at a time is what you must do with every other module out there. Not desbaser! :) Probably my favorite feature. Don't drop it ! Second fave feature is the ability to insert custom player code easily into the module.

Had to hack the crap out of it to make the interface work the way I wanted it to, simple stuff like the amount of things displayed at once and how many rows the main menu would display. I'll post more as i think of it.

Love this module. Lots of fun using it.
I feel I should like, donate for using something this nice. I never feel that way about anything usually :)

Did you ever figure out how to fix this problem? I see this module is about3 years old and I am just amazed that a pile of crap programming like this ever made it to a website. I use the bugfix indicated in the forum, however that just causes another error to appear in its place. At this point it looks like this module is dead and the author doesnt really care. I cant believe the audacity of the devs tho to put out version 1.1 and claim it has all the fixes ppl have complained about. It has the SAME errors, nothing changed! wth! 3 years and noone has bothered to upload a fixed version of this module? Thats it. Im tired of working with a dead portal project. Im going to Drupal.

Some themes are just broken. Or depend on you to customize something on your system in order to get them to work. ie WF_Matrix and Borg themes. Both made my XOOPS site go blank. Change back to a reliable theme and it works. Even the other WF themes were ok, just that one didnt work. Why? Dont know. Just make your own themes I guess. Wonder if there is a XOOPS Theme howto anywhere (goes off to look).

Short version: XOOPS devel team, write step by step docs on how to use and implement Secure Login feature of XOOPS and publish to faq or docs section of www.xoops.org.


Long version: I am a bit dissapointed and this leads to anger with the level of frustration felt by this question. The secure login feature on XOOPS is completely screwed up. I have read the threads so do not respond to me with links to another thread from this forum about this subject. Ive read it. I have been trying to impletement the SSL login (secure login) feature on my site. It is part of XOOPS preferences. You guys even wrote a php script to handle it. However, there is only 1 comment in the whole darn thing to even give you a clue on what happening in it. There isint even any documentation on how to setup the ssl portion of prefernces. Just a single line in the docs that repeats what the screen already has. I have also searched the faq, not one mention on how to implement the XOOPS secure login feature.

Also, I have seen for the past 2 years now, that people have been trying to get a normal setup procedure to get the SSL feature to work. I have not seen one single satisfied response. It usually involves adding some lines to mainfile.php to change the XOOPS url to https instead of http. Making the webmaster have to work for his CMS instead of his CMS working for him. While this may make use of SSL itself, its not making use of the XOOPS secure login feature. Thats what we want. We dont want the whole site encrypted, we dont want to hack a single php file in strange ways, we want the feature to work like it is supposed to. Just a ssl session during login, then return back to unencrypted session. There is no reason we should have to hack php software this old to make a built in feature work. It is time for someone from the XOOPS devel team to step in and explain it to us once and for all. No hacks, no maybes, no "well try this" BS. Concrete procecures, step by step. 1. 2. 3. 4. And update/write your docs for crying out loud. I mean I understand its a open source volunteer project, but geez guys, other people are gonna see and use your code and site, dont you want it complete/bug free? I find so much old stuff from years ago on here. If you had a faq that explained the complete usage of this feature, I wouldnt even be bother you with this rant.