Check where you took the snippet from and do a WinMerge compare for diffs and see if there are any syntax / sequence order issues for the lines of code.

The function display_notification() is defined in includes/ui/ui_msgs.inc and needs to be included in your script if not already loaded by some other included script.

The second argument in the said function defaults to true anyway and can be omitted in the second call.

The FA Login with

user_name_entry_field
password
company_login_name

gets posted to itself (index.php) which includes the session file (includes/session.inc) that checks if a session exists and if not, includes the  login form (access/login.php).

It is in the last file referred to above that you will need to create a secondary hook for your dual authorisation using a special unique session variable as a flag.

1,129

(10 replies, posted in Development)

Please add "bin" for warehouse stock.

Also this one for tax info.

Use SMS OTP to generate a dynamic password valid for that session only directly in the db - maybe an extra field in the use record.

@poncho1234's PurV1 theme: Whilst the font sizes are okay and the menus have no clutter, it may cause issues during remote desktop refreshes.

Unlike @kvvaradha's theme, @poncho1234's theme is not yet available for download and local testing.

@poncho1234: Yes, it is @kvvaradha's theme from the link he provided. If your PuroV1 is elsewhere, please provide the link.

@kvvaradha: I tested out on 1440x900 and had to scroll.

I would still prefer the existing default theme. The PurV1 @kvvaradha's default theme (screenshots attached here)  is a little large and well spaced out but needs scrolling on smaller monitors. No clutter now.

1,134

(21 replies, posted in Modules Add-on's)

When designing any extension and keeping it uptodate, let us use the Git Master version of FA when not changed too often as sometimes the released versions have fixes applied thereafter.

The osc_orders extension to FA 2.4.x repo is here. Those of you who have tested it it, please state FA version and osCommerce versions used.

There are several versions of osCommere and most are listed here:

osCommerce v3.0.2 was released on 2011-08-06
https://github.com/osCommerce/oscommerce/releases
It's last real commit was on 2012-03-14 and the readme was updated on
2012-10-30
https://github.com/osCommerce/oscommerce/commits/master

The officially supported online merchant version is 2.3.4.1
https://www.oscommerce.com/Products
The beta version there is 2.4.0
There is also a v2.2RC2a version listed at:
https://www.oscommerce.com/Us&News=130

https://forums.oscommerce.com/topic/412630-github-tls12-sourcetree-broken/
For a new install or if your store isn't mobile-friendly, get the
community-supported responsive osCommerce (2.3.4.1 CE) here:
https://github.com/gburton/Responsive-osCommerce/archive/2341-Frozen.zip
With Bootstrap 3:
https://forums.oscommerce.com/topic/396152-bootstrap-3-in-234-responsive-from-the-get-go/
Last release of https://github.com/gburton/Responsive-osCommerce with
Bootstrap 4 is on 2018-05-18:
https://github.com/gburton/Responsive-osCommerce/releases
And the last commit there is at 2019-04-10
Discussions at:
https://forums.oscommerce.com/forum/107-oscommerce-online-merchant-community-bootstrap-edition/

The Sourceforge version is stuck at v2.2ms2-060817 dated 2006-08-17
https://sourceforge.net/projects/tep/files/osCommerce/2.2%20Milestone%202%20060817/

oscMax2 is at v2.5.4 released on 2014-07-03 - https://github.com/osCmax/oscmax2/releases
osCmax is based on osCommerce 2.2RC2a and is an
extension of that application.
Last commit on 2016-04-10 - https://github.com/osCmax/oscmax2/commits/2.5.5
Showcased at: https://www.oscmax.com/

osCommerce v2.4.x is on GitHub at https://github.com/osCommerce/oscommerce2
The latest version 2.4.2 was released on 2016-11-21
https://github.com/osCommerce/oscommerce2/releases
The last commit in that branch was on 2016-11-24

Need some controls on use of common words that will deluge the report.
Modify the GL Transactions report rep704.php and chaneg the sql as desired using _memo LIKE ....

Generate your own and place it in the sql folder and use it.

If you can help with translation, take the .po file and edit it and submit it to the project.

@boxygen: Please state what logic can be applied to such transactions especially when stock moves, costing / valuation, etc are going to be affected and all transactions since will have to have their reports amended.

It should suffice to make a separate transaction in the current date with all current values for the changed part alone as only now the error came to light.

Otherwise, all average values since the Month 1 will get affected and so will all transactions that rely on such computed values.

In your situation, a backdated Journal Entry to an adjustment revaluation account may be in order and contra-ed on current date so as not to affect the entries in between.

It appears that you are using an outdated version of some chart of accounts. FA 2.4.6+ uses only InnoDB as the Engine Type and your MySQL seetings too should then be checked.

State your Server Platform and PHP/MySQL/FA versions and which chart you are using. For a start, check your chart of accounts and replace all instances of MyISAM with InnoDB and then try again after dropping / emptying your existing FA DB.

1,141

(9 replies, posted in Reporting)

The sizing of what you want is attached - 5cm x 3cm.

As the code in my previous post has all the necessary variables and functionality, you can now engage anyone in the Job Board to do it for you specific to your printer.

If you print all your barcodes in one A4 page then you can use a regular printer with Avery like labels - but printing on them may waste paper if you just need one or two.

1,142

(13 replies, posted in Report Bugs here)

The new code works for now.
More testing is needed to check for edge conditions stated above.

I had to set config.php variable "$no_check_edit_conflicts = 1;" in windows for it to work though - it did not work for earlier commits.

1,143

(13 replies, posted in Report Bugs here)

!isset($_POST['stock_id'])

does not necessarily mean that the stock_id does not exist - it merely states that it was not chosen in the $_POST variable.

The database must not be removed at any cost as in shared hosting it may contain tables pertaining to other applications and the end user may not have permissions to create a new database at all.

1,145

(8 replies, posted in Accounts Receivable)

If a transaction was made and then voided, then the branch is needed to be deleted before the customer is deleted.

FA has the ability to use a different database for each company. When setting up a new company, choose the dbname as needed and make sure that the db user has the rights to create a new db or have it created and provide it's access credentials therein.

Deleting a company does not delete the database. It merely removes the stanza from config_db.php file. The database and the tables therein need to be removed manually.

1,147

(9 replies, posted in Reporting)

Here is a first draft of rep311.php which should do the job.

@joe: Move the defines to sys_prefs table with appropriate settables in the Company Setup and incorporate it into the core if found useful.

Additional variables could be number of barcodes per sheet (here 1) besides suppressing the header if not necessary.

The first default company must not be removed.

However all is not lost.

Edit your config_db.php and set your default company to the index of the company you now have. It is also possible that your original company 0 database is still there and you can create a stanza for it in the sid file as well.

Start from scratch and install FA 2.4.6+ anew.
Use the en_US-new.sql chart - the one with no demo data for your default install and keep this "0" company as default. Only this company can create other companies.

FA has been in production use around the world for over a decade now.

1,150

(9 replies, posted in Reporting)

If rep303.php has the 'EAN' replaced with 'C128B', the attached Stock Check Sheets would ensue.