2
ok - as a module developer, you define your templates in xoops_version.php like so:
$modversion['templates'][1]['file'] = 'mylinks_brokenlink.html';
$modversion['templates'][1]['description'] = '';
$modversion['templates'][2]['file'] = 'mylinks_link.html';
$modversion['templates'][2]['description'] = '';
$modversion['templates'][3]['file'] = 'mylinks_index.html';
$modversion['templates'][3]['description'] = '';
all module template files belong in the /modules/<moddir>/templates/ directory. Now when a user installs your module the templates specified in xoops_version.php will be added to the available site templates.
Quote:
"Choose a template set package to upload
Must be a tar.gz/.tar file with a valid XOOPS template set structure"
All this is trying to say is that the uploaded file needs to be in the same format as one created when clicking on the 'download' link by each template set. This is used to transport a template set from one XOOPS installation to another.
Quote:
"Zlib support must be enabled on your server"
PHP supports many optional modules, one of which is Zlib. Zlib allows you to manipulate zip archives programmatically. On a windows machine this entails opening your server's php.ini file and finding the line:
Quote:
and removing the ';' from the line. After changing the php.ini file, you may need to restart the web service to see the changes.