Thank you sooo much. It worked great!

I need to make a list pulled from a MySQL table usable for options in a drop down box.

When I put the HTML in the class (I know it should not really be there) is pulls the data and formats is correctly. It then throws it at the top of my page, before the Smarty template kicks in.

When I try to pass the results to a Smarty variable and let the template handle the HTML, it generates "Array" on the HTML output.

I am sure that I am way off base in how I am trying to do this. This is my first module. Is there a good example of the proper way to do this?

Thanks,

JMass

I do agree. Thinking of XOOPS as only a framework for user authentication and view technology I see that it really is the right platform (in PHP land anyways).

I guess I was just expecting a base of modules to start from. I do get that with XOOPS even if they are not specifically for what I need. They are a lot better than starting from scratch. One one the biggest draws of opensource is the opportunity to leverage others work and give back at the same time. I guess that this may be a great opportunity for me to do just this.

Thanks,

Jason

Thank you so much!

That is exactly what we need. I will give it a try.

Thanks again,

Jason

First of all let me say that I am very impressed with Xoops! I am a Domino developer, and have been looking for an open source platform to migrate to. Until now, nothing has come close to Domino. XOOPS however seems very well coded, powerful, and has a great user base.

My concern is in the flexability. I code mostly client centric (read user/group specific) web applications. A client logs in an is presented with only their information tailored to them. Like looking at your credit card statements online. You do not get a list of all of their customers na pick your account, you log in and get your info.

Most of XOOPS seems to be more community oriented. This is great if that is what you want to build. But that is not what I want to use it for.

Are there any modules that are more along the line of filtered content and navigation based on loggin? To begin with I know you can limit what modules can be accesses based on user/group. But would I have to create sepetate module sets for each client/user? I think that their must be a much better way. Any thoughts? Or is this a great product for only a community site?

Jason

This is a much needed snippet of code. I could see using this type of thing to build a user/group specific knowledge base of anything else user/group specific.

I wish I could help but I am not much of a PHP guru. TCP/IP I can help with, PHP no so much. But I do hack at it, and would love to see an example of this as well.

Jason

This is a much needed snippet of code. I could see using this type of thing to build a user/group specific knowledge base of anything else user/group specific.

I wish I could help but I am not much of a PHP guru. TCP/IP I can help with, PHP no so much. But I do hack at it, and would love to see an example of this as well.

Jason

Hello,

This is just to expand upon the other explanations since you asked for specifics.

Edit the hosts file on the server to include the name on the XOOPS server and 127.0.0.1 The layout will be self explanitory. This file is usually at:
WINDOWS NT - C:\WINNT\SYSTEM32\DRIVERS\ETC\HOSTS
WINDOWS 95 - C:\WINDOWS\HOSTS
WINDOWS 98 - C:\WINDOWS\HOSTS
(or do a file search for "hosts" with no extention)

Edit the hosts file on each client to resolve the name of the XOOPS server and the internal IP of it.

Either install the XOOPS system using the server's name as part of the URL in the install, or modify the mainfile.php if you already did the install with localhost.(BTW: Is their really a good reason to have this hardcoded? Every othe CMS/Portal I have used did not build refers this way. It is not a big deal but requires this type of tweaking.)

That should do it.

Jason

I likewise am in a chatty mood.....

I agree that anyone who spend so much time coding open-source code would be very proud of it. I also think that they will and should not support a fork of their work, especially if it is not a real diversion from the orig.

However, many people who are interested in open-source software are not interested in giving back. They want to gloss over the work of others, and claim it as their own.

I understand, and have been involved with, both points of view. One is about community involvement. The other is about selfishness (often called profitability).

A prime example is my use of the LEAF project. I found this project that was exactly what I needed to make a GREAT solid state firewall. I contributed what I could to doc and code (not much was needed) and even donated some cash. Then I repackaged the code, integrated it into a tight little hardware setup, and sell it for $$$. I both contribute to and take from this project. All licenses and credits are left in place, but I sure don't point those I sell this to to the homepage of this project.

The XOOPS coders seem a little defensive about their work, and rightfully so. But none of their possesiveness can stop someone from repackaging or extending their work: IBM HTTP Server (Repackaged Apache w/ SSL), e-Groupware (Repackaged PHP-Groupware), and many many more.

I really have no point to this rant, I was just feeling a little chatty.

Anyways, THANK YOU DEVELOPERS!!!!! You do so much hard work. And I appreciate it very much.

Jason

Thanks for pointing me in the right direction!

Jason