WordPress.org

Ready to get started?Download WordPress

Forums

Upgraded to 2.6.1, better blogroll plugin no longer works, memory error (6 posts)

  1. c0y0te
    Member
    Posted 5 years ago #

    Upgraded from 2.5.1 to 2.6.1 and hit a 'memory error' with the better blogroll plugin (currently using v2.8) which I can't seem to fix.

    Error text:-

    WordPress database error: [Out of memory (Needed 20431824 bytes)]
    SELECT DISTINCT link_url, name, link_name, link_target, link_image, link_description, link_rel FROM wp_links INNER JOIN (wp_term_relationships INNER JOIN( wp_terms INNER JOIN wp_term_taxonomy ON wp_terms.term_id=wp_term_taxonomy.term_id) ON wp_term_taxonomy.term_taxonomy_id=wp_term_relationships.term_taxonomy_id)ON wp_links.link_id=wp_term_relationships.object_id WHERE wp_term_taxonomy.taxonomy='link_category' AND wp_links.link_visible = 'Y' ORDER BY rand() LIMIT 22

    Anyone else hit this problem, or even better, anyone fixed it?

    c0y0te

  2. gt112
    Member
    Posted 5 years ago #

    Hi

    I had the same problem. I upgraded from 2.6 to 2.6.1. I followed the upgrade instructions exactly. When I had finished the upgrade, I logged onto my site where I was presented witha button to upgrade my database. Upon clicking this I get the following

    Upgrade Complete
    Your WordPress database has been successfully upgraded!

    Continue
    WordPress database error Out of memory (Needed 20550240 bytes) for query SHOW INDEX FROM wp_postmeta; made by dbDelta WordPress database error Multiple primary key defined for query ALTER TABLE wp_postmeta ADD PRIMARY KEY (meta_id) made by dbDelta WordPress database error Duplicate key name 'post_id' for query ALTER TABLE wp_postmeta ADD KEY post_id (post_id) made by dbDelta WordPress database error Duplicate key name 'meta_key' for query ALTER TABLE wp_postmeta ADD KEY meta_key (meta_key) made by dbDelta

    This is really worrying and I would dearly love someone to explain to me what it means and if I am in trouble. Th eblog seems to be running fine but after that horrendous message, I am terrified.

  3. c0y0te
    Member
    Posted 5 years ago #

    Can anyone help us out here please?

  4. flick
    Member
    Posted 5 years ago #

    Has anyone tried contacting the developer as well?

    http://dyers.org/blog/contact/

  5. c0y0te
    Member
    Posted 5 years ago #

    Yup. Did that.

    However since then it appears there may have been an issue at the webserver end of things, because I also contacted my hoster and they confirmed there were some 'problems'. Once sorted I accessed my DB again, ran a "REPAIR" to be on the safe side and then everything was working fine after that.

    No idea what caused it in the first place though.

  6. flick
    Member
    Posted 5 years ago #

    Glad it's all sorted out :)

Topic Closed

This topic has been closed to new replies.

About this Topic