shipperhq / module-logger

shipperhq/module-logger

ShipperHQ Logger

magento2-module Compatibility: 2.4.7-2.4.9 Code Quality: Fail Tests: N/A Security: Pass OSL-3.0, AFL-3.0

Are you the maintainer of shipperhq?

Packagento pulls shipperhq'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 →

ShipperHQ Logger for Magento 2

ShipperHQ Logger provides advanced, granular logging for Magento 2. It gives merchants and developers visibility into ShipperHQ's behaviour at checkout, with graded log levels, per-module filtering, and a built-in admin panel log viewer.


Features

  • Graded Log Levels: Log at debug, info, warning, and critical levels to capture exactly the detail you need.
  • Per-Module Logging: Enable or disable logging granularly per ShipperHQ extension or module.
  • Log File Output: Write log entries to specified log files for easy access and integration with external monitoring tools.
  • Admin Log Viewer: View log entries directly from the Magento 2 admin panel without needing server access.

Installation

Install using composer, you can find full instructions in the ShipperHQ documentation.


Requirements

  • Magento 2.4.4+
    • Compatibility with earlier editions is possible but not maintained
    • Supports both Magento Opensource (Community) and Magento Commerce (Enterprise)
  • A valid ShipperHQ account. Sign up here for your 15-day free trial!

Configuration

If you don't have a ShipperHQ account:

  1. Sign up for a free 15-day trial at www.shipperhq.com
  2. You can then follow the steps the basic configuration wizard will guide you through

Enable and configure logging:

  1. API Credentials:

    • Log in to your ShipperHQ account.
    • Navigate to Websites and find your API key and generate an Authentication Code.
    • Paste the key and code into the plugin settings under Stores > Configuration > Sales > Shipping Methods > ShipperHQ.
    • Set the Enabled dropdown to Yes.
    • Save the store configuration settings.
  2. Logger Settings:

    • Navigate to the ShipperHQ Logger configuration in your Magento admin panel.
    • Set the desired log level and enable logging for the modules you want to monitor.
    • You can find detailed setup guides in our documentation.
  3. View Logs:

    • Log entries can be viewed from the admin panel log viewer or from the configured log files on your server.

Frequently Asked Questions

1. Do I need a ShipperHQ account to use this module?

Yes, an active ShipperHQ account is required to use this module.

2. Is there a free trial available for ShipperHQ?

Yes, ShipperHQ offers a free trial for new users. You can sign up for the trial on the ShipperHQ website and explore the platform's features before committing to a subscription.

3. How do I troubleshoot missing log entries?

  • Verify that the Logger module is enabled and the correct log level is configured.
  • Ensure file write permissions are set correctly for the configured log file path.
  • Check our extensive documentation for troubleshooting tips.

4. Can I log only specific ShipperHQ modules?

Yes, logging can be enabled or disabled per module in the Logger configuration, allowing you to focus on the areas most relevant to your investigation.


Support

For assistance, please visit our Help Center or contact ShipperHQ support at [email protected].

For alternative contact methods, please visit our Contact Us page.


Contributing

Any contribution is highly appreciated. The best way to contribute code is to open a pull request on GitHub.


License

See license files


Copyright

Copyright (c) 2016 Zowta LLC (http://www.ShipperHQ.com)

Change Log

20.4.0 (2018-06-21)

SHQ18-331 remove module-common dependency

20.5.0 (2020-09-17)

MNB-657 Remove logging per extension switches

20.6.0 (2022-02-18)

MNB-5 Move to declarative schema

20.7.0 (2022-05-13)

MNB-2430 M2.4.4 compatibility

20.7.1 (2024-06-27)

SHQ23-1281 Fix security linter warnings

20.7.2 (2026-05-29)

ENG26-26 Modernise copyrights and namespaces. Update readme

Versions
Version Stability QA Status Compatibility Released
20.7.2 stable Fail Magento 2.4.7-2.4.9 Details 2026-05-29 10:48:00
20.7.1 stable Not tested Not yet tested Details 2024-06-27 08:55:16
20.7.0 stable Not tested Not yet tested Details 2022-05-13 09:17:55
20.6.0 stable Not tested Not yet tested Details 2022-02-18 12:36:49
20.5.0 stable Not tested Not yet tested Details 2020-09-17 09:20:16
20.4.0 stable Not tested Not yet tested Details 2018-06-21 15:32:58
20.3.3 stable Not tested Not yet tested Details 2018-05-18 08:46:41
20.3.2 stable Not tested Not yet tested Details 2018-04-13 08:55:39
20.3.1 stable Not tested Not yet tested Details 2018-04-03 10:13:48
20.3.0 stable Not tested Not yet tested Details 2018-04-03 10:13:39
20.2.0 stable Not tested Not yet tested Details 2018-03-15 16:46:54
20.1.3 stable Not tested Not yet tested Details 2017-10-12 09:33:16
20.1.2 stable Not tested Not yet tested Details 2017-08-11 08:35:56
20.1.1 stable Not tested Not yet tested Details 2017-08-08 10:35:22
20.1.0 stable Not tested Not yet tested Details 2017-07-31 09:09:42
20.0.9 stable Not tested Not yet tested Details 2017-02-22 09:42:22
20.0.8 stable Not tested Not yet tested Details 2017-02-13 09:56:55
20.0.7 stable Not tested Not yet tested Details 2016-12-09 09:47:21
20.0.6 stable Not tested Not yet tested Details 2016-09-02 13:08:42
20.0.5 stable Not tested Not yet tested Details 2016-06-09 03:34:38
20.0.4 stable Not tested Not yet tested Details 2016-06-07 03:20:56
20.0.3 stable Not tested Not yet tested Details 2016-05-18 13:51:59
20.0.2 stable Not tested Not yet tested Details 2016-05-03 01:25:55
20.0.1 stable Not tested Not yet tested Details 2016-04-25 08:24:42

Requires 1

Package Constraint
magento/framework >=100.0

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 Pass
2.4.9 Pass Pass

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 74 1 error, 73 warnings (ruleset: Magento2) — 25 auto-fixable with phpcbf
PHPMD Warning 16 16 rule violations (UnusedFormalParameter:6, IfStatementAssignment:2, UndefinedVariable:2, CyclomaticComplexity:2, MissingImport:1)
Cpd Pass 0
Composer validate Info 2 valid; 2 advisory notes (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 50 50
2.4.8 51 51
2.4.9 50 50

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
OSL-3.0, AFL-3.0
Authors

More from shipperhq

View vendor
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.