Can have a cronjob to do it.

5,752

(6 replies, posted in Translations)

You may have to put in another parameter for RTL (right to left) rendering of text in the said languages. Please refer the comments in the lang/installed_languages.inc file.

5,753

(7 replies, posted in Translations)

If you are in a hurry, then make your own empty.po files from the latest FA repo code and grab the script from the Wki.

5,754

(2 replies, posted in Reporting)

Meanwhile just take a nice dump of the suppliers table - Adminer is quite good at it.

5,755

(11 replies, posted in Items and Inventory)

Dimensions and Tags also help segregate transactions for split-up reports.

Great Janusz. Your HG Changesets 3155 and 3157 did the job.

You can use separate database and separate prefix for the second company as they own the physical hardware and have access to the MySQL Server itself.

In fact the new install can be on a separate domain with the newest version on the same physical server and you would need to migrate the COA with no opening balances only.

5,758

(9 replies, posted in Setup)

29.30 * 0.21 = 6.153 (Stored as 6.15)

29.30 - 6.153 = 23.147

23.147 may have been stored as 23.14 in the table
23.14 + 6.15 = 29.29 -> one possibility.

Now when preparing the report (dividing factor = 1.00 - 0.21):
23.14 / 0.79 = 29.2911 rounded off to 29.29 -> second possibility.

That is how the error comes in.

The fix should be in storing the properly rounded value in the table and in small value divisions these errors make it to the hundredths position and show up.

Anyone working in a bank that uses FA type accounting system can take all the less than 1 cent values into their account and make millions on billions of transactions!

Refer Wiki Screenshot for Setup -> Company Setup -> Search checkboxes.

User Access Roles will overlap and allow one user from one school to enter details in the dimension for another school.

5,761

(1 replies, posted in Items and Inventory)

Try federated databases - first on databases on the same server.
Or just views on the item related tables form one "main" database (read/write fror items) in the other databases (read only).

In these methods, no "synch"ing will be needed.

Which version are you upgrading from?
What platform / hosting service is being used?

There is a cache issue introduced in v2.3.14 when adjusting the includes/session.inc for faillog protection (not because of faillog protection) and is a known issue for certain shared hosting that relies on numerous redirects (302 error).

Refer link for causes.

5,763

(7 replies, posted in Announcements)

First of all you are using a very old update now that FA v2.3.14 has been released.

Your issue is that you need to uncheck the Search boxes in the middle of the right side in the page Setup -> Company Setup.

The screenshot is here.

Please refer the Wiki first and trawl the forum to minimize support issues.

5,764

(2 replies, posted in Installation)

Yes this is a known issue with some shared hosting accounts especially with subdomain accounts using the redirect method.

FA v2.3.11 works in such circumstances.

The includes/session.inc file got changed to accommodate faillog and may need header session changed from private to private nocache.

Make sure that in such VPSes, the /etc/hosts file has the subdomain entry as well.

One incompatible hosting service identified is shell.gridhost.co.uk on their CentOS 5.2 VPS (read from the /etc/issue file).

If anyone finds the settings to make it work despite disabling the .htaccess file do let the users know.

5,765

(10 replies, posted in Announcements)

Attached in this post is the diff file set from FA v2.3.13 to v2.3.14 along with a single patch file as well.

The new release is equivalent to Mercurial Changeset 3153.

Kindly note that the mere extraction of this zip file is insufficient in general to perform a real update. The new config.default.php variables need to be scrutinised and appropriately inducted into the existing config.php file. Any database changes between the standard schema of the sql/en_US-new.sql and the existing database for each company must be propagated thru with any new fields being accounted for with sensible defaults. The Upgrade page in the Wiki can be updated with user experience for each version migration.

5,766

(23 replies, posted in Wish List)

All fixes in this post have been incorporated except ed10's link request where the fix is provided here in Janusz post #18.

5,767

(3 replies, posted in Reporting)

Is this desirable to be added in the current version?

Thanks Joe, Mercurial Changeset 3143 fixed it.

5,769

(23 replies, posted in Wish List)

sales/customer_invoice.php was slated to be updated with the fix here in v2.3.14 - it appears not to have been done as yet.

Thanks Joe. Mercurial Changeset v3142 did it.

recalculate() is now a normal function in includes/current_user.inc instead of being in 2 different class files. It can be further modified to (intelligently) selectively expand only the text fields needed - possibly through an array containing boolean values in each report for allowing expansion.

Thanks Joe.
For the record, Mercurial Changeset 3150 did it.

During an inadvertant commit in Mercurial Changeset 2297 of the file update.html the encoding got changed to iso-8859-2. Please revert to iso-8859-1 in the said file as well as in both (application and install) empty.po files.

In that case, then the default page to be displayed should be Add New Quotation Form when there are no Quotations in the database - that way we need not bother about the database warning ever occurring here.

Thanks for the clarification.

In sales/includes/db/sales_order_db.inc in the function get_sales_order_header we have a few hardcoded strings:

Line 310: You have duplicate document in database

Line 317: You have missing or invalid sales document in databaseYou have missing or invalid sales document in database

In the demo company, Reports => Customers => Print Sales Quotations results in the following error:

You have missing or invalid sales document in database (type:32, number:0).

The database does not have any demo data for sales quotations - it does not degrade gracefully.

Almost all variables in reporting/inxludes/doctext.inc need to be gracefully degraded like line 40:

$this->formData['document_date'] = this->formData['ord_date'] ;

which should become

$this->formData['document_date'] = isset($this->formData['ord_date']) ? $this->formData['ord_date'] : '';

Attached is the patch file to update the reporting/repXXX.php files in synch with the unstable branch prior to the Orientation Feature induction. This will help clarify errors if any before orientation inclusion.