|
|
So, something is seriously broken. I remember it that until a few days ago, even if the entire page is not fully loaded, I can click and open a message that is visible on the screen (while some portions of the page are still loading).
But, now the entire page is reloading when I click on any message. If I allow the page to completely load once, then it doesn't reload. This is particularly irritating because before clicking on any message to read, I need to wait for every tiny elements in the page to completely load. Very frustrating. 
Let me know if I'm not clear.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
| We've rearranged some of the javascript to help speed page load, but I'll investigate this and get it back to normal cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
This annoying bug still exists. I also feel the new Javascript enhancements haven't decreased the page load time (if it hasn't slowed it down).
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
The javascript is back exactly where it was before so my only thought is that you're either seeing caching issues (hit Ctrl+F5) or the jQuery file is taking its sweet time to be downloaded from Microsoft's servers.
Essentially, though, we're back to where we were before we made a change so it will be slower than it could be, but safer for you. If it's still not working out well enough for you then we'll have to get creative.cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
The speed seems to be better now, but sadly the page still reloads if I click on a message before every tiny element of the page is entirely loaded.
I've tried Ctrl+F5, tried cleared the entire cache, tried kicking my dog, etc., but to no avail. 
I'll try how this works at my home - if it goes good there, then it must be a caching issue here (office PC).
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Hello everybody!
The checkbox "Mark this article as updated?" does not convey a clear meaning. Much better if it would state "Publish article" or something similar. It should either be renamed or its' meaning made obvious in a textual explanatory note underneath it.
All the very best,
Mihnea
modified 20-Aug-18 21:01pm.
|
|
|
|
|
That checkbox determines whether or not the article is marked as being updated. If it isn't checked then the contents of the article are updated, but it's not tagged as an update. This allows you to make a small change without sending the adoring hordes of fans screaming to see your latest and greatest.
I feel the checkbox is labelled correctly, but am certainly open to further suggestions.cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I agree with Mihnea Radulescu.
I was wondering if this is the expected behavior, but it was a hunch - nothing certain. I had to google the checkbox's text and bump into this thread in order to understand the meaning of it.
IMO, an explanation text (in brackets) would help. Something similar to the fields Co-Author IDs and License.
|
|
|
|
|
Any suggestions on wording?
What about "Update the article's 'modified' date?" (checked by default)
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Wow - you're quick 
Yes, I actually thought about this:
This is a major update (subscribed users will be notified)
Maybe the opposite would make even more sense (but I'm aware of the fact that it'll require a bit of coding as well):
This is a minor update (subscribed users will not be notified)
(*) I'm not 100% sure who will be notified so I assume it has something to do with users who subscribed to the article.
|
|
|
|
|
Whether or not a change is major or minor is separate from whether you wish to update the modified date. We calculate automatically whether it's a minor update (and don't update the modified date) but if this checkbox was used to override whether we mark an update as "major" then a potentially major update could be hidden in the list of article versions on the Revisions page. (By default we hide minor updates).
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
In that case, I'm even more perplexed than before.
Reading your last answer I think you mean that it changes the article's date (but I'm not sure anymore)...
Reading your original answer to Mihnea Radulescu, I was positive that it's the major/minor boolean (and I quote: "... This allows you to make a small change without sending the adoring hordes of fans screaming to see your latest and greatest").
|
|
|
|
|
So there's two bits here:
1. When you edit an article, the article's 'modified' date is updated. Unless you choose otherwise. If the article is marked as updated then it will appear on the homepage as updated and also in the weekly newsletter
2. When you edit an article, a new version of an article is created, and these versions (well, revisions) are listed on the article's Revisions tab. If a revision is minor then it's not shown in the list by default.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I understand (I think). Well, I was not aware of the homepage updates and the weekly newsletter (maybe I didn't do enough "community service" )
Thanks for the rapid reply and for clearing things up, I appreciate it.
And I love this website!
|
|
|
|
|
I hope it's clear(er), but please: if you have any wording (or other) suggestions then throw them in the hat.
(and thank you!)
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Sometimes, at work, we could discuss a single checkbox for days. Seems like "Mark this article as updated?" qualifies.
Sorry in advance for the lengthy answer, but I write because I care:
What is an Update?
I revisited the submit page, the Submission Guidelines[^] page and all the articles it points to, but the term "an update" in the context of the checkbox is not explained anywhere.
I reviewed our correspondence and unless I'm wrong, it seems that CodeProject's point of view is that "an update" in this context will simply change the article's modified-date.
Manually Changing the Modified-Date?
I have to say I don't really see the point in this. Moreover, it feels to me that unchecking the checkbox (thus freezing the modified-date) is a bit of a hoax: The Revisions tab is there. Anyone can visit it and see the real modified-date, it'll be the one of the latest revision. If someone will continuously uncheck the box when submitting changes, then the modified-date will remain the same as the first-posted date, but the last revision date will be later than that.
See my latest article for an example: modified-date = first-posted-date = 4-Oct-2011, but last-revision-date = 5-Oct-2011 (so who am I kidding here?). I thought that by unchecking the box I'm preventing a major update so I was really confused when I saw the revisions start piling up.
My Point of View (the way I would have it)
1. As an article author I'm the one who should be deciding if an update is major or minor:
If I want to correct a word or change a sentence, then I would like it to be a minor update - one that does not publish anything to anyone.
When I add content, a new revision or when I update the code samples/files, only then I would like to mark it as a major update a cause notifications to be sent.
2. IMO, the modified-date should be just that - automatically show the last date in which the article was modified.
3. Regarding revisions, I wouldn't mind having the ability to tag a revision as private (or at least make all minor revisions to be private). I don't really want to share the whole evolution of my article - especially the part when I had the "work in progress" button switched on.
Back to Reality
Albeit all I wrote, The CodeProject is doing very well in the past 12 years, so I do understand that I will be the one aligning/adhering/adjusting.
So, while I have my reservations regarding the checkbox's behavoir, to answer the original (wording) question I believe that your suggestion "Update the article's 'modified' date?" sounds closer to reality than the current text. I might extend it to "Update the article's 'modified' date to the current one?".
While we're at it, this checkbox is the only filed that doesn't remember its previous value as it will be checked by default. The author should be aware of this before submitting any change, so I think it should be moved to a clearly visible location at the vicinity of the submit-button (instead of hiding somewhere in the middle of the page).
Regards,
Avi.
|
|
|
|
|
Whenever I post a message, I want the "Send me an email if someone responds to this message" enabled by default, and in fact I want everything else enabled except for "Allow private email replies to this message" option.
If I uncheck the "Send email if someone replies to this message" once, then it keeps unchecking itself even if I enable it before posting a message. This is very irritating as I do not receive an email notification for messages posted, and I have to manually enable it every time.
I suggest a "Message and email settings" on my profile page where I can set some "permanent" options. If I change any of those options for a particular message, the next message I post will still use the information stored on my permanent options.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Hi Rajesh,
AFAIK this is how it works (or worked once):
- the 4 checkboxes are available on your "My Settings" page ("Forum" tab), where you can set their default state;
- the 4 checkboxes are also available on the reply page, where you can change them when creating a message, and the changed state becomes the default for the next message; however changing them while editing an existing message has limited or no effect, not sure, I never understood why nor what was going on here.
Hope this helps.
I wouldn't mind this being simplified:
- either have them changable and effective at all times;
- or get them disabled and differently styled when not changable.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that. All Toronto weekends should be extremely wet until we get it automated in regular forums, not just QA.
|
|
|
|
|
Luc Pattyn wrote: - the 4 checkboxes are available on your "My Settings" page ("Forum" tab), where you can set their default state;
Yes, but that isn't working right. If I uncheck the "Send me an email if someone..." for a particular message, then it persists when I post another new message. I want the default value to be picked from my settings every time, which is not happening. This kinda makes the options I stored on my settings page useless.
I do not want to be clicking on those options every time I post a new message. If I change any of those, it's ONLY for that particular message I'm composing.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
I understand; that is not what Chris intended.
Initially the checkboxes only existed on the reply page; many people didn't find them, so I suggested to put a copy on the settings page, which Chris did.
Whatever system gets implemented, I would prefer it to show a sentence or two explaining exactly how it works, so everyone can read and understand it.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that. All Toronto weekends should be extremely wet until we get it automated in regular forums, not just QA.
|
|
|
|
|
OK, so what I'm asking for is different: A "default settings" for posting messages on forums.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
| Actually, I think what you're asking is a "Update my settings to reflect the settings for this message" button. cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I think what Rajesh wants could be explained by:
on the settings page/forum tab:
"Choose the default values for the checkboxes that will appear on the reply message page when creating or editing a reply to a forum message."
and on the reply page:
"Choose how this message should be handled; changes will not influence older nor future messages. If this is a new message, these checkboxes got their default from the corresponding checkboxes on your settings page/forum tab; if this is an existing message, they reflect your earlier choices."
PS: I yield all rights on the above; feel free to improve the wording as long as it remains very clear.
Luc Pattyn [Forum Guidelines] [Why QA sucks] [My Articles]
I only read code that is properly formatted, adding PRE tags is the easiest way to obtain that. All Toronto weekends should be extremely wet until we get it automated in regular forums, not just QA.
|
|
|
|
|
What Luc said!
I need the site to remember my "default settings" for posting a message on the forums. My defaults are to have everything else enabled except "allow private email replies".
If I change those settings for a particular message for some reason (like, I didn't want to be notified of replies for that SINGLE post), then I will uncheck the "send me an email if yada yada" option. This must have no effect when I post the next message (I must see the defaults).
“Follow your bliss.” – Joseph Campbell
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
