OMG. Thanks, Blue. FYI, the .zip's act corrupted for Macs, too. Thank goodness the original author posted them in tar.bz.

For this module, this is the preferred filetype, as it uses a somewhat convoluted upgrade scheme, involving the use of its internal archive management. Kinda cool, really.

Can any enterprising Xoopser point me toward a recent version of the module DMS (Document Management System)? I have seen mention of a version as high as 1.91. The most recent I have in my archive is 1.2, which doesn't seem to be working. Any insight you may be able to offer would be greatly appreciated. Thanks in advance.

Andy - sorry I don't have any answers for your issue. I was hoping you could point me to where you obtained DMS 1.91. The latest version I can find is 1.2, from my own archive. Since dev.xoops.org is offline, there appears to be no easy way to get this module. Any assistance you can offer would be much appreciated. Thanks in advance.

Wow! Now that's what I call action. I'll be looking for ways to contribute, and welcoming suggestions.

I am a sysadmin / developer, and a long-term XOOPS user. Visit here for my portfolio and here to learn a bit more about my experience and qualifications.

I am a long-time user of Xoops, though as my post count will attest, more a lurker than contributor, so I assume my comments will carry less weight than perhaps they ought.

Strictly from the POV of someone who has created a large number of sites using Xoops, and someone who always found the community to be welcoming and helpful, I have to say now, that all seems to be in doubt for the future. There is more sniping, griping, hand-wringing and finger pointing than I ever expected to see.

I seriously considered throwing my hat into the ring and volunteering for a role in the future of XOOPS when the recent restructuring took place, but I didn't. If that makes me a bad person, or unveils a character flaw, that's my problem. I can't blame anyone for staying out of the fray considering the spirit that has enveloped this community, whose collective efforts are now seemingly all in jeopardy of being overshadowed by personal conflicts, old grudges and what appears to be out-and-out malice toward some.

The last thing I want is to lose Xoops. The next-to-last thing I want is to be labeled as another me-too griper, but I just had to get this off my chest. If someone can suggest a role I might take that would move this juggernaut-threatening-to-become-a-ghost-ship in a more positive direction, without exposing myself to ridicule for offering positive suggestions, I would gladly accept its mantle.

Until then, I will continue to read these posts with the same detachment I reserve for emails from old friends who have fallen and refuse to get back up.

fosterm: The path "my_trust_path/modules/protector/configs" is supposed to be a directory OUTSIDE of your web path. For example, if your XOOPS root directory exists at the path /www/xoops_root, you would create a directory, let's say, at /www/trusted_path. This secures the Protector configs from any unauthenticated access by 'casual visitors' to your site. Hope this helps.

I hate to me-too, but I am having the same problem:

Xoops 2.2.3-RC1
Apache 2.0.54
MySQL 4.1.12
PHP 4.4.0

Fields Tab in module profile yields:

Fatal error: Call to a member function on a non-object in /path-to-apache-root/html/modules/profile/admin/field.php on line 93

Any help would be much appreciated.

Thanks, Ted. Will do.

I have been able to reproduce, and subsequently fix, this problem of rendering only the last element in the form, as many times as the form has elements. When you view the form elements in the Modify tab of Formulaire, the form looks fine. Go to user side of form, and the last element in the form is repeated again and again.

Environment: Darwin > Apache 2.0.52 > MySQL 4.0.21 > PHP 4.4.0 > XOOPS 2.0.13 || 2.0.10 || 2.0.9.2 > Formulaire 3.2.2. I haven't tested it yet on XOOPS 2.2.2.

Backgrade PHP to 4.3.9, problem goes away, Formulaire works as expected. Weird.

My problem is, I need to recompile PHP with iODBC support. I used Server Logistics' CompletePHP to install PHP4 originally (4.3.9) and it uses deprecated dylib libiodbc. Current PHP wisdom sez you need to build against newer, framework-based libs. I can recompile PHP 4.4.0 no problem, but then Formulaire (on which I have come to depend... THANKS for a GREAT module, by the way) breaks.

I would be glad to help in whatever way possible (PHP recomps, debug, test, etc) to fix this issue. I have a major database port proj on hold until I can get this working. Thanks in advance for any info you may be able to pass on.