WooCommerce Fortnox Integration 4.5.6
Does "Fortnox integration for WooCommerce" work with WordPress 6.8.1 and PHP 8.1.12? A smoke test was performed on .
Summary
Errors
| The plugin could not be activated | |
| 3 | PHP notices |
| No JavaScript exceptions | |
| No resource errors |
Performance
No data available.
Environment
| WordPress version | 6.8.1 |
|---|---|
| PHP version | 8.1.12 |
| MySQL version | 10.6.10 |
| PHP memory limit | 512M |
Plugin Info
| Last updated | |
|---|---|
| Active installs | 300+ |
| WordPress.org page | https://wordpress.org/plugins/woocommerce-fortnox-integration/ |
| Badges |
|
Pages 1
Plugins ‹ Test site — WordPress
| URL | /wp-admin/plugins.php?plugin_status=all&paged=1&s |
|---|---|
| Requested URL | /wp-admin/plugins.php?action=activate&plugin=woocommerce-fortnox-integration%2Fplugin.php&plugin_status=all&paged=1&s&_wpnonce=623dceeaa2 |
| Aspect | after-activation |
| HTTP status | 200 |
| Load time | 0.269 s |
| Memory usage | 3.6 MiB |
| JS errors | None |
| Resource errors | None |
Benchmark
No benchmark data available.
Code Statistics
Note: Third-party libraries and minified JS/CSS files are excluded from these statistics where possible, so the numbers you see here may be lower than those reported by other tools.
| Language | % | Lines of code | Comment lines | Files | |
|---|---|---|---|---|---|
| PHP | 86.9% | 5,314 | 1,390 | 46 | |
| PO File | 11.0% | 673 | 376 | 1 | |
| Bourne Shell | 1.6% | 99 | 7 | 1 | |
| SVG | 0.3% | 17 | 0 | 4 | |
| JSON | 0.1% | 4 | 0 | 1 | |
| CSS | 0.0% | 3 | 0 | 3 | |
| JavaScript | 0.0% | 2 | 0 | 2 | |
| Total | 6,112 | 1,773 | 58 | ||
PHP Code Analysis | More results »
| Lines of code | 5,200 |
|---|---|
| Total complexity | 834 |
| Median class complexity | 9.0 |
| Median method complexity | 2.0 |
| Most complex class | inc\fortnox\api\WF_Orders |
| Most complex function | inc\fortnox\api\WF_Customers::format_customer_payload() |
| Classes | 42 |
|---|---|
| Methods | 263 |
| Functions | 10 |
Additions
No data available.
PHP Error Log 3 lines
[26-Jun-2025 13:46:35 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>twentyseventeen</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6121
[26-Jun-2025 13:46:35 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>twentyseventeen</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6121
[26-Jun-2025 13:46:35 UTC] PHP Notice: Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>twentyseventeen</code> domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the <code>init</code> action or later. Please see <a href="https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/">Debugging in WordPress</a> for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6121
See also: All tests for this plugin