Author:
Hi everyone!
We've been working on some internal changes to BigCloset TopShelf, and we're currently testing a few updates intended to improve the site's reliability and overall performance.
One of the issues we're specifically addressing is the infamous "phantom logout" problem, where the site appears to randomly log you out, or acts like you're logged out even though your session should still be active.
IMPORTANT: Please Log Out and Log Back In!
As part of these changes, we've made adjustments to how the site handles login sessions.
To make sure these changes take effect properly, we're asking everyone to completely log out of BigCloset TopShelf and then log back in.
This should help resolve the phantom logout issue by allowing the site to establish a fresh session using the updated session handling.
We Need Your Feedback!
We're also looking for feedback from our authors and bloggers.
If you've experienced problems posting blogs or stories in the past, we'd really like to know whether things are getting better, worse, or staying about the same.
Specifically, we'd like to hear about:
- Problems creating or publishing new blog posts.
- Problems creating or publishing stories or chapters.
- Unexpected logouts while writing, editing, or posting.
- Issues saving changes to existing content.
- Anything else that seems to be working better or worse than before.
Even if everything is working perfectly, we'd love to hear that too! Knowing what's working is just as helpful as knowing what's broken.
Thanks for Helping Us Test!
These changes are part of our ongoing efforts to keep BigCloset TopShelf running smoothly. Some of the work happens behind the scenes, so your feedback is incredibly valuable in helping us identify problems we might otherwise miss.
Please report any issues you encounter, and let us know whether your experience has improved compared to how things worked previously.
And one more reminder: Please log out and log back in!
Thanks for your patience, your feedback, and for being part of the BigCloset community!
-Kirstyn
Comments
I used to..
...have this issue where everytime I logged in it would get the infamous back-end fetch failed error. EVERY. SINGLE. TIME. Now I logged out and logged back in and there were errors. Will still keep an eye out for the problem and let you guys know.
Thank you for all the effort you guys put in for the community!
Back end fetch
Me too. It has resulted in accidentally posting repeats. Particularly when posting new content, which I do, er, rather a lot at the moment, I hit 'preview... long wait. I hit save, 'back end fetch'.
What I then do is hit my browser back-arrow, which takes me back to the submission page, and then click 'home', which does as asked and I find my submission posted already.
as
Steph says - 'kin annoying!
Madeline Anafrid
Madeline Anafrid Bell
Just logged out…….
And had zero issue logging in. Only difference I noticed was that logging in took me to my account page rather than the home page.
D. Eden
“Hier stehe ich; ich kann nicht anders. Gott helfe mir.”
Dum Vivimus, Vivamus
Took 3 attempts to log back in
I just logged out on reading this blog, and tried logging back in, there were at least a couple of 503 errors on hitting the login button before it worked.
did the same just now
with the same result - had to reload page (very slow) to find i was now logged back in
Madeline Anafrid
Madeline Anafrid Bell
Just keep Searching... Just keep Searching... :P
Finding and fixing the previous bugs lead to a new one. I'm currently testing one of the backend servers, to see if a new fix will fix it. So far so good. But you may still have issues as I've only rolled out the fix to one server for testing.
-Kirstyn
just did it
Logged out; logged in -- no problem
Hugs
Patricia
Happiness is being all dressed up and HAVING some place to go.
Semper in femineo gerunt
Ich bin ein femininer Mann
Took Two Tries...
...to get back in, and I got another 503 when I posted a comment on John-in-W's blog just now.
(Since they've coming up so often, the line from Allan Sherman's 1960s Automation Waltz keeps running though my head: "There's an IBM 503 / standing next to me, dear, where you used to be...")
Eric
Back Fetch 503 Failure was a dear old friend most of Friday
Got back on aprox 4:30 am Saturday
Used the Navigation sidebar? Log Out tab, then closed the page in my browser, the default Windows 11 uses
Our wifi is via AT&T and the fiberoptic connection to the line behind our house was replaced this spring
The modem was tested then and though a few years old is considered UpToDate
Had the Back Fetch 503 page again but with a secondary popup that I needed to respond to instead of just clicking the refresh button
Search anew for Bigcl, that brings up BigCloset Topshelf | TopShelf TG Fiction in the BigCloset as the first listing among others
Which I then clicked and BC loaded quickly
Clicked login and remember me in Navigation and everything seems well
If only the same would work to relaunch all the Star Trek actors, we lost recently
John in Wauwatosa
So far it hasn't helped
Since I re-logged in, I have to reload each page for the unread stories I have open that I intend to read before I can do things like bookmark and kudos, and most of those reloads have failed with 503 Backend fetch failed.
Site is loading and Back Fetching fine now
At 9:20 pm CDT Saturday
CDT switches to CST (Central Standard Time) at 2am Sunday
An extra hour of sleep tonight YAY!
John in Wauwatosa