Quick Blogcast 2.2.2 Autosave
One of the worst things that can happen when online blogging is losing what might be your best blog entry ever because you get logged out of your account or because a toddler, cat, or spouse accidentally yanks out the power cord at an inopportune moment. Whatever action crashes your draft entry, the common factor is you forgot to save your draft while you were ’ writing it. It’s even more frustrating when you try to rewrite the post and it ends up a fraction of the original length, because you’ve lost 20 minutes of material and only remember 1/3 of what you first wrote.
No longer will you suffer this fate. We’ve added additional protection to Quick Blogcast with an autosave function to ensure that if you have to take that trip down memory lane you’ll only have to go back two minutes at the most.
Save Me!
We now save your work in progress every two minutes. Should the worst case happen and you lose your work, we ask you if you want to continue work on your draft in progress or start another one. While this is a fabulous safety feature, it’s truly an emergency measure and shouldn’t be used as a substitute for saving a draft post.
For a detailed explanation of this feature, see About Quick Blogcast Autosave.
Enhanced Blog Search:
Blogcast visitors now have more control over their search options, so they can perform entry searches more efficiently.
How to make use of New Entry Search?
Visitors to your blog can perform a Basic Search or Advanced Search using the search component in the blog sidebar.
Basic Search
The Quick Search or Basic Search will fetch results by matching the search term with entry titles from the prior three months.
Advanced Search
In the Advanced Search, visitors have more control over the search they want to perform by selecting an option from the “Search in” and “Date Range” lists.
We also released several performance enhancements that we hope were so seamless never noticed. Please keep your comments and feedback coming and remember to check out the new forum within Go Daddy Connections.
Categories: Power Tips, Know Your Settings, Release Notes
When will you add support to view older posts at the bottom of the screen? Currently people have to either search, or use the calendar to go back in my posts.
Greetings,
Thanks you for the feedback. We do have this enhancement on our product roadmap and it will be within a future release. I don't have a public timeline for its inclusion.
Regards
John
QBC team.
I also would like to see the inclusion of a nav button at the bottom of the page to go to a previous page of entries. Most blogs seem to have them?
Are these items on your roadmap as well?
- 2 sidebars
- "most popular posts" widgets
Greetings,
Thanks for your feed back with regards to the roadmap. Having the option of 2 sidebars in indeed on the roadmap but the templates would need a change to accommodate that. Secondly yours is an original request that would indeed make sense I'll bring that up at our next discussion on new features.
Regards
John
QBC team .
Once again, I have to say I love the improvements! Keeping up with what other blogging platforms can do is great. One thing I personally would LOVE to see is a "previous" and "next" post auto hyperlink at the bottom of each post. I hate that my readers have to go back to the main page to read my next entry. If this isn't on the roadmap, can we add it???
:D
Greetings,
I'd rather exceed what they can do , on a few things we do , but the good news is that we do intend to add navigation to the main page to accommodate a prev/ next view. Keep a look out for this in a future release.
Regards
John
QBC Team
As a long time exclusive user of GoDaddy for ALL of my hosting and domain needs (225 domains or so), I decided to go with GoDaddy's blog software to do my first serious blog.
I AM NOT HAPPY. As I have now done more than 3 months of intensive blogging and looking at other blog software, I find Quick Blog to be severely deficient and will likely NOT use it again. Why?
(1) Poor support -- currently and for over five days now, the Sidebar function is malfunctioning and won't allow me to update links or blogrolls.
(2) No preview function. Very bad. If I was a developer at GoDaddy, that would be the VERY FIRST THING I WOULD DEVELOP FOR QUICK BLOG
Number 2 is a deal breaker for me after 3 months of noting how difficult it is for people writing responses to get spacing and other things fixed before they hit submit.
(3) Timing out of security code number while people are writing. This is VERY PROBLEMATIC in that what happens is the security number times out and when people hit Submit Comment they get an error message. The go down the page and enter the security code, but they may NOT notice and usually DO NOT notice that their comment is being repositioned as a comment instead of a reply, which is confusing to writers and readers alike. A real big problem. Wish list: Fix that function so that there is no time out on the Security Code number or if there is, and an error message is generated that the person's response is NOT repositioned to a comment instead of a reply.
Thanks for your kind attention. One really dissatisfied customer (and disappointed -- I used to hold GoDaddy in high esteem.... it has slipped quite a bit). I guess ignorance is bliss...
Greetings Ron,
Thank you for taking the time to provide us with your feedback on the current incarnation of Quick Blogcast. I'll address your points in the order provided.
1) The sidebar item, is a known issue , which will be addressed in the next release of the Blogcast. Other than apologizing for the current state and getting this working again , quickly there's no reasonable excuse for this.
Meantime there is a workaround using the html/ custom text box to create blog rolls and links. I realize that doesn't get into addressing the ability to edit existing items but it's an option should you wish to recreate the links in that form in the interim.
2) Preview is on our to do list but the first incarnation was a preview within the QBC admin itself and not on the visitor's site for comments. I'll re examine this and see if it's feasible to address them at the same time. I was waiting for the inclusion of a rich text editor in that section prior to enacting preview.
3) I'm certainly concerned over the swap out of a reply into a comment regardless of the reason it occurs that's an intent we should preserve and when all is said and done it's unexpected behavior.
Over the coming weeks I hope we can earn back your prior satisfaction and if there's anything I can do to assist meantime please let me know.
Regards
John
QBC team
Hi John:
Thanks for the quick reply. I actually like the Custom html box much better than the Blogroll and Links sidebar add-ons anyway. For someone like me who has some html skills, it is so much easier to put things in alphabetical order and change things out when using the HTML Custom Text Box... way better. Thanks! Didn't know that is what it did.
And, yep, Preview would be a real plus and fixing the timing out on the code for Replying would really help, because it is NOT noticeable to users and then their Replies end up being posted as comments out of context so to speak.
Thanks again. I look forward to the fixes and improvements.
John,
I have a question for you about a horizontal scroll bar that I am getting on my blog. What is happening is that on most of my pages there is no horizontal scroll bar (the pages show up normally); however, on any page with a comment, there is a horizontal scroll bar. It seems as though, for some reason, quick blogcast "thinks" the page should be wider than it really is as soon as someone posts a comment to one of my entries. Check out my blog and click on an entry with a comment and you'll see what I'm talking about. Why is this happening?
I hope you'll answer me. I posted a question here some time ago and was disappointed to get no response... I had to go elsewhere for help :-(.
Thanks,
Chris
Chris,
This is an issue within the template that we're going to amend in a future version. The good news is that you can make a small update to the custom CSS now that will get this working as you'd expect. Basically it's switching the italic style off on the creation date which IE7 seems to prefer.
Here's the code
a.commentcreationdate{
font-style:normal;
}
You can get to this by going to Design Blog, customize, and then into the style sheet, paste the above in the themes style and then update / save it. If you've ever made changes to the CSS prior please ensure that you copy the old custom css over prior to publishing.
Regards
John
QBC Team
Thanks John! I put the new code in and it worked great!
--Chris
Two annoyances:
1) If the autosave occurs while you are typing, the cursor appears to go all the way to the bottom regardless of where in the document you are typing.
2) When you publish a draft, it uses the date of when you started the draft as opposed to when it was actually published, possibly changing the order of the articles.
Otherwise, I like the product and the interface is clean.
Thanks.
Greetings,
Thanks for the feedback on the autosave. I've heard of this occurring and it seems to be handled differently based on the browser in use. I suspect we'll take a further look at that.
The latter part has been a debate in the past that the first time you publish the item live then that date should match, I was pretty sure that we'd done that again will check on this.
Regards
John
Thanks for the autosave feature.
I do have two bugs to report. If there's a formal forum for doing so, let me know please. It would be great if these were trackable, as when I enter bugs against Firefox or Facebook
Anyway, the first is a design bug. On the log-in screen your "Forgot Password" button is far too close to the submit button. This means it gets clicked accidentally every now and then. That wouldn't be bad except that you immediately reset the password without any confirmation dialog. Simply horrible as now I have to go to mail, retrieve the link... etc. Waste of time.
Second, the challenge bitmaps for submitting comments on the comments page are apparently too easy to machine decode. I'm getting random gibberish spam comments on posts and track backs unlike anything I've ever seen before. Here's an example:
ngjalobr wrote:
[URL=http://dxnkyrqo.com]nukdguoc[/URL] zvwnbqtx http://ipbfdrds.com wyullwxy thczejjt nikdlohn">nikdlohn">http://ojwqtpnq.com">nikdlohn
This is annoying, as I get a dozen or so of these each month. I cannot fathom why someone would be doing them, unless they're working on code to bypass your challenge system. Please step up the challenge system.
Thanks,
-Ric
Very good posting...
Carmelo Lisciotto