Fatal error after downgrade to 3.6.4
-
Report No. BVNBKAIY
Hi LS,
As I downgraded from 4.2 to 3.6.4 I was met with the fatal error message below.
I was able to login into WP afterwards and activate the 3.6.4 LS-plugin, and the site now works without problems. So I do not need further help or support.
I just want to let you know in case it may be helpful for future bug fixes etc.
Fatal error: Uncaught Error: Call to protected LiteSpeed\Data::__construct() from context 'LiteSpeed\Root' in /home/iotedk/public_html/wp-content/plugins/litespeed-cache/src/root.cls.php on line 84 Call stack: LiteSpeed\Root::cls() wp-content/plugins/litespeed-cache/src/purge.cls.php:270 LiteSpeed\Purge::_purge_all_cssjs() wp-content/plugins/litespeed-cache/src/purge.cls.php:159 LiteSpeed\Purge::_purge_all() wp-content/plugins/litespeed-cache/src/purge.cls.php:148 LiteSpeed\Purge::purge_all() wp-includes/class-wp-hook.php:305 WP_Hook::apply_filters() wp-includes/class-wp-hook.php:327 WP_Hook::do_action() wp-includes/plugin.php:470 do_action() wp-admin/includes/class-wp-upgrader.php:857 WP_Upgrader::run() wp-admin/includes/class-plugin-upgrader.php:231 Plugin_Upgrader::upgrade() wp-content/plugins/litespeed-cache/src/activation.cls.php:485 LiteSpeed\Activation::upgrade() wp-content/plugins/litespeed-cache/src/debug2.cls.php:90 LiteSpeed\Debug2::beta_test() wp-content/plugins/litespeed-cache/src/debug2.cls.php:454 LiteSpeed\Debug2::handler() wp-content/plugins/litespeed-cache/src/router.cls.php:730 LiteSpeed\Router::handler() wp-content/plugins/litespeed-cache/src/core.cls.php:291 LiteSpeed\Core::proceed_action() wp-content/plugins/litespeed-cache/src/core.cls.php:238 LiteSpeed\Core::after_user_init() wp-includes/class-wp-hook.php:303 WP_Hook::apply_filters() wp-includes/class-wp-hook.php:327 WP_Hook::do_action() wp-includes/plugin.php:470 do_action() wp-settings.php:578 require_once() wp-config.php:103 require_once() wp-load.php:50 require_once() wp-admin/admin.php:34
The page I need help with: [log in to see the link]
Viewing 3 replies - 1 through 3 (of 3 total)
Viewing 3 replies - 1 through 3 (of 3 total)
- The topic ‘Fatal error after downgrade to 3.6.4’ is closed to new replies.