Search options (Page 26 of 97)

Looks like some temporary cacheing error.
Janusz

The whole upgrade process is too complex to do it manually. You should just find the exact problem which block the upgrade, and fix it before you continue.
You should check the list above and fix the database scheme respectively. When it is done right, you should see upgrade option for version 2.3 in place of 'partially Installed (1/4)' info.

There is no right place here to explain all the nuances  of the license, so in short words:
. FrontAccounting can be sold providing all GPL license requirements are fullfiled;
. The result product have to be distributed on GPL license too;
. If the result product is distributed, it should be done in source form, so no code obfuscation is allowed;
. We do not give permissions to remove any licensing info from application
files; Any changes done in sources should be clearly stated as made by modification author;
. We retain rights to make license changes in future;

We do not agree on shameless usurpation of FrontAccounting authors work anyway.
FrontAccounting LLC

No, nor it is planned in 2.4. The only changes in date support are planned in next minor release, and you can download them from stable mercurial branch. The changes hopefully make manual date field edition less painfull using defaults for month/year.
But if you would like to contribute complete implementation for the proposed new date format, we can integrate it even in 2.3.x.
Janusz

While FA was based on webERP ideas, the code was completely rewritten on start (unmaintainable original code was primary reason for opening separated FA project). Currently probably the only common part of code is installer moved back to webERP, some similarities you can find also in database scheme, and that's all. Of course the comparision always can be done, but I preffer to leave this work for third party reviewers. Our opinion have to be naturally biased .
Janusz

I'm not sure which setting you mean. AFAIK all settings have to be defined here, otherwise posting errors could appear in GL.

Some of the settings like Prompt Payment Discount Account are potentially optional, but currently is no code dealing with 'Not Assigned' option.
Janusz

What about integration with calendar?

The id is created automatically by related link helper. I really don't know why this depends on them, it shouldn't. AFIR the id is necessary for arrows navigation between links on application page.
Janusz

Prepayment invoicing is not available in current FA version, however it is implemented in version 2.4 whcih is planned to be released soon.

The Profit/Loss account have to be defined as it is used on year close.
Janusz

First, seems you have partially upgraded database, and this can block 2.2 to 2.3 upgrade process. Before the update is preformed following database structure elements are checked:
. type field is included in 0_comments table index;
. 0_sys_prefs table exists;
. 0_sales_orders.payment_terms field exists;
. 0_purch_orders.tax_included field exists;

If any of those preconditions are met, the database is considered as partially upgraded. You should fix the database structure manually (e.g. via phpmyadmin) before upgrade.

But those are not the only changes which could rise errors during upgrade: any database structure change done on elements involved in FA upgrade procedure  can rise errors and block the upgrade. To avoid any errors, generally your database should have structure exactly as it is defined in en_US-*.sql in 2.2 distribution tarball.

Janusz