I believe you are talking about this: A Complex - Yet Quite Intelligible - Pathfinding in C#[^]
I saw it in the moderation queue Friday afternoon (US Pacific time). It does look like something is wrong since the "Updated date" on the article page currently says 18 Aug, 2013.
CodeProject was down for a few minutes Friday afternoon, so perhaps the hamsters got confused.
Looking at the revision history[^], the "Updated date" should say 24 Aug, 2013.
Hopefully this will alert the CodeProject staff to take a look at it and make sure the posted article has all the latest updates.
"When you don't know what you're doing it's best to do it quickly" - Jase #DuckDynasty
Yes and yes. For "new" articles an article only has the first week to get those 3 votes. After the first week is over it will not be considered for the "new" section of the upcoming newsletter. However, if you were to update it and it had 3 votes it would be considered for the "updated articles" section of the newsletter.
recently I added my blog feed and the first article got pulled fine. Now when I added more posts none of them are getting consumed.
Now, I've added the <a style="display: none;" href="href="http://www.codeproject.com/script/Articles/BlogFeedList.aspx?amid=7823767" rel="tag">CodeProject link to the bottom of every post but still it's not working.
You are totally correct. First time I posted my first post I had the posts set up in a way that they were showing full content (not excerpts). After that I changed it to only show excerpts, and posted two additional posts. Then, when I saw that the codeproject wasn't pulling in my blog feed I changed the posts settings back to the full content, but that didn't help so I was lost.
Currently posts are set to show full content, thereby the feed shows the full content of all posts.
I have been trying to publish this article for AppInnovation. But everytime that I click on Publish it gives an error: "The content is either too short or default". The article looks fine when I Preview it. The article ID is: 640977
This error is thrown even though the lenght of the article is substantial. Any suggestions as to what should I do?