fixed width adjusted. Now, awaiting for AAC :zzz: ; after woken up :OMG:

I've just posted a tip/trick, with images. I previewed it, and it was OK (with images). Now, after submitting it, when I see it in my browser, the images don't show up. Why?

For sure the article is an article(!), which means you don't know what you're writing about. You should read some posts that are been accepted as an article, telling that complex numbers have 2 types! Complex number have no 2 types! A complex number has 2 very common representations (and if you are creative enough, you can add a representation of your own). Moreover, this post accepted as an article, is just bloating the post with trivialities like 2+2=4, but 1+3=4 too! This is not an article! Maybe a technical post for naive academic purposes. I do understand the the nature of community approval here: it's voluntary (and looking for high status, right?), which means that if you don't like it, don't do it, and mainly, don't complain doing it. Right? By the way, if you cared to see the article posted by the AAC (Article Approval Community) you'd had seen an article full of problems created by them, not by me (I previewed my article, and it was OK). And with no images! And with a formatted code full of extraneous span tags! Once more, you don't understand what you're writing about. Also, if they just checked what they posted, they'd have seen the problems, but for sure, they didn't. By the way, it's the 2nd post you did against me; what's your problem? Don't you have something else (that you understand) to write about? And don't come back to tell about the voluntary work you (and others) do. I'm not interested, as much as I'm not interested in your opinion about article/tip classification. Thanks for reading. :) ADDED: by the way, I'd have down voted your post, but it's impossible. You all do rules to protect all of you right?

MFC is a good friend, and a good friend is forever. :)

Yes, it is correct now; many thanks. By the way, my article MFC PowerShells Easily: Using RunAsync and CSS3 Gradients[^] was transformed in tip/trick by someone. Would you, please, transform it back into an article? Many thanks once more.

And don't change it to tip/trick. Thanks.

First version? There's no second version. Please, don't be confused: the writing made with don't publish keep it private check-button set are not versions to be published. The only version to be published, is the the one I submitted with the publish check-button set, and this one got the images in place of the buggy pre tags for PowerShell. Please, publish the article I submitted to be published: it contains no errors. All the errors came from AAC intervention doing what they don't understand. Thanks.

The Article Approval Community has made a real mess out of my article MFC PowerShells Easily: A JSON API and Random Numbers[^]. They made the images with PowerShell code with proper color syntax vanish, and also made the only code currently visible, full of span tags. The tag for PowerShell language is buggy, thus cannot be used: it does not add color syntax properly, and worse change the code by insertion of many hyperlinks! Clearly, inside pre tags, except for color syntax, nothing should be changed, let alone with insertions of hyperlinks. So, the article is published with the images missing and many span tags in the only visible code that uses the pre tags. Please, publish my original article exactly as I posted/submitted and delete the article as it is currently published. Also, don't make it a tip; read the articles after mine in the C++ page and you'll see they follow the pattern as mine. Thanks.

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... :zzz: Thanks. :)

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... :zzz: (*) AAC - Article Approval Community

I think it's a good idea, as long as na extension link is added to the article.

Hi, I guess you did some work since my last post, because it's improved since then. I started 2 new articles using Chrome and IE11, and both are working exactly the same. The 2 new articles are called Delete this - using Chrome and Delete this - using IE11, both with status Work in progress: don't publish. If you preview both, the result will be the same: I see colors, but the color syntax is not correct. For instance, in the PS code, you can see: dir $f $t. Both ($f and $t) must have the same color, but they haven't. Anyway, now, things are much better (the code is not moved out of pre tags, and the language PowerShell appears as the selected language in the dropdown listbox). Please, after previewing the 2 articles above, could you delete them? Thanks.

Sorry, but it doesn't work for me. I have just tried again, and it failed. After I changed the language from C++ to PowerShell inside the pre tag ( <pre Lang="PowerShell"> ), and switched the editor to design mode, I saw the PowerShell code moved out of the pre tags, and with a-href's tags added to some text. Inside the pre tags either nothing, or sometimes, a PowerShell language comment ( when I have such comment as the 1st line in the code ). :omg: Did you try the steps I mentioned in a previous reply? I followed them again.

The category Article Extension would imply to the reader that the post is relative to an Article authored by the same person who posts the extension (after all, anyone can post a tip/trick relative to any article or subject). These Article Extensions would aggregate value to the original Article, without making it boring and massive. Also, it'd be interesting if these Article Extensions could be listed (as links), automatically, at the end of the Article, in an appropriate place.

Thanks, for considering the suggestion.

What I mean is not an update of the article text, but just the code in the zipped solution/project that appears at the top. Take for instance, my article, sorry, Tip/Trick MFC PowerShells Easily: Encrypt and Decrypt. I posted a solution/project saturday (02/28/2015), officially updated today (02/02/2015), but it appears as posted 3 days ago (without mentioning any alteration). That's an example, where I think it'd be informative the tag CODE UPDATED (or something equivalent), starting the day it was officially updated, of course.

How can anyone know an article/tip/trick has the code updated if no tag is appended to the title? I have my post in this situation. SUGGESTION: add a tag CODE UPDATED whenever the code is updated or included for the first time.

You agree with me, although you didn't perceived it. There's no risk of any fight, because as I wrote in my OP, "I do not mean unveiling the voter's identity". So, any fight back is impossible. But, it is important to know the "vote quality".

Shouldn't the author of an article (also tip/trick) know who voted and what voted in his work? I do not mean unveiling the voter's identity, but the voter's status. For instance, status like: admin, mvp, author, less-than-30-days-old-member, etc... This would allow the author of an article to conclude more consistent information about his/her work. Maybe this is already possible, but I don't find the correct button to click.

Hi, I just saw I can't include an image here, so, let me explain it, in steps: 1- start an article or tip/trick 2- in the default article shown, click over the code shown below title USING THE CODE. 3- on the LANGUAGE dropdown combobox (it's probably C++ by default) try to choose PowerShell - you won't find it there. Thus, leave it as C++ and go on. 4- switch the design to html mode, and go to the text **<pre lang="C++">**and change it to <pre lang="PowerShell"> 5- switch back to design mode and see the result - it's not what we'd expect. Thanks. :)