-<h2>Important Notes for release 2.3.17.</h2>\r
-\r
-<h4>New global flags in config.php (config-default.php):</h4>\r
-/*<br>\r
- Choose Exchange Rate Provider<br>\r
- Default is ECB for backwards compatibility<br>\r
-*/<br>\r
-<span style="font-weight: bold;">$xr_providers = array("ECB", "YAHOO", "GOOGLE", "BLOOMBERG");<br>\r
-$dflt_xr_provider = 0;<br>\r
-<br>\r
-</span>/*<br>\r
- Set to true when remote service is authoritative\r
-source of exchange rates, and can be stored automatically without<br>\r
- manual edition. Otherwise exrate is stored on first new currency transaction of the day.<br>\r
-*/<br>\r
-<span style="font-weight: bold;">$xr_provider_authoritative = false;<br>\r
-</span><h2>Important Notes for release 2.3.16.</h2>\r
-<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>\r
-<h4>New global flags in config.php (config-default.php):</h4>\r
-/* default print orientation. 0 = Portrait, 1 = Landscape */<br>\r
- <span style="font-weight: bold;">$def_print_orientation\r
-= 0;</span><br>\r
-<h2>Important Notes for release 2.3.13.</h2>\r
-<h4>New global flags in config.php (config-default.php):</h4>\r
-/* No check on edit conflicts. Maybe needed to be set to 1 in certains\r
-Windows Servers */<br>\r
- <span style="font-weight: bold;">$no_check_edit_conflicts\r
-= 0;</span><br>\r
-<h2>Important Notes for release 2.3.12.</h2>\r
-<h4>New global flags in config.php (config-default.php):</h4>\r
-/* <br>\r
- Display a dropdown select box for\r
-choosing Company to login if false.<br>\r
- Show a blank editbox only if true where\r
-the Company NickName<br>\r
- will have to be manually entered. This\r
-is when privacy is needed.<br>\r
-*/<br>\r
- <span style="font-weight: bold;">$text_company_selection</span> \r
-= false;<br>\r
-<br>\r
-/* Should FA hide menu items (Applications, Modules, and\r
-Actions) from the user if they don't have access to them? <br>\r
- 0 for\r
-no 1 for yes<br>\r
-*/<br>\r
-<br>\r
- <span style="font-weight: bold;">$hide_inaccessible_menu_items</span>\r
-= 0;<br>\r
-<br>\r
-/*<br>\r
- Brute force prevention.<br>\r
- $login_delay seconds delay is required\r
-between login attempts after $login_max_attemps failed logins.<br>\r
- Set $login_delay to 0 to disable the\r
-feature (not recommended)<br>\r
-*/<br>\r
- <span style="font-weight: bold;">$login_delay</span>\r
-= 30;<br>\r
- <span style="font-weight: bold;">$login_max_attempts</span>\r
-= 10;\r
-<h2><strong></strong>Important Notes for release\r
-2.3.5.</h2>\r
-Change in the behaviour of <span style="font-weight: bold; font-style: italic;">Recurrent\r
-Invoices</span>.<br>\r
-<ul>\r
-<li>Now\r
-the Last Sent day is stamped with the former Last Sent (or Begin date\r
-the first time) + months + days. Before the Last Sent day was stamped\r
-with tthe creation date (today). The Invoice date is still todays date.\r
-</li>\r
-<li>If you for some reason want to make a pause in the\r
-recurrent\r
-invoices, you can now edit the Last Sent day in the Management section\r
-of Sales tab.</li>\r
-<li>Before the days value, together with a month\r
-value, decided which day in the month the invoice was due..\r
- This\r
-does not work now. You can change the day in the\r
-month you\r
-want the recurrency to happen by setting the Last Sent day with the new\r
-day in the Management section. </li>\r
-<li>If you create a new Recurrent Invoice the Beginning date\r
-can be set to the day in the month you want the recurrencies to be due.</li>\r
-</ul>\r
-<h2>Important Notes</h2>\r
-<p>Upgrade process can be done only by administrator of the first\r
-company created during FrontAccounting installation. This person is\r
-considered as a site admin who have granted access to potentially\r
-dangerous setup options, like Setup/Software Upgrade.</p>\r
-<p>In the following description sections related to older FA\r
-versions are\r
-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\r
-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;">\r
-. Y</span>ou can skip tagged fragment safely if currently FA\r
-application is newer than the version in tag.</p>\r
-<p>Upgrade process consists of up to four stages, some of them\r
-are\r
-optional:</p>\r
-<ol>\r
-<li>\r
-<p>Application source files update </p>\r
-</li>\r
-<li>\r
-<p>Database upgrade – this step is needed only during upgrade\r
-which involves change in major application version number (e.g. from\r
-2.2.x to 2.3.x), and sometimes during upgrade from beta release to\r
-stable version. Otherwise this step can be skipped.</p>\r
-</li>\r
-<li>\r
-<p>Final cleanup – is needed when some old source files,\r
-obsoleted by new release should be removed.</p>\r
-</li>\r
-<li>\r
-<p>New features configuration – this is optional step needed\r
-for most major releases and some minor ones. </p>\r
-</li>\r
-</ol>\r
-<p style="margin-bottom: 0cm;">Before starting upgrade\r
-ensure nobody\r
-is using the application and make database backup for all companies.\r
-To be on safe side backup also old source files, especially those\r
-locally customized (if any).</p>\r
-<p>Log into admin account of first company.<strong> </strong><strong><span style="">If\r
-you use a theme other than the standard 3 (aqua, cool or default),\r
-switch to one of these before going further.</span></strong></p>\r