Article posting
-
Hi, all I have a problem in publishing an article. Last Thursday, August 31, I submitted an article for publishing. After pressing the submit button the article showed up and everything seemed OK. But the article did not appear in the list of articles yet. When going to My Articles it shows there as Article 5365607. But when I click on it I get a black box with the message
Quote:
Ticket: Error: An error occurred in this page. The error has been recorded and the site administrator informed. Abort, Retry, Fail?_
in it. Can someopne help, please?
-
Hi, all I have a problem in publishing an article. Last Thursday, August 31, I submitted an article for publishing. After pressing the submit button the article showed up and everything seemed OK. But the article did not appear in the list of articles yet. When going to My Articles it shows there as Article 5365607. But when I click on it I get a black box with the message
Quote:
Ticket: Error: An error occurred in this page. The error has been recorded and the site administrator informed. Abort, Retry, Fail?_
in it. Can someopne help, please?
Unfortunately the article is unrecoverable. I suspect it may have been closed by the community, but since I cannot see the article, I cannot surmise why. Do you happen to have a local copy of it? If you could please email it to me (sean@codeproject.com) I'll investigate and restore if appropriate.
Thanks, Sean Ewington CodeProject
-
Unfortunately the article is unrecoverable. I suspect it may have been closed by the community, but since I cannot see the article, I cannot surmise why. Do you happen to have a local copy of it? If you could please email it to me (sean@codeproject.com) I'll investigate and restore if appropriate.
Thanks, Sean Ewington CodeProject
Hi, Sean I have a copy of the text and, of course the attachment. I can rewrite it if it is easier. In that case, must I change the title? Thanks, Tasos Kipriotis
-
Hi, Sean I have a copy of the text and, of course the attachment. I can rewrite it if it is easier. In that case, must I change the title? Thanks, Tasos Kipriotis
If indeed the article was closed by the community, it would be better if I could see the article to guide a potential re-write, or title change.
Thanks, Sean Ewington CodeProject
-
If indeed the article was closed by the community, it would be better if I could see the article to guide a potential re-write, or title change.
Thanks, Sean Ewington CodeProject
Hi, Sean Any news?
-
Hi, Sean Any news?
Apologies it seems it went to the Junk folder. Currently you've written the article coming at your subject explaining, "attached is what I have done, and here are some explanations of what I did and why I made some decisions." I suggest a different approach for the article. Walk them through everything you did. Show the your readers the math. We have LaTeX capability, and we can show the formulas in images if that is too painful (I recommend images). Explain the math. Show your code. Explain your code. Treat your article like a classroom of students of varying levels or understanding. How are you going to explain it so that the majority of them understand? As an example, here’s an article from one of our top authors: HTML5 WebWorkers Experiment[^] His primary goal is to demonstrate “Using HTML5 WebWorkers and a custom jQuery plug-in to create a Flickr image wall.” He treats the reader like a beginner. He defines jQuery, explains what WebWorkers are, then gets into why he wanted to create a jQuery plugin. Each progressive section of the article expands on his topic, thoroughly explains the code, explains the limitations he chose in his scope, discusses how each element to his plug-in works, provides numerous code examples, and most importantly, gives a source code download at the top for the reader should they need it. Every time the community considers whether or not to approve an article, this is the style of article they have in mind. They love it, they want it, and they praise the authors enormously when they get it (and we want authors to feel like their hard work is appreciated).
Thanks, Sean Ewington CodeProject
-
Apologies it seems it went to the Junk folder. Currently you've written the article coming at your subject explaining, "attached is what I have done, and here are some explanations of what I did and why I made some decisions." I suggest a different approach for the article. Walk them through everything you did. Show the your readers the math. We have LaTeX capability, and we can show the formulas in images if that is too painful (I recommend images). Explain the math. Show your code. Explain your code. Treat your article like a classroom of students of varying levels or understanding. How are you going to explain it so that the majority of them understand? As an example, here’s an article from one of our top authors: HTML5 WebWorkers Experiment[^] His primary goal is to demonstrate “Using HTML5 WebWorkers and a custom jQuery plug-in to create a Flickr image wall.” He treats the reader like a beginner. He defines jQuery, explains what WebWorkers are, then gets into why he wanted to create a jQuery plugin. Each progressive section of the article expands on his topic, thoroughly explains the code, explains the limitations he chose in his scope, discusses how each element to his plug-in works, provides numerous code examples, and most importantly, gives a source code download at the top for the reader should they need it. Every time the community considers whether or not to approve an article, this is the style of article they have in mind. They love it, they want it, and they praise the authors enormously when they get it (and we want authors to feel like their hard work is appreciated).
Thanks, Sean Ewington CodeProject
Thanks for your reply, Sean. One more question, what are the limits (words, code snippets, etc) for an article? Thanks, Tasos Kipriotis
-
Thanks for your reply, Sean. One more question, what are the limits (words, code snippets, etc) for an article? Thanks, Tasos Kipriotis
We have no official word limit, the article can be as long as you want. There's probably a technical word limit, but no one has ever hit it to my knowledge.
Thanks, Sean Ewington CodeProject