• Hello.

    Our WordPress Site Health screen flags one critical issue on our site: autoload options could affect performance.

    When investigating the list of autoloaded options, we find that um_options is by far the largest item at 1.19 MB. This is 5X the size of the next largest autoloaded option on our site.

    Is this size normal / expected? If not, is there a way to mitigate this?

    Thanks for any advice.

Viewing 10 replies - 1 through 10 (of 10 total)
  • @silversee

    Total size of UM Options over 1 MByte is not normal.
    You can try this new “Show All Options” plugin to identify your largest UM Option values.

    https://github.com/MissVeronica/um-show-all-options

    Thread Starter silversee

    (@silversee)

    @missveronicatv

    Thank you for this, it is very helpful. We already use several of your other extensions on our site, and are grateful for your work.

    It appears the that main culprit here is the block_disposable_emails option, from the UM Core extension Block Disposable Email Domains. When sorted by size reversed, it shows a size of 1236645.

    However, even after deactivating this extension, the option still appears in the list. If we wanted to get rid of this, is it necessary to edit the database manually?

    Thanks in advance.

    @silversee

    There is an update to this UM Extended plugin which fixes this size issue.
    The updated plugin will remove the Disposable Emails from UM Options and save the emails in an own option.

    You can read the story here and how to fix it

    https://github.com/ultimatemember/Extended/issues/91

    Thread Starter silversee

    (@silversee)

    @missveronicatv

    Excellent, thank you. I will follow up on this.

    • This reply was modified 3 months, 2 weeks ago by silversee.
    Thread Starter silversee

    (@silversee)

    @missveronicatv

    So, I installed the Blocked_Disposable_Email_Domains plug-in from the 2.1.0-beta.16 beta release on Github, but it appears that there is no change in behavior. Looking at your recent comment on issue #91, it seems the change was made in source, but not to the release zip file?

    I don’t really have the ability or environment to build it from source. Any ideas, other than to wait for a proper release?

    Thanks again for the help.

    @silversee

    Installing from the ZIP with single plugins will not fix this issue.
    The fix is made when you install all 19 Extended plugins.

    Try to deactivate the plugin and activate the plugin again
    to force a reload of the Disposable emails.

    • This reply was modified 3 months, 2 weeks ago by missveronica.
    Thread Starter silversee

    (@silversee)

    @missveronicatv

    Thank you.

    I wanted to start fresh, so I proceeded as follows:

    1. Deactivated and uninstalled the separate um_block_emails plugin that I had recently installed. (Note that this procedure seemed to leave an empty um-block-emails directory in /plugins for some reason.)
    2. Deactivated and uninstalled the UM Extended original plugin (full package)
    3. Reinstalled UM Extended (full package) from the latest Github release containing the fix (it installed and activated fine)
    4. From the UM Extended settings page, I activated the Block Disposable Email Domains subcomponent

    Unfortunately, this triggered an immediate site crash, throwing up the following error: Invalid Class Name: \UM_Extended_Block_Emails\Core

    I had no access to the WordPress dashboard, but my hosting provider was able to deactivate UM Extended via File Manager, and the site came back.

    I am wondering if this error had something to do with us having installed the separate um_block_emails plugin side-by-side with UM Extended package? (I did not realize this is what would happen when I installed it–I thought it would just replace the existing subcomponent.)

    In any case, our site is working again, but I am unsure how to reset things so that UM Extended will work again.

    Based on the pathname shown in the error, I think the code may be looking for the individual plugin in the root of the /wp-content/plugins directory. Does this sound right? Does this mean that if I reinstalled the individual plugin, things might work?

    Looking at the file system, it is unclear where the full UM Extended package actually gets installed, since it does not seem to have its own separate directory.

    I appreciate that you are not paid to be tech support, but if you have any thoughts, we would appreciate them! πŸ™

    All the best.

    Edit: and of course, we still have the very large um_options payload at this point. πŸ™

    • This reply was modified 3 months, 2 weeks ago by silversee.
    • This reply was modified 3 months, 2 weeks ago by silversee.

    @silversee

    I have reported this issue to the UM Developers here

    https://github.com/ultimatemember/Extended/issues/86

    Your solution to do is (copied from the issue link):

    I have tried with “Version 2.0.5” active before activating “2.1.0-beta.15” and I get “PHP Fatal error: Cannot redeclare um_extended_plugin()”.

    I deactivated all 6 extended plugins with “Version 2.0.5”
    Deactivated “Version 2.0.5”
    Activated “2.1.0-beta.15” now OK when there are no extended plugins activated
    Activated all 6 extended plugins with “2.1.0-beta.15”

    It’s the only solution with current version of “2.1.0-beta.15”

    Thread Starter silversee

    (@silversee)

    Thank you, but unfortunately, this fix does not work for me.

    After installing and activating UM Extended version 2.10 beta.16, whenever I enable the Block Disposable Email Domains extension, it crashes my site with the following error:

    Invalid Class Name: \UM_Extended_Block_Emails\Core

    If I uninstall the beta version and reinstall version 2.04, I can activate this extension without issue, so I assume the problem is introduced with new version.

    I am running WordPress 6.8.3 and PHP 8.3, in case that is relevant.

    Unfortunately, this means that as of now, I have no resolution to original autoload performance issue, since the the email domain list is still present within um_options.

    How can I report this as a bug or get some further assistance?

    Thanks in advance.

Viewing 10 replies - 1 through 10 (of 10 total)

You must be logged in to reply to this topic.