Upgraded from 4.13 to 4.2 Patch 2 and now members can't read new PMs

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • duvik
    New Member
    • Nov 2009
    • 7
    • 3.8.x

    [Forum] Upgraded from 4.13 to 4.2 Patch 2 and now members can't read new PMs

    Members unable check new PMs unless they first select and mark them read. When they click on a private message that is not marked as unread the following error message is displayed:

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 72 bytes) in ~/forums/includes/functions.php on line 6560

    I also get a similar error when I try to access my own member page:

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 71 bytes) in ~/forums/includes/class_bbcode.php on line 1280

    I searched around and found a post recommending that the person ask his host to allot more memory for php in the php.ini file, but it wasn't for the exact same error and it was for an old 3.4 version of vBulletin thread. I just don't think that is the solution. It's never been an issue before the upgrade.

    Another post in the same thread mentioned adding this line to the begginning of the config.php file:

    Code:
    ini_set('memory_limit', 32 * 1024 * 1024);
    I did this and it did not help.

    The website is http://www.thetangledweb.net
  • Zachery
    Former vBulletin Support
    • Jul 2002
    • 59097

    #2
    Well, that sets it to the same limit you're already running out of. Change 32 to 48.

    Comment

    • duvik
      New Member
      • Nov 2009
      • 7
      • 3.8.x

      #3
      Originally posted by Zachery
      Well, that sets it to the same limit you're already running out of. Change 32 to 48.
      You, my friend, are a genius! Thanks for the prompt reply. It worked like a charm. Is there any reason that this needed to be changed between versions?
      Last edited by duvik; Fri 31 Aug '12, 6:49pm. Reason: added a question

      Comment

      • Zachery
        Former vBulletin Support
        • Jul 2002
        • 59097

        #4
        Not sure of the specific reasons, sorry!

        Comment

        widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
        Working...
        😀
        😂
        🥰
        😘
        🤢
        😎
        😞
        😡
        👍
        👎