Sent you an example - don't run it, because even if you think it doesn't work, you will want to look at your queues...

I would imagine that when the new version of XOOPS comes out, I will incorporate, and maybe XOOPS will incorporate officially

I won't tell you specifically how it is done, but you can inject the POST_PAYLOAD subject with the correct BCC string to make it work. I watched a site get injected with over 500 aol email accounts. It worked like a champ, right before we purged their queue. The worst part, once the script-kiddies find out your site is open, they do it without ever hitting your site. They just send the right HTTP string with a post payload configured and your site is SPAMming the world.

That's why this contact module was invented for XOOPS. It will take care of those issues along with the proper security codes. You, the admin, control how secure your contact form is!

I develop for both, and others...but unless you are a developer, the differences can't really be appreciated. Suffice it to say that you have more initial work in planning a proper module for XOOPS that in the long-run should equate to more stable code. In Joomla, you have less up-front planning because everything is encapsulated, but you have longer debug times getting everything to work the way you want.

Joomla was Mambo -which didn't have a "huge" user base compared to others. Since becoming Joomla, it seems larger, but appearances could be deceiving. The biggest thing I notice on the surface is there is a lot more commercialization of extensions. It seems to be 50/50, but there are a lot of cool things out there to purchase, not download for free. My opinion is, Joomla is solid, and yet another CMS. Is it worth jumping over and working - don't know, that's an individual decision. The only reason I play with so many CMS's is because I am a developer first, CMS zealot second.

Okay, you brought up security. First and foremost, no PHP based CMS is without security worries. I monitor logs on a very frequent basis watching what folks try to do on my servers. Any PHP based CMS will suffer the same fate - global polution, POST-Payload injection, SQL injection, etc., etc. Unfortuantely, it is a catch-up world for most CMS. Further, for the average site sitting on todays shared environments - you can only do so much! That's why it's important to pay attention to what is going on in your logs.

Okay, enough of that - I have seen an equal amount of injection occur under Joomla and I see in XOOPS - PHPNuke get's the prize though! You want to know what the number one injection hack to any site is? BCC injection in your contact page! Number 2? SQL injection to try to steal account info - specifically administration info. Number 3? I call it /tmp ownership - but basically the script-kiddies love to try to run "wget" "curl" fetch" and "stat" on your server to copy and run commands from your server. It could be worms, it could be email exploits so they end up relaying off your site, it could be rootkits...ah, the life of a server master!

Anyway, as with anything, there are all kinds of outside influences. Don't make decisions based on the superficial. Are you really tired of the perceived bickering amoungst creative folks, or are you just ready to throw this girl away for a new one?

Good Luck with your decision!

Quote:
Then you might have noticed it was not just on the forum page...

If you mean convert the entire application phpBB to a XOOPS module, then...

It depends on the complexity, and this would be big. If the mod has it's own user authentication system. If it uses a database that can be easily merged. the coding part is also big. You can use the builtin routines of XOOPS for things like forms, database access, etc - or you can use what's in phpBB.

there are just a lot of variables, so it's not as easy as yes or no.

Nope - Quote:

Quote:

nope - there are two versions on XOOPS@IBDeeming!

for XOOPS 2.0.13.x

XOOPContact for XOOPS 2.0.13.x

for XOOPS 2.2.x

XOOPContact for XOOPS 2.2.x

XoopContact v.1.6 for XOOPS 2.2.4

Here's the problem - and it's not meant to stir any bad emotions on the topic of stable release...Just an opinion follows, nothing more...

We (VelocityWebHost) were actually going to release 2.0.13.1 with the Plesk autoinstaller and make it public doamin...why didn't we - too many bugs. Shortly thereafter, 2.0.13.2 comes out - but low and behold, we now have 2.2.0. The last release we made a package for was 2.0.9...Ensim. We later upgraded all of our servers to PLESK dedicated.

The others (Fantastico, Ensim) stopped for either similar reasons or because they saw that the base install demand was low. For instance, Plesk is all about Mambo - well, we now know where mambo is going - joomla. Don't you love the forks/rebrands/whatever?

Now, we are waiting on 2.3.0/2.4.0 - when a "stable" single release is out, I think you will begin to see more auto-installer support. The industry (hosting) is saturated, but very selective in what they choose to do. It doesn't have to make a lot of sense, ultimately it's all about marketing and dollars.

I can assure you, we will have a XOOPS package for Plesk when there is ONE XOOPS package. I think XOOPS is on the right track, but progress has to be shown...

Now, to answer the question on what it takes. It depends on the installer, but you build the install with all of the features you want, you create a script (that sets up the settings), and package it up. Most want either zip or tar. You can usually get the spec straight from the hosting panel manufacturer. If XOOPS is successful with 2.4.0 (the ultimate goal), and packagers are made and distributed, touted as the highly secure, stable release of XOOPS, you will probably see a growth bump in useage. I just shake my head everyday I see loaders for PHPNuke - not my first choice, but "yet another CMS"