|
Bad admin. Bad, bad admin...
While you're testing things, click the Email link and let's see if that gets through, as that's the part that wasn't working. I was getting post notifications and the newsletter just fine, but for some reason wasn't receiving emails generated by users in this manner.
Say, where can I get my hands on that Big Red Button? It sounds like loads of fun...
|
|
|
|
|
Hacked by the source
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP blog: TDD - the Aha! | Linkify!| FoldWithUs! | sighist
|
|
|
|
|
There's never been a more appropriate time for using the icon than when I saw that post.
I hope there isn't a big "Impersonate Vikram" button.
Cheers,
Vikram.
The hands that help are holier than the lips that pray.
|
|
|
|
|
I have a feeling Chris has a big ticker, scrolling all our names, with a button beside each
"impossible" is just an opinion.
|
|
|
|
|
A ticker that scrolls 5 million member names? That must be a laaawng one, I guess.
Nobody can give you wiser advice than yourself. - Cicero
.·´¯`·->Rajesh<-·´¯`·.
Codeproject.com: Visual C++ MVP
|
|
|
|
|
It would be nice if the author of an article could update the download links. This could be usefull when you have some minor bug fixes and you don't need to change the article contents for example. That will also reduce the work of the editors.
|
|
|
|
|
Yes it would
(On the TODO)
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Hi Chris,
I am afraid I don't like the idea.
if the sources get changed, it MUST be reflected in the history paragraph inside the
article text.
How else would the interested reader/user be aware something has changed?
At the bare minimum, you should add an automatic message to the history, but nothing
would replace the author himself updating the history and explaining what he did and why.
A way to subscribe to an article, so any modification creates an opt-in e-mail would
be nice and useful, and might alleviate my above concerns. So maybe you should provide this first?
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
We can do even better than that, Luc.
Give us some time and we'll put something valuable together.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Hi Chris,
unfortunately I am not able to give time, but I trust you will be wise and take the time
you need.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
I was mainly talking about problems like missing files in the archive, wrong archive uploaded,...
For example, I updated my article last week and I saw that one of the download link was not up-to-date, so it would be easier that I could fix that myself. I also had the experience that I forgot to add some files in the archive and so, the first person that download the zip complains that the project can't compile. For those problems, there's no real point on having a history.
But I agree with you on the fact that it would be really nice to have the history separated from the article contents (in any kind of way). So that you could specify some information when you update the code (a bit like a commit message for SVN).
|
|
|
|
|
Hi Cedric,
I trust first intentions are good, but such a feature soon will get abused to sneak in
some essential changes. The modified message now gets added automatically to forum posts,
and that is good; if it is wanted for messages, it is even more useful for articles
and their collateral.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Hi,
Apologies if this is addressed elsewhere, I haven't been able to turn anything up.
I just posted an article (http://www.codeproject.com/KB/architecture/di-with-autofac.aspx) that uses ids to implement a table of contents. It seems like the article submission wizard is stripping the id="..." attributes off of the headings.
Any suggestions?
Thanks in advance,
Nick
|
|
|
|
|
ID's aren't what you want. You need to use <a name="anchor>...</a> to set bookmarks for use in tables of contents
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Thanks, Chris, I'll give that a shot!
Cheers
Nick
|
|
|
|
|
The same way there is an approve button, shouldn't there be a reject button? Only I don't think its fair that articles should approved of rejected out of hand, say by the first 5 or so members? Because honestly, its a chore looking at some of these 'articles' which are nothing more than labeled templates.
"Every time Lotus Notes starts up, somewhere a puppy, a kitten, a lamb, and a baby seal are killed. Lotus Notes is a conspiracy by the forces of Satan to drive us over the brink into madness. The CRC-32 for each file in the installation includes the numbers 666." Gary Wheeler
"The secret to a long and healthy life is simple. Don't get ill and don't die." Pete O'Hanlon, courtesy of Rama
"I realised that all of my best anecdotes started with "So there we were, pissed". Pete O'Hanlon
|
|
|
|
|
I would suggest an article gets rejected if its has been viewed N times (say 100) and
never accepted for public view in that time. That way the queue empties itself no matter what.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
That's certainly one way to do it, but my way provides more satisfaction
Either way, the whole point is to assist in emptying the queue as fast as possible.
"Every time Lotus Notes starts up, somewhere a puppy, a kitten, a lamb, and a baby seal are killed. Lotus Notes is a conspiracy by the forces of Satan to drive us over the brink into madness. The CRC-32 for each file in the installation includes the numbers 666." Gary Wheeler
"The secret to a long and healthy life is simple. Don't get ill and don't die." Pete O'Hanlon, courtesy of Rama
"I realised that all of my best anecdotes started with "So there we were, pissed". Pete O'Hanlon
|
|
|
|
|
Mustafa Ismail Mustafa wrote: Either way, the whole point is to assist in emptying the queue as fast as possible.
True. But I believe CP Team is having 'Publish' only because no innocent article should be dropped inadvertantly. Perhaps, they can associate number of button clicks by Gold member and number of button clicks by Platinum member and then decided on 'Publish'/'Reject' route.
Wouldn't that be a viable option?
Vasudevan Deepak Kumar
Personal Homepage Tech Gossips
A pessimist sees only the dark side of the clouds, and mopes; a philosopher sees both sides, and shrugs; an optimist doesn't see the clouds at all - he's walking on them. --Leonard Louis Levinson
|
|
|
|
|
Vasudevan Deepak K wrote: I believe CP Team is having 'Publish' only because no innocent article should be dropped inadvertantly.
That speaks sense and I think Chris meant just that (after reading his explanation below).
"Every time Lotus Notes starts up, somewhere a puppy, a kitten, a lamb, and a baby seal are killed. Lotus Notes is a conspiracy by the forces of Satan to drive us over the brink into madness. The CRC-32 for each file in the installation includes the numbers 666." Gary Wheeler
"You're an idiot." John Simmons, THE Outlaw programmer
"I realised that all of my best anecdotes started with "So there we were, pissed". Pete O'Hanlon
|
|
|
|
|
Mustafa Ismail Mustafa wrote: Because honestly, its a chore looking at some of these 'articles' which are nothing more than labeled templates
We're offering you a chance to help out the rest of the community by filtering out those articles that simply are not suitable for publishing. We appreciate whatever help you can provide but if it's a chore for you then please feel no obligation to exercise the option to help out.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: by filtering out those articles that simply are not suitable for publishing
there is a flaw in the logic: if the readers are to help get rid of substandard articles
there should be a reject button, not an accept button.
Right now if I don't like an article at all, I vote 1 and I report, which is a lot of
clicks and several page reloads.
So I would suggest you provide a "vote down" button, and after N down votes by different
gold/platinum members the article is gone.
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|
|
Luc Pattyn wrote: if the readers are to help get rid of substandard articles
A subtelty here: I'm not asking readers to 'get rid of' substandard articles. I'm specifically asking them to approve only those that are appropriate. Many substandard articles are deemed substandard because of formatting or language issues. I'll often check out an article that has been not approved, read it, and if it's reasonable and of possible value I'll reformat and let it sit a little longer. Sometimes this can make an unacceptable article an acceptable one.
In this case a "Reject" article would not add any value to the process.
Luc Pattyn wrote: Right now if I don't like an article at all, I vote 1 and I report,
There's no need: Just don't click the 'accept' button. If it's truly not acceptable we'll catch it within a day or so.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: we'll catch it within a day or so.
it would be nice to not show them again to a prior visitor; when I visit CP home page
a couple of times a day, I tend to view each of those articles, often seeing the same
one more than once because I can't remember all those strange titles (I noticed a lot of
substandard articles have bizar and often very short titles).
So maybe you could provide an "I don't want to see this ever again" button then?
Added bonus: I sometimes am inclined to accept an article, that I would (or do) vote a 2,
because it is not a bogus article but not a good one either, and I want to get it out of the
way. Giving me the "I don't want to see this ever again" button would keep me from being
so forgiving ...
Luc Pattyn [Forum Guidelines] [My Articles]
This month's tips:
- before you ask a question here, search CodeProject, then Google;
- the quality and detail of your question reflects on the effectiveness of the help you are likely to get;
- use PRE tags to preserve formatting when showing multi-line code snippets.
|
|
|
|