201 Reply by joe

(3 replies, posted in Translations)

Hi,

You can send it to me and I will upload it to the repository maintained by @itronics.

Joe

Go to forum: Translations

202 Reply by joe

(9 replies, posted in Setup)

We had srarted this initiative many years back, but stopped it again due to scamming.

I could also see some biasing in creating such a page.

Another approach is to use this Search on the Internet:

Frontaccounting Review. This will give some objective reviews, I think.

Please be aware that this is an Open Source project, and we are all overloaded with other work too.

Joe

Go to forum: Setup

203 Reply by joe

(9 replies, posted in Announcements)

@kvvaradha

There are some initiatives to this in the Developers Forum.

Joe

Go to forum: Announcements

204 Reply by joe

(6 replies, posted in Modules Add-on's)

Itronics is responsible for the administration of the repo.
We are all responsible for updating the modules. So please will someone upgrade and send it to itronics (or me and I will relay it to itronics).

Joe

Go to forum: Modules Add-on's

205 Reply by joe

(2 replies, posted in Report Bugs here)

I will ask @itronics to look into this.

Joe

Go to forum: Report Bugs here

206 Reply by joe

(2 replies, posted in Accounts Receivable)

Hello,

The COGS account in the Service Items is only used if you buy this type of service from a vendor (supplier) and resell it to your customers.
Otherwise just ignore the COGS field.

Joe

Go to forum: Accounts Receivable

207 Reply by joe

(7 replies, posted in Accounts Receivable)

I have tried the email routines and I cannot reproduce the double emails on the last contact.
Please make a dump of the customer contacts and the branch contacts. Maybe there are something here.

Or try to elaborate with removing the customer contacts and only use branch contacts.

Try eventually emtying the internet cache.

Anybody here in the forum that can help us?

/Joe

Go to forum: Accounts Receivable

208 Reply by joe

(9 replies, posted in Announcements)

If you are up-to-date with the FA repo, you don't have to download and install the new release from SourceForge. You are already on this release.

Joe

Go to forum: Announcements

209 Reply by joe

(9 replies, posted in Announcements)

No, all repo changes are included in this release up to today. You can see all the changes in the CHANGELOG.txt.

Joe

Go to forum: Announcements

210 Topic by joe

(9 replies, posted in Announcements)

Announcement

This is a 2.4.11 release, which is mainly bugfix release, but also contains a couple of improvements and additional security fixes.

This release should also be PHP 8 compatible. The following versions has been tested: 8.0.0, 8.0.7 and 8.0.12.

Please report any bugs/problems found via our Mantis Bugtracker at http://mantis.frontaccounting.com.

Download instructions

In Sourceforge FrontAccounting (http://sourceforge.net/projects/frontaccounting), select
Files -> FrontAccounting 2.4 ->2.4.11.

For Windows users select the zip file. For all other users select the tar.gz file.

Common

  • Theme Default is now RTL compatible by commenting out the table class (line 31) in default.css.

  • Improved the Graphic Engine to show correct legends also in RTL.

  • Many Mysqli errors: Trying to access array offset on value of type bool. Fixed. Please report any remains.

  • Function money_format is deprecated in above PHP 7.4. Replaced with price_format.

  • config.default.inc error on startup. Fixed.

  • Fixed exchange rate working in FA (EXCHANGE-RATES.ORG).

  • PHP 8 doesnt support imagettfbbox. Replaced with imageftbbox.

  • Curly braces {} in arrays replaced in Workbook.php (Excel).

  • Added security policy file, SECURITY.md.

  • Bug 5509. Installer: Fixed errors handling, fixed errors on db passwords containg special characters or longer than 20 chars. Allowed passwords up to 32 chars long.

  • PHP 8 bugs in simple_crud_class.inc fixed.

  • The secure flag was not set on session cookie. Fixed.

Sales

  • Select item not working in purchase order and sales order entry. Fixed.

  • Customer Credit Invoice: fixed invalid processing of invoice payments (triggering blank page on php8 too).

  • Unable to void a sales invoice. Fixed.

  • Bug 5490: qty_done is not updated correctly when partial invoice is voided. Fixed.

  • Rep109 in Print Profiles fixed.

  • Bug 4530. Customers with 0 left to allocate shown on Customer Allocations when using Journal Entry for paying. Fixed.

  • Customer Statements shows wrong balances for Journal Entries. Fixed.

  • Error calculating customer aging regarding journal entries. Fixed.

  • Bug 5512: Customer Allocation Inquiry - No alloc-icon for DEBET-Accounts-receivable-Journal Entries. Fixed.

Purchasing

  • Item selection not working in purchase order and sales order entry. Fixed.

  • Bug 5471: Fixed Direct supplier payment bug introduced by 'Dimension wise balance sheet items - AR/AP implemented'.

  • Credit This Option for Supplier Invoice Doesn't Show Quantity Invoiced. Fixed.

  • Bug 5522,5523,5524: Fix TAX in GL rows in supplier invoice.

  • Receive Purchase Order Items: fixed error on page opening (blank page in recent php versions).

Items and Inventory

  • Bug 5466: user_qty_decimals handled incorrectly by code that calls get_item_edit_info. Fixed.

  • Wrong parameter passed to qty_cell in sales kits. Fixed.

  • New Line Bug in Inventory Location Transfer. If editable field, then next line item is also editable. Fixed.

Manufacturing

  • Unable to void Work Order. Fixed.

  • Update_material_cost function makes one unnecessary call to get_item. Fixed

Fixed Assets

  • Bug 5498. Items/Fixed Assets: Fixed item image adding/update.

Bank and General Ledger

  • Updated default COA dates one year forward.

  • 2.4.10 Balance and Profit and loss reports failed to print. Fixed.

  • Bug in GL Journal fixed.

  • Report GL Trans: fixed timeout on huge transactions database.

  • hook_db_prewrite is not properly used inside journal entry. Fixed.

  • Allowing multiple journal entries on one trans_no. Ex. trans_no, Journal Entry, customer_id.

  • Bug 5518: Total Amount of a Journal Entry with multiple rows (>2) is wrong in Journal Entry Inquiries. Fixed.

  • Bug 5527: Tax Type not displayed during initial setup if default Sales and/or Purchase Tax account deleted. Fixed.

  • Bug 5522, 5523, 5524: Journal Entry Affecting in both sales and purchase and more. Fixed all three bugs.

Fixes

Go to forum: Announcements

211 Reply by joe

(7 replies, posted in Accounts Receivable)

@Bobloblian

If you change the last parameter in 

$contacts = get_branch_contacts($branch['branch_code'], 'invoice', $branch['debtor_no'], true);

in /reporting/rep107.php to false (default true], all the branch contacts with the action 'invoice' will get the Invoices.

If you don't want to change the core files, you can copy the rep107.php to /company/X/reporting and change the true to false here. The X indicates the table preference number for the client database tables.

/Joe

Go to forum: Accounts Receivable

212 Reply by joe

(3 replies, posted in Reporting)

I guess this has been fixed on Oct 17 2021 and is included in next minor release next week.

Joe

Go to forum: Reporting

213 Reply by joe

(1 replies, posted in Report Bugs here)

Fixed and committed to stable rep. Thanks @kvvaradha.

joe

Go to forum: Report Bugs here

214 Reply by joe

(3 replies, posted in Report Bugs here)

Ah, yes. The tax system is not built that way. You cannot create an item of tax to use for tax issues. Please use FA as it is intended.

Joe

Go to forum: Report Bugs here

215 Reply by joe

(3 replies, posted in Report Bugs here)

We have been doing a lot of fixes the last weeks on tax issues.

With these fixes I can not reproduce your error. We are shipping a minor release shortly, so wait and see. It should work with these fixes.

Joe

Go to forum: Report Bugs here

216 Reply by joe

(10 replies, posted in Report Bugs here)

Fixed and committed to stable repo. Thanks for helping @rafat.

Joe

Go to forum: Report Bugs here

217 Reply by joe

(10 replies, posted in Report Bugs here)

Ok, I see.
Will have a look. It is rather complex all these issues, however we will fix it.

Joe

Go to forum: Report Bugs here

218 Reply by joe

(10 replies, posted in Report Bugs here)

Tax Report (rep709.php) has been checked, tested and committed to stable repo.

/Joe

Go to forum: Report Bugs here

219 Reply by joe

(10 replies, posted in Report Bugs here)

Yes, I guess I will have to check the rep709 again.

Joe

Go to forum: Report Bugs here

220 Reply by joe

(10 replies, posted in Report Bugs here)

This issue has now been fixed and committed to stable repo.

Joe

Go to forum: Report Bugs here

221 Reply by joe

(7 replies, posted in Setup)

There might be some cache problem, when chaging this thing.

I would logout and login again to eliminate this.

The layout of the screen forms are based on a long time of experience.

I would also point out, that there is a context sensitive FAWiki help available by pressing the Help link.

Joe

Go to forum: Setup

222 Reply by joe

(7 replies, posted in Setup)

@ScrriptBASIC

Under menu item Sales, there is a submenu called 'Sales Types'. There you can either change an existing or create a new one. You see a checkbox 'Tax included'. If this is unmarked, you will get the info you want on your documents.

In your case you simply unmark 'Tax included' for the Retail Sales Type. That's so simple, right?

Joe

Go to forum: Setup

223 Reply by joe

(12 replies, posted in Report Bugs here)

You are welcome and thanks.

I have nothing to do with the api. I don't recall who is maintaining this.
We will try to CALL for him, please.
So the author of the API, please help us with Mr. DrCard's contribution.

Joe

Go to forum: Report Bugs here

224 Reply by joe

(12 replies, posted in Report Bugs here)

I will try to make things a little more clear.

You started with a Journal Entry with 40 Cr.
This is handled as some kind of a pre payment. Your customer owes this money. Hasn't got any services yet.
Then you invoiced a 10.
Instead of using the customer payment you could use the pre payment for allocating the invoice in the menu 'Allocate Customer payments ...'.
You still have 30 Cr, on the pre payment so this can also be used for allocating the second invoice.

I hope you see this. You have been overpaid by your customer.

Regarding the Balance of -40 is that your customer owes it. Thats the reason it is in minus.

Joe

Go to forum: Report Bugs here

225 Reply by joe

(12 replies, posted in Report Bugs here)

@DrCard

Your discussion is right until
'once paid the customer balance....'
You still haven't allocated the -40 that was booked in the Journal Entry.
They should not be paid (it is already some kind of payment). They should instead be used for allocation as I told in my former answer.
I can understand that this is tricky to see, but this is the way it is done.

Joe

Go to forum: Report Bugs here