WordPress.org

Ready to get started?Download WordPress

Forums

WordPress SEO by Yoast
BuddyPress 1.5.3.1 breaks it (5 posts)

  1. cinemaminima
    Member
    Posted 2 years ago #

    After updating BuddyPress to 1.5.3.1 the Yoast feed on the Dashboard breaks, showing this error:

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 3257 bytes) in /home/server/public_html/example.com/public/wp-includes/class-simplepie.php on line 14403

    Turning off WordPress SEO ‘solves’ the problem

    http://wordpress.org/extend/plugins/wordpress-seo/

  2. Diesel12
    Member
    Posted 2 years ago #

    You need to increase your WP memory ...

  3. cinemaminima
    Member
    Posted 2 years ago #

    Whoa! Mr. diesel12 — while I appreciate the goodwill embodied in your suggestion — Dilating the memory as the first resort when two plugins have a conflict is neither practical nor prudent. Particularly when the benefit derived is so insignificant (The Yoast feed on the dashboard is inessential).

    My site's users don't need WordPress SEO; they do need BuddyPress. I'll just leave WordPress SEO deactivated until this problem is resolved.

    There is something broken here and it needs to be fixed: That is why I have posted a bug report here.

  4. Diesel12
    Member
    Posted 2 years ago #

    @cinemainima: I might be off on this but it looks like you've only got 32 mb of memory allocated, which I would consider very much so on the low side ... I personally wouldn't opt for less than 128 myself with buddy press ... but that's just my personal preference ... If you had 128 mb and were still getting memory errors, that would be one thing, but in this case it looks like you may have an amount much lower than I think a lot of people would suggest using .... just my two cents, worth what you paid for it. :)

  5. cinemaminima
    Member
    Posted 2 years ago #

    Thanks — but — we've had zero problems — for years — under our plain-vanilla set up: It works just fine; there is no need to fix something that is not broken.

    A minor conflict between two plugins has been identified, however; and I am reporting it here.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic