Sourcecode in SysMgr/setup.skin:
1: <form method="post" action="<% response.action %>">
2: <table border="0" cellspacing="0" cellpadding="2">
3: <tr>
4: <td colspan="2" nowrap="nowrap"><strong>General</strong></td>
5: </tr>
6: <tr>
7: <td valign="top" nowrap="nowrap">Title:</td>
8: <td><% root.sys_title as="editor" size="20" %><br /><span class="small">This is the main title of your Antville installation.</span></td>
9: </tr>
10: <tr>
11: <td valign="top" nowrap="nowrap">System URL:</td>
12: <td><% root.sys_url as="editor" size="20" %><br /><span class="small">This URL will be used by Antville in the footer of various confirmation mails. You should set it to the URL of the front page of your Antville installation.</span></td>
13: </tr>
14: <tr>
15: <td valign="top" nowrap="nowrap">Front page<br />site:</td>
16: <td><% root.sys_frontSite as="editor" size="20" %><br /><span class="small">If you enter the alias of a public site here the front page of this Antville installation will display the selected site instead of the default front page.</span></td>
17: </tr>
18: <tr>
19: <td valign="top" nowrap="nowrap">Layout:</td>
20: <td><% root.layoutchooser firstOption="--- choose layout ---" %><br /><span class="small">Choose the layout to use for this Antville installation. It will also be the default layout for any newly created site.</span></td>
21: </tr>
22: <tr>
23: <td valign="top" nowrap="nowrap">e-mail:</td>
24: <td><% root.sys_email as="editor" size="20" %><br /><span class="small">Antville will use this e-mail address to send various confirmation messages (e.g. when a user registers within the front page)</span></td>
25: </tr>
26: <tr>
27: <td valign="top" nowrap="nowrap">Allow notification:</td>
28: <td><% root.sys_allowEmails as="editor" %><br /><span class="small">By enabling this option site owners can define the receipients for notification e-mails (e.g. for new or updated stories and comments or uploaded images and files)</span></td>
29: </tr>
30: <tr>
31: <td valign="top" nowrap="nowrap">Language:</td>
32: <td><% root.localechooser %><br /><span class="small">This defines the language of Antville's confirm and error messages. If you select a language that Antville doesn't know, it will display all messages in english. Whatever language you specify here will also be the default for every new site created here.</span></td>
33: </tr>
34: <tr>
35: <td nowrap="nowrap">Time zone:</td>
36: <td nowrap="nowrap"><% root.timezonechooser %></td>
37: </tr>
38: <tr>
39: <td nowrap="nowrap">Long date format:</td>
40: <td nowrap="nowrap"><% root.longdateformat as="chooser" width="20" %></td>
41: </tr>
42: <tr>
43: <td nowrap="nowrap">Short date format:</td>
44: <td nowrap="nowrap"><% root.shortdateformat as="chooser" width="20" %></td>
45: </tr>
46: <tr>
47: <td valign="top" nowrap="nowrap">Allow files:</td>
48: <td><% root.sys_allowFiles as="editor" %><br /><span class="small">Enabling this means that users can upload files.</span></td>
49: </tr>
50: <tr>
51: <td valign="top" nowrap="nowrap">Quota per site:</td>
52: <td><% root.sys_diskQuota as="editor" %> Kb<br /><span class="small">Maximum amount of disk space, which can be used for images and files per site. This does not apply for trusted sites. If left empty, then the disk space per site is not restricted.</span></td>
53: </tr>
54:
55: <% sysmgr.moduleSetup %>
56:
57: <tr>
58: <td colspan="2" nowrap="nowrap"><div class="blockSeparator"> </div><br /><strong>Creation of new sites</strong></td>
59: </tr>
60: <tr>
61: <td valign="top" nowrap="nowrap">Sites may be<br /> created by:</td>
62: <td><% root.sys_limitNewSites as="editor" %><br /><span class="small">Here you can choose who may create new sites: all registered users or just those who are "trusted" (system administrators have this right anyway).</span></td>
63: </tr>
64: <tr>
65: <td valign="top" nowrap="nowrap">Users must be<br />registered for:</td>
66: <td><% root.sys_minMemberAge as="editor" %><span class="small"> days</span></td>
67: </tr>
68: <tr>
69: <td valign="top" nowrap="nowrap">or since:</td>
70: <td><% root.sys_minMemberSince as="editor" %><span class="small"> (eg. 2002-05-25 00:00)<br />Here you can either specify the time a user has to be registered or you define a timestamp which means that only users who have registered <em>before</em> are allowed to create a site.</span></td>
71: </tr>
72: <tr>
73: <td valign="top" nowrap="nowrap">Delay between<br />creation of<br />two sites:</td>
74: <td><% root.sys_waitAfterNewSite as="editor" %><span class="small"> days<br />This is the amount of time a user has to wait before creating a new site (this doesn't affect "trusted" users or system administrators).</span></td>
75: </tr>
76:
77: <tr>
78: <td colspan="2" nowrap="nowrap"><div class="blockSeparator"> </div><br /><strong>Automatic cleanup</strong></td>
79: </tr>
80: <tr>
81: <td colspan="2" class="small" valign="top">Antville has some features that ease system administration: it can automatically clean up the accesslog, block those sites being private for too long, and it can automatically remove sites that are inactive (both features can be enabled or disabled separately below). Whatever you choose, it will be done once in 24 hours.</td>
82: </tr>
83: <tr>
84: <td valign="top" nowrap="nowrap">Enable cleanup:</td>
85: <td><% root.sys_enableAutoCleanup as="editor" %><br /><span class="small">Enabling this feature means that Antville will search for inactive or private sites once in 24 hours.</span></td>
86: </tr>
87: <tr>
88: <td valign="top" nowrap="nowrap">Start at hour:</td>
89: <td><% root.sys_startAtHour as="editor" %><br /><span class="small">Here you can define when Antville should start the cleanup process (you should choose a time when there is low traffic, e.g. at night)</span></td>
90: </tr>
91: <tr>
92: <td colspan="2" nowrap="nowrap"><div class="blockSeparator"> </div><br /><strong>Watching private sites</strong></td>
93: </tr>
94: <tr>
95: <td colspan="2" class="small" valign="top">Antville can host both public and private sites. Since private sites are accessible for members only and won't appear on the front page or in the site directory this can be a risky thing (system administrators can access those private sites, though). To ease administration Antville can automatically search for private sites hosted here and disable them being private for too long (below you can define the time span). However, please note that his does not affect sites created by "trusted" users.</td>
96: </tr>
97: <tr>
98: <td valign="top" nowrap="nowrap">Block private<br />sites:</td>
99: <td><% root.sys_blockPrivateSites as="editor" %></td>
100: </tr>
101: <tr>
102: <td valign="top" nowrap="nowrap">Warn via e-mail:</td>
103: <td><% root.sys_blockWarningAfter as="editor" size="10" %><span class="small"> days<br />Here you can define the time a site is allowed to be private before Antville will send a message to the owner telling that the site will be blocked, soon.</span></td>
104: </tr>
105: <tr>
106: <td valign="top" nowrap="nowrap">Time before<br />blocking:</td>
107: <td><% root.sys_blockAfterWarning as="editor" size="10" %><span class="small"> days<br />Choose the time between sending the warning e-mail and actually blocking a site that has been private for too long. After blocking a site its owner will receive a message that the site was blocked.</span></td>
108: </tr>
109: <tr>
110: <td colspan="2" nowrap="nowrap"><div class="blockSeparator"> </div><br /><strong>Removing inactive sites</strong></td>
111: </tr>
112: <tr>
113: <td colspan="2" class="small" valign="top">Antville can automatically remove sites that are inactive for too long. Here you can decide if you want to enable this feature, define the number of days of inactivity before Antville will send warning e-mails or finally remove inactive sites.</td>
114: </tr>
115: <tr>
116: <td valign="top" nowrap="nowrap">Remove inactive<br />sites:</td>
117: <td><% root.sys_deleteInactiveSites as="editor" %></td>
118: </tr>
119: <tr>
120: <td valign="top" nowrap="nowrap">Warn via e-mail:</td>
121: <td><% root.sys_deleteWarningAfter as="editor" size="10" %><span class="small"> days<br />Here you can define the time a site can be inactive before Antville will send an e-mail to the owner telling that the site will be removed soon.</span></td>
122: </tr>
123: <tr>
124: <td valign="top" nowrap="nowrap">Time before<br />removing:</td>
125: <td><% root.sys_deleteAfterWarning as="editor" size="10" %><span class="small"> days<br />Choose the time between sending the warning e-mail and actually removing sites that have been inactive for too long. After removing those sites their owners will receive an e-mail telling them that their site has been removed.</span></td>
126: </tr>
127: <tr>
128: <td> </td>
129: <td> <br /><% input type="submit" name="save" value="Save" %> <% input type="submit" name="cancel" value="Cancel" %></td>
130: </tr>
131: </table>
132: </form>
133:
|