This post may contain affiliate links and Corporette® may earn commissions for purchases made through links in this post. As an Amazon Associate, I earn from qualifying purchases.
Hi guys – if you haven't noticed, I've been having some nightmare tech problems. I've been trying to update folks via the Corporette Facebook page and the @Corporette Twitter feed, but in the event tech troubles continue, I do have an emergency blog set up at http://corporette.blogspot.com. I'll keep you posted. And hey, here's hoping I haven't torn out ALL my hair by the time we're back up and running.
Thank you for your patience.
h
love you kat! we’ll wait for it!
Bonnie
I was home sick yesterday and missed corporette!
academicsocialite
You’re back (for me anyway)!
ChiLawGirl
Stay tough, Kat – we’re with ya!
Anon in nc
It happens to all sites…hang in there. We’ll keep checking in.
AL
I can read the blog AND you’re still coming up in my google feeder. Hang in there.
SF Bay Associate
We can’t seem to subscribe to the comments anymore. BUMMER. That will make weekend open threads impossible to read. Any chance that can be fixed?
Kat
i think i can fix that. a lot of the backend features of the site are turned off for the moment — of the 25 plugins I have like 3 running. i think that subscribe to comments is a plugin — will go check it out.
Star
No worries Kat. We are all addicts and keep coming back for a fix. (I hope this comment is in no way offensive to anyone actually struggling with an addiction, but I am legit addicted to Corporette.)
Suzanne
Everything has been fine for me in Sydney all along.
P.
It’s been working fine on my home computer but not at work. At work, it started to go downhill when I got an error message about posting too quickly. I haven’t been able to get to the site since. I can’t download any other browsers per work’s IT rules and we have internet explorer.
AIMS
I also have had almost no issues at home (Mac) and no luck whatsoever at work (PC, IE only). I tried going through proxy.org as someone suggested, but apparently that’s banned at my workplace (boo, censorship).
Anyway, although I must say I have gotten much more work done, it’s very unfortunate not to be able to take a “coffee break” hereabouts. I hope this gets resolved soon. It seems this trouble all started when Kat was adjusting the cache (?) settings in anticipation of a traffic spike, is there no way to just go back to how it was before?
Kat
That stupid program I used to adjust the cache settings apparently edited the root code of the blog, which I’m just not comfortable fixing myself. Trying to get a professional on board to fix it, but people keep giving me the runaround. (The site runs so smoothly most times that I don’t need a regular tech person, even though I’ve offered to pay a few different people a monthly retainer to be available if I have an emergency. One of the things I hope to do with my free time, once I get some, is to learn the programming languages better so I understand this stuff.) Thanks for your patience though!