It's much more fun, when you can discuss your problems with others...
You are not logged in. Please login or register.
FrontAccounting forum → Posts by apmuthu
The committed fix now renames the function del_image to delete_image as used in the codebase. The re-run of the commit now changes the usage to del_image and rolls back the function name change.
This error in coding occurred as the earlier function name was used as the $_POST variable from the form.
Such usages are in some extensions as well - additional_fields and fronthrm but mostly as $_POST variables.
Effective workaround to use the newer commit only for https and not for http:
Replace hardcoded line 14 of includes/session.inc:
define('SECURE_ONLY', true);to be
define('SECURE_ONLY', (parse_url($_SERVER['REQUEST_URI'], PHP_URL_SCHEME) == 'https'));This way newer installs will not break when not using https. The last few times, the released versions seem to have some showstopper for existing users. This will only make existing users especially on legacy systems not to upgrade as that would warrant "consultant costs". FA should herd and retain it's flock as that is where the network wealth of the project lies - bulk satisfied standard users who can upgrade atleast in minor versions safely.
@joe: Kindly fix this.
Add another option for Education / Training purposes.
It is then better not to be hardcoded as a define but dynamically computed if https is in the URL. As it stands after the current commit, we still need to set the define manually.
Looks like it should be del_image instead of delete_image.
The function is defined in inventory/manage/items.php at 59 to 67:
function del_image($stock_id)
{
foreach (array('jpg', 'png', 'gif') as $ext) {
$filename = company_path().'/images/'.item_img_name($stock_id).".".$ext;
if (file_exists($filename) && !unlink($filename))
return false;
}
return true;
}Which version of FA, PHP and MySQL are you using?
Line 338 of inventory/manage/items.php is:
delete_image($stock_id);The said function literal is absent in whole of the FA codebase and wonder how the image gets deleted.
@joe: Any changes, if minor, can be accommodated for 2 languages in Quotations into the core.
Try the latest FA v2.4.11+ and see if it persists.
It is likely that many such voids will confuse the admin. A better way is needed. @joe?
Check the order of the entries. Looks okay except for the order.
The said field sales_orders.prep_amount is defined as:
`prep_amount` double NOT NULL DEFAULT '0',The default for double type field may not be accepted as 0 in your MySQL version or needs to be 0.0. and / or the initialisation to be:
$this->prep_amount = 0.0;@joe: This needs to be automagically set based on PHP version or by a server wide config variable.
Post Release Fixes attached.
Github Master (Bleeding Edge) Official Download Link
These fixes can be applied to (overwrite) the release version to be fully functional.
Will need this additional fix to work for https installs now.
Attached is the set of changed files between FA 2.4.10 and FA 2.4.11.
Changes in translatable strings:
New Strings:
Half Donut
Splines
Tables
Salesmen
Sales Total
Aging Total
New Orders
Locations
Below Reorder Level
Assembled Items
Manufactured Items
Open Workorders
Categories
Total Sales
Total Costs
Total Results
Type 2 Dimensions
Dimensions Total Balance
Dimensions Total Result
Receivables
Payables
Todays Deposits
Todays Payments
Extensions
Languages
Database Size
Results
Result
Totals
Last %s weeks Performance
Weeks
Last %s Months Performance
Month
Months
Total Customers Aged Analysis
Balances
Total Suppliers Aged Analysis
Last %s Months Cash Flow
No Data available yet!
items are below Reorder Level
Reorder
Replaced Translations:
<del>Purchase => Purchable Total => (should be Purchasable Total)</del> ->> corrected on 2022-02-05
Show Shortage => Show Only Shortages
Case alternates as new strings:
Kits < kits already exists
Fixed Asset Classes < "Fixed Asset classes" already exists
Stock Id < "Stock ID" already exists
qty < "Qty" already existsAs the original release posts got cluttered with many issue posts, this thread is started to address details for this specific release.
Release date 2021-12-04 as of GitHub commit https://github.com/FrontAccountingERP/FA/commit/75a6c36f067b8a728934f0f89ba33381a2bbec06
MD5 Hash for above tar.gz file: c82477d8ad679319a0c3da5e82860af9
Filesize: 1,874,152 bytes
A backup and restore may suffice better when no other users are trying to enter data.
Maybe required when no. of listing entries grow.
Disable https://bitninja.io/ service for the said page.
A non default company when logged in does not allow change of "admin" password.
This is expected to be changed from the default company login only.
The error message is however quite cryptic.
If there exists only one backup in the Backup and Restore page, then we will not be able to delete it. There is no message to that effect.
1. Create 1 Supplier and 1 Customer for the same client.
2. From time to time, pass a Journal entry from one to the other to transfer outstanding balance.
3. Settle by allocation of payments at the transferred account.
Lightweight AjaxCRUD is superb to integrate too.
https://sdk.invoicing.eta.gov.eg/start/
FrontAccounting forum → Posts by apmuthu
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 4 official extensions. Copyright © 2003–2009 PunBB.