Search options (Page 155 of 247)

FA 2.3.x is designed for PHP 5 to 5.3 and a few have reported success with PHP 5.4 possibly with some mods.

In case you are testing with PHP 5.6+, please see what functions are deprecated / dropped in 5.4, 5.5 and then 5.6 and make sure you make appropriate changes / replacements.

There is no intention of the devs and myself in supporting any later versions of PHP other than 5.3 for FA v2.3.x. You are pretty much on your own here.

To assist others however, you may post your findings in a separate thread for such later PHP versions. Such findings posted in this thread will only serve to confuse end users - yes, it will make for big consultancy business...... but FA has been designed with simplicity in mind and for self service.

The code portion for activating extensions has not been touched in this fix and if it doesn't work for you now, then it never did in the first place prior to this fix as well.

@joe: Can pull it in from my repo.

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.