Search options (Page 65 of 246)

Make it part of the Logo image

Actually, this is the way it is by default.

The en_US-demo.sql has the following error on navigating to Banking and General Ledger => Trial Balance:

The Opening Balance is not in balance, probably due to a non closed Previous Fiscalyear.

This appears to be a false positive as the balances (without zeroes for clarity) do actually tally.

Cannot duplicate your date picker error - is it specific to your choice of date format? The en_US date format seems to work okay.

date_picker.js is created for the specific date choices in the config.php and placed in the company/#/js_cache/#/ folder where "#" is company index number.

The function get_js_date_picker() in includes/ui/ui_view.inc includes the said file and generates the js include code based on user select options.

Hence purge the said file in the js_cache and it should get generated anew and all should be well.

Yes. Looks like it got orphaned:
https://frontaccounting.com/fawiki/index.php?n=Main.OpeningBalances
https://frontaccounting.com/punbb/viewtopic.php?pid=30427#p30427
https://frontaccounting.com/punbb/viewtopic.php?pid=31547#p31547
https://frontaccounting.com/punbb/viewtopic.php?id=1587
https://frontaccounting.com/punbb/viewtopic.php?id=7387
https://frontaccounting.com/punbb/viewtopic.php?pid=31548#p31548

If all receivables and payables are moved into the new FA using Journal entries, then allocation towards invoices cannot be done. Where such allocations are desired, the invoices that remain unpaid need to be manually entered in the previous fiscal year and the remaining should be entered using the Journal entry method.

What about the paginated entries that overflow to next page?

Banking and General Ledger => Maintenance => Bank Accounts +> Select Bank Account and make it Default (Dflt).

@joe: a nice functionality but may affect a lot more tables fields / scripts.

That will just prevent editing an existing Purchase Order's price.
Probably clone the said role as a new role, switching of the edit permission and create one for switching off the add/view purchase price permission as well which needs to be instantiated in the role instanciation script as well. Then use that role in your new purchase order form to replace the existing one possibly as an extension.

Your genealogy site is proprietary that may result in externally processed PHP code obfuscated/encoded code being used.
Your server's PHP can be tested by running a php file having <?php echo "Hello World!";  ?>.

PM the access details to have a look removing and confidential info / resetting passwords to be other than your normally used ones you can revert to later.

Since your FA webroot does not have config.php and config_db.php files, FA has not been installed. It could be a matter of file permissions of the webserver user for the folder in question.