- Joined
- Jan 31, 2005
- Messages
- 9,910
Not working here, either. I just figured all you guys took the day off....
Not working here, either. I just figured all you guys took the day off....
Not working here, either. I just figured all you guys took the day off....
Still down here. This seems to be happening a lot lately.
Not working on mobile device either. How am I supposed to drive and search cigar pass at the same time? Geez todd :sign:
Not working here, either. I just figured all you guys took the day off....
Not working here, either. I just figured all you guys took the day off....
Still down here. This seems to be happening a lot lately.
Did someone unplug the New Content Accumulator Machine again?
Did someone unplug the New Content Accumulator Machine again?
She done broke...again!
Did someone unplug the New Content Accumulator Machine again?
She done broke...again!
I think Rod stumbled going to the bathroom last night and tripped over the cable again. Hopefully when he wakes up he'll see the unplugged cable and respond.
Am I the only one that has problems with the View New Content feature not showing very many entries? I mean sometimes if I'm away for a couple of days and I come back and click View New Content it says there were only 3 or 4 threads with new content in them. I know this can't be right. Is anyone else having this problem, and more importantly if there's a way to fix this what is it?
Am I the only one that has problems with the View New Content feature not showing very many entries? I mean sometimes if I'm away for a couple of days and I come back and click View New Content it says there were only 3 or 4 threads with new content in them. I know this can't be right. Is anyone else having this problem, and more importantly if there's a way to fix this what is it?
I'm having the same problem. I'll get on the computer in the morning and after hitting the "view new content", it only shows posts from about 4am on.
Sounds like a bug. I'll check with the vendor to see if this has been reported.
Sounds like a bug. I'll check with the vendor to see if this has been reported.
Is this fixed, yet?
:laugh: