Well...I'm stumped. I've tried every sort of path/url possible, every CHMOD I could fathom and yet it doesn't work in either module (Tiny Content or C-Jay). Oh well, would've been nice to have a WYSIWYG editor to use, lol.

Edit..just saw your reply; here's my mainfile.php:

<?php
// $Id: mainfile.dist.php,v 1.5 2003/02/12 11:36:33 okazu Exp $
// ------------------------------------------------------------------------ //
// XOOPS - PHP Content Management System //
// Copyright (c) 2000 XOOPS.org //
// <https://xoops.org/> //
// ------------------------------------------------------------------------ //
// This program is free software; you can redistribute it and/or modify //
// it under the terms of the GNU General Public License as published by //
// the Free Software Foundation; either version 2 of the License, or //
// (at your option) any later version. //
// //
// You may not change or alter any portion of this comment or credits //
// of supporting developers from this source code or any supporting //
// source code which is considered copyrighted (c) material of the //
// original comment or credit authors. //
// //
// This program is distributed in the hope that it will be useful, //
// but WITHOUT ANY WARRANTY; without even the implied warranty of //
// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the //
// GNU General Public License for more details. //
// //
// You should have received a copy of the GNU General Public License //
// along with this program; if not, write to the Free Software //
// Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA //
// ------------------------------------------------------------------------ //

if ( !defined("XOOPS_MAINFILE_INCLUDED") ) {
define("XOOPS_MAINFILE_INCLUDED",1);

// XOOPS Physical Path
// Physical path to your main XOOPS directory WITHOUT trailing slash
define('XOOPS_ROOT_PATH', '/home/burnsp2/public_html');

// XOOPS Virtual Path (URL)
// Virtual path to your main XOOPS directory WITHOUT trailing slash
define('XOOPS_URL', 'http://www.burnspot.com');

// Database
// Choose the database to be used
define('XOOPS_DB_TYPE', 'mysql');

// Table Prefix
// This prefix will be added to all new tables created to avoid name conflict in the database. If you are unsure, just use the default 'xoops'.
define('XOOPS_DB_PREFIX', 'xoops');

// Database Hostname
// Hostname of the database server. If you are unsure, 'localhost' works in most cases.
define('XOOPS_DB_HOST', 'localhost');

// Database Username
// Your database user account on the host
define('XOOPS_DB_USER', 'EDITED OUT FOR POSTING');

// Database Password
// Password for your database user account
define('XOOPS_DB_PASS', 'EDITED OUT FOR POSTING');

// Database Name
// The name of database on the host. The installer will attempt to create the database if not exist
define('XOOPS_DB_NAME', 'EDITED OUT FOR POSTING');

// Use persistent connection? (Yes=1 No=0)
// Default is 'Yes'. Choose 'Yes' if you are unsure.
define('XOOPS_DB_PCONNECT', 0);

define('XOOPS_GROUP_ADMIN', '1');
define('XOOPS_GROUP_USERS', '2');
define('XOOPS_GROUP_ANONYMOUS', '3');

if (!isset($xoopsOption['nocommon'])) {
include XOOPS_ROOT_PATH."/include/common.php";
}
}
?>

I am as stumped as you, so possible one of the developers can help out. I think they would want to know your PHP version and Server setup

Wfsections does not use spaw..:) I have a version for download at my site, but this may not be spaw related

Operating system Linux
Kernel version 2.4.20-27.7smp
Apache version 1.3.29 (Unix)
PERL version 5.8.1
PHP version 4.3.4
MySQL version 4.0.15-standard

Hmm, haven't looked at WFSections yet...really been trying all sorts of stuff out since I've only recently started working with Xoops, heh heh.

wfsections is an advanced article creation/management system with a lot of features. It was developed by a Scotsman, need I say anymore..

Oh dear....

I'm going to set it up on my testbed and see how it compares, heh.

I'm having a tiny content problem! I just moved to a new server (MtHoodHosting) and everything is working right and tiny content will show it's index page when I click on the link for it. But...I when I set it as the start module in general settings, I get a blank page.

Why is it that I can access modules/tinycontent/when I click on the link directly and all content shows correctly while in it but I can't load it as the start module now? I was able to do it before I moved to the new server. I have practically chmod'ed the whole tiny content module to 777 just to see if that would fix the problem and it doesn't.

I fixed my problem. I had to reupload several files because those files were corrupted and weren't even the right size.

Good deal! I finally solved my problems by just installing WF-Sections; seems to fit the bill quite nicely for me :)

Apart from the first two warnings, you can ignore the rest, this will not affect the editor one little bit.

I think your problem is the path to mainfile.php
Why don?t you try to short yuor "(../../../../../mainfile.php): " path?
Once this solved me a problem like yours.

Hope this helps