Author:
Taxonomy upgrade extras:
I just wrote a long comment to Katie Leone about why she was seeing so few comments and Kudos for OEM. I read six of the seven chapters today. I had to search for them as the list of chapters at the right of the screen was screwed up.
The same was true of the forward and back controls. Sometimes they were absent, sometimes they gave nonsensical options. Chapter 7, for instance listed chapter 4 for back and chapter 5 for forward.
The kudo button also had to be pressed twice to get a thank you, and I’m not talking about the short pause that I’m used to seeing. As an experiment, I waited a full minute for a response, but it came immediately after the second press.
Then when I had completed my comment, I click the “preview” button, only to see a message that the site was down. I clicked it twice more, at intervals, only to discover that my comment was gone when the site again appeared.
This is not intended as a complaint, but rather as more grist for the mills of your troubleshooting. I’m actually quite impressed by how thorough you have all been in tracking down continuing problems. Where’s a kudo button when you need one.
BTW, Ms. Leone’s work is the best that I have seen from her!
Liz
Comments
There will be continuing problems
for the next 2 - 3 weeks as we move our fragile database onto a new server. Right now it's in the process of being positioned in a new location. Expect a few days down while we move BigCloset onto it. Then we will tackle the huge problem of cleaning up glitches on our new server. The sad fact is that our current server took too many shocks from equipment failures and while it is steady now, it is not going to last too long.
So for now, please bear with us and these glitches until everything has been changed over.
Sephrena
How to save your input after a server reset
When the server craps out on you while commenting or posting a story and gives either a server not responding message on either preview or save, remember that the information you entered is in your browser cache. All you have to do is wait about five minutes and hit the back button and there it is. If you hit refresh a couple of times before you realize it is not going to respond, you'll have to hit back as many times as you hit refresh, plus 1.
Open another browser window if you need to do something else while waiting. I have to do this all the time and it works in Safari, Chrome and Firefox on all my machines. In fact, it just happened to me when I was making this comment.
Hugs,
Erin
= Give everyone the benefit of the doubt because certainty is a fragile thing that can be shattered by one overlooked fact.
Thanks!
For the info. As I said this wasn't a complaint, but rather a reassurance to Katie that we love her work, even if it wasn't showing up as comments or Kudos.
Liz