queueit / knownuser

queueit/knownuser

Using queueit known user to manage magento integration

magento2-module Compatibility: 2.4.7 Code Quality: Fail Tests: N/A Security: Pass MIT

Are you the maintainer of queueit?

Packagento pulls queueit's Composer packages from the public registry so buyers can find them here.

Claim the namespace to take ownership, publish new releases directly, and start charging for premium versions.

Claim this namespace →

Functionality

Server-side implementation of the QueueIT queueing system. This will put customers into a queue before they can enter the site.
FPC modules could prevent this module from working properly.(Please contact queue-it for the practices of handling FPC scenario.)

Installation

How to install the module using different methods.

Manual

First clone this repository inside your Magento2 app/code folder like below:

cd <your Magento 2 install dir>/app/code
git clone https://github.com/queueit/KnownUser.V3.MagentoV2.git Queueit/KnownUser

Afterwards install the extension:

cd <your Magento 2 install dir>
php bin/magento setup:upgrade

Doing so you can run the below command. It should show Queueit_KnownUser as an installed module:

bin/magento module:status

If Queueit_KnownUser was listed as Disabled module run the below command to enable it

php bin/magento module:enable Queueit_KnownUser
php bin/magento setup:upgrade

Composer

Install queueit module using composer

$ composer require queueit/knownuser

Enter your authentication keys. Your public key is your username; your private key is your password.
Afterwards install it with

$ php bin/magento setup:upgrade

Doing so you can run the below command it should show Queueit_KnownUser as an installed module

$ bin/magento module:status

You can find an official help about how to install a Magento extension here.

Configuration

After installing the module, go to the below menu and enable the module, enter your CustomerId and Secret Key which you have got from QueueIT.
Stores -> Configuration -> Services -> Queueit KnownUser

In here

  • Enabled: Enable/disable module execution. If enabled this will generally give a redirect on every request. So it is advanced to enable it only before an event is starting.
  • CustomerID: This is usually your account name
  • Secret Key: This is the secret key found in QueueIt: Account -> Security -> Known User (tab) -> Default secret key
  • How are the configs updated: The way changes on QueueIT's side are requested
    • Push: Configure url in QueueIT. Postback url is {{store_url}}/rest/V1/queueit/integrationinfo/
    • Manual: To Update configuration manually or to see the current configuration: Content -> QueueIt KnownUser -> Admin. You can see the current config at this page and also upload confugartion file for updating it.

FPC (Protecting ajax calls on static pages)

If you have Full Page Cache enabled you should add queue-it javascript to your pages as below :

  1. Make sure KnownUser code will not run on static pages (by ignoring those URLs in your integration configuration).
  2. Add below JavaScript tags to all static pages :
    You can add this tag in the header files : ...\vendor\magento\module-theme\view\frontend\templates\html\header.phtml
    <script type="text/javascript" src="//static.queue-it.net/script/queueclient.min.js"></script>
    <script
     data-queueit-intercept-domain="{YOUR_CURRENT_DOMAIN}"
       data-queueit-intercept="true"
      data-queueit-c="{YOUR_CUSTOMER_ID}"
      type="text/javascript"
      src="//static.queue-it.net/script/queueconfigloader.min.js">
    </script>
    
  3. Add some triggers for your dynamic ajax calls you want to queue users on.

No changelog yet

The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.

Versions
Version Stability QA Status Compatibility Released
1.3.6 stable Fail Magento 2.4.7 Details 2026-05-26 11:03:08
1.3.5 stable Not tested Not yet tested Details 2021-08-26 11:59:03
1.3.4 stable Not tested Not yet tested Details 2021-02-03 11:50:03
1.3.3 stable Not tested Not yet tested Details 2020-12-08 10:53:18
1.3.0 stable Not tested Not yet tested Details 2019-07-29 15:12:59
1.2.0 stable Not tested Not yet tested Details 2018-11-16 16:07:25
1.0.0 stable Not tested Not yet tested Details 2018-02-13 16:46:14

Requires 2

Package Constraint
ext-json *
queueit/knownuserv3 ^3.6.1

Requires-dev 3

Package Constraint
magento/framework *
magento/module-store *
psr/log 1.1.3

Compatibility

Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.

Compatibility matrix (Magento × PHP)
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 Pass Pass
2.4.8 Pass Fail di error
2.4.9 Fail di error Fail di error

Code Quality

Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.

Static analysis

Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.

Static analysis results
Tool Status Findings Summary
PHPCS Fail 88 6 errors, 82 warnings (ruleset: Magento2) — 34 auto-fixable with phpcbf
PHPMD Warning 3 3 rule violations (UnusedFormalParameter:2, MissingImport:1)
Cpd Pass 0
Composer validate Info 1 valid; 1 advisory note (composer validate --strict)

PHPStan

Type-checks the module's PHP against a real Magento install at the configured gate level. Re-runs per Magento and PHP version because resolvable symbols differ between releases.

PHPStan results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 24 24
2.4.8 24 28
2.4.9 28 28

Tests

Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.

Unit tests

Unit tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Integration tests

Integration tests results by Magento and PHP version
Magento PHP 8.2 PHP 8.3 PHP 8.4 PHP 8.5
2.4.7 N/A N/A
2.4.8 N/A N/A
2.4.9 N/A N/A

Security

Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.

Security results
Tool Status Findings Summary
Composer audit Pass 0
Malware scan Pass 0
License
MIT
Make it pay

Turn an existing module into recurring revenue.

If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.