Search options (Page 99 of 246)

Download the P8000 specs and the SDK without registration. Modify the reporting/repXXX.php files to suit your printer width and use the fonts available in the device. The device will be having the default printer as the thermal one as it is integrated in it.

Thanks @joe/@itronics. This will help streamline all the extensions as well and avoid security tinkering in the themes.

No need to execute add_access_extensions(); in any theme's renderer.php and in any extension file as well normally. We can place it in the beginning / end of the includes/page/header.inc file (has only global functions) which is always loaded just before the renderer.php wherever the latter is used. The header.inc is called in the following files:

access/login.php
access/logout.php
access/password_reset.php
includes/main.inc

The function add_access_extensions() is defined in includes/access_levels.inc and is explicitly called in admin/security_roles.php (called only by applications/setup.php - visit to Access Setup enables extension) and index.php which pretty much covers it's entire use. Hope Ajax does not become vulnerable because of all this...

@joe: is this how we fix this?

I have tested it both on Windows (XAMPP v1.7.3 / PHP 5.3.1) and on Debian 6 (PHP 5.3.3-7). The default FA 2.4.2+ works fine with official import_items module - you can try to patch it to the latest as well from my FA24extensions repo - it will also work.

The reason is that the said function add_access_extensions() is executed on line 12 of import_items.php itself and there is no need for it in the renderer.php of the themes at all.

Themes get populated with data mostly from the $_SESSION variable which would have got populated with the security parameters before the display template is used. Hence the add_access_extensions() is not required to be executed in any theme at all.

Dropdown theme has now been removed from the Official PKG Repo since it is part of the core. Thanks.

@kvvaradha & @boxygen: There is no use of solutions where none are needed. Ambiguous statements will only confuse the end user.

The standard FA 2.4.2+ works with the standard import_items PKG from the official PKG repo. Minor updates to it are available from the FA24extensions repo which I maintain independent of the official FA repos..

Users are best advised to update their install to the latest release / master before seeking assistance in the forum and state the versions of all pertinent applications used and any dated / specific versions assistance can be taken offline so as not to confuse other users.

The FA 2.4 version of the import_items module has been updated.

See this commit.

The import_items module has many fixes and needs to be updated from the FA24extensions repo as the official PKG has not yet been updated as on date (under review).

Batch delivery of items from multiple sales orders has there for quite some but deliveries to Invoices - check. Easily tested.

1. Make 2 or more Sales orders from same customer.
2a. Bunch them into a single delivery (can invoice this single delivery).
2b. Make 2 or more deliveries from same or across sales orders and then try to make a single invoice out of them.

From @joe's post:

Isn't it better removed from the Official 2.4 PKG repo?

@joe: Please remove the dropdown theme from the official PKG repo as this is the one that is causing all the issues.

Was it left behind to help those migrating by merely overwiting files with the ones from FA 2.4.x? Then it it would be a veritable nightmare with all kinds of files that may get accidentally auto included and executed inadvertently.

If it must be there, then synch it with the one that is shipped with FA 2.4.2. Then the default and canvas themes too can find a place in it.

It is best to remove all themes that will not work with FA 2.4.x. The fact that the existing official PKG had the version number as 2.4.0-2 and also stated so inside it's renderer.php file is what confused me. In fact I thought it was an improved version of the one that shipped with FA 2.4.2 which doesn't appear to have been updated in quite a while - the last time it was modified was on 2015-12-24.

I have removed it from the FA24extensions repo since it is in the AF 2.4 core - otherwise, updating it will be redundant here.

@boxygen: add_access_extensions() is executed in FA 2.4 in index,php, admin/security_roles.php and is defined in include/access_levels.inc. If the themes are a legacy carryover from FA 2.3.x, then they will be present for now and may be used with care. These themes are: bluecollar, dashboard_theme, dynamic, exclusive, exclusive_db.

The dropdown theme is the one in the official repo for FA 2.4. Must it not match the one in the FA 2.4 repo too?

@boxygen: are you using the said theme in FA 2.3.x or in FA 2.4.x - the file path in the errors states fa24?

You must take a backup each year. Then close the year and take another backup and then purge it and start your new year. Keep atleast one previous fiscal years data for reference and awaiting closure while the new year is online. Dont forget to backup the entire web install folder as well since it will have the item images and attachments too (company/#/*).

There is a higher probability of large databases getting corrupt more frequently than smaller ones that are properly indexed.

Whenever you need to check on older years that have since been purged, just restore them into some other cloud instance and restore from the backups and view it!

Note that the fiscal years table must have the id in sequence without any gaps and must match the Start Date order as well, otherwise closure and purging will hang / get corrupted.