Ibtana - WordPress Website Builder 1.2.5.1

Does "Ibtana - WordPress Website Builder" 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
4PHP notices
No JavaScript exceptions
1Page failed to load
  • 1 302 Found
No resource errors
Performance

No data available.

Environment
WordPress version6.8.1
PHP version8.1.12
MySQL version10.6.10
PHP memory limit512M
Plugin Info
Last updated
Active installs 20,000+
WordPress.org page https://wordpress.org/plugins/ibtana-visual-editor/
Badges

WordPress compatibility badge PHP compatibility badge

Get badge code

Pages 1

Plugins ‹ Test site — WordPress

Page screenshot: Plugins ‹ Test site — WordPress
URL /wp-admin/update.php?action=install-theme&theme=sirat&ive-sirat-installed=true&_wpnonce=c1d3b3af0b
Requested URL /wp-admin/plugins.php?action=activate&plugin=ibtana-visual-editor%2Fplugin.php&plugin_status=all&paged=1&s&_wpnonce=521aafd625
Aspect after-activation
HTTP status 302
Load time 1.424 s
Memory usage 4.04 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.

PHP
Language % Lines of code Comment lines Files
PHP91.9%15,7951,42239
JavaScript5.5%94832310
CSS2.0%336142
JSON0.7%11601
Total 17,195 1,759 52

PHP Code Analysis | More results »

Lines of code 15,348
Total complexity 2,690
Median class complexity 14.0
Median method complexity 4.0
Most complex class IVE_Block_Helper
Most complex function IVE_Block_Helper::get_productscarousel_css()
Classes 30
Methods 227
Functions 28

Additions

No data available.

PHP Error Log 4 lines

[05-May-2025 11:52:30 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>ibtana-visual-editor</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
[05-May-2025 11:52:31 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>ibtana-visual-editor</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
[05-May-2025 11:52:31 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>ibtana-visual-editor</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
[05-May-2025 11:52:31 UTC] PHP Notice:  Function _load_textdomain_just_in_time was called <strong>incorrectly</strong>. Translation loading for the <code>ibtana-visual-editor</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