factotum
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: backend 500 & 404 errorsI finally found the problem. It was indeed in an htaccess file, which I had placed in the directory above my WordPress installation back in 2011 under direction from my webhost to force it to run php 5 instead of php 4 (which was my host’s default php version at the time). Although my host now runs php 5.5, that file was keeping it at php 5, which is now too low to run WordPress. I updated the file (which I did by changing 5 to 55, NOT 5.5, in case anyone else needs to do this), and the problem was finally fixed.
Thanks to everyone who tried to help me with this!
Forum: Fixing WordPress
In reply to: backend 500 & 404 errorsOriginal poster here, still trying to fix this. I’ve been reading various troubleshooting guides on this error, and they all refer to an htaccess file in the same directory as the wp-content, wp-admin and wp-includes folders. I don’t have an htaccess file there (a bunch of other places, but not there). Should I?
I tried going to my permalinks setting in my dashboard and saving settings, which (according to these same troubleshooting guides) supposedly generates a new and correct htaccess file if you don’t already have one there, but nothing happened. Still no htaccess file.
Forum: Fixing WordPress
In reply to: backend 500 & 404 errorsBut our web host is primarily an ISP, so I think their directory structure is a little different. I’ve already spoken to them. They said it was a WordPress issue, but they don’t really know anything about WordPress. If I can identify a problem on their end, they are usually pretty responsive, but I’m on my own for figuring out what it is before I go to them. We’re a non-profit and get our hosting free, so we can’t really complain!
Forum: Fixing WordPress
In reply to: backend 500 & 404 errorsNo.
Forum: Fixing WordPress
In reply to: backend 500 & 404 errorsThere are two, not sure which one you mean. The one at the same level as the WordPress folder is the password protection one, I believe.
AuthUserFile [PATH] .htpasswd
AuthGroupFile /dev/null
AuthName [HIDING IT]
AuthType Basic
<limit GET>
require valid-user
</limit>The one in the level above the WordPress folder:
Action php-cgi /cgi-bin/php5
AddHandler php-cgi .php
SetEnv DEFAULT_PHP_VERSION 5I think the php version is something our host had me put in.
Forum: Everything else WordPress
In reply to: Why did you close my unanswered thread???Thank you. I’d also like to feel respected, but enough said. Anything you can do to encourage people to check out the question would be much appreciated.
Forum: Everything else WordPress
In reply to: Why did you close my unanswered thread???How had it been “hijacked by other posters”?? ONE person posted that they were having the same problem, which was certainly on-topic (unless you don’t want anyone to know that this problem might not be specific to me), and one other person posted a single sentence indicating it might be a caching problem, which also seems apropos. All the other posts in the thread were by me, the original poster, describing my unsuccessful attempts at troubleshooting the issue myself, which seemed like it might help someone with more knowledge to identify my problem.
As for referencing an older version of wordpress, I already addressed that. I updated from that version, as I said in my subsequent post, and the current version is also mentioned in the thread. Are we forbidden from even mentioning previous versions of WordPress??
I have seen you scold people for starting a new thread on the same unresolved problem (and close down their new thread) many times, so don’t you think you’re being a little inconsistent? More to the point, the reason the post is a month old is that no one is helping me. Wouldn’t answering my question be more constructive than closing down my thread?
I have to say, it doesn’t seem like you read the thread before you closed it down, and you still don’t seem to have actually read it. And you wonder why end users won’t volunteer…
Forum: Fixing WordPress
In reply to: backend 500 & 404 errorsI am curious what theme you are using? My older, not updated theme is one of the suspects in my case.
BTW, I am back to receiving the error on the login page if I enter the password incorrectly (for awhile there it reverted to normal headshaking behavior, but no longer, and I’m pretty sure I haven’t changed anything, this time).
What’s more, I’m getting the error on the login page even when I enter the <i>correct</i> password. If I refresh the page (without re-entering the password), it does log me in the second time. I don’t think it should be saving my entered password info so that it’s still there for a page reload, should it? (Though of course I’m glad I can log in to my dashboard).
The only other person who has bothered to respond to this thread said something about caching issues (which the above also sounds like, no?). Unfortunately, that person did not elaborate, so I don’t really know what to do with that information.
Please bear in mind, folks, that if we were programmers, we would probably not need to post to this forum in the first place.
Forum: Fixing WordPress
In reply to: backend 500 & 404 errorsI’m not sure what that means, or what to do with it.
I updated to WordPress 3.8.1 to see if that would fix the problem. I had to do it manually, as the updates page of my Dashboard is one of the pages I can’t access. Wow, what a hassle compared to the one-click update! After updating, I no longer got the 500/404 error when logging in with an incorrect username or password. The logon page returned to its cute head-shaking behavior when incorrect info is entered in either field.
However, the update to 3.8.1 did not fix the errors when attempting to access the Dashboard/Updates and Appearance/Themes pages. Furthermore, after the update, my Plugins/Installed Plugins page also returned the 50/404 error, which was a headache, since I had deactivated the plugins to do the manual update, and couldn’t get to them to turn them back on. However, I was able to fix this by deleting hello.php from the plugins directory (which is the only file I had added to that directory during the WordPress update). Then I was able to access Plugins/Installed plugins again and reactivate my plugins.
Additional information:
“500” does not actually appear in the title of the error page. I added it to “Internal Server Error” because the browser tab shows “500 Internal Server Error” as the page title.
The URLs for the pages that return the 500/404 errors are:
our_domain/subfolder/WordPress/wp-admin/update-core.php (Dashboard/Updates page)
our_domain/subfolder/WordPress/wp-admin/themes.php
(Appearance/Themes)What do those two pages have in common that is not true of any other page in the dashboard? Could really use some help from people who know more about this than I do….
BTW, my login userID no longer seems to be case sensitive. Is that new, or has that always been true and I’m just now noticing it?
Forum: Plugins
In reply to: styling widget / sidebar bulletsWish I could, but it’s a private page. We use it as an in-house document download and calendar center, not a blog.
Forum: Fixing WordPress
In reply to: need help with the way categories widget displaysNever mind, I figured it out. Thanks again. 😀
Forum: Fixing WordPress
In reply to: need help with the way categories widget displaysYes, that was it! (archive.php) Thank-you so much, I have been trying to figure that out for weeks! Can you tell I’m excited by my exclamation marks?!!
If I can ask a followup question, I deleted all the text from the footer of each message (category and tag), but there is still a gray bordered box in which the text used to reside. I’ve pasted the code from that section below – what would I delete to get rid of the gray box?
<?php get_header(); ?> <div id="content"> <div id="contentleft"> <div class="postarea"> <?php if (have_posts()) : while (have_posts()) : the_post(); ?> <div <?php post_class(); ?>> <h1><a href="<?php the_permalink() ?>" rel="bookmark"><?php the_title(); ?></a></h1> <div class="postauthor"> <p>Posted on <?php the_time('F j, Y'); ?></p> </div> <?php the_content(__('Read more'));?><div style="clear:both;"></div> <div class="postmeta"> [this is where I deleted the footer data] </div> </div>