Search options (Page 131 of 245)

The function user_use_date_picker () is not part of core FA 2.3 but in includes/current_user.inc in FA 2.4. Assume it is part of your module.

function user_use_date_picker()
{
    return $_SESSION["wa_current_user"]->prefs->use_date_picker();
}

The function get_js_date_picker is in FA 2.3 and FA 2.4 in includes/ui/ui_view.inc.

The version of the above function in FA 2.3 uses:

$fpath = company_path().'/js_cache/'.'date_picker.js';

whilst that in FA 2.4 uses:

$fpath = user_js_cache().'/'.'date_picker.js';

This is available in the Wiki too.

The line 74 in includes/errors.inc is:

    $bt = $SysPrefs->go_debug>1 ? get_backtrace(true, 1) : array();

Try to replace it with and see:

    $bt = (($SysPrefs->go_debug > 1) ? get_backtrace(true, 1) : array());

$go_debug is defined in config.php and gets into the $SysPrefs object is all is well.
The backtrace comes in correctly.

The line 85 in the same file is:

        error_log(user_company() . ":$user:". basename($file) .":$line:$context $errstr");

Try to replace it with:

        $msg_tmp = user_company() . ":$user:". basename($file) .":$line:$context $errstr";
        error_log($msg_tmp);

The function user_company() is defined in lines 425 - 430 in includes/current_user.inc:

function user_company()
{
    global $def_coy;
    
    return isset($_SESSION["wa_current_user"]) ? $_SESSION["wa_current_user"]->company : $def_coy;
}

Make sure that the user you logged in as exists in the company's database's users table.

Convert the least count as a unit and provide price per unit. Then translate that into tax % for that item.

FA v2.3.25 was released on 2016-02-21. Since then there have been many fixes. Please use FA 2.3.25+ which was last updated on 2016-07-26.

The errors you are getting possibly arise with incompatible php settings for your later version of PHP. What is your PHP/MySQL version and what platform and version is your server on (CentOS 6, Debian 8, etc)?

The offending line 295 in gl/gl_journal.php is:

    $_SESSION['journal_items']->add_gl_item($_POST['code_id'], $_POST['dimension_id'],
        $_POST['dimension2_id'], $amount, $_POST['LineMemo']);

The class member function add_gl_item is defined in includes/ui/items_cart.inc and it was last changed on 2014-09-22, much before the release of the version you are using. The file gl/gl_journal.php was last changed on 2015-03-15 and that too hasn't changed in your version. Hence it must be a generic issue of handling $_POST array's elements and that points to the newer PHP's idiosyncracies.

If the custom cron php file is in the FA web folder then anyone from outside too can execute it. Why would you want a security vulnerability?

If you wish to directly interact with the FA's DB tables, then write your own php file and keep it outside your webroot and include the relevant files like config_db.php, includes/db/connect_db.inc and operate on them directly.

If you wish to simulate a login and perform the FA's form based operations then use php cURL to achieve it. Teaching PHP is outside the scope of this forum.

Provide an example of what you wish to achieve and in which version of FA?

I shall assume you are working on FA 2.4RC1 with all fixes till date.

As for the 4 GL Accounts issue, check their entries in the db tables for any record / field differences other than account code and name. Also check their entries in the sys_prefs table if the mischief is in it's being set as some default.

As you are using PHP7, there seems to be a sticky post in announcements that could be useful.

Counterparty is just the contra account in a transfer transaction. It can be between 2 bank accounts or even between some balance sheet entries and P&L entries like in depreciation entry transactions apart from the ones you already mentioned.

The dashboard theme must be installed
and then the dashboard extension as well
and then activated too.
Backup before installing them.

If you are upgrading,
take a backup,
then de-activate the dashboard extension,
choose a normal standard theme and
uninstall the dashboard theme and extension.
Now upgrade the FA, install the dashboard theme and extension and activate and choose them. Import your reminders selectively from your backup.

Check the same type of transactions in the demo Chart of Accounts and see what difference it makes. State FA version / build.

Kindly post links of sample templates you find missing in FA after checking to see if they are already there amongst the reports. What you expect from within FA may already be there in the Wiki. As for PHP hooks, you can fork the FA codebase and design as per your needs and submit a pull request.

@trecords: Use the latest version 2.3.25+. State your Browser/Server/Platform/PHP versions. Clear cache of browser.

@ericgroen: Clear cache of browser. Test with latest version and provide feedback.

Please check if the error still persists in the latest FA code so that it can warrant inspection. The URLs listed (amongst others) may have changed the functionality that may have cleared the error.

@joe: is this by design?