WordPress.org

Ready to get started?Download WordPress

Forums

Updating plugins page goes nowhere after 3.3 (4 posts)

  1. fenton.m
    Member
    Posted 2 years ago #

    My upgrade went smooth. Loving the new changes.

    But.....When I go to update a plugin, the following page say's it's downloading the update but goes no further. I left it for a minute or two then clicked on the plugins link to bring up the plugin list and found the plugin had updated. This happened twice to me which means there could be a problem...or is it just me :/

  2. robthecomputerguy
    Member
    Posted 2 years ago #

    I think it's just that you ran out of memory while activating the plugin.

    On shared hosting accounts, they restrict your memory usage.

    I didn't think that affected me as much as it does until I was running WordPress locally one day and although my memory was set just fine, I kept trying to activate certain plugins and they crashed because of being out of memory. It was shocking. Then I started to realize that I was being heavily throttled whenever I was doing a function in WordPress that took too much memory.

    Like you, it would usually go through, but I would be waiting and just see it happened when I refreshed the page. For what it's worth, if the plugin shows activated, you should be fine.

    Now I am selling WordPress friendly hosting, making lemonade out of lemons :)

  3. fenton.m
    Member
    Posted 2 years ago #

    "I think it's just that you ran out of memory while activating the plugin."

    Possible. I run a VPS. It's got other sites on it.

    The funny thing is that it did the same thing twice. I will have to wait for another update to come through to try again.

  4. robthecomputerguy
    Member
    Posted 2 years ago #

    Oh well if you run a VPS...!

    Check your php.ini to allow some more memory.

    I was shocked that the standard 64M I had specified in mine was causing out of memory errors --- but only when I activated plugins! And repeatedly, same plugins. I don't program so I just didn't expect to have the process of activating the plugin taking up more memory than actually running it...

Topic Closed

This topic has been closed to new replies.

About this Topic