PodPress Plugin > Deadly Plugin!

  • cgavin

    (@cgavin)


    17 years, 4 months ago

    Grr.

    I installed and enabled the PodPress plugin, which imediately killed my blog.

    How do I manually disable the plugin? I’m not now able to access my Dashboard or administration panel at all.

    All I get is:

    Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 512220 bytes) in /home/virtual/site122/fst/var/www/html/wp-admin/admin.php on line 10

    Good isnt it? You’d think they (the plugin author) would at least have included a warning .. Oh well.

    Anyone help?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter cgavin

    (@cgavin)

    17 years, 4 months ago

    Actually, could I just bump up the max memory limitation in admin.php line 10 ?

    EDIT: Scratch that. My host is not willing to allow more memory ..

    So to re-iterate, how do I disable a plugin manually? Ta! 🙂

    Thread Starter cgavin

    (@cgavin)

    17 years, 4 months ago

    Hmm nevermind I managed to up the amount of executable memory available by editing my .htaccess via ssh

    I still think the plugin should contain a clear and prominent warning about its memory needs – if I didnt have shell access on my account it could have been a hassle.

    If any other n00b out there is interested I did it by adding the line:

    php_value memory_limit 16M

    Sorted.

    I presume in answer to my own question, deleting the plugin from wp-content would work around the issue?

    Chris_K

    (@handysolo)

    17 years, 4 months ago

    As you noticed, volunteer (and unpaid) support folks can’t always get to all posts within 20 minutes. 😉

    But to answer your final question: Yes, just delete the plugin from the wp-content/plugins

    Thread Starter cgavin

    (@cgavin)

    17 years, 4 months ago

    Not all old old chap. Free is good. You weren’t too tardy either, only a few minutes out. 🙂

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘PodPress Plugin > Deadly Plugin!’ is closed to new replies.