|
Validity check: When a member is added as an co-author, an acceptance from the co-author would be required before the article is let to enter into moderation.
This would prevent cases like this[^] or other abuses of co-authors.
|
|
|
|
|
It's already in place. I'll have to check into what happens for pending.
cheers
Chris Maunder
|
|
|
|
|
Ah, see, I told you the hamsters stole a bottle of vodka from the hidden cave.
|
|
|
|
|
I have a strong dislike for article-descriptions that are a plain copy of the article's title, especially if they either don't convey the point of the article or assume that you know what the author is talking about beforehand. Recent example:
Title: Overview of Intel XDK
Description: Overview of Intel XDK
I don't know what the Intel XDK is so I don't know if that article will be of interest to me before I read it.
Then the first sentence of the Introduction: "Intel XDK is a cross platform mobile application development environment which lets you create mobile and tablet apps using HTML5 and JavaScript. "
So why didn't he write in the description something like "Overview of Intel XDK for cross platform mobile application development" ?
Suggestion: Let expressive descriptions be mandatory for article approval. Let either the author supply it or if he fails to do so and the CP member who is about to approve the article is so inclined, let him edit the description.
- Sebastian
|
|
|
|
|
|
Same error for me.
The quick red ProgramFOX jumps right over the Lazy<Dog> .
|
|
|
|
|
Try now. We introduced a bug with the latest 'Improvements'.
|
|
|
|
|
Now it works. Thank You!
Docendo Discimus
|
|
|
|
|
Hi
Would it be possible to have a new category called Continuous Delivery to sit under Development Lifecycle please? With the DevOps movement gathering momentum CD is getting increasing attention.
Thanks - Graham
|
|
|
|
|
The AAC (*) is still in doubt about my latest article, even after almost 24 hours. Maybe they approve, maybe don't.
My suggestion: increase the clock timing...
(*) AAC - Article Approval Community
|
|
|
|
|
There's no bug, but there are formatting issues with your article.
Correct them and your article will be approved very quickly.
cheers
Chris Maunder
|
|
|
|
|
Thanks for the quick reply. The article is already approved. I reviewed it and corrected some extraneous garbage that appeared inside the penultimate code block (C++).
The last code block is PowerShell code, and I can't correct its syntax coloring. You can see the correct syntax coloring by copy/pasting that code into the PowerShell ISE edit window.
I guess this update will go through the AAC too...
Thanks. 
|
|
|
|
|
I always configure my settings (both Forums and Newsletters&E-Mails) so all e-mail notifications are disabled, but 4 times today they have been reset.
thanks, Bill
«To kill an error's as good a service, sometimes better than, establishing new truth or fact.» Charles Darwin in "Prospero's Precepts"
|
|
|
|
|
We've had some database outages this morning due to some emergency maintenance. It should be better now.
cheers
Chris Maunder
|
|
|
|
|
I have already posted a question[^] on CodeProject to get help in making multiple tabs for code in different languages. Sadly, I didn't get lucky to get an answer. I was trying to write an article, that contains code for different languages, merging them up into one having C++ in it caused an havoc, the C++ code is never merged into one tab, is always visible, and once clicked on the title "C++" the window scrolls down to the code block of C++.
But I found out, that the problem is with the title (lang="") having a value of C++, if I enter C+ it works, if I enter C, it works. But not when the value is C++ (or any other case of similar value). I have had put Java, VB.NET, C# in the tabs, so I think putting the C++ code as a C code would be an alternative until you guys fix it up.
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
|
Yep - it's the "+". I've fixed this and will be deploying the fix soon.
cheers
Chris Maunder
|
|
|
|
|
Hey,
I inserted some code from VS into the new Article editor on CP and it looks great in editor but not in preview.
Image
|
|
|
|
|
Unfortunately the editor can get cranky with that. If you go into the HTML mode you can strip out the bad stuff. Or if you just don't want to deal with the editor email me and I would be happy to on your behalf. I've fixed the formatting for you on this one.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Thank you, but i think in future it would be nice when WYSIWYG within the editor.
|
|
|
|
|
|
Are you using an add-in or extension that copies the code as HTML? (PowerCommands or something?) This is the issue because the code is no longer pure code, it's actually marked-up code, so pasting into a PRE block makes the editor think you're pasting a HTML sample, not a C# or C++ or whatever sample.
Simple solution is to use the "Paste as plain text" button. Top row of the article editor's toolbar, 4th icon along.
cheers
Chris Maunder
|
|
|
|
|
That is a good point im actually using the PowerTools from MS. That will cause this error, but its still confusing that the Editor shows a Makeup that will not be the expected outcome.
|
|
|
|
|
|
He's just missed the "http://" from the start of the link in his biography.
Without it, the browser interprets the URL as being relative to the current page. Since the page doesn't exist on CodeProject, you get the standard "page not found" error.
It's a simple mistake by @newtonsaber; it's not a bug in the site, and there's no malicious intent.
webkitWeird is part of the CodeProject menu script. It's just a variable name; there's nothing to worry about.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks so much for explaining that.
I'm trying to figure out what I've done wrong in my bio.
I will try to fix it, but it must've been like this for a long time.
I haven't changed anything recently. Hmmm...
I thought that link to my site previously worked. I'll check it all out and fix it up.
Thanks again.
|
|
|
|