Beast wrote:
I'd like to try this hack, can you please make it available again?

I am having trouble putting a table in a forum post... it adds a heap of blank lines before the table. I know that Tiny Content can get around this, but I don't know how it does it.

Wingz wrote:
Updated wfsection in 2.0.6, and I have only one apparent problem - when wfsection is called from the menu there is just a blank page shown ('done' is shown in the browser).

However, if the entire URL is typed;
http://www.mysite.org/modules/wfsection/index.php

then the index page is shown instantly.

No other module has this problem; any ideas please? Already lost hundreds of comments in the upgrade and this is incredibly frustrating.

Anonymous wrote:
Yes its a bug and being looked into

include($agendax_path.\"/checkemail.inc.php\");

require_once './config.inc.php';
include($agendax_path.\"/checkemail.inc.php\");

include_once $agendax_path.'/gettext.php';

require_once './config.inc.php';
include_once $agendax_path.'/gettext.php';

$agendax_path = XOOPS_ROOT_PATH.'/modules/agendax';

if (!defined('XOOPS_ROOT_PATH')) {
exit();
}
$agendax_path = XOOPS_ROOT_PATH.'/modules/agendax';

if (!isset($agendax_path)) $agendax_path =XOOPS_ROOT_PATH.'/modules/agendax';
if (!isset($agendax_path)) $agendax_url = XOOPS_URL.'/modules/agendax';

require_once '../config.inc.php';

the first operator of these functions:
include(), include_once(), require(), require_once()
should not be started by variables.

I write modules, but I have NO idea, whether it is a secure one or if there are similar problems with them. Therefore, I would be very happy to get some more guidelines as to how to avoid opening security holes.

dheltzel wrote:
Excuse my relative ignorance of the XOOPS development process, but wouldn't it be helpful to release a preview, beta, RC, or whatever you want to call it, to get more eyes looking for problems? You know, the old "with enough eyes, all bugs are shallow" thing.

It's your project and I doubt my post will change the way you see things, but I like to try new code, find and fix things and feel like I'm giving something back to the community, instead of being merely a "consumer" of OSS goods.

The slow, secretive development process was what caused me to abandon XOOPS a year ago and go find another CMS. I'm back because I like the way the code base works and I see that the new releases are much improved, but I'm still a bit confounded by the dev community. Not that you don't produce good code, but that the development process is more like proprietary software than the Bazaar approach that I'm accustomed to.

I appreciate the code and the way it is licensed, but it is little wonder that so many folks are inclined to fork code, as that is the only avenue they see to make improvements and give them back to the community.