Search options (Page 154 of 246)

The $hooks->deactivate_extension() is not being called anywhere in FA and hence the drop.sql is not being executed when an extension is deactivated. The Ajax on the Web UI just looks after the tick mark in the checkbox and removes the entry in the $installed extensions arrays in the installed_extensions.php files.

The variable $no_check_edit_conflicts can now be removed from FA and the file sales/includes/sales_ui.inc can have it's last function:

function check_edit_conflicts($cartname='Items')
{
    global $Ajax, $no_check_edit_conflicts;

    if ((!isset($no_check_edit_conflicts) || $no_check_edit_conflicts==0) && get_post('cart_id') && $_POST['cart_id'] != $_SESSION[$cartname]->cart_id) {
        display_error(_('This edit session has been abandoned by opening sales document in another browser tab. You cannot edit more than one sales document at once.'));
        $Ajax->activate('_page_body');
        display_footer_exit();
    }
}

changed to:

function check_edit_conflicts($cartname='Items')
{
    global $Ajax;

    if (!empty($_SESSION[$cartname]->cart_id) && get_post('cart_id') && $_POST['cart_id'] != $_SESSION[$cartname]->cart_id) {
        display_error(_('This edit session has been abandoned by opening sales document in another browser tab. You cannot edit more than one sales document at once.'));
        $Ajax->activate('_page_body');
        display_footer_exit();
    }
}

Steps to check in a fresh FA v2.3 install on Windows XAMPP using en_US-demo.sql:
Sales => Direct Invoice => Customer => Ghostbusters
No error should crop up.

You can put in the Address in the Comments for now.

Another solution would be to make a Cash Customer and keep editing their address in it before choosing it in Direct Invoice each time.

Have a Salary Account where the $113/- Salary+Taxes of all Musicians are debited and the respective musicians accounts get credited with 89.5% (100-2-8.5) of the salaries whilst 8.5% gets credited to the Pension Plan Account and 2% gets credited to the Musicians Union Account. Also credit the GST payable Account with 5% and credit the PST Payable Account with 8%. All of this can be a single Journal Voucher probably made for each week / month / event.

Unless you have PayRoll module made and customised for your needs (Musicians payout rates, etc), QuickEntries would be a cludge of a substitute, a tad better than making a set of direct SQL executions generated from some spreadsheet (=CONCATENATE("INSERT INTO...) and possibly programmed into a trigger in MySQL. PM me for assistance in implementing the latter.

Raising a Supplier (Govt Body, Pension plans, etc) Invoice for services (withheld tax/deductions) and settlement under normal means would qualify as a Standard Operating Procedure in FA. Recurrent Invoices will need editing amounts....

Wiki-ed it.

It is possible to make all Reference fields in new element forms to be readonly. The attached screenshots are for making just one form (Direct Invoice) or all forms to have their Reference field as non-editable.

Apart from being defined in includes/ui/ui_input.inc, there are 17 files that use the function ref_row - once each. The said function is currently not used in any standard extension.

Placed on Wiki.

Dimensions are generally used for cost centres. Try Tags first before using dimensions - these are just for groups of transactions pertaining to a specific deal.

Wiki-ed it.

Short of creating an extension for your extended CRM needs with a 1:1 table mapped to an existing branch/person FA table, the non field db data method "abusing" large fields like notes will be the "documented" way out.

Use a permanent holding table (managed externally with the likes of Adminer or phpMyEdit) or a spreadsheet for your separate fields and combine them into the large FA field each time anything changes!

When companies are deleted out of order as is in practice, finding a missing prefix in the array would clash with possible non numeric table prefixes and the possiblility of restoring from a deleted company into it's original prefix.

When a new company is created, an entry is made in the config_db.php table for it. This entry contains the prefix to be used and the key for the entry need not be the same as the prefix used.

1. Create your 3 companies anew so you have 0 (Default), 1,2,3 companies.
2. Note down the config_db.php entries (backup the file).
3. Delete company with prefix 1_.
4. The entry for the company "1" is removed from the config_db.php file
5. The value of the variable $tb_pref_counter in the config_db.php will signal the next prefix - alter it as needed even temporarily so as to create your company "1" again and then revert back.