forked from FrontAccountingERP/FA
-
Notifications
You must be signed in to change notification settings - Fork 2
/
update.html
326 lines (312 loc) · 18.3 KB
/
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
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html><head>
<meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1"><title>FrontAccounting Update</title>
<meta name="GENERATOR" content="OpenOffice.org 2.4 (Linux)">
<meta name="CREATED" content="0;0">
<meta name="CHANGED" content="20100902;19041400"></head><body style="direction: ltr;" lang="en-US">
<h4><strong><font color="#cc6600"><font style="font-size: 20pt;" size="5"><i>Front</i></font></font></strong><strong><font style="font-size: 20pt;" size="5">Accounting
Update</font></strong></h4>
<h2>Important Notes for release 2.4.1.</h2>
<h3>This is a preliminary FrontAccounting ERP 2.4.1 release. </h3>
This version provides a couple of new important features (in addition to all the <br>
features merged from latest 2.3.26 release), but main development effort was <br>
focused on internal architecture changes and cleanups to make future FA development <br>
easier. <br>
<br>
At the time of release most of optional extension modules available from central<br>
extensions repo has been also ported to 2.4 and should be mostly usable. Most Themes are<br>
updated and many new Themes are available.<br>
<br>
Due to deep changes made under the hood, we highly encourage all current FA 2.3 users<br>
to make test upgrades on a copy of your working installation connected to separate database<br>
filled with your real company data. This will allow us find and fix any possible<br>
upgrade issues before final 2.4 release. Please report any bugs/problems found via our <br>
Mantis Bugtracker at http://mantis.frontaccounting.com.<br>
<h3>Download instructions</h3>
In Sourceforge FrontAccounting (http://sourceforge.net/projects/frontaccounting), select <br>
Files -> FrontAccounting 2.4 ->2.4.1.<br>
<br>
For Windows users select the zip file. For all other users select the tar.gz file.<br>
<h3>Notice for certain Windows wamp servers.</h3>
Due to experienced long upgrade time for release 2.3 databases to release 2.4 on certain wamp <br>
servers, we just ask you to be patience. It might take a while, but should end successfully. <br>
<h4>New global flags in config.php (config-default.php):</h4>
/* Optional popup search enabled if this is true. $max_rows_in_search = 10 <br>
is used for maximum rows in search */<br>
<span style="font-weight: bold;">$use_popup_search = true;</span><br>
<span style="font-weight: bold;">$max_rows_in_search = 10;</span><br>
<h2>Important Notes for release 2.3.22.</h2>
<h4>New global flags in config.php (config-default.php):</h4>
/* Show average costed values instead of fixed standard cost */ In Enventory Valuation Report.<br>
<span style="font-weight: bold;">$use_costed_values = 0;</span><br>
<br>
/* Print Item Images on Sales Quotations. Set to 1 if so. */<br>
<span style="font-weight: bold;">$print_item_images_on_quote = 0;</span><br>
<h2>Important Notes for release 2.3.21.</h2>
<h4>Crucial security patches:</h4>
This version consists of crucial security patches and this applies especially to all publicly available servers, <br>
f.i. installations which are run in not fully trusted environment like public demos, shared accounts or SAAS.<br>
<h4>New global flags in config.php (config-default.php):</h4>
/* Whether to allow sending new password by e-mail */<br>
<span style="font-weight: bold;">$allow_password_reset = false</span><h2>Important Notes for release 2.3.20.</h2>
<h4>Crucial security patches:</h4>
This version consists of crucial security patches and all guest FA
installations (I mean whenever FA is run in not fully trusted
environment) should be updtaed.<br>
<h2>Important Notes for release 2.3.17.</h2>
<h4>New global flags in config.php (config-default.php):</h4>
/*<br>
Choose Exchange Rate Provider<br>
Default is ECB for backwards compatibility<br>
*/<br>
<span style="font-weight: bold;">$xr_providers = array("ECB", "YAHOO", "GOOGLE", "BLOOMBERG");<br>
$dflt_xr_provider = 0;<br>
<br>
</span>/*<br>
Set to true when remote service is authoritative
source of exchange rates, and can be stored automatically without<br>
manual edition. Otherwise exrate is stored on first new currency transaction of the day.<br>
*/<br>
<span style="font-weight: bold;">$xr_provider_authoritative = false;<br>
</span><h2>Important Notes for release 2.3.16.</h2>
<h4>New global flags in config.php (config-default.php):</h4><span style="font-weight: bold;">/*<br> </span> Optional sorting new sales documents lines according to item code<span style="font-weight: bold;"><br>*/<br>$sort_sales_items = false;<br><br>/*<br> </span>Trial Balance opening balance presentation option.<br> When set to true past years part of opening balance is cleared.<span style="font-weight: bold;"><br>*/<br>$clear_trial_balance_opening = false;</span><h2>Important Notes for release 2.3.14.</h2>
<h4>New global flags in config.php (config-default.php):</h4>
/* default print orientation. 0 = Portrait, 1 = Landscape */<br>
<span style="font-weight: bold;">$def_print_orientation
= 0;</span><br>
<h2>Important Notes for release 2.3.13.</h2>
<h4>New global flags in config.php (config-default.php):</h4>
/* No check on edit conflicts. Maybe needed to be set to 1 in certains
Windows Servers */<br>
<span style="font-weight: bold;">$no_check_edit_conflicts
= 0;</span><br>
<h2>Important Notes for release 2.3.12.</h2>
<h4>New global flags in config.php (config-default.php):</h4>
/* <br>
Display a dropdown select box for
choosing Company to login if false.<br>
Show a blank editbox only if true where
the Company NickName<br>
will have to be manually entered. This
is when privacy is needed.<br>
*/<br>
<span style="font-weight: bold;">$text_company_selection</span>
= false;<br>
<br>
/* Should FA hide menu items (Applications, Modules, and
Actions) from the user if they don't have access to them? <br>
0 for
no 1 for yes<br>
*/<br>
<br>
<span style="font-weight: bold;">$hide_inaccessible_menu_items</span>
= 0;<br>
<br>
/*<br>
Brute force prevention.<br>
$login_delay seconds delay is required
between login attempts after $login_max_attemps failed logins.<br>
Set $login_delay to 0 to disable the
feature (not recommended)<br>
*/<br>
<span style="font-weight: bold;">$login_delay</span>
= 30;<br>
<span style="font-weight: bold;">$login_max_attempts</span>
= 10;
<h2><strong></strong>Important Notes for release
2.3.5.</h2>
Change in the behaviour of <span style="font-weight: bold; font-style: italic;">Recurrent
Invoices</span>.<br>
<ul>
<li>Now
the Last Sent day is stamped with the former Last Sent (or Begin date
the first time) + months + days. Before the Last Sent day was stamped
with tthe creation date (today). The Invoice date is still todays date.
</li>
<li>If you for some reason want to make a pause in the
recurrent
invoices, you can now edit the Last Sent day in the Management section
of Sales tab.</li>
<li>Before the days value, together with a month
value, decided which day in the month the invoice was due..
This
does not work now. You can change the day in the
month you
want the recurrency to happen by setting the Last Sent day with the new
day in the Management section. </li>
<li>If you create a new Recurrent Invoice the Beginning date
can be set to the day in the month you want the recurrencies to be due.</li>
</ul>
<h2>Important Notes</h2>
<p>Upgrade process can be done only by administrator of the first
company created during FrontAccounting installation. This person is
considered as a site admin who have granted access to potentially
dangerous setup options, like Setup/Software Upgrade.</p>
<p>In the following description sections related to older FA
versions are
prefixed with <span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[color
tags]</span><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">
. Y</span>ou can skip tagged fragment safely if currently FA
application is newer than the version in tag.</p>
<p>Upgrade process consists of up to four stages, some of them
are
optional:</p>
<ol>
<li>
<p>Application source files update </p>
</li>
<li>
<p>Database upgrade – this step is needed only during upgrade
which involves change in major application version number (e.g. from
2.2.x to 2.3.x), and sometimes during upgrade from beta release to
stable version. Otherwise this step can be skipped.</p>
</li>
<li>
<p>Final cleanup – is needed when some old source files,
obsoleted by new release should be removed.</p>
</li>
<li>
<p>New features configuration – this is optional step needed
for most major releases and some minor ones. </p>
</li>
</ol>
<p style="margin-bottom: 0cm;">Before starting upgrade
ensure nobody
is using the application and make database backup for all companies.
To be on safe side backup also old source files, especially those
locally customized (if any).</p>
<p>Log into admin account of first company.<strong> </strong><strong><span style="">If
you use a theme other than the standard 3 (aqua, cool or default),
switch to one of these before going further.</span></strong></p>
<h2><strong><b>1. Application files update</b></strong></h2>
<p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4"><strong><span style="">a. Source
files update</span></strong></font></font></p>
<p><strong><span style="">Extract distribution
zip/tar.gz file in empty directory, and copy all the files to your
FrontAccounting directory overwriting old files. If it is major
release upgrade you can skip next step and go directly to cleanup.</span></strong></p>
<p style="margin-top: 0.42cm; page-break-after: avoid;"><strong><font face="Liberation Sans, sans-serif"><font size="4"><span style="">b. Configuration
files update</span></font></font></strong></p>
<p><strong><span style="">Compare new
</span></strong><strong><i><b>config.default.php</b></i></strong><strong>
</strong><strong><span style="">file with the
old
</span></strong><strong><i><b>config.php </b></i></strong><strong><span style="font-style: normal;"><span style="">and
add all n</span></span></strong><strong><span style="">ew
settings (if any). </span></strong>
</p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.2beta]</span></span></strong></p>
<p><strong> <span style="">$show_users_online
= 0;</span></strong></p>
<p><strong> <span style="">$def_print_destination
= 0;</span></strong></p>
<p><strong><span style="">$dflt_date_fmt=0;</span></strong></p>
<p><strong><span style="">$dflt_date_sep=0;</span></strong></p>
<p><strong><span style="">$table_style,table_style2
changed</span></strong></p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.3beta]</span></span></strong></p>
<p><strong> <span style="">$alternative_tax_include_on_doc=0;</span></strong></p>
<p><strong><span style="">$suppress_tax_rates
= 0;</span></strong></p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.3RC1]</span></span></strong><strong> </strong>
</p>
<p><strong><span style="">Application version
information and a couple of other private FA variables are stored in
</span></strong><strong><i><b>version.php</b></i></strong><strong>
</strong><strong><span style="">file. The
application version displayed in footer is defined in $version
variable unless this is set in config.php file. If you want current
release version to be displayed on every FA update just remove or
comment out $version variable in </span></strong><strong><span style="font-style: normal;"><span style="">config.php</span></span></strong><strong><span style="">.</span></strong></p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.3RC2]</span></span></strong></p>
<p><strong> <span style="">$save_report_selections
= 0; // A value > 0 means days to save the
report selections.</span></strong></p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.3]</span></span></strong></p>
<p><strong> <span style="">$save_po_item_codes
= 0; // show item codes on purchase
order </span></strong></p>
<p><strong><span style="">$def_print_destination
= 0; // default print destination. 0 = PDF/Printer, 1 = Excel</span></strong></p>
<p><strong><span style="">$alternative_tax_include_on_docs
= 0; // 1 = print Subtotal tax excluded, tax and Total tax
included</span></strong></p>
<p><strong><span style="">$suppress_tax_rates
= 0; // suppress tax rates on documents. 0 = no, 1 = yes.</span></strong></p>
<strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"></span></span></strong><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"></span></span></strong>
<h2><strong><b>2. Database upgrade</b></strong></h2>
<p><strong><span style="">This step can be
skipped
for small version updates i.e. when you have already installed
FrontAccounting version 2.3.1 or later. Before database upgrade is
done on all company databases backup file is created automatically to
enable database restore after failure.</span></strong></p>
<p><strong><span style="">After major version
upgrade overwriting files in first step makes the system unaccessible
for all users but site admin, who have to run upgrade procedures to
update all company databases to the new version provided with the
release. After logging to administrator account of first installed
company go directly to Setup/Software Upgrade screen, mark all
subsequent 'Install' checkboxes and press 'Upgrade System'.</span></strong></p>
<p style="">If something goes wrong during
upgrade, you can eventually try forced upgrade option. Forced upgrade
ignores some smaller errors which can arise during upgrade due to
some exotic database configuration. This is depreciated option, so
first read error messages if any, try to fix signalized problems,
restore databases from backup and retry normal installation. To run
upgrade in forced mode check box 'Force Upgrade', and press 'Upgrade
System' again.</p>
<h2>3. Final cleanup</h2>
<p>Remove or rename install folder in main FrontAccounting
directory.
</p>
<p>After upgrade is installed you can remove files obsoleted by
new
FrontAccounting version. Also old, unused settings <span style="font-style: normal;"><span style="">can
be removed from </span></span><i><b>config.php</b></i><span style="font-style: normal;"><span style="">
file.</span></span></p>
<p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4">a.
Source files cleanup</font></font></p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.2beta]</span></span></strong></p>
<p><strong><span style=""><span style="background: transparent none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">/includes/reserved.inc
– removed.</span></span></strong></p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.1]</span></span></strong><strong> </strong>
</p>
<p><strong><span style="">/admin/db/v_banktrans.inc
- removed</span></strong></p>
<p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4"><span style="font-style: normal;"><span style="">b.
Config.php cleanup </span></span></font></font>
</p>
<p><strong><span style=""><span style="background: rgb(235, 97, 61) none repeat scroll 0% 50%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;">[<FA
2.2RC1]</span></span></strong><strong> </strong>
</p>
<p><strong><span style="">$security_headings,
$security_groups arrays – moved to database (see Access Setup) </span></strong>
</p>
<p><strong><span style="">$def_app – moved
to user configuration in database.</span></strong></p>
<p><strong><span style="font-style: normal;"><span style="">$version
– moved to </span></span></strong><strong><i><b>version.php</b></i></strong><strong><span style="font-style: normal;"><span style="">
file. Remove</span></span></strong></p>
<h2>4. New features configuration</h2>
<p>During upgrade process new features are initialized to default
status, and sometimes old settings are also changed to conform with
new security policy. This automatic process is designed to be as
neutral for end users as possible, however sometimes site or company
admin intervention can be necessary to set thing after changes to
their best state. Below you will find description of new settings
available after upgrade.</p>
<p><br>
<br>
</p>
<p>----------------------</p>
<ul>
</ul>
</body></html>