***Warning read the readme*** Prior to using id you already have an addfields_cust table in your database
repo is here git branch is additional_fields_w/brancheshttps://github.com/trafficpest/FA24extensions/tree/additional_fields_w/branches
https://github.com/trafficpest/FA24extensions/tree/master/Extensions/additional_fields
A new column `cust_branch_no` as 2nd primary key, was added to addfields_cust . I created new functions maintaining the old. I wasn't sure how the author @poncho wanted to go with it.
you could allow null in branch_no but I dont see why since FA creates a branch when you create a customer automatically.
You could use the `all branches` option. copy the add_field info to all branches in the customer you are working on.
I needed branches for the route_delivery extension I made. I have a few clients that have multiple delivery locations, under one account (branches)
]]>https://github.com/trafficpest/FA
]]>I am getting some warnings in the log but I don't think they are fatal. I also tried uploading a document, so I don't think it's a permission problem for upload (BTW where do these files upload to?)
Can anyone help or give me ideas what to try next. I'm trying to move stuff over from QB and this is my first hurdle!
[30-Oct-2023 00:10:27 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_repgen::$path is deprecated
[30-Oct-2023 00:10:27 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_items::$path is deprecated
[30-Oct-2023 00:10:27 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_multijournalentries::$path is deprecated
[30-Oct-2023 00:11:36 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_transactions::$path is deprecated
[30-Oct-2023 00:11:36 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_repgen::$path is deprecated
[30-Oct-2023 00:11:36 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_items::$path is deprecated
[30-Oct-2023 00:11:36 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_multijournalentries::$path is deprecated
[30-Oct-2023 00:11:37 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_transactions::$path is deprecated
[30-Oct-2023 00:11:37 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_repgen::$path is deprecated
[30-Oct-2023 00:11:37 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_items::$path is deprecated
[30-Oct-2023 00:11:37 Asia/Taipei] 1::hooks.inc:245:[before upgrade] Creation of dynamic property hooks_import_multijournalentries::$path is deprecated
[30-Oct-2023 00:14:51 Asia/Taipei] 1:admin:frontaccounting.php:66: Creation of dynamic property front_accounting::$renderer is deprecated
This is the relevant function: (line 245 is the last nine before the first closing bracket.
// install hooks provided by active extensions
if (isset($installed_extensions) && !empty($installed_extensions)) {
foreach($installed_extensions as $ext) {
$hook_class = 'hooks_'.$ext['package'];
if ($ext['active'] && class_exists($hook_class)) {
$Hooks[$ext['package']] = new $hook_class;
$Hooks[$ext['package']]->path = $ext['path'];
}
}
}
}This is API module above that we are using to integrate with with our external React App.
The issue regarding this module is that whenever we try to make an API request to any endpoint provided in this module
i.e: www.baseurl.com/modules/api/category
it always gives an error regarding Allowed Origin not present in headers (CORS) but on the other hand when we are trying the same exact endpoint with Postman it runs as it is supposed to run.
I have gone through the help at slim framework site and found the solution below. But I am not sure where to embed this code in our API module.
https://www.slimframework.com/docs/v3/c … -cors.html
Kindly help us resolve this issue
Thanks for helping and coorperating.
]]>I have entered timeslips for an employee, and the transaction report for the employee screen is accurate. But when I click on an individual payslip to review the document, it doesn't match the transaction report. I think the report button has a bug.
Employees need their paystubs to apply for apartments, financing activity etc, so these have to be right in general. Is there a way to fix the report?
This is on the Employee Transaction Report ---> Clicking on the Printer Icon...generates an incorrect report that doesn't match the summary screen.
]]>function can_process()
{
return true;
}
Can someone please advise?
]]>It has a FrontAccounting plugin with automated accounting support. Everything is completely documented in the git wiki.
It is compatible with payments from any (custodial or non custodial) bitcoin lighting wallet (Cash App, Strike, Blue Wallet etc.) from anywhere in the world.
The git is here:
https://github.com/trafficpest/strikeout
Wiki is here:
https://github.com/trafficpest/strikeout/wiki
Screenshots here:
https://github.com/trafficpest/strikeou … Sceenshots
Please see the total process I followed in this video. https://drive.google.com/file/d/1TBYEIskSx3yumNalHOTltLNMUr51_jMx/view?usp=share_link
]]>Am interested in SMS Module for front accounting. Basically i want to trigger SMS for: Invoice Created , Payment Received from Client and Payment Reminder.
Attached is sample of the SMS Gateway configuration in Php.
Your assistance is highly appreciated on this matter.
]]>https://github.com/andresamayadiaz/FrontAccountingSimpleAPI
Currently we are using 1 api package that is built with slim 2 and that is not compatible with php 8.
I am trying use this with front accounting 2.14.4.
Any solution for this.
Or alternatives
]]>Thanks.
]]>we have a new WhatsApp module for FrontAccounting, Which will help you to send and receive messages through your whatsapp from FA itself. Here are informations of the module and demonstration video.
and product information here available.
Thank you
]]>