Search options (Page 28 of 246)

Although the specific rep301.php has not changed in the meanwhile, some functions it directly / indirectly uses may have been changed post release in other files. No harm in putting in the post release changed files - it does not change the db in any manner and any missing sys_prefs variables entries will get auto populated. Then see if the situation changes.

An example of curly brace correction is available in another project's commit.

A migration script to automatically make these changes is here.

This is an issue since 2008 when both square and curly brackets were used interchangeably for arrays and string elements though it was the intention to sue them for separate purposes as explained at:

https://wiki.php.net/rfc/deprecate_curly_braces_array_access

Though currently in PHP 7.4, only the square braces can be used to initialise arrays and also assign to them values, the curly braces can generally be used everywhere else where the square bracket is used.

Other threads elsewhere that refer to this problem are at:
https://github.com/squizlabs/PHP_CodeSniffer/issues/2558
https://stackoverflow.com/questions/59158548/array-and-string-offset-access-syntax-with-curly-braces-is-deprecated

Check if this was a server time zone issue at the time when you tried it. This is a very old thread. Hope you have all the post release fixes in your install. Also a latest change was reverted to await v2.5 but is in mt FA24Mods folder (2019-06-24).

@x-roast: Kindly share your workaround for peer review to ensure that you are on the right track.

@joe: An alert in both instances before acceptance stating the possible ambiguity may be in order.

Which version of MySQL / PHP are you using? Later versions of MySQL may prevent blank value for salesman not to be taken as NULL and may wrongly insist in a NOT NULL field definition (with a default of 0) and strict mode enabled in the MySQL settings.  See that there is atleast one entry in the "0_salesman" table and make sure that is chosen for the new company's default salesman.

CREATE TABLE `0_cust_branch` (
...
...
`salesman` int(11) NOT NULL DEFAULT '0',
...
...

Creation of the DB would require additional privileges that the FA's DB user should have atleast for the duration of the install. Use phpMyAdmin / SQLyog / MySQL Workbench or some such MySQL client tool or just operate from the hosting control panel or the SSH terminal if you have access. Otherwise contact your hosting provider.

What platform are you having your FA hosted (Webserver / PHP / MySQL / OS) and their versions and what privileges and skills you have in manipulating them? If you are handicapped in the above skills, then take professional assistance providing a bounty on the Job Offers board.

Check if the attachment is what you need.

@joe: if acceptable, it can be placed with a checkbox in the filter fields to achieve this feature.

Banking & GL => Trial Balance
already has the drill down to the account numbers of interest links.

What drill down are you expecting beyond this?

Yes. Check if there is enough space on the report's lines to accommodate it. A memo is unlimited for all practical purposes to be contained within the space available.

First, enable the availability of the long_description field in the function get_customer_trans_details in sales/includes/db/cust_trans_details_db.inc by inserting the following line as line 23:

        item.long_description As StockLongDescription,

** @joe: the above can be implemented now **

Then put in these lines at line 166 in reporting/rep107.php:

                $c--;
                $rep->TextColLines($c++, $c, $myrow2['StockLongDescription'], -2);

If you have your Arabic fonts correctly setup to print Arabic characters in reports, all should be well.

Without Arabic Reporting fonts, some testing snapshots are attached.