-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathsupport.php
109 lines (97 loc) · 7.92 KB
/
support.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
<?php
/*
Website Baker Project <http://www.websitebaker.org/>
Copyright (C) 2004-2006, Ryan Djurovich
Website Baker 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.
Website Baker 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 Website Baker; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*/
require('../../config.php');
$print_info_banner = true;
// Include WB admin wrapper script
require(WB_PATH.'/modules/admin.php');
if (LANGUAGE_LOADED) { // load languagepack
if(file_exists(WB_PATH."/modules/procalendar/languages/".LANGUAGE.".php")) { // if exist proper language mutation
require_once(WB_PATH."/modules/procalendar/languages/".LANGUAGE.".php"); // load it
} else {
require_once(WB_PATH."/modules/procalendar/languages/EN.php"); // else use english
}
}
?>
<div style="width:70%;">
<h2><?php echo $CALTEXT['SUPPORT_INFO']; ?></h2>
<h3> </h3>
<h3>Options</h3>
<p>The basic options you can set for an event are:
<ul>
<li><strong>Start date:</strong> the day the event starts. This may be the only day, if it's a one-day event.</li>
<li><strong>Name:</strong> the name or title of the event.</li>
<li><strong>Category:</strong> the category or type event, for example workshop, training, meeting, conference. You can add unlimited categories in the Settings. After that, you can select the category of your choice when entering the data for an event.</li>
<li><strong>Visibility:</strong> you can set the event to a public or a private status. When set to public, every site visitor can view the event. When set to private, only logged in visitors can view it.</li>
<li><strong>Description:</strong> this is the description of the event, created in a full WYSIWYG editor field.</li>
</ul>
<p><strong>Event start date & end date:</strong> The options offer the possibility to use either a start date, or use both a start date and an end date. If you will have only one-day events, obviously there's no need to use end dates. If you have events that span multiple days, you can set the option to use both start and end dates. If you set the option for both start and end dates, you can still use only the start date field if you like. If the end date field is left empty in the backend, the field title won't be visible on the website. It's best to use the date picker for entering a date, otherwise you may enter an end date that's earlier then the start date. Using the date picker will prevent that.</p>
<p><strong>Event times:</strong> You may choose to add times to your start and end dates. If you choose to use times, time fields will be available when entering a new event. However, you are aloowed to leave them empty if you like. Leaving a time field empty or setting it to 00:00 will prevent it from being visible on the website. So you can set the option to Use Times, but not actually using the time fields when entering an event, if you like.</p>
<hr />
<h3>Custom Fields</h3>
<p>You can add up to 9 extra input fields to the calendar settings. They are called custom fields and appear as extra input fields when entering the information for a new event. The input from the backend is shown on the frontend, in the context you set in the custom field template. There are several types of custom fields:</p>
<ul>
<li><strong>Text field:</strong> a single line of information, typically used for a few words or a single sentence.</li>
<li><strong>Text area:</strong> multiple lines of information,typically used for small texts consisting of several sentences.</li>
<li><strong>WB link:</strong> a link to another WB-page on the same website.</li>
<li><strong>Image:</strong> an image you can upload or refer to in the Media section. The image may be automatically resized to the maximum width or height you set in the first option on the Custom Fields page.</li>
</ul>
<p>You are free to use any of the 9 available custom fields by setting the type, and modifying the field template. Only custom fields that are "switched on" by setting the type, will be available when entering a new event. You can set the field name to anything you like, and change the field template to your liking. </p>
<p>The default field templates are:</p>
<p><strong>Text field</strong> / <strong>Text area</strong><br />
<code><div class="field_line"> <br />
<div class="field_title">[CUSTOM_NAME]</div> <br />
[CUSTOM_CONTENT] <br />
</div></code></p>
<p><strong>WB link</strong><br />
<code><div class="field_line"> <br />
<a href="[wblink[CUSTOM_CONTENT]]">[CUSTOM_NAME]</a> <br />
</div> </code></p>
<p><strong>Image</strong><br />
<code><div class="field_line"><br />
<img src="[CUSTOM_CONTENT]" border ="0" alt="[CUSTOM_NAME]" /> <br />
</div></code> </p>
<hr />
<h3>Template</h3>
<p>In the "master" template you can set the layout for the header and footer of the events index page, and the layout for the complete event detail page. You may use any text, HTML, or droplets in these fields.</p>
<p><strong>Header and footer</strong><br />
By default the header and footer of the events index page are empty. You can add text and HTML-code here to complete your index page. Droplet tags work fine here as well. A special ProCalendar tag you can use in the header field is [CALENDAR]. This will show a full width (within the content container, that is) visual calendar with clickable dates, above the events list.</p>
<p><strong>Post (=event detail page)</strong> <br />
The post template field may contain text, HTML, droplets and the special ProCalendar tags: [NAME], [DATE_FULL], [ACTIONTYPE], [CUSTOM1], [CUSTOM2], [CUSTOM3], [CUSTOM4], [CUSTOM5], [CUSTOM6], [CATEGORY], [CONTENT], and [BACK]. You are free to use or delete tags or move them around. The default post template is:</p>
<p><code><div class="event_details"> <br />
<h2>[NAME]</h2> <br />
<div class="info_block"> <br />
[DATE_FULL] <br />
[CUSTOM1] <br />
[CUSTOM2] <br />
[CUSTOM3] <br />
[CUSTOM4] <br />
[CUSTOM5] <br />
[CUSTOM6] <br />
[CATEGORY] <br />
</div> <br />
[CONTENT] <br />
</div> <br />
[BACK] </code></p>
<p> <strong>The combination of the custom fields and the master template offers a very flexible and powerful system to modify the calendar setup and output exactly to your wishes!</strong></p>
<hr />
<h3>Edit CSS</h3>
<p>Like many other WB modules, ProCalendar gives you the opportunity to edit the stylesheets for both frontend and backend. Make sure the CSS-files have writing permissions, otherwise your changes won't be saved.</p>
</div>
<br />
<input type="button" class="edit_button" value="<?php echo $CALTEXT['BACK']; ?>" onclick="javascript: window.location = '<?php echo WB_URL."/modules/procalendar/modify_settings.php?page_id=$page_id&section_id=$section_id"; ?>';" />
<?php
$admin->print_footer();