PluginUs.Net - Business Tools for WooCommerce and WordPress

[realize your idea - make your dreams come true]

Support Forum

You need to log-in to create request (topic) to the support

Large autoload footprint from BEAR

🎄 Holiday Notice - Support Vacation 🎄

ATTENTION: From December 28, 2025 to January 6, 2026 our support team will be on vacation.

Important information:

  • ❌ No ticket responses from December 28 to January 6
  • ✅ Support will resume on January 7, 2026
  • 📝 You can still submit tickets during vacation - they will be queued and answered starting January 7
  • ⚠️ Urgent technical issues: Please check our documentation and codex first

🎅 Season's Greetings! 🎅

We want to thank all our amazing customers for your trust and support throughout 2025!
Merry Christmas and Happy New Year to you and your families! 🎉

We wish you:

  • 🚀 Successful online stores
  • 💰 Growing sales
  • 😊 Happy customers
  • 🎯 Achieved goals in 2026

Thank you for being with us! We appreciate every one of you and look forward to continuing our work together in the new year.

Rest, recharge, and see you in 2026!

Best regards,
PluginUs.Net Team

The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday. If you have problems with registration ask help on contact us page please
If you not got email within 24~36 business hours, firstly check your spam box, and if no any email from the support there - back to the forum and read answer here. DO NOT ANSWER ON EMAILS [noreply@pluginus.net] FROM THE FORUM!! Emails are just for your info, all answers should be published only here.
The support doesn work on Saturdays and Sundays, so some Friday requests can be answered on Monday.
nimaghaziii(@nimaghaziii)
2 Posts
Customers
November 11, 2025, 19:27

I’m optimizing a WooCommerce site that uses BEAR (WOOBE) and noticed a pretty big autoload footprint in wp_options coming from the plugin — roughly ~0.5 MB. Most of it looks like UI stuff: profiles/options, e.g.

  • woobe_options_*

  • woobe_profiles_*

  • woobe_shop_manager_visibility

  • other BEAR-related arrays

I’d like to keep total autoload under 1MB, so I’m planning to set these to autoload = no so they only load on BEAR admin screens.

Questions:

  1. Is it safe to switch these BEAR options to autoload = no? (Assuming they’re just for the BEAR admin UI and not needed on the front end.)

  2. Does BEAR (or an update/migration) ever flip them back to autoload=yes or recreate them with autoload on? If yes, any hook/setting to stop that so the change sticks?

Thanks!

#1
Alex Dovlatov(@alexdev)
466 Posts
November 12, 2025, 13:23

Hello

Thank you for bringing this optimization issue to our attention.

Will BEAR flip them back to autoload = yes - unfortunately, yes (for this current moment) - this is the main issue. When BEAR updates these options (for example, when you save settings or profiles), it will likely reset them back to autoload = yes. This is standard behavior for most plugins using update_option().

I think you can do it without problem as BEAR need only when you using it on admin panel. Here is the screen https://share.pluginus.net/image/i20251112130403.png where function update_option used inside the plugin - you can set false there where its not applied and do tests - all should work.

We just did tests and all works fine.

You can do next:

  1. open phpmyadmin
  2. do query to see all options:
    UPDATE wp_options
    SET autoload = 'off'
    WHERE option_name LIKE 'woobe_%'
    AND option_name != 'woobe_version'
    AND autoload != 'off';
  3. do query to set 'off' for autoload
    SELECT option_name, LENGTH(option_value) as size, autoload
    FROM wp_options
    WHERE option_name LIKE 'woobe_%'
    ORDER BY size DESC;
  4. make changes in the plugin code for all functions update_option, we did it for the next update already in the plugin code
  5. Test it. On ourr side it works as it been

Welcome!

 

 

#2