dorisballard

DoodleBee – I found the same search earlier today, and had already made an .htaccess file and placed it in the directory – but it didn’t work.

The same search turned up ‘/tmp’ and ‘/etc/’ as causing errors, and needing to remove the forward slash at the beginning of the addy … one person substituted the ASCII value. My side bar is HUGE (double side bar, and it’s FULL) but I haven’t been able to find any addresses that begin with forward slash.

I think they may have been talking about files other than the files which weren’t uploading though … perhaps akin to our wp-admin files. I’m not sure.

There’s just too little information to go on. :o(

HandySolo, is there a way for me to find that out short of contacting them? They’re not real good about replying …

I just found out that another person who also has a Word Press blog on my domain began having the same problem at about the same time – with the same file (sidebar.php)

We do not have the same themes.

To answer DoodleBee, I haven’t done much with my blog since that started, however when it started, I was *always* uploading something, or making changes, or adding plugins … or what have you … however, I remember at the time that I had not just made any additions.

I’ve never had any problem troubleshooting difficult plugins … and when they don’t work, I get rid of them. I don’t remember what I was doing at the time of the first error 406, but I know that if I had just done something I was at all unfamiliar with, I would have known where the new issues were originating from. At the time, the error was completely mystifying … and I just haven’t had time to try to track it down and squash it before now.

Thanks for your time. I hope one of you has seen this before and can aim me in the right direction.

Never mind … I just found the problem. Thank you

Thanks! I’ll install the new version, and see if that helps. If not, I’ll (reluctantly) get rid of it. It’s a rather nice little bit of blogging software … even does a few things WP doesn’t do … colored fonts, for example.

Thank you! Off to deal with it now.

Those are exactly the same line errors as the other person told me.

More info … different person:

I get the error “Stack Overflow 72” when I click on the comments link.

I got a “Stack overflow on line 110” just now when clicking to post my comment.

A bit of research tells me that she’s using IE:

Browser: MSIE 6.0
Operating System: Windows 98

Thanks! Passing on the info! :o)

This is what I got in reply:

“the stack overload is a pop-up that occurs any time I click any link on your blog. The banner at the top of the pop-up says Internet Explorer, which is what I am running on Windows. Yeah, I know, Firefox is better, but I hate their drop-down arrangement for bookmarks. With IE, I can just keep a list open on the left side of my screen with all the bookmarks/favorites that I can click on easily. so I put up with IE just for that. The pop-up on your blog consistently says: Stack overload at line 72 or (occasionally) line 110. It doesn’t interrupt loading the page I am trying to navigate to. ”

Web server logs only show a handful of 404’s … mostly from bots.

The shout box is relatively recent, but the complaints aren’t. I had the same complaint before I put this or the previous shout box in.

I’ll try to get more info from those it’s happening to … if possible! *LOL*

Thanks lots!

Thanks … I’ll do that right now, HandySolo. Manstraw, I’ve left questions for a lady who complained to me this morning. Hopefully she’ll fill out the picture a bit.

I’ll be back when I have more info, and I thank you!

Manstraw … I’ve never seen it either, but I’ve been told by enough people that it happens, that I believe it.

The people who mention it give me the impression that it happens to them relatively often on my blog — but others say they’ve never seen it happen.

Could it be their browsers?

Whatever it is … I’m wondering what could cause it so that I can try to prevent it.

Thanks.