New error since installing WP-O 3.2.1

  • Resolved jsm06278

    (@jsm06278)


    3 years, 2 months ago

    I reported an error a few days ago and I have another (see below) we haven’t seen before that seems to point to the new 3.2.1 version. We’re also noticing slower results from Pagespeed and GTMetrix but I haven’t explored that thoroughly. I’m also following the Innodb thread because we converted our tables from MyISAM too. 

    [06-Dec-2021 16:57:42 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function _wp_get_current_user() in /home4/ctbirdin/public_html/wp-includes/pluggable.php:70
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/pluggable.php(1072): wp_get_current_user()
#1 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(36): is_user_logged_in()
#2 [internal function]: wpo_cache('<!DOCTYPE html>...', 9)
#3 {main}
  thrown in /home4/ctbirdin/public_html/wp-includes/pluggable.php on line 70
[06-Dec-2021 17:29:16 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 17:59:16 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 19:10:57 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 19:11:00 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
[06-Dec-2021 19:14:47 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function _wp_get_current_user() in /home4/ctbirdin/public_html/wp-includes/pluggable.php:70
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/pluggable.php(1072): wp_get_current_user()
#1 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(36): is_user_logged_in()
#2 [internal function]: wpo_cache('<!DOCTYPE html>...', 9)
#3 {main}
  thrown in /home4/ctbirdin/public_html/wp-includes/pluggable.php on line 70
[06-Dec-2021 19:16:55 UTC] PHP Fatal error:  Uncaught Error: Call to undefined function wp_cache_get() in /home4/ctbirdin/public_html/wp-includes/option.php:143
Stack trace:
#0 /home4/ctbirdin/public_html/wp-includes/l10n.php(63): get_option('WPLANG')
#1 /home4/ctbirdin/public_html/wp-includes/l10n.php(137): get_locale()
#2 /home4/ctbirdin/public_html/wp-includes/l10n.php(1278): determine_locale()
#3 /home4/ctbirdin/public_html/wp-includes/l10n.php(1240): _get_path_to_translation_from_lang_dir('wp-optimize')
#4 /home4/ctbirdin/public_html/wp-includes/l10n.php(1210): _get_path_to_translation('wp-optimize')
#5 /home4/ctbirdin/public_html/wp-includes/l10n.php(1308): _load_textdomain_just_in_time('wp-optimize')
#6 /home4/ctbirdin/public_html/wp-includes/l10n.php(177): get_translations_for_domain('wp-optimize')
#7 /home4/ctbirdin/public_html/wp-includes/l10n.php(289): translate('Output is too s...', 'wp-optimize')
#8 /home4/ctbirdin/public_html/wp-content/plugins/wp-optimize-premium/cache/file-based-page-cache-functions.php(32): __('Output is too s...', 'wp- in /home4/ctbirdin/public_html/wp-includes/option.php on line 143
Viewing 6 replies - 1 through 6 (of 6 total)

  • @jsm06278 Could you please try to de-activate and delete the plugin and then re-install and activate the WP-Optimize plugin and check if it helps to fix the issue?

    Thread Starter jsm06278

    (@jsm06278)

    As requested I deactivated WPO Premium 3.2.1, deleted it, and re-installed it. I think I’ve discovered a number of anomalies so bear with me while I write a book.

    I configured settings before starting page caching and minify then turned on page caching … waited … then turned on minify … waited … tried to turn on Preload but kept getting an error msg “Unexpected … ” shortly after starting it and it would fail to begin the process. Finally, I purged the page cache and after the msg came back saying it was completed started Preload again and it finally started preloading (took an hour to complete). If it’s necessary to purge the page cache before Preloading then I would suggest that be incorporated into the process that starts when you click Run Now.

    Regarding performance after reinstalling, there seems to be no improvement.

    Regarding the new error that I reported originally, time will tell if that continues to be an issue. I wouldn’t expect it to appear immediately and I have no idea what would trigger it. Presumably, WPO has looked at the error from their side.

    Lastly, I was very surprised to discover that after deactivating and uninstalling the existing WPO 3.2.1 version of the plugin then re-installing it, when I looked at Database/Options which shows all the tables in the database it was offering to convert my MyISAM tables to InnoDB AGAIN. Prior to deactivating, uninstalling while running 3.2.1 I had already “converted” these tables to InnoDB. So I have to ask, are these tables actually being converted??? Why would I be offered the option again if they were? Something seems very wrong with this so I look forward to solving this mystery.

    In case it matters, we are also running a paid version of UpdraftPlus – another one of your products.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    ” WPO Premium 3.2.1,”

    @jsm06278

    You’re using a commercial/premium plugin, so please use their official support channel. We feel they are best equipped to support their products.

    https://getwpo.com/

    Commercial products are not supported in these forums.

    Thread Starter jsm06278

    (@jsm06278)

    Thank you. I’ve reposted on their support page.

    Thread Starter jsm06278

    (@jsm06278)

    Importantly, I’ve made a serious mistake reporting a problem that does not exist.

    I’m chewing on crow at the moment …

    I’d like to apologize profusely to the WPO team regarding the conversion to InnoDB. It turns out that I had converted the tables on our staging site but not the production site. I was reporting my findings on the production site which I had never converted.

    So sorry.

    @jsm06278 I’ve replied back to your ticket, please respond there, for now closing this thread.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘New error since installing WP-O 3.2.1’ is closed to new replies.