September 10, 2003
My day started with a bang! I opened up my weblog and this message popped up on my screen:
Sorry. There was an error: Array index is out of range. The table structure doesn’t have an item #1.
What in the world is this? I panic and send out an email to every other weblogger I have an email address for. At the same time I’m really worrying about myself that this weblog is causing me to freak out. I had things to write and I don’t want to wait. OK, I tell myself, have patience. This is just a weblog. Then Tim (my co-worker) comes in and I don’t even give him a chance to sit down before I bombard him with what’s going on. He’s worried that I will take a bludgeon to him if he does not solve this problem so he gets right on it and proceeds to contact Lawrence Lee at Frontier.
So, I go back to other items I need to do, and try (without success) to put this out of my mind.
Then the emails start coming in my mailbox. Will is first to the rescue (Isn’t it great to have those you can always count on?) and chimes in with just the right amount of sympathy to make me feel better.
Not a good day for Manila…my school server’s down again…yuck…
You might want to e-mail Lawrence at Userland directly: lawrence@userland.com. He’s been pretty good about getting back to me when I have bad issues.
Sorry for your problems…really stinks doesn’t it?
Then Tim Lauer offers help (and he’s a new principal so I know how busy he is!).
The fix will most likely involve some kind of update/script from
userland and then a rebuild. When I was running Manila I found the guys who work for Userland to be very helpful. I would suggest writing to Lawrence Lee. I did a little looking around and see from the discussion forum that you have Tim Merritt on the job…
I have found that writing them directly sometimes moves things along quicker.
I start thinking about what a great community we have, “our group of webloggers.” That sense of community is what it is all about. There’s no way you can get that in the 4 walls of a classroom. And the spirit of help and giving is overwhelming. Thanks to everyone!
OK, back to the day. Next comes a message from Lawrence Lee who has heard from Al Delgado about my plight. Lawrence is ready and willing to help. I’m really impressed. Will had said he was pretty good about getting back to him when he had bad issues. I would say so. Wow! Not only is our community great but the Frontier community is terrific, too.
I’m also more than impressed with Al because he goes another extra mile and forwards my question on to Sam DeVore, also. Sam always has excellent suggestions. I’m getting excited now because I am beginning to understand the solutions (even if I can’t implement them yet!) I need to let Sam know that Tim sits right next to me here at Georgia State. Sam has rescued us many times in the past and we are always amazed at his generosity. Thank you, Sam!
Do you have access to the server (or know someone who does?) This is often an indication of a root file (the data structure of Frontier) has
some problems and it is often fixed by saving a copy of the database
that holds the weblog and replacing the old version with the new one.
This can happen if your log gets a lot of traffic and your website is
getting large.
Sam comes back again with even more suggestions to a follow-up question I tossed his way.
No problem, let Tim know that he can email me anytime (I can’t
guarantee answers though ;) On preventing this, it depends on what the problems turns out to be. My first suggestion would be to look at
putting all the high traffic weblogs in individual root files, to make
sure that homepage caching is turned on, and try as much as possible to have frontier not serve any static content ( I would love to see the
ability to static render rss feeds to another server (I have played
around with this and it is a big help. The splitting off of the websites into individual roots is a big thing because it really expands your flexibility in backing up the high traffic (and therefore more problematic roots)
And then Pam comes along with encouraging words
ARGGHHHH…Anne, you’ve got to be going crazy. I’ve never had that. I hope you¢â¡Áve found someone that has helped you to fix it. That’s the one thing about Manila. It’s buggy sometimes (though, I’m sure the other CMS are too, I’m just not as familar with them).
I wish I could help you, but I don’t know what is causing that error message. Sometimes, I get weird messages, but usually if I close my browser and reopen it fixes it. Let me know if its not fixed and I’ll post it on my blog that you need help and maybe someone who knows will respond to the posting.
Pam is always the encourager. She perked me up! We frequently bounce ideas back and forth and she is always so willing to help.
No, I don’t have my weblog back yet because the day’s schedule could not just come to a halt, much as Tim and I would have liked to just throw everything to the side and work on weblogs. But, tomorrow is another day and I reminisced on a post Will made the other day.
Educators are using blogs to help students express themselves and learn from each other.
Hmmm…is that what we’re doing? Sounds so, I dunno, vapid, doesn’t it? (I kinda picture this as a line from a “Betty Boop Talks Web Logs” documentary.) Sure feels like there’s more depth to all of this from where I sit at least. But, hey, ok…I understand…space constraints. It’s just a teaser. I can live with it…
It’s a heck of a lot more than that! We are building a dynamic on-line community of educators who want to make a difference with our students. Plus we’re there for each other. We see the changing nature of learner needs as well as the changing nature of educator needs. Our learning community is dynamic. Knowledge and ideas are shared, mulled over, “tweaked”, and we are constantly trying to make it better. I keep learning from this wonderful community. Thank you Tim M., Will, Tim L., Al, Lawrence, Sam, Pam and everyone else out there in our weblogging community.
And the community keeps growing…isn’t it exciting?
—–