WPIntell

Source evidence

Error After Update to Latest Version 3.3.15

Order Tracking – WordPress Status Tracking Plugin · support · 2024-09-12T13:27:00+00:00

mixedsentiment
highseverity
0.95relevance
2replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

10 / 38 rows with source links

26.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
hollowdra resolved
Hello, After I updated to latest version 3.3.15 a critical error happened in WordPress admin area. This is the error: An error of type E_ERROR was caused in line 49 of the file /home2/tradenb7/public_html/wp-content/plugins/order-tracking/lib/simple-admin-pages/simple-admin-pages.php. Error message: Uncaught Error: Class “sapLibrary_2_6_19″ not found in /home2/tradenb7/public_html/wp-content/plugins/order-tracking/lib/simple-admin-pages/simple-admin-pages.php:49 Stack trace: #0 /home2/tradenb7/public_html/wp-content/plugins/order-tracking/includes/Export.class.php(52): sap_initialize_library(Array) #1 /home2/tradenb7/public_html/wp-includes/class-wp-hook.php(324): ewdotpExport->register_install_screen(”) #2 /home2/tradenb7/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array) #3 /home2/tradenb7/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array) #4 /home2/tradenb7/public_html/wp-admin/includes/menu.php(161): do_action(‘admin_menu’, ”) #5 /home2/tradenb7/public_html/wp-admin/menu.php(412): require_once(‘/home2/tradenb7…’) #6 /home2/tradenb7/public_html/wp-admin/admin.php(158): require(‘/home2/tradenb7…’) #7 /home2/tradenb7/public_html/wp-admin/plugins.php(10): require_once(‘/home2/tradenb7…’) #8 {main} thrown Please help, I don’t want to deactivate the plugin. Thank you for reporting this. Looks like there was an issue with a version number in yesterday’s update. We’ve just released a new version (3.3.16) with a fix. The new version fixed the issue. thank you.

Comments

2 shown
jaysupport 2024-09-12T13:50:00+00:00

Thank you for reporting this. Looks like there was an issue with a version number in yesterday’s update. We’ve just released a new version (3.3.16) with a fix.

hollowdra 2024-09-12T13:59:00+00:00

The new version fixed the issue. thank you.