{
$from = date2sql($from);
$to = date2sql($to);
- $sql = "SELECT ".TB_PREF."stock_master.category_id,
- ".TB_PREF."stock_category.description AS cat_description,
- ".TB_PREF."stock_master.stock_id,
- ".TB_PREF."stock_master.description, ".TB_PREF."stock_master.inactive,
- ".TB_PREF."stock_master.mb_flag,
- ".TB_PREF."stock_moves.loc_code,
- ".TB_PREF."debtor_trans.debtor_no,
- ".TB_PREF."debtors_master.name AS debtor_name,
- ".TB_PREF."stock_moves.tran_date,
- SUM(-".TB_PREF."stock_moves.qty) AS qty,
- SUM(-".TB_PREF."stock_moves.qty*".TB_PREF."stock_moves.price*(1-".TB_PREF."stock_moves.discount_percent)) AS amt,
- SUM(-IF(".TB_PREF."stock_moves.standard_cost <> 0, ".TB_PREF."stock_moves.qty * ".TB_PREF."stock_moves.standard_cost, ".TB_PREF."stock_moves.qty *(".TB_PREF."stock_master.material_cost + ".TB_PREF."stock_master.labour_cost + ".TB_PREF."stock_master.overhead_cost))) AS cost
- FROM ".TB_PREF."stock_master,
- ".TB_PREF."stock_category,
- ".TB_PREF."debtor_trans,
- ".TB_PREF."debtors_master,
- ".TB_PREF."stock_moves
- WHERE ".TB_PREF."stock_master.stock_id=".TB_PREF."stock_moves.stock_id
- AND ".TB_PREF."stock_master.category_id=".TB_PREF."stock_category.category_id
- AND ".TB_PREF."debtor_trans.debtor_no=".TB_PREF."debtors_master.debtor_no
- AND ".TB_PREF."stock_moves.type=".TB_PREF."debtor_trans.type
- AND ".TB_PREF."stock_moves.trans_no=".TB_PREF."debtor_trans.trans_no
- AND ".TB_PREF."stock_moves.tran_date>='$from'
- AND ".TB_PREF."stock_moves.tran_date<='$to'
- AND (".TB_PREF."debtor_trans.type=".ST_CUSTDELIVERY." OR ".TB_PREF."stock_moves.type=".ST_CUSTCREDIT.")";
- if (!$show_service)
- $sql .= " AND (".TB_PREF."stock_master.mb_flag='B' OR ".TB_PREF."stock_master.mb_flag='M')";
- if ($category != 0)
- $sql .= " AND ".TB_PREF."stock_master.category_id = ".db_escape($category);
- if ($location != '')
- $sql .= " AND ".TB_PREF."stock_moves.loc_code = ".db_escape($location);
- if ($fromcust != '')
- $sql .= " AND ".TB_PREF."debtors_master.debtor_no = ".db_escape($fromcust);
- $sql .= " GROUP BY ".TB_PREF."stock_master.stock_id, ".TB_PREF."debtors_master.name ORDER BY ".TB_PREF."stock_master.category_id,
- ".TB_PREF."stock_master.stock_id, ".TB_PREF."debtors_master.name";
++<<<<<<< HEAD
+ $sql = "SELECT item.category_id,
+ category.description AS cat_description,
+ item.stock_id,
+ item.description, item.inactive,
++ item.mb_flag,
+ move.loc_code,
+ trans.debtor_no,
+ debtor.name AS debtor_name,
+ move.tran_date,
+ SUM(-move.qty) AS qty,
+ SUM(-move.qty*move.price) AS amt,
+ SUM(-IF(move.standard_cost <> 0, move.qty * move.standard_cost, move.qty *(item.material_cost + item.labour_cost + item.overhead_cost))) AS cost
+ FROM ".TB_PREF."stock_master item,
+ ".TB_PREF."stock_category category,
+ ".TB_PREF."debtor_trans trans,
+ ".TB_PREF."debtors_master debtor,
+ ".TB_PREF."stock_moves move
+ WHERE item.stock_id=move.stock_id
+ AND item.category_id=category.category_id
+ AND trans.debtor_no=debtor.debtor_no
+ AND move.type=trans.type
+ AND move.trans_no=trans.trans_no
+ AND move.tran_date>='$from'
+ AND move.tran_date<='$to'
- AND (trans.type=".ST_CUSTDELIVERY." OR move.type=".ST_CUSTCREDIT.")
- AND (item.mb_flag='B' OR item.mb_flag='M')";
- if ($category != 0)
- $sql .= " AND item.category_id = ".db_escape($category);
- if ($location != '')
- $sql .= " AND move.loc_code = ".db_escape($location);
- if ($fromcust != '')
- $sql .= " AND debtor.debtor_no = ".db_escape($fromcust);
- $sql .= " GROUP BY item.stock_id, debtor.name ORDER BY item.category_id,
- item.stock_id, debtor.name";
++ AND (trans.type=".ST_CUSTDELIVERY." OR move.type=".ST_CUSTCREDIT.")";
++
++ if (!$show_service)
++ $sql .= " AND (item.mb_flag='B' OR item.mb_flag='M')";
++
++ if ($category != 0)
++ $sql .= " AND item.category_id = ".db_escape($category);
++
++ if ($location != '')
++ $sql .= " AND move.loc_code = ".db_escape($location);
++
++ if ($fromcust != '')
++ $sql .= " AND debtor.debtor_no = ".db_escape($fromcust);
++
++ $sql .= " GROUP BY item.stock_id, debtor.name ORDER BY item.category_id,
++ item.stock_id, debtor.name";
++
return db_query($sql,"No transactions were returned");
}
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
- <html><head>\r
- \r
- \r
- \r
- \r
- \r
- \r
- \r
- <meta http-equiv="CONTENT-TYPE" content="text/html; charset=iso-8859-1"><title>FrontAccounting Update</title>\r
- \r
- <meta name="GENERATOR" content="OpenOffice.org 2.4 (Linux)">\r
- <meta name="CREATED" content="0;0">\r
- <meta name="CHANGED" content="20100902;19041400"></head><body style="direction: ltr;" lang="en-US">\r
- <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\r
- Update</font></strong></h4>\r
- <h2><strong><b>1. Application files update</b></strong></h2>\r
- \r
- <p style="margin-top: 0.42cm; page-break-after: avoid;"><font face="Liberation Sans, sans-serif"><font size="4"><strong><span style="">a. Source\r
- files update</span></strong></font></font></p>\r
- \r
- <p><strong><span style="">Extract distribution\r
- zip/tar.gz file in empty directory, and copy all the files to your\r
- FrontAccounting directory overwriting old files. If it is major\r
- release upgrade you can skip next step and go directly to cleanup.</span></strong></p>\r
- \r
- <p style="margin-top: 0.42cm; page-break-after: avoid;"><strong><font face="Liberation Sans, sans-serif"><font size="4"><span style="">b. Configuration\r
- files update</span></font></font></strong></p>\r
- \r
- <p><strong><span style="">Compare new\r
- </span></strong><strong><i><b>config.default.php</b></i></strong><strong>\r
- </strong><strong><span style="">file with the\r
- old\r
- </span></strong><strong><i><b>config.php </b></i></strong><strong><span style="font-style: normal;"><span style="">and\r
- add all n</span></span></strong><strong><span style="">ew\r
- settings (if any). </span></strong>\r
- </p>\r
- \r
- <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 style="background-color: white;">The following variables has been moved from config.default.php into sys_prefs table:<br>\r
- <br>\r
- $no_zero_lines_amount = 1;<br>\r
- $show_po_item_codes = 0;<br>\r
- $accounts_alpha = 0;<br>\r
- $loc_notification = 0;<br>\r
- $print_invoice_no = 0;<br>\r
- $allow_negative_prices = 1;<br>\r
- $print_item_images_on_quote = 0;<br>\r
- <br>\r
- These values can be maintained in Setup tab -> System and GL Setup.<br>\r
- <br>\r
- The following variables has been moved from config.default.php into sys_refs table:<br>\r
- <br>\r
- $alternative_tax_include_on_docs = 0;<br>\r
- $suppress_tax_rates = 0;<br>\r
- <br>\r
- These values can be maintained in Setup tab -> Company Setup.<br>\r
- <br>\r
- The following variables has been moved from config.default.php into users table:<br>\r
- <br>\r
- $save_report_selections = 0;<br>\r
- $use_date_picker = 1;<br>\r
- $def_print_destination = 0;<br>\r
- $def_print_orientation = 0;<br>\r
- <br>\r
- These values can be maintained in Setup tab -> Display Setup or Preferences.<br>\r
- <br>\r
- Please also remove these variables from your existing config.php file</span><br>\r
- </span></span></strong><h2><strong><b>2. Database upgrade</b></strong></h2>\r
- <p><strong><span style="">This step can be\r
- skipped\r
- for small version updates i.e. when you have already installed\r
- FrontAccounting version 2.4 or later. Before database upgrade is\r
- done on all company databases backup file is created automatically to\r
- enable database restore after failure.</span></strong></p>\r
- <p><strong><span style="">After major version\r
- upgrade overwriting files in first step makes the system unaccessible\r
- for all users but site admin, who have to run upgrade procedures to\r
- update all company databases to the new version provided with the\r
- release. After logging to administrator account of first installed\r
- company go directly to Setup/Software Upgrade screen, mark all\r
- subsequent 'Install' checkboxes and press 'Upgrade System'.</span></strong></p>\r
- <p style="">If something goes wrong during\r
- upgrade, you can eventually try forced upgrade option. Forced upgrade\r
- ignores some smaller errors which can arise during upgrade due to\r
- some exotic database configuration. This is depreciated option, so\r
- first read error messages if any, try to fix signalized problems,\r
- restore databases from backup and retry normal installation. To run\r
- upgrade in forced mode check box 'Force Upgrade', and press 'Upgrade\r
- System' again.</p>\r
- <h2>3. Final cleanup</h2>\r
- <p>Remove or rename install folder in main FrontAccounting\r
- directory.\r
- </p><h2>4. New features configuration</h2>\r
- <p>During upgrade process new features are initialized to default\r
- status, and sometimes old settings are also changed to conform with\r
- new security policy. This automatic process is designed to be as\r
- neutral for end users as possible, however sometimes site or company\r
- admin intervention can be necessary to set thing after changes to\r
- their best state. Below you will find description of new settings\r
- available after upgrade.</p>\r
- \r
- <p>----------------------</p>\r
- <ul>\r
- </ul>\r
+ <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.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>
projects / fa-stable.git / commitdiff