I wanted to start a discussion around Xyli, a keyword that is gaining attention in different online communities and digital platforms. As industries continue to evolve rapidly, new terms like Xyli often represent tools, services, or concepts that improve user experience, efficiency, or accessibility in various fields.

Many users are curious about how Xyli (ไซไล) can be applied in real-world scenarios, especially in areas like online networking, digital services, and modern web-based platforms. With the rise of advanced technologies, such keywords often become part of larger ecosystems that focus on user convenience and better interaction.

One interesting aspect of Xyli is how it can potentially be integrated into platforms that focus on user discovery, communication, or service-based environments. Whether it is used for branding, system functionality, or digital identity, the adaptability of Xyli makes it a topic worth exploring.
Read more: fiwfan.app

I was installing the new 2.4.20 version and it could't finish installation

I'm using

MariaDB 10.4.32
PHP Version 8.1.25

The problem I notice is when the system tries to execute the script

CREATE TABLE `0_bank_accounts` (
  `account_code` varchar(15) NOT NULL DEFAULT '',
  `account_type` smallint(6) NOT NULL DEFAULT '0',
  `bank_account_name` varchar(60) NOT NULL DEFAULT '',
  `bank_account_number` varchar(100) NOT NULL DEFAULT '',
  `bank_name` varchar(60) NOT NULL DEFAULT '',
  `bank_address` tinytext,
  `bank_curr_code` char(3) NOT NULL DEFAULT '',
  `dflt_curr_act` tinyint(1) NOT NULL DEFAULT '0',
  `id` smallint(6) NOT NULL AUTO_INCREMENT,
  `bank_charge_act` varchar(15) NOT NULL DEFAULT '',
  `last_reconciled_date` timestamp NOT NULL DEFAULT '1900-01-01 00:00:00',
  `ending_reconcile_balance` double NOT NULL DEFAULT '0',
  `inactive` tinyint(1) NOT NULL DEFAULT '0',
  PRIMARY KEY (`id`),
  KEY `bank_account_name` (`bank_account_name`),
  KEY `bank_account_number` (`bank_account_number`),
  KEY `account_code` (`account_code`)
) ENGINE=InnoDB AUTO_INCREMENT=3 ;

the failure is because in the newer MariaDB does not allow this line   
`last_reconciled_date` timestamp NOT NULL DEFAULT '1900-01-01 00:00:00',

so in order to make it work change it to 
`last_reconciled_date` DATETIME NOT NULL DEFAULT '1900-01-01 00:00:00',

After I did it it works, hope I can help someone.

Two innocent pieces interacting:

1. `0_audit_trail.stamp` is defined as `TIMESTAMP ... ON UPDATE CURRENT_TIMESTAMP` (FA default, used to track edit time).
2.  close_transactions() in `includes/db/audit_trail_db.inc` runs `UPDATE 0_audit_trail SET gl_seq=$seq WHERE id=...

The UPDATE only sets `gl_seq`, but MySQL auto-refreshes `stamp` as a side effect of the `ON UPDATE` clause. The `if ($row['gl_seq'] != $seq)` guard is why only some rows get hit — exactly the ones being re-sequenced.

I tried fixing it with the following change

$sql2 = "UPDATE ".TB_PREF."audit_trail SET"
    . " gl_seq=$seq"
    . " WHERE id=".$row['id'];

to:

$sql2 = "UPDATE ".TB_PREF."audit_trail SET"
    . " gl_seq=$seq,"
    . " stamp=stamp" // preserve original timestamp
    . " WHERE id=".$row['id'];

Explicitly listing `stamp` in the SET clause suppresses the `ON UPDATE CURRENT_TIMESTAMP` auto-refresh in MySQL. No schema change needed, and normal `add_audit_trail()` edits are unaffected since they already set `stamp` explicitly.

Has anyone else hit this? Kindly share your experience.

Thanks

This is a 2.4.20 stable release with improved PHP 8 compatibility and a couple of usability and security bugfixes.
Therefore please consider urgent upgrade of your installation to this version, to keep your FA instances safe.
This is especially important in not fully trusted environments like publicly accessible installations (demos or other installations accessibly by not fully trusted users).

This release fixes some problems on php versions 8.2 to 8.4. The following versions has been tested: 8.0.0, 8.0.7, 8.0.12, 8.1.6, 8.2.0, 8.3.2, 8.4.13 and 8.5.5.

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.20.

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

FrontAccounting should NOT be used via unsecure http protocol. If you really need this - change SECURE_ONLY constant in /includes/session.inc to false (comment in the file added). Unfortunately this option cannot be added in sysprefs/config.php because the settings are not available before session is started.
Common

● Multiply cleanups/security fixes in attachments editor.
● Database procedures in reports fixed to be compliant with codebase rules.
● Bug [0005737] Attachment editors: fixed input field width to underlying db field size.
● Attachments should be deleted when related document/entity is deleted. Fixes [0005757].
● Bug [0005750] Fixed hangs in barcode generation.
● Feature [0005712] Added fast date input edition with keyboard shortcuts (CtrlAlt-Arrows).
● Install/Activate Extensions: fixed deprecation warning on php ]=8.2.

Sales

● Feature [0005738] Customer/Supplier Allocation Inquiry: changed default sort order to ascending by Due Date.
● Feature [0005752] Customer Statements Report: added customer reference column.
● Feature [0005751] Customer Payments, Supplier Payments: added contractor reference for easier allocations.

Purchases

● $trans_no was missing in purch_order definition class. Fixed.
● Feature [0005738] Customer/Supplier Allocation Inquiry: changed default sort order to ascending by Due Date.
● Feature [0005751] Customer Payments, Supplier Payments: added contractor reference for easier allocations.

Bank and General Ledger

● Added two XRPL Payment Links. By Leslie Proud.
● Changed Bank Account Reconcile to sort descending.
● New exchange-rates organisation update. Can also fetch historical rated.
● Fixed safety issues in bank and audit reports.

I have progressed to the point where no errors are reported and the FA interface feeds back a line highlighted in green of the data that was processed.  However, when I check to see if a new SO record was created I don't find one.

I would expect that the feed back resulting from a successful upload would be more than the green highlighted information.

Also, the menu option to IMPORT TRANSACTIONS is perpetually greyed out, forcing me to go through the steps to save the access rights for the Administrator (me) each time I want to try to import.  Not sure if this is somehow related but even if it isn't it's very frustrating!

You guys are doing a great Job here. Thank you all.

I discovered that the Stock check sheet reports and the Inventory Item movement report end total are different. What can be the cause of it? Both figure are supposed to be same. KIndly help out.

Secondly, I want the name of the person who raised an Invoice to appear on each Invoice. How can I achieve that?

Thanks

Popsicles12

Pros of Unofficial APIs
* You bypass Meta’s per-message pricing entirely. Whether you are sending a transactional receipt or a promotional blast, there are zero official WhatsApp fees.
* No Approvals or Templates: You do not need to submit message templates to Meta for approval. You can send any content, at any time, without waiting for the official green light.
* No 24-Hour Service Window: Unlike the official API, which restricts free-form replies to a 24-hour window after a customer messages you, unofficial APIs allow you to initiate or reply to conversations whenever you want.
* Simultaneous Mobile App Use: Because these tools typically work by mimicking a "Linked Device" (WhatsApp Web), you can keep your primary phone number active on your physical smartphone while still automating messages through the API.
* Access to Native Features: Unofficial APIs often support features that the official Cloud API restricts, such as creating and managing WhatsApp Groups, updating Statuses, and interacting with Communities.
* Instant Setup: There is no lengthy Meta Business verification process. You can generate a QR code, scan it, and start testing your API integration in minutes.

Cons of Unofficial APIs
* High Risk of Permanent Bans: This is the biggest drawback. Unofficial APIs strictly violate Meta’s Terms of Service. If WhatsApp's automated systems detect bot-like behavior, non-human typing speeds, or spam patterns, your phone number can be permanently banned without warning.
* Zero Official Support: If your number gets banned or a message fails to deliver, you have no recourse or customer support from Meta.
* No Official "Green Tick": You cannot apply for the verified Official Business Account badge (the green checkmark), which can lower trust for customers interacting with your brand.

I am attaching the zip file here.
Install it in the latest version of FA.

1. Create Invoice.
2. Add Chat Id in the customer setup. It can be number with country code without + Or the Customers Group Id.
3. Open Customer INquiry page
4. Send WhatsApp.
5. It will check for company email (if not defined) for creating session
6. It will ask for scanning like whatsapp web
7. Now you can send invoice, payments, delivery notes

Let me know your feedback.

ON line 69 there is a function call

add_bank_transaction($entry->trans_type, $bank_account, $entry, $entry->tran_date, // FA built-in function
            false, false, false, $entry->reference, $entry->memo_, false);

But there is no bulit in function with this name.

bank_account_reconcile did NOT list the items, so I searched the GL Enquiry for transactions in case they were registered against wrong GLs.

gl_account_inquiry listed these items with the non zero values (the values I was expecting - but with extra lines)

gl_trans_view.php opened the items, displayed looking like a Journal Entry rather than the normal Payment/Deposit pop ups.

gl_journal.php?ModifyGL=yes opened into the Bank Deposit or Bank Payment editored, but all lines were of zero value, and the date was today's date.  Altering and saving resulted in the next screen saying transaction 0 was updated.

I am currently on 2.4.19 but was on 2.4.1 until a month or so ago, so this data corruption could be from a while ago.

PROPOSAL:
1) A report that cross references the various tables that store this data and reports mis-matches.
2) an editor to clean these up - either a "force" for void or similar zero everything.  I haven't worked through this yet as EOY tax reporting is less than a week away.

How I can import COA for Serbia. I have .csv file tor this.

Thks in advance,
Leka

At the same time when I translate frontacount to serbian I need click many times on menu to see translate.

Thks in advance

trial and error in attachments.php around line 37, replacing the following:

                        $type = ($row['filetype']) ? $row['filetype'] : 'application/octet-stream';
                        header("Content-type: ".$type);
                        header('Content-Length: '.$row['filesize']);
                        header("Content-Disposition: inline");
                        echo file_get_contents(company_path(). "/attachments/".$row['unique_name']);
                exit();

with

                      header( "location: " . $_SERVER['PHP_SELF'] . "/../" . company_path(). "/attachments/".$row['unique_name'] );
                exit();

works.  I don't see any security issue by passing a URL instead of a stream?

I've been working on a Chart of Accounts (COA) specifically for individual users in Pakistan, and I’d like to share it with the community. My goal is to see if we can eventually get this added to the "Install/Activate Chart of Accounts" list in the official setup.

I have hosted the project on GitHub to make it easier for others to contribute or review: https://github.com/xehroz/fa-pakistan-coa

The main challenge for users in Pakistan is that the FBR (Federal Board of Revenue) requires very specific reporting for the annual Wealth Statement and Income Tax Return. A standard business COA usually doesn't cut it for a freelancer who also has agricultural land or diverse investments.

I have designed this COA to solve those specific problems. It includes:

1. Tax Receivable Tracking: I have set up a 13xx series under Current Assets to track Withholding Taxes (WHT). This is a lifesaver for tracking tax deducted on University Fees, mobile bills, and bank transactions so they can be claimed back during filing.
2. Freelance & IT Export Logic: Dedicated accounts for IT revenue to help with PSEB (Pakistan Software Export Board) documentation.
3. Agricultural Support: Separate categories for Farm Land and Agri Income to keep Federal and Provincial tax data distinct.
4. Personal Wealth Assets: Proper slots for Household effects, PSX (Stocks), and Mutual Funds, which are required for the FBR Wealth Reconciliation.

IMPORTANT NOTE ON TESTING:
Please note that this is a first draft based on the required financial structure. It has not been fully field-tested in a live production environment yet. I am sharing it for community testing, evaluation, and feedback before it is considered for full incorporation into the main FrontAccounting package.

Implementation Notes:

* It’s best to enable USD for the Freelance Revenue and Foreign Currency bank accounts to handle remittances correctly.
* The WHT accounts are intentionally placed in Assets (not Expenses) so they don't get wiped out at year-end before the tax return is filed.

Feel free to check out the repo, submit pull requests, or leave feedback here. I would love to get some guidance from the devs on how to refine this into a standard installable module.

Thank You!

Shehroz Kaleem