Blogger Blogs, and similar online and other IT products, use peer support to help their customers. Blogger, similar to other companies, provides Blogger Help Forum: Something Is Broken, where Bloggers with various problems can write in and say
If you properly compose your problem report in Blogger Help Forum, and state your version of [My Problem], one of several things may happen.
Now, if you are so fortunate to have scenario 1 or 2 apply in your case, it is possible that the solution can be found in either Beta Known Issues, Blogger Help, or Blogger Status. It's possible - but not too likely - if it was, you (or someone like you) would have found it, and publicised it, long ago.
If the solution is provided by a helper, the chances are that it came from a prior thread in the forum, under scenario 3. And here's the problem. Of all of the threads mentioned in the many posts linked from Beta Blogger Problems, and from Classic Blogger Problems, how many of those threads end with somebody actually saying
Besides non-existent peer support, we have Blogger Support which is part of The Problem. Whether posting as Blogger Employee, Pete Hopkins, or anybody posting in Beta Known Issues, Blogger Help, or Blogger Status, Blogger only rarely publicises problem resolutions. I have previously discussed this issue as The Silence.
When a thread actually is closed, by anybody (preferably by the original poster of the thread), I would greatly prefer to transcribe the solution, into the appropriate Classic Blogger Problems or Beta Blogger Problems detail problem post. I would prefer. Very few can I do this way, though.
Why is this?
Because of the dozens of individual threads about the various problems, please tell me how many actually end in
The majority of these threads simply end. And there is The Problem.
Rarely, someone will post
then sometime later they may post back
without any interactive problem analysis. So we don't get to help solve the problem, but maybe we can still learn from the solution. This person is now part of The Solution.
But here's an odder scenario. Someone will post
then sometime later they may post back
without any interactive problem analysis, or the solution. So we don't get to help solve the problem, nor do we get to learn from the solution. This person is now part of part of The Problem.
Not everybody realises the benefits, and the requirements, of peer support. Peer Support works - if you make it work.
So, if you are involved in any of these threads, or other threads, and you find your problem solved (either by a forum helper, or by yourself), please post back in your thread
Provide your version of [The Solution]. The helpers are constantly learning, as they help others. Your feedback may help them learn, or encourage them to continue.
And having provided your your version of [The Solution], you are now experienced in your problem. Now you need to do some research. Find out what caused your problem, and why the solution was necessary.
Then come back to the forum occasionally, and look for other folks with what looks like your problem. When you see someone reporting their version of your problem, describe your solution to them.
But be selective here. Remain aware of computer and system uniqueness. Mention your problem, and your solution, but be aware of possible reasons why neither will be 100% universal. Read other folks reports of their problem, too.
Become part of The Solution, not The Problem.
>> Top
I have a problem [My Problem]. Can anybody help me?
If you properly compose your problem report in Blogger Help Forum, and state your version of [My Problem], one of several things may happen.
- A solution will be known, and will be instantly provided by one of the many helpers.
- A solution will be derived, from subsequent questions by one of the many helpers.
- You will be advised to report your problem, to Blogger Support.
Now, if you are so fortunate to have scenario 1 or 2 apply in your case, it is possible that the solution can be found in either Beta Known Issues, Blogger Help, or Blogger Status. It's possible - but not too likely - if it was, you (or someone like you) would have found it, and publicised it, long ago.
If the solution is provided by a helper, the chances are that it came from a prior thread in the forum, under scenario 3. And here's the problem. Of all of the threads mentioned in the many posts linked from Beta Blogger Problems, and from Classic Blogger Problems, how many of those threads end with somebody actually saying
YAY! It's fixed! And this was [The Solution]
Besides non-existent peer support, we have Blogger Support which is part of The Problem. Whether posting as Blogger Employee, Pete Hopkins, or anybody posting in Beta Known Issues, Blogger Help, or Blogger Status, Blogger only rarely publicises problem resolutions. I have previously discussed this issue as The Silence.
When a thread actually is closed, by anybody (preferably by the original poster of the thread), I would greatly prefer to transcribe the solution, into the appropriate Classic Blogger Problems or Beta Blogger Problems detail problem post. I would prefer. Very few can I do this way, though.
Why is this?
Because of the dozens of individual threads about the various problems, please tell me how many actually end in
YAY! It's fixed! And this was [The Solution]
The majority of these threads simply end. And there is The Problem.
Rarely, someone will post
I have a problem [My Problem]. Can anybody help me?
then sometime later they may post back
I found the solution [To My Problem]. Here is [My Solution]
without any interactive problem analysis. So we don't get to help solve the problem, but maybe we can still learn from the solution. This person is now part of The Solution.
But here's an odder scenario. Someone will post
I have a problem [My Problem]. Can anybody help me?
then sometime later they may post back
I found the solution [To My Problem].
without any interactive problem analysis, or the solution. So we don't get to help solve the problem, nor do we get to learn from the solution. This person is now part of part of The Problem.
Not everybody realises the benefits, and the requirements, of peer support. Peer Support works - if you make it work.
So, if you are involved in any of these threads, or other threads, and you find your problem solved (either by a forum helper, or by yourself), please post back in your thread
YAY! It's fixed! And this was [The Solution]
Provide your version of [The Solution]. The helpers are constantly learning, as they help others. Your feedback may help them learn, or encourage them to continue.
And having provided your your version of [The Solution], you are now experienced in your problem. Now you need to do some research. Find out what caused your problem, and why the solution was necessary.
Then come back to the forum occasionally, and look for other folks with what looks like your problem. When you see someone reporting their version of your problem, describe your solution to them.
But be selective here. Remain aware of computer and system uniqueness. Mention your problem, and your solution, but be aware of possible reasons why neither will be 100% universal. Read other folks reports of their problem, too.
Become part of The Solution, not The Problem.
>> Top
Comments
However, I strongly recommend that you plan the change with more care than that.
You replied to my request for help at Blogger Help group when i explianed my difficulty in posting and the missing buttons such as font color. I cannot post from audioblog without getting an error message. I read every one of your possible solutions then worked my way down them. I cleared the cache and the rest, added blogger to my trusted zone for IE and allowed cross-frame scripts for the Navbar to work. Nothing has helped. Blooger compose is still missing buttons and audioblog can't be posted. Any other suggestions?
Why not update the forum thread with your comments, so we can continue from there?
The questionnaire would gather data and send them on to an email address.
I suspect that questionnaire couldn't be in HTML to be active.
Any ideas?
I read that Blogger In Draft has added a Poll option.
And, as you said, while I was asking for help, I was able to solve someone else's problem that I recognized as one I had seen in the past.
And I promise, I will go back when this is all resolved and put the "finishing touch" to my thread!!
Thanks again!!!
Rosemary
Plush Memories Lost Toys Search Service
That is, what is the best way to get in touch with the admin of a large web-site to alert them to security flaws?
Nobody can tell you the answer to your question - they are Google, and seldom listen to anybody but Google. I've been helping them with support issues for 2 years, and they don't listen to me for coding or design issues either.
Start a blog, and enumerate your concerns. If it's interesting, people will read it. Eventually, Google may read it.
Thank you so much,
dlevitt
I tried almost every thing still I got the error
"Another blog is already hosted at this address"
so ultimately I had to go for the link
https://spreadsheets.google.com/viewform?key=pZHHZdeYKeHitQbvxkvwnCg&ifq
Lets see whether my issue can be resolved or not...
No, that's not going to happen. When the blog is confirmed as spam, it's gone. Give it up, or start over.