Article is exposed as updated
-
Previously, I complained that a brand new article was not exposed properly on the page "Latest Articles", https://www.codeproject.com/script/Articles/Latest.aspx. Now, the problem is just the opposite :-). The article not marked as updated appears on the page "Latest Articles". I intentionally did not check "Mark as updated" on the submission of my old article update, just because this is a major new release I'm trying to publish. I cannot leave the article as is, to avoid confusing the readers, and the problem is serious enough: VSCode extension API broke backward compatibility again and rendered the old version of my product defunct, so I fixed the software and mentioned it in the article. At the same time, I planned to mark the article as updated only after thorough testing and a complete review of the documentation and the article content. The article is: https://www.codeproject.com/Articles/1194125/Article-Writing-Toolchain-with-VSCode. By the way, this is the software I use to generate my articles for CodeProject in one click and a single paste operation in the article submission wizard, already automatically formatted to Code Project standards (and even stricter). In the past, submission of the article update without "Mark as updated" performed successful update without having the article enlisted in "Latest Articles". Can it be fixed? Any advice for now? Thank you.
—SA
Sergey A Kryukov
-
Previously, I complained that a brand new article was not exposed properly on the page "Latest Articles", https://www.codeproject.com/script/Articles/Latest.aspx. Now, the problem is just the opposite :-). The article not marked as updated appears on the page "Latest Articles". I intentionally did not check "Mark as updated" on the submission of my old article update, just because this is a major new release I'm trying to publish. I cannot leave the article as is, to avoid confusing the readers, and the problem is serious enough: VSCode extension API broke backward compatibility again and rendered the old version of my product defunct, so I fixed the software and mentioned it in the article. At the same time, I planned to mark the article as updated only after thorough testing and a complete review of the documentation and the article content. The article is: https://www.codeproject.com/Articles/1194125/Article-Writing-Toolchain-with-VSCode. By the way, this is the software I use to generate my articles for CodeProject in one click and a single paste operation in the article submission wizard, already automatically formatted to Code Project standards (and even stricter). In the past, submission of the article update without "Mark as updated" performed successful update without having the article enlisted in "Latest Articles". Can it be fixed? Any advice for now? Thank you.
—SA
Sergey A Kryukov
I'll be taking a look at this one.
"Time flies like an arrow. Fruit flies like a banana."
-
I'll be taking a look at this one.
"Time flies like an arrow. Fruit flies like a banana."
Thank you, Matthew. I like the aphorism that goes below your messages about flies, a well-known one, one of my favorite. However, a while ago I started to publish my own ones, and the most recent one (about the ridiculous, in the blog on my profile page) was inspired by this very article and some related ideas. Thank you.
—SA
Sergey A Kryukov
-
Previously, I complained that a brand new article was not exposed properly on the page "Latest Articles", https://www.codeproject.com/script/Articles/Latest.aspx. Now, the problem is just the opposite :-). The article not marked as updated appears on the page "Latest Articles". I intentionally did not check "Mark as updated" on the submission of my old article update, just because this is a major new release I'm trying to publish. I cannot leave the article as is, to avoid confusing the readers, and the problem is serious enough: VSCode extension API broke backward compatibility again and rendered the old version of my product defunct, so I fixed the software and mentioned it in the article. At the same time, I planned to mark the article as updated only after thorough testing and a complete review of the documentation and the article content. The article is: https://www.codeproject.com/Articles/1194125/Article-Writing-Toolchain-with-VSCode. By the way, this is the software I use to generate my articles for CodeProject in one click and a single paste operation in the article submission wizard, already automatically formatted to Code Project standards (and even stricter). In the past, submission of the article update without "Mark as updated" performed successful update without having the article enlisted in "Latest Articles". Can it be fixed? Any advice for now? Thank you.
—SA
Sergey A Kryukov
If you made significant changes to the article, it may have been added to "Latest Articles" solely on that basis.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
If you made significant changes to the article, it may have been added to "Latest Articles" solely on that basis.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing.Really? Hmm... How do you know? This is not exactly what I observed. I think my article was added to the "Latest Articles" list after the first update in 2021, while earlier updates have been done in 2017. Then I've done several updates between February 27 to March 1, but in "Latest Articles" it still stays on February 27, even though later updates were somewhat more massive. Any ideas? Thank you.
—SA
Sergey A Kryukov
-
Really? Hmm... How do you know? This is not exactly what I observed. I think my article was added to the "Latest Articles" list after the first update in 2021, while earlier updates have been done in 2017. Then I've done several updates between February 27 to March 1, but in "Latest Articles" it still stays on February 27, even though later updates were somewhat more massive. Any ideas? Thank you.
—SA
Sergey A Kryukov
Sorry, no other ideas. It was just my impression based on updating my own articles. Sometimes a revision would appear on the site's main page, even though I wasn't checking the "Mark this article as updated?" box.
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Previously, I complained that a brand new article was not exposed properly on the page "Latest Articles", https://www.codeproject.com/script/Articles/Latest.aspx. Now, the problem is just the opposite :-). The article not marked as updated appears on the page "Latest Articles". I intentionally did not check "Mark as updated" on the submission of my old article update, just because this is a major new release I'm trying to publish. I cannot leave the article as is, to avoid confusing the readers, and the problem is serious enough: VSCode extension API broke backward compatibility again and rendered the old version of my product defunct, so I fixed the software and mentioned it in the article. At the same time, I planned to mark the article as updated only after thorough testing and a complete review of the documentation and the article content. The article is: https://www.codeproject.com/Articles/1194125/Article-Writing-Toolchain-with-VSCode. By the way, this is the software I use to generate my articles for CodeProject in one click and a single paste operation in the article submission wizard, already automatically formatted to Code Project standards (and even stricter). In the past, submission of the article update without "Mark as updated" performed successful update without having the article enlisted in "Latest Articles". Can it be fixed? Any advice for now? Thank you.
—SA
Sergey A Kryukov
I am not able to reproduce this issue. Maybe we've 'fixed' it as part of another bug fix. If you see this again, let me know and I'll tackle it again.
"Time flies like an arrow. Fruit flies like a banana."
-
I am not able to reproduce this issue. Maybe we've 'fixed' it as part of another bug fix. If you see this again, let me know and I'll tackle it again.
"Time flies like an arrow. Fruit flies like a banana."
Thank you Matthew, I'll surely will. I'll pay close attention to the potential issue next time.
—SA
Sergey A Kryukov
