lapsa,

Not sure what your last post meant...

NOTE: On a Windows hosting system you can not set permissions the same way as you can on a nix or linux host.

You can download Filezilla, a free FTP client which will allow you to see and set permissions for a nix box.

If you are hosting your site on a Windows based server the permission system works differently.

While I can see people have gone to great lengths to help you perform a write test, perhaps it would help us help you more if you stated WHY you are wanting to perform this test, as well as providing server environment information.

Or, if you are just looking to verify if mainfile.php is not writeable, you can just enter the admin section... if mainfile.php is writeable you will see a big red warning.

It would help us would help if you can add some version info.

try changing to default theme and see if that fixes it... if so it's a theme issue... you can also try updating the module from sys system admin>modules.

hth

check line 492 & 495 in submit.php in the module root dir.

Kaotik,

Mithy showed how to call a dB based template.. Here's more info in case you are trying to create a new smarty template (that is not already in the dB)...


Using Xoops, You assign a smarty template in a PHP page using:

After you make that decleration you can add values (still in the .php page):


Now in template_name_here.html, you can use anything you have passed to the template via php (above) as well as native smarty tags & XOOPS smarty tags:


Hope that helps.

Hey James,

The Undefined index is not causing the blank page, this is a PHP5/cache & smarty (combined) issue that we have fixed for the upcoming release.

Hoping to have a Final out by the end of the month.

Hey Snow,

Unfortunately, this is not really possible for the module dev's if they adhere to using all of the available XOOPS functions.

EG: All of the 'Preferences', 'Comments', 'Notifications', and Module / Block permissions are tied to functions (and tables) from the core.

Sure it takes some time to reset the options, etc... But what I think we need to push more for is for Module Devs to use the tools that GIGOE has put together for D2 & D3 (Duplicatible) Modules. All the sudden it only takes a couple of minutes to reset the permissions when everything you need to set is available from within the module admin section (Group & Block Permissions & positioning, Prefs, etc).

Unfortunately, there is still a real lack of clarity and standards for Module Development, made worse by the current Repository problems and lack of PHP5 support in legacy modules (which can usually be fixed in a matter of minutes if you know how) etc...

While it would be nice to have all of the data related to a module within the module tables, that would essentially require a much stricter (Development) standards set, would break most, if not all current modules, if introduced into the core, and would alleviate the benifits of having core functions for developers to 'Hook' into.

So while I understand the issue you raise, I think the resolution lies in providing all of the modules Options to be accessible from within the module as opposed to trying to move the Core data/functions into Module tables.

Thoughts?

Not sure what you mean... can you elaborate? If your asking if you can display a block in the top (commonly refered to as header) portion of the page, you can, by editing your theme.html file and determining a type of block to display there. You may also need some conditional logic (if statements to check and see if the block should be displayed).

I'm not sure what you mean by 'customer block' either.. it will be easier to get help if you can be more specific.

GL

usually in a css file in the active theme directory or theme.html if the theme you are using is hardcoded.