Search options (Page 186 of 246)

Check out Dimensions, Tagging and sub ledgers for addressing your needs. The FA Wiki is your friend and these forum posts are your treasure trove.

I have wiki-ed the discussions here starting from your first post here to help others taking their first steps in FA(iry) Land.

FA v2.4 changes:

most $_POST['xxx'] => get+post('xxx')
some $_POST['xxx'] => check_value('xxx')
blank strings => ALL_TEXT

All MyISAM tables now InnoDB
All closing php tags removed

Quite a few blank strings will need the ALL_TEXT replacements for easy readability. Some are single quoted and others are double quoted. Some are preceeded by == and others by !=.

Like most of the constants, ALL_TEXT is defined as a blank string in includes/types.inc file.
function check_value() is in includes/ui/ui_input.inc and checks if the $_POST element has been set (isset()).
function get_post() is in includes/ui/ui_controls.inc and retrieves the $_POST element's value if it exists or returns the second argument if it exists or a blank string.

Some good constructs like:

    if (isset($order_number) && $order_number != "") 

have got changed to

    if ($order_number != "") 

This snapshot has been tested to install correctly both for the en_US-new.sql and the en_US-demo.sql CoAs. A few of the reports have been tested and appear to be working (sample attached).

1. Delete company/2 folder and reset your credentials in config_db.php so that the counter - $tb_pref_counter - is set back and the array element for the second company is removed.
2. Empty (not truncate or drop) the database used for the company 2.
3. It is best to use a separate database for each company
4. The database should already have been created, a user privileged for it and privileges flushed.
5. Now test your CoA sql that it has no create database and use database statements and conforms to the standard en_US-new.sql format. Manually executing it on the target database and then emptying it out on successful execution is one way to fish for errors.
6. Login to default company as admin
7. Create your second company all over again, logout and login to the second company and go ahead.

All companies by default have the same administrator username of "admin" on creation. The username can only be changed in the database - phpMyAdmin / SQLyog. Within the FA Web UI, another administrator roled user can be created and then logged in using that and then the original one deleted but I do not know what will happen if some stupid script was to assume that user id 1 should always be admin!

The company name given during company creation is the one in the dropdown list during login that determines which db and FA company will be used. This info is stored in the company's entry in config_db.php. For security reasons, there is a variable in config.php - $text_company_selection - that can be set to make the dropdown box to a text box for manual entry.

Yes, this thread has now become the "FA Install Tips" topic.....

Do not depend on Softaculous or any hosting service's backup facility for critical data - solely. Yes, it is convenient to start with, but deciphering which backup to revert to and what it's actual state was is to get lost in the maze. In fact, an uninstall in Softaculous will simply wipe out the entire FA and it's database!

Whenever you want to backup, FA has a nice feature within it's user interface - Setup => Backup and Restore - where you can put in a comment as to it's snapshot contents and state - and in my mod, rename it as well - and download it to your machine in gzipped form. This however requires you to take a backup of the company/# folder separately to match the sql backed up.

Assuming all my mods are good is indeed a vote of confidence - thanks - please provide feedback.

What happens is that the $_POST info gets cleaned using the db_escape() function that does some scrubbing that may not be useful in your context. htmlspecialchars and url_decode and the state of some MySQL / PHP constants that change the way these functions work.

Some other posts in this forum that may be useful here are:

https://frontaccounting.com/punbb/viewtopic.php?id=3119
https://frontaccounting.com/punbb/viewtopic.php?id=5372
https://frontaccounting.com/punbb/viewtopic.php?id=5371
https://frontaccounting.com/punbb/viewtopic.php?id=4530

Study the changes between files in my FAMods with their counterparts in the core to see how you want to implement it.

It is generally okay to install applications via Scriptaculous / Simple Scripts / Fantastico, and other one-click installers for testing and evaluation purposes and for long unsupported projects (later correct it and update it manually).

After the release of FA v2.3.22, several fixes have been added and these will not reflect in such installs.

Modifications that consultants use for their customers are rarely put out for public view. For my part, I have placed every single mod in the FAMods folder in my GitHub repo that I think will be of some use to any end user. This, I hope will provide for exhaustive testing and feedback - very little has come my way so far and is indicative of the closeness (euphemism for selfishness and possible malicious intent) with which most developers would like to keep critical code to themselves. The real value of a project is it's community and the trust it emanates to grow it's userbase.

Several of my mods have yet to make it to the core and extension repos for various reasons and all of them have been listed with a detailed changelog.

The change to the said sql file will be valid for new company creation only. All existing companies must be manually corrected with appropriate SQL statements.

If your system has been in jeopardy hitherto, be happy that you did not know it to be worried about it at least till now and were able to enjoy the Christmas and New Year celebrations whilst some of us at FA were busy saving everyone hassles in it's wake .

This is now evident from the ERD at the Wiki.

Those who want to make the change can apply the following with the appropriate table prefix for each company:

ALTER TABLE `0_bank_trans` CHANGE `person_id` `person_id` INT(11) DEFAULT NULL;
ALTER TABLE `0_budget_trans` CHANGE `person_id` `person_id` INT(11) DEFAULT NULL;
ALTER TABLE `0_gl_trans` CHANGE `person_id` `person_id` INT(11) DEFAULT NULL;

It appears that you are not using the latest code. The ref and name fields were actually swapped while populating the table and the code was corrected in a commit on 2014-10-09. It would be best to use the stable snapshot.

Also, you seem to be using some non standard table prefix naming convention since FA usually uses numeric prefixes with an underscore but this will not be an issue here.

Furthermore, if you are using the en_GB Chart of Accounts from the official pkg repo then you will do well to do a line by line compare of the fields with the sql/en_US-new.sql in the db schema since in atleast 2 instances there are field order issues. As the devs are busy with getting FA v2.4 out, these remain in limbo.