5,426

(9 replies, posted in Accounts Payable)

See if any php script can send email from your server - try it in CLI too. Possible solutions will have to use SMTP email relay or authenticated webmail relay of proper config of the sendmail / php.

5,427

(3 replies, posted in Installation)

Making all as ENGINE=InnoDB is okay as far as FA v2.3.x is concerned - it just won't use the Foreign Key CASCADE ON INSERT/DELETE/UPDATE feature..

Use the Tag feature to tag both invoice numbers to one delivery note number.

5,429

(3 replies, posted in Accounts Receivable)

Set in config.php:

    /* Creates automatic a default branch with contact. Value 0 do not create auto branch */
    $auto_create_branch = 1;

Make sure that the openSSL extension is installed and activated in you PHP install

5,431

(6 replies, posted in Accounts Receivable)

Treat as advance payment and make invoice on account (credit type)

That is the reason why I have created my unofficial repo. Download and use offline - will be slightly outdated though.
https://github.com/apmuthu/frontaccounting/blob/master/farepo.zip

5,433

(2 replies, posted in Reporting)

Check this post.

Share the code?

Make the extra fields in a new table with a 1:1 relationship with the parent table and have the inserts and updates done using a trigger. This way all will be fine when the db schema changes and it can be made into an extension.

Install the old version so that the files and folder permissions and apache configs will be okay. Now update to the latest code from Sourceforge.
Empty the database using phpmyadmin or some other mysql client. That way the db user for the FA db will exist. Now install from the web GUI.

5,437

(2 replies, posted in Setup)

Make sure you empty the database first before the restore.

5,438

(6 replies, posted in Translations)

Use the file from:
install/lang/new_language_template/LC_MESSAGES/empty.po as a template and make your translations in a new file (pt_PT.mo) and then compile it into pt_PT.mo file (or Joe will do it for you) if you submit it to the project.

5,439

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

Joe, wouldn't you want to include it in the core?

5,440

(24 replies, posted in FA Modifications)

Wouldn't you want to share how you did it?

5,441

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

Activate the extension and theme in the specific company and use it.

5,442

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

Re-Updated the RegGen v2.3.9-3 extension to v2.3.13-1 at my personal GitHub Repo.
View Git ChangeLog.

The real change is in the sql file and hence the table xx_reports must be updated.

The changed files are attached in this post..

Change the installed_extensions.php files at the webroot and the company specific folder as well to reflect the change in version of the extension.

5,443

(18 replies, posted in Reporting)

Look at this post and change the default language for printing to suit your needs.

Install the old version from the repo, replace the /var/www/frontaccounting folder contents with the latest one and purge the database and install from the web browser.

5,445

(24 replies, posted in FA Modifications)

FA v2.3.x does not use the Foriegn Keys as yet (aka CASCADE ON DELETE, ON UPDATE, etc). It will be implemented only in FA v2.4. In PHP, the SQL statement will manually connect the tables using the JOIN syntax only. The keys will be there and the indexes will be available to speed up the execution.

The ERD is to show what links to what but is used to understand and frame the SQLs only.

5,446

(4 replies, posted in Announcements)

Official Git and Primary SF Mercurial Repos are now in synch after some SF hiccups some time ago.

5,447

(12 replies, posted in Announcements)

Diff Files from FA v2.3.16 to FA v2.3.17 is attached herein.

5,448

(3 replies, posted in Announcements)

FA v2.3.16 is synched with the unstable v2.4.

The diff file set from v2.3.15 to v2.3.16 is attached herein. Minor SQL changes pertaining to extra fiscal years and default company fiscal year are needed (see the sql file diffs).

5,449

(4 replies, posted in Announcements)

The changed list of files that can safely overwrite existing ones for migration from FA v2.3.17 to FA v2.3.18 is attached herein.

No database changes needed.

No attached files. Zip up the font files together and upload the zip file.