Now the article is ready to be published. But when I uncheck the box "Work in progress", the article still keeps in "Composing" state after publishing it, rather than changing to "Pending" state.
What is wrong here? I know that the article submission wizard is still beta. But how to solve this problem now?
I tried with Safari Web-Browser on Mac as well as with Opera and Chrome on Windows. So it doesn't seem to be a browser issue.
In this response[^], on the C# forum, I selected the paragraphs that appear preceded by numbers (one at a time), and chose "indent."
No error thrown, but no indenting in final result.
I wonder if auto-line-wrap somehow comes into play here ?
"Humans are amphibians ... half spirit and half animal ... as spirits they belong to the eternal world, but as animals they inhabit time. This means that while their spirit can be directed to an eternal object, their bodies, passions, and imaginations are in continual change, for to be in time, means to change. Their nearest approach to constancy, therefore, is undulation: the repeated return to a level from which they repeatedly fall back, a series of troughs and peaks.” C.S. Lewis
I posted a new article on 05.13.2012 and my score was about 19500. Yesterday my score was about 20300. When I deleted the article my score becomes about 16500. So I don't know where these thousands of points are gone.
Is this a bug?
Also, I am facing an issue with some tips I've never posted. When I delete them, they appear as deleted but when I refresh the page they still be there. I can't delete them from my tips tab.
Thanks for letting us know about this. We'll dig into your reputation to take a closer look.
As for the tips, it could be you are attempting to delete tips that are in composing status, which I don't believe you can do. Would you like me to delete them for you? Are you looking to delete these?
Split a file into chunks
How to log Console Standard input asynchronously
Drag and Drop Records in ASP .NET TreeView
Multi Core Binary File Splitter
What you're seeing is an issue with caching of old data. We've had a long, long project of updating the rep points to reflect changes in rep policies (modified limits, new ways to score points etc) and as a bonus this recalc will fix an issue whereby removal of some points was not being reflected in overall scores.
As part of a quick fix we made it that certain events will trigger a resync of points, and so that's what would have happened with you. The underlying points were correct, but your published total was more than it should have been.