I use NewBB for forums on my site, and Publisher for news and editorials. They seem to offer the best performance, and consistency in coding to the current version of XOOPS.
Setup a local install and try all of them 1 at a time to get the feel for what you are looking for.
The more I know, the more I know that I really didn't wanna know.
Upgrade to 2.5.5 went without issues, I created new article and published with no errors using Rev 365.
I'll be looking around the user submission stuff and will let you know what I find. Looking forward to that option working well.
XOOPS Version XOOPS 2.5.5 PHP Version 5.3.13 mySQL Version 5.5.23-55 Server API cgi-fcgi OS Linux safe_mode Off register_globals Off magic_quotes_gpc Off allow_url_fopen Off fsockopen On post_max_size 64M max_input_time 60 output_buffering max_execution_time 30 memory_limit 128M file_uploads On upload_max_filesize 64M
The more I know, the more I know that I really didn't wanna know.
I have it running on my site without any issues so far. Currently running 2.5.4 I'm getting off my butt today to do the upgrade to 2.5.5 so I'll let you know how that goes..
The more I know, the more I know that I really didn't wanna know.
Publisher, newbb, tdmdownloads, all good choices. Here's a wild suggestion, how about integrating the smallworld social mod into the core, with FB and Twitter functionality as options?
At least a nod to social networking is called for in future efforts.
/2cents
The more I know, the more I know that I really didn't wanna know.
Its flawless with my 2.5.4 install. I'm lazy and haven't done the upgrade to 2.5.5 yet. As a temp security measure I require admin approval for registration as a fix until the upgrade.
Great work.
The more I know, the more I know that I really didn't wanna know.
Move the folders out of root. Like Flipse said there's no reason not to. More troubling than the presentation of info re: the "Trust Path" is the lack of insistence that people adjust the php.ini files correctly.
Doesn't matter where you locate the trust path if folks are able to traverse directories due to a php.ini oversight.
There's also a great example of an .htaccess file here somewhere that should come stock with the cms package.
Its always that 1 thing you overlook, or deem not required that will be the thing that gets exploited..
And yes, XOOPS is the most secure cms I've found. That doesn't mean anyone should get lazy about doing all the right things..
The more I know, the more I know that I really didn't wanna know.