jeremyrosen
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: PHP Warning When Accessing Admin Panel and SiteI spoke too soon, of course, now I’m magically getting an “No input file specified” error when attempting to login to the admin panel. I seriously can’t wrap my head around what’s going wrong.
Forum: Fixing WordPress
In reply to: PHP Warning When Accessing Admin Panel and SiteI now suspect this has something to do with Ultimate Tag Warrior. It was the only new thing I added to my site earlier in the week and many of the errors I received had UTW specifically in the name (maybe about 30%).
I let it sit for the night and everything was working fine when I got up. Then things slowed down again and I received an error when responding to a comment. I just shut off UTW and things seem to be zipping along again.
Forum: Fixing WordPress
In reply to: PHP Warning When Accessing Admin Panel and SiteI received these errors on the one rare occasion I actually got to the control panel:
(Where the WordPress blog updates appear)
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
CGI-limits reached (-1), please try again later!(Where the incoming links normally appear)
You don't have permission to access /wp-admin/index-extra.php on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.
(On my web site above all the content)
Warning: main(/homepages/1/d95366573/htdocs/axesroot/wp-content/plugins/akismet/akismet.php) [function.main]: failed to open stream: Too many open files in system in /homepages/1/d95366573/htdocs/axesroot/wp-settings.php on line 205
Warning: main() [function.include]: Failed opening '/homepages/1/d95366573/htdocs/axesroot/wp-content/plugins/akismet/akismet.php' for inclusion (include_path='.:/usr/local/lib/php') in /homepages/1/d95366573/htdocs/axesroot/wp-settings.php on line 205
Forum: Fixing WordPress
In reply to: PHP Warning When Accessing Admin Panel and SiteThose files are there and set to readable permissions. Furthermore, I’ve done nothing with the site at all in the last day.
As some additional information, I am now getting an occasional Internal Server Error 400; also, sometimes the admin panel is loading up, but I’m receiving similar error messages located about where incoming links would appear which related to Akismet and Ultimate Tag Warrior (both of which I’ve been able to deactivate with no effect).
Forum: Fixing WordPress
In reply to: Upgrade from 2.0.4 to 2.0.5: Theme Editor ErrorsOh yes, I’ve had to do that today anyway. I just want to try to fix the problem.
Forum: Fixing WordPress
In reply to: Upgrade from 2.0.4 to 2.0.5: Theme Editor ErrorsAny ideas, folks?
Forum: Fixing WordPress
In reply to: Upgrade from 2.0.4 to 2.0.5: Theme Editor ErrorsNope, still having the same problem.
Forum: Fixing WordPress
In reply to: I broke my search form.Oh, absolute duh. I was working with the straight searchform.php code locally as I updated the theme and forgot to change it back. Thanks whooami.
Forum: Fixing WordPress
In reply to: wp-rss2.php screwed upYeah, I have absolutely no clue. I don’t like it when things fix themselves, but I’m not complaining. Thanks for your help, regardless!
Forum: Fixing WordPress
In reply to: wp-rss2.php screwed upHrm. Just did that and now the feed’s completely borked.
Forum: Fixing WordPress
In reply to: wp-rss2.php screwed upYeah, I did just copy and paste it in there, so I’m not sure what’s going on.
Here’s the validator link:
https://tinyurl.com/q2wwaHere’s the whole block:
`
<?phpif (empty($wp)) {
require_once('wp-config.php');
wp('feed=rss2');
}header('Content-type: text/xml; charset=' . get_settings('blog_charset'), true);
$more = 1;?>
<?php echo '<?xml version="1.0" encoding="'.get_settings('blog_charset').'"?'.'>'; ?>Forum: Fixing WordPress
In reply to: wp-rss2.php screwed upThanks Otto. I’m not sure what happened there, I think it was just a bad copy and paste. I put the above in, which solved the one problem, but when I run it through the feed validator, it tells me there’s something wrong with the comma before .get_settings.