WordPress.org

Forums

podPress
HTTP Error 500 at wp-admin (15 posts)

  1. Matt Crosslin
    Member
    Posted 3 years ago #

    I get the following error on the admin section of site on my WordPress install when the podpress plugin is activated:

    HTTP Error 500 (Internal Server Error): An unexpected condition was encountered while the server was attempting to fulfill the request.

    Deactivating it solves the problem. The sites will still work fine - it is just the wp-admin area that gives this code. Is there a way to fix this by any chance? Thank you!

    http://wordpress.org/extend/plugins/podpress/

  2. ntm
    Member
    Plugin Author

    Posted 3 years ago #

    Hi Matt,

    of course it should be possible to fix this and when I know what the problem is I definitely going to fix it.

    But this problem does not seem to occur in every blog including my test blogs. Furthermore this error message isn't helping me identify the problem. It is a very general error message and can have diverse causes.
    But since this problem is not occurring in every blog, it seems likely that the cause has something to do with the configuration of the server of your blog (e.g. available memory to execute php scripts) or an unwanted interaction with a different plugin (or the theme).

    You can test whether it is a memory problem by deactivating other plugins temporarily.
    This would also show whether it is an interaction between the plugins. You may deactivate the plugins one after another and try whether it makes a difference before you deactivate the next plugin.

    Did install a further plugin recently? Did podPress work before?

    Once we know which other plugin is connected to this error, I can analyse the plugins and try to fix this problem.

    Tim

  3. Matt Crosslin
    Member
    Posted 3 years ago #

    Thank you Tim. I forgot to include two details:

    - PodPress was working great for a year or so. This problem happened when I finally got a chance to update to the newest version of WordPress. So I know there might be something on the WP side.
    - Only one blog on my site uses this plugin, and it is the only plugin that it has because it is pretty much a podcast only site. When I deactivate podpress on the site, the admin area works. If I activate podpress on another blog with a different theme, I get the same problem. If I activate it on the network, it crashes the whole admin for the whole site. So I have to keep it deactivated for the network even though it stays activated on that one site. It has been that way since I started the site, not sure why. I think I just never thought to activate it on the network - just the one site that uses it.

  4. ntm
    Member
    Plugin Author

    Posted 3 years ago #

    Okay. It is obviously no interference with a different plugin.
    That makes the debugging more difficult.

    I have created a new Multi Site blog to see whether I can reproduce the error with a WP 3.4.1 MU blog and podPress 8.8.10.13. But I did not have a problem to activate the plugin in a single blog nor for the complete network. I could also create podcast post in the sub blog.

    So far I have no idea why this error happens in your blog system. It is imaginable that something went eventually wrong during the upgrade. But I don't know that.
    That is why I would like to suggest that you remove the plugin files and folders and also remove the rows podPress_config and podPress_version from the db table wp_options and the options tables of the sub blogs. Afterwards install the podPress plugin fresh via the plugins page of the blog.
    (The other entries which contain the relations between media files and posts are in the wp_postmeta table and won't get lost in this process.)

  5. ntm
    Member
    Plugin Author

    Posted 3 years ago #

    Maybe there is a possibility to find out whether any other error happens before the server throws the "HTTP 500" error.

    If you would set the wp_debug constant then there is maybe a chance that WP throws an error message before the server it does. An error message of WP would probably be more helpful.
    Maybe set the constant and activate the plugin afterwards. Can you see any other error messages?

  6. Matt Crosslin
    Member
    Posted 2 years ago #

    Thank you for these suggestions - I will check into them and see what happens.

  7. Matt Crosslin
    Member
    Posted 2 years ago #

    Deleting the rows and folder and then re-installing unfortunately didn't work.

    Here was the additional error that came up with the debug turned on:

    Notice: Undefined index: enablePodangoIntegration in /home1/mattcro1/public_html/site-downthelinezine/wp-content/plugins/podpress/podpress.php on line 265

  8. ntm
    Member
    Plugin Author

    Posted 2 years ago #

    Thank you for doing these tests!

    The debug message is helpful and I have fixed at least this particular issue. It would be great if you would install the current Development
    Version
    of podPress (in the list among the other versions) and see whether the modification solve also the bigger problem.
    This notice is related some a line of code which has been a little bit sloppy but I'm not sure that this was the cause for the HTTP 500 error. I fixed some other lines of the code which would cause a comparable notice and I hope that in case the HTTP 500 error still occurs you could do a further test with the debug constant set to TRUE.
    This Development Version is probably not the solution but a step forward.

  9. ntm
    Member
    Plugin Author

    Posted 2 years ago #

    Sometimes it is possible to view the error.log file of the rented webspace. This file which is created automatically by the server software contains all types of error messages and notices. Sometimes it lies in a sub folder of the webspace which one can reach via FTP. Maybe this file contains other messages which occur right before the HTTP 500 error occurs.

  10. Matt Crosslin
    Member
    Posted 2 years ago #

    So far, no luck with the dev version or error.log. There are some other errors from the debug now, but they all seem to deal with WP files:

    Notice: add_option was called with an argument that is deprecated since version 2.3 with no alternative available. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2714

    Notice: wp_register_script was called incorrectly. Scripts and styles should not be registered or enqueued until the wp_enqueue_scripts, admin_enqueue_scripts, or init hooks. Please see Debugging in WordPress for more information. (This message was added in version 3.3.) in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2748

    Notice: Undefined variable: plugin in /home1/mattcro1/public_html/site-downthelinezine/wp-content/plugins/wp-fb-fan-box/wp-fb-fan-box.php on line 71

    Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2628

    Notice: load_plugin_textdomain was called with an argument that is deprecated since version 2.7 with no alternative available. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2714

    Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /home1/mattcro1/public_html/site-downthelinezine/wp-admin/includes/ms.php on line 556

  11. ntm
    Member
    Plugin Author

    Posted 2 years ago #

    You are right. All these messages seem to be related to other plugins or the theme. Most of them are only notices - nothing what would disturb the server or the WP software. But the last one is a "Fatal error" message and it points that there is not enough RAM memory to execute all plugins. I guess that is the problem which causes in the end the HTTP 500 error.
    This is consistent with the information that you have updated WP recently. New WP versions require sometimes more memory. I have noticed that during the upgrade from WP 2.3 to 2.6. WP 2.6 needed more memory.

    I'm not sure what the best way is to solve this problem.

    It seems that you are using other plugins (which register widgets - obviously with a deprecated method). Maybe you could deactivate those if using podPress is more important.
    The other possibility would probably be asking your hosting provider for the permission to use more RAM (increase the PHP limit called memory_limit). Although the memory_limit in your case seems to be 64 MB which should be enough for WP + podPress. I have a test blog with the same amount of available memory. I use only one other plugin besides podPress and it seems that opening the Dashboard > Home screen costs approximately 33 MB (with podPress deactivated: 28.16 MB). But this is no Multi Site blog.
    I use the WP System Health plugin to measure the memory usage. Could you do this to? Please install it and look how much memory is available while podPress is deactivate. You can see the memory usage in the footer line of the admin screens. Maybe go to the Dashboard > Home screen too.

  12. Matt Crosslin
    Member
    Posted 2 years ago #

    I did the system health, and it said this on the main site:

    Memory: 61.46 MB of 64.00 MB ~ 96.04 %

    On the site with PodPress installed, it had this:

    Memory: 69.06 MB of 64.00 MB ~ 107.9 %

    I went through all of my plugins, and still couldn't find the one that is causing all of those sidebar widget errors. BUT - I did find that when I deactivated the "Register Plus Redux" widget site wide, the podcast site admin area started working. I thought I had checked that one, but I guess not. I don't know if I need that plugin, but I know where the problem is now.

    Once it started working, there were three additional notices that only appeared on the podcast site when the debug constant was one. They might be of use to you at some point, but I have no idea if the first two are related to your plugin or not:

    Notice: has_cap was called with an argument that is deprecated since version 2.0! Usage of user levels by plugins and themes is deprecated. Use roles and capabilities instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2722
    
    Notice: is_site_admin is deprecated since version 3.0! Use is_super_admin() instead. in /home1/mattcro1/public_html/site-downthelinezine/wp-includes/functions.php on line 2638
    
    Notice: Undefined index: enablePodangoIntegration in /home1/mattcro1/public_html/site-downthelinezine/wp-content/plugins/podpress/podpress.php on line 495
  13. ntm
    Member
    Plugin Author

    Posted 2 years ago #

    I tried to install the Register Plus Redux plugin to see how it influences the whole process. But I could not find the plugin. I found only this article which basically says that the plugin contained a vulnerability and has been removed from the plugin repository.

    But I would say that this particular plugin was not the problem in your case. As your memory measurements show, almost all memory of your blog is in use. Deactivating a plugin decreases the memory usage and leaves more memory for podPress. You could probably deactivate every other plugin and would see the same effect - that podPress works.

  14. Matt Crosslin
    Member
    Posted 2 years ago #

    I was going through the plugins one at a time to see which one was causing all those errors with the register widget. If it didn't fix it, then I reactivated it. I was also checking the podcast site each time just in case. The Register Plus Redux plugin was the only one that brought the podcast site admin area back up. So whatever it was, it seemed to be causing the problem.

  15. ntm
    Member
    Plugin Author

    Posted 2 years ago #

    Okay. I understand. I'm happy that you have found this solution and that podPress works again in your blog.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags