When Smugmug goes into read-only mode, such as now, what is the point of directing users to the status page, when that page was last updated (in this case) 4 days ago? There is no information about the current down time, and all that users see is information about the very many historic down times. Whom does that benefit?
When Smugmug goes into read-only mode, such as now, what is the point of directing users to the status page, when that page was last updated (in this case) 4 days ago? There is no information about the current down time, and all that users see is information about the very many historic down times. Whom does that benefit?
this was about 7 minutes of RO, not even enough time for me to make a post on the blog, by the time I found out it was all back to normal. Sorry for the brief hassle, folks.
Andy, I'm not suggesting you should have posted an update on the status blog for what amounted to a hiccup.
I am suggesting that is looks extremely unprofessional to direct users to the status blog when there is no new information there to be seen.
It does not inspire confidence in my personal Smugmug site or Smugmug in general when the current issue is not addressed, but there are endless accounts of previous "site issues".
Andy, I'm not suggesting you should have posted an update on the status blog for what amounted to a hiccup.
I am suggesting that is looks extremely unprofessional to direct users to the status blog when there is no new information there to be seen.
It does not inspire confidence in my personal Smugmug site or Smugmug in general when the current issue is not addressed, but there are endless accounts of previous "site issues".
They're saying that the read-only message refers one to those records, but during today's read-only session, there was nothing in the status blog about the issue so it was kind of pointless to refer one to a place with no info about the current issue.
This lastest RO occurred on March 15. The last update on the blog is dated March 11. That update does not pertain to the current RO issue, so why direct me, and my site followers, in an "oops" message on MY site to it?
If there is no pertinent information on the blog, it can only be detrimental to point occasional users to it.
It is certainly not to my benefit, and I'd think not Smugmug's, to unnecessarily let occasional users know exactly how often Smugmug has been down lately. If there is no pertinent information there, then do not advertise that blog on MY site.
To me, pointing to that blog reads: "Sorry, site is down now, for no particular reason. You may also want to know we were down on 3/4, 3/8, and 3/9 as well. Thanks, Smug management"
Comments
Portfolio • Workshops • Facebook • Twitter
Portfolio • Workshops • Facebook • Twitter
EDIT: Looks liek it's out of Read Only mode now...
Facebook Fan Page
Blog
Portfolio • Workshops • Facebook • Twitter
I am suggesting that is looks extremely unprofessional to direct users to the status blog when there is no new information there to be seen.
It does not inspire confidence in my personal Smugmug site or Smugmug in general when the current issue is not addressed, but there are endless accounts of previous "site issues".
Am I missing something?
Portfolio • Workshops • Facebook • Twitter
Homepage • Popular
JFriend's javascript customizations • Secrets for getting fast answers on Dgrin
Always include a link to your site when posting a question
If there is no pertinent information on the blog, it can only be detrimental to point occasional users to it.
It is certainly not to my benefit, and I'd think not Smugmug's, to unnecessarily let occasional users know exactly how often Smugmug has been down lately. If there is no pertinent information there, then do not advertise that blog on MY site.
To me, pointing to that blog reads: "Sorry, site is down now, for no particular reason. You may also want to know we were down on 3/4, 3/8, and 3/9 as well. Thanks, Smug management"
Portfolio • Workshops • Facebook • Twitter