-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathreadme_update.html
251 lines (251 loc) · 16 KB
/
readme_update.html
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
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>Wedge Update Guide</title>
<style>
body
{
background: #444;
color: #ccc;
font: 88%/130% Arial, sans-serif;
margin: 0;
padding: 0 6px;
}
h1.forumtitle
{
letter-spacing: -1px;
color: #fdc;
}
#main_screen
{
padding: 0 40px;
}
#main_screen h2
{
font-size: 2em;
border-bottom: solid 1px #d05800;
line-height: 2em;
margin: 0 0 0.5em 0;
color: #d05800;
}
h3
{
color: #d05800;
}
#main .panel
{
padding: 1em 2em 1em 1em;
line-height: 1.6em;
}
#main h2
{
font-size: 1.5em;
border-bottom: solid 1px #d05800;
line-height: 1.5em;
margin: 0 2em 0.5em 0;
color: #d05800;
}
#main li
{
line-height: 1.6em;
font-weight: bold;
color: #555;
}
#main li ul
{
padding-bottom: 0.7em;
}
#main li li
{
font-weight: normal;
line-height: 1.6em;
}
#liftup
{
background: #fff;
color: #444;
}
#footer
{
color: #999;
padding: 8px;
}
#footer a
{
color: #ccc;
}
dt {
font-weight: bold;
margin-bottom: .1em;
color: #555;
}
dl {
margin-top: .2em;
margin-left: 2em;
margin-bottom: .5em;
}
dd {
line-height: 1.5em;
margin-left: 2em;
margin-bottom: .1em;
}
#header, #content_section, #footer_section
{
width: 90%;
margin: 0 auto;
}
a:link, a:visited
{
color: #3E5D8F;
}
a:hover
{
color: #346;
}
</style>
</head>
<body>
<div id="header"><div class="frame">
<div id="top_section">
<h1 class="forumtitle">Wedge Update Guide</h1>
</div>
<div id="upper_section" style="overflow: hidden">
<div class="user"></div>
<div class="news normaltext">
</div>
</div>
</div></div>
<div id="content"><div class="frame">
<div id="main">
<div id="liftup">
<img id="wedgelogo" src="Themes/default/images/wedgelogo.png" alt="Wedge" title="Wedge" style="float: right">
<div class="panel" style="clear: right">
<h2 id="contents">Updating your forum</h2>
<p>Thank you for deciding to update your installation of <a href="http://wedge.org/">Wedge</a>. Before you get started, please remember that there is <a href="http://wedge.org/">a place for help at wedge.org</a> if you run into any problems at all.</p>
<p>You can find the following information in this file:</p>
<ul style="list-style-type: none">
<li>» <a href="#requirements">Minimum installation requirements</a></li>
<li>» <a href="#recommendations">Recommendations for best performance</a></li>
<li>» <a href="#backups">Backing up data</a></li>
<li>» <a href="#uploadingftp">Upload files method 1: using FTP</a></li>
<li>» <a href="#Set_File_Permissions">Set file permissions</a></li>
<li>» <a href="#Run_the_upgrading_tool">Run the upgrading tool</a></li>
<li>» <a href="#webinstall">Upload files method 2: using webinstall.php</a></li>
<li>» <a href="#finishing">Finishing the update and cleaning up</a></li>
</ul>
</div>
<div class="panel">
<h2 id="requirements">Minimum installation requirements</h2>
<p>Your server must meet a few requirements to be able to run Wedge. If you are unsure as to whether your webserver meets these, please try to update anyway - it should detect any problems.</p>
<ul>
<li>Any webserver that properly supports PHP, such as <a href="http://httpd.apache.org/" target="_blank">Apache</a> or <a href="http://www.microsoft.com/iis" target="_blank">Internet Information Services (IIS)</a>.</li>
<li>
<a href="http://www.php.net" target="_blank">PHP</a> 5.2.4 or higher. The following directives are required to be set correctly in php.ini:
<ul>
<li>the engine directive must be On.</li>
<li>the <a href="http://www.php.net/sybase#ini.magic-quotes-sybase" target="_blank">magic_quotes_sybase</a> directive must be set to Off.</li>
<li>the <a href="http://www.php.net/session#ini.session.save-path" target="_blank">session.save_path</a> directive must be set to a valid directory.</li>
<li>the <a href="http://www.php.net/manual/en/ini.core.php#ini.file-uploads" target="_blank">file_uploads</a> directive must be On.</li>
<li>the <a href="http://www.php.net/manual/en/ini.core.php#ini.upload-tmp-dir" target="_blank">upload_tmp_dir</a> must be set to a valid directory.</li>
</ul>
</li>
<li>Database system <a href="http://www.mysql.com/" target="_blank">MySQL</a> 5.0.3 or higher.</li>
<li>At least 2 megabytes of storage space in the database, although more is highly recommended.</li>
<li>The database user must have at least the following privileges: SELECT, INSERT, UPDATE, DELETE, ALTER, and INDEX.</li>
</ul><br>
<h2 id="recommendations">Recommendations for best performance</h2>
<ul>
<li><a href="http://www.linux.org/" target="_blank">Linux</a> or another Unix based operating system.</li>
<li>the <a href="http://aspell.sf.net/" target="_blank">GNU Aspell</a> 0.50 or higher and <a href="http://ftp.gnu.org/gnu/aspell/dict/" target="_blank">its dictionaries</a> for spell checking functionality.</li>
<li><a href="http://httpd.apache.org/" target="_blank">Apache</a> with <a href="http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html" target="_blank">mod_rewrite</a> installed for Pretty URL support.</li>
<li>
<a href="http://www.php.net" target="_blank">PHP</a> 5.2.4 or higher, with the following set in php.ini:
<ul>
<li>the <a href="http://www.php.net/manual/en/info.configuration.php#ini.max-input-time" target="_blank">max_input_time</a> directive is set to a value of at least 30.</li>
<li>the <a href="http://www.php.net/manual/en/ini.core.php#ini.post-max-size" target="_blank">post_max_size</a> and <a href="http://www.php.net/configuration.directives#ini.upload-max-filesize" target="_blank">upload_max_filesize</a> directives set to the size of the largest attachments you wish to be able to upload.</li>
<li>the <a href="http://www.php.net/session#ini.session.use-trans-sid" target="_blank">session.use_trans_sid</a> directive set to Off.</li>
<li>the <a href="http://www.php.net/manual/en/ini.core.php#ini.memory-limit" target="_blank">memory_limit</a> directive is set to at least 8M.</li>
<li>the <a href="http://www.php.net/manual/en/info.configuration.php#ini.max-execution-time" target="_blank">max_execution_time</a> directive is set to at least 15.</li>
<li>the <a href="http://www.php.net/manual/en/ini.core.php#ini.register-globals" target="_blank">register_globals</a> directive is set to Off.</li>
<li><a href="http://www.php.net/manual/en/features.safe-mode.php" target="_blank">Safe mode</a> is disabled, or <a href="http://httpd.apache.org/docs/2.0/suexec.html" target="_blank">suEXEC</a> is enabled.</li>
</ul>
</li>
<li><a href="http://www.mysql.com/" target="_blank">MySQL</a> 5.0.3 or higher with query caching enabled.</li>
<li><a href="http://www.boutell.com/gd/" target="_blank">GD Graphics Library</a> 2.0 or higher.</li>
</ul>
<p>If your server does not meet these requirements, Wedge may not work properly.</p>
</div>
<div class="panel">
<h2 id="backups">Backing up data</h2>
<p>Before starting the update process, a backup of the live database should be taken. This protects the forum from accidental damage and any issues from updating. Although all steps are taken, and extensive testing carried out, sometimes issues develop. Therefore, having a backup is crucial. The upgrading tool can backup all database tables before it runs, however the best practice is to have a full backup available. </p>
<h3>Back up a database using PHPMyAdmin</h3>
<p>PHPMyAdmin gives the option to export a database, from the initial page, select the "Export" option and follow the instructions. Select your Wedge database. These are different based on host.</p>
<h3>Back up a database using a control panel</h3>
<p>If your hosting service provides a control panel interface, this can be used to back up a database. Selecting the "Backups" or "Backups Wizard" options should take you to a page, prompting you to back up your database. With different hosts, these options may have different titles. </p>
</div>
<div class="panel">
<h2 id="uploadingftp">Upload files method 1: manually uploading files</h2>
<p>If your server doesn't support webinstall.php than you can use an FTP client and an FTP access to upload the files to your server.</p>
<p>All you need to do is upload all of the files in this package, excluding this file itself, to your server. You should upload it to the same directory as your previous installation of Wedge. If you are given the option to "resume" uploads, make sure you do not do that - you must upload all of the files. You may wish to make sure that all of the files were uploaded, such as those in <tt>Themes/default/languages</tt>, because some FTP clients have been known to drop files.</p>
</div>
<div class="panel">
<h2 id="Set_File_Permissions">Set file permissions</h2>
<p>After the upgrade archive has been uploaded and extracted, you need to set the files' permissions. This is commonly done by use of the Unix utility <b>CHMOD</b>. The correct CHMOD value for Wedge files is either 777, 775 or 755, depending on your hosting service. There are two methods for this step, the method used depends on the hosting service that you use.</p>
<h3>Setting File Permissions With the Upgrader</h3>
<p>The Wedge upgrader can set file permissions simply and easily. Navigating to the directory where Wedge is located should redirect you to the upgrade.php file and prompt the upgrader. For example: www.yourdomain.com/forum/upgrade.php. If the upgrader detects files that need their permissions adjusted it will prompt for FTP details so it can <b>CHMOD</b> the files it requires for the upgrade. This may not work on some servers.</p>
<h3>Setting File Permissions With FTP</h3>
<p>Using a control panel or FTP client, file permissions can be changed quickly and easily. Usually, FTP programs will allow permissions to be changed by right-clicking files/directories and selecting "Properties", "Attributes" or "Permissions". The desired numerical value can be entered, or if provided, check boxes can be changed.</p>
<p>The following files and directories must be writable. Depending on how your server is set up, this could mean that they must have <b>CHMOD</b> values of 644, 664 or 666 for files, and 755, 775 or 777 for folders:</p>
<ul>
<li>/attachments</li>
<li>/avatars</li>
<li>/Plugins</li>
<li>/Smileys</li>
<li>/Themes</li>
<li>agreement.txt</li>
<li>Settings.php</li>
<li>Settings_bak.php</li>
<li>upgrade.php</li>
</ul>
<p>If the permission on your files or folders does not make them writable, the Wedge upgrader will report the problem. In that case, use your FTP client or host panel to reset the permissions for the files or folders the upgrader reports.</p>
</div>
<div class="panel">
<h2 id="Run_the_upgrading_tool">Run the updating tool</h2>
<p>The final step in updating Wedge, is to run the updating tool. Navigate to the directory where Wedge is located. It should redirect you to the upgrade.php file and prompt you to run the upgrade. In example: www.yourdomain.com/forum/upgrade.php. </p>
<p>The first page you see may request your FTP information. If you see this screen, it is because the installer found some files or folders with inadequate permissions for Wedge to run properly. If you enter your FTP information here, the installer can automatically fix these permissions for you. Please note that the path should be the same path you see in your FTP client. For example, it might be "public_html/forum". And remember, the installer will not save your FTP password anywhere.</p>
<h3>Upgrade settings</h3>
<dl>
<dt>Backup database with the prefix "backup_"</dt>
<dd>Selecting this option will get the upgrade tool to copy all data in the database before upgrading within the original database.</dd>
<dt>Maintenance Mode</dt>
<dd>Selecting this option will place the forum into maintenance mode while upgrading rather than showing errors, this is highly recommended.</dd>
<dt>Output extra debugging information.</dt>
<dd>The upgrade tool can give detailed information while performing an upgrade by selecting this option, it will aid the support team to solve any errors if they occur while upgrading.</dd>
</dl>
</div>
<div class="panel">
<h2 id="webinstall">Upload files method 2: using webinstall.php</h2>
<p>Your server may support webinstall.php. This script will automatically download Wedge to your server. This may not work on all servers and also may require providing it with FTP details.</p>
<p>The first thing you need to do is upload webinstall.php to the location of where Wedge is to exist on your server.</p>
<p>After you have finished uploading the file, point your browser to http://www.yourdomain.tld/forum/webinstall.php - where www.yourdomain.tld/forum is the URL to where you uploaded it. You should then see the webinstall interface.</p>
<p>The first page you see may request your FTP information. If you see this screen, it is because the webinstaller found some files or folders with inadequate permissions for Wedge to run properly. If you enter your FTP information here, the webinstaller can automatically fix these permissions for you. Please note that the path should be the same path you see in your FTP client. For example, it might be "public_html/forum". And remember, the webinstaller will not save your FTP password anywhere.</p>
<p>On the webinstall interface you have an option to login, this is useful for charter members to easily download early releases. You may have an option to select multiple versions of Wedge to download. It is up to you to decide which version of Wedge you wish to install. Additionally you may have options of additional languages to download.</p>
<p>After specifying these options and agreeing to the agreement, webinstall will attempt to download all Wedge files and decompress them in the same folder as webinstall.php. If successful you will be prompted to the Wedge upgrade screen. If this fails you will need to follow the process below to upload files.</p>
<p>In most cases, you'll want to have "Put the forum into maintenance mode during upgrade." checked, because it will ensure that nothing is messed with while the upgrader is working. You may also wish to check "Backup tables in your database...", which will make a backup of your old information and tables before making any changes in the database.</p>
</div>
<div class="panel">
<h2 id="finishing">Finishing the update and cleaning up</h2>
<p>Once all parts of the update have completed, check the box to remove the upgrade files from the server. If this does not work, they will need to be deleted via FTP. All upgrade files should be removed from the server once the update process is complete. These files are upgrade.php and the .sql files whose name starts with 'upgrade'. They are a major security risk if they are left on a server unattended. Once Wedge has been updated, they are no longer needed.</p>
<p>Good luck!<br>
The Wedge Team.</p>
</div>
</div>
</div>
</div></div>
<div id="footer"><div class="frame">
<div class="smalltext padding"><a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/"><img alt="Creative Commons License" style="border-width: 0; margin-bottom: 0.7em" src="http://i.creativecommons.org/l/by-sa/3.0/80x15.png"></a><br>This work is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.</div>
<div class="smalltext"><a href="http://wedge.org">Wedge</a></div>
</div></div>
</body>
</html>