WP-Members

  • Rich Schnieders

    (@rschnieders)


    1 year, 4 months ago

    Since the update to 3.5.0 we have experienced difficulties. I have updated to 3.5.1 but still receive the following debug errors: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 12288 bytes) in /var/www/4d769572-f7a3-48c6-9441-8dc1181e77c4/leeares.com/wp-includes/functions.php on line 650

    Debug also gives us two notices:

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/4d769572-f7a3-48c6-9441-8dc1181e77c4/leeares.com/wp-includes/functions.php on line 6114

    Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms-user-management domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/4d769572-f7a3-48c6-9441-8dc1181e77c4/leeares.com/wp-includes/functions.php on line 6114

    With WP-Members deactivated the page loads properly. The two notices still pop up but the page loads. With Ninja forms deactivated the two notices go away.

    Under Site Health we have the following critical issue: Autoloaded options are configuration settings for plugins and themes that are automatically loaded with every page load in WordPress. Having too many autoloaded options can slow down your site. Your site has 678 autoloaded options (size: 6 MB) in the options table, which could cause your site to be slow. You can review the options being autoloaded in your database and remove any options that are no longer needed by your site.

    Thanks for all you help.

    Rich

    The page I need help with: [log in to see the link]

Viewing 10 replies - 1 through 10 (of 10 total)
  • Plugin Author Chad Butler

    (@cbutlerjr)

    1 year, 4 months ago

    The two notices you’re getting for _load_textdomain_just_in_time being loaded incorrectly are coming from ninja forms. So unfortunately, that’s not something I can help you with.

    With WP-Members deactivated the page loads properly. The two notices still pop up but the page loads. With Ninja forms deactivated the two notices go away.

    What about with WP-Members activated, but Ninja Forms deactivated?

    Thread Starter Rich Schnieders

    (@rschnieders)

    1 year, 4 months ago

    With WP-Members active but Ninja forms deactive we receive: Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 12288 bytes) in /var/www/4d769572-f7a3-48c6-9441-8dc1181e77c4/leeares.com/wp-includes/functions.php on line 650

    thanks for the help!

    Rich

    Thread Starter Rich Schnieders

    (@rschnieders)

    1 year, 3 months ago

    is there a way to download and install a previous version of WP-Members so that we can correct the issues remaining on our website until another patch is developed? We are currently running with WP-Members deactivated which limits some of our functionality.

    Thanks you

    Rich

    Plugin Author Chad Butler

    (@cbutlerjr)

    1 year, 3 months ago

    You can always get previous versions from the “advanced options” section on the following page:
    https://ww.wp.xz.cn/plugins/wp-members/advanced/

    However, what’s probably of more concern is what you noted in your post above:

    Your site has 678 autoloaded options (size: 6 MB) in the options table, which could cause your site to be slow.

    You should take a deeper look at that because that could very well be a big part of your site’s memory problem.

    The size of the options WP-Members loads will vary depending on your setup of the plugin. However, it’s generally unlikely to be large – typically in the 12K – 24K range, and that would be total, not just autoloaded options.

    Note that you can test things out by deactivating plugins that are upstream in the load order, but that alone won’t necessarily track down what’s loading. The autoload options from any plugins that left behind their stored options will still be autoloaded even if the plugin was removed. You may need to review your wp_options table to see what is being autoloaded.

    You can handle things as you deem best, but from the information you provided here, the issue seems to be some memory issues that need to be addressed.

    Plugin Author Chad Butler

    (@cbutlerjr)

    1 year, 3 months ago

    Followup question(s):

    How many users do you have on the site?

    Does your registration form fields include any file upload fields (image or file)?

    Thread Starter Rich Schnieders

    (@rschnieders)

    1 year, 3 months ago

    We have 20 or so entries currently. We are in the process of setting up the system for users to log into protected areas of the site and update their records on the site. But we have not opened up to all of our members yet as it is in development. Mos of the updates to the files is text, I don’t think we have added any uploads of files or pictures yet.

    I am starting to investigate the memory issues and possible ways to correct it.

    Thanks

    Plugin Author Chad Butler

    (@cbutlerjr)

    1 year, 3 months ago

    One possibility that I have discovered that exhausts memory is a setting in the plugin’s memberships.

    Are you using “memberships”? And if you are, do you have memberships that are set up in a parent-child relationship? If so, do you have “Access by child membership” enabled in any child membership? If so, this may be the issue.

    An example of how this setting is used would be if you had a membership that had different expiration periods. You would have a parent membership with a child membership for each expiration period. The parent would have “Access by child membership” enabled so that the user is accessing the parent membership when they have one of the child memberships.

    Right now, this setting isn’t working as intended.

    If you enable this option for a child membership that has no children below it, it will cause an endless loop in the plugin when it checks user access, thus exhausting the memory.

    If this is the case for you, check that you actually need this option enabled. It should be used for parent memberships that the user would access by having one of the possible child memberships. If you have it enabled on a membership that has no children, then it is misconfigured and you can uncheck it (which would solve the memory problem).

    I’m working on this issue so that the setting will work as intended, but the quick fix is if it’s not used properly to begin with, just disable it.

    • This reply was modified 1 year, 3 months ago by Chad Butler.
    Plugin Author Chad Butler

    (@cbutlerjr)

    1 year, 3 months ago

    Regardless of whether the setting mentioned above is right or wrong, the following alpha build is intended to correct it. If you want to test this out and let me know if it resolves the issue:

    https://github.com/rocketgeek/wp-members-dev/releases/tag/3.5.1.3

    Thread Starter Rich Schnieders

    (@rschnieders)

    1 year, 3 months ago

    Chad, you are the man. Once I uploaded and activated 3.5.2.a.3 the website began to work again. No more fatal errors. it is all working properly now. Memory is staying consistent.

    Thanks for all the help, I look forward future updates.

    Rich

    Plugin Author Chad Butler

    (@cbutlerjr)

    1 year, 3 months ago

    Glad to hear that resolved the problem for you. The issue did lead me to a definite improvement in the plugin, with some items for future improvement as well.

    I had expected to release 3.5.2 as production this evening, but there’s one more thing I’m working on that will hopefully I will be able to resolve before releasing it (it’s an issue with the upgrade script getting any previously selected stylesheet that was not the default). Once that’s resolved, I see this being pushed out.

    Thanks for your patience while I figured this one out. It was not an easy one to find.

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

The topic ‘WP-Members’ is closed to new replies.