|
I do not know what's going on. Sean has, as usual, been a great help. But there are serious problems with the publishing process at Code Project.
1. In attempting to use a PNG within a recent article, I was thwarted by something I had no control over. Were it not for Sean, the PNG would never have appeared in the final published article.
2. When I viewed the published article, I found that an HTML end-tag was removed. The original HTML was
If set <span style="color: #4169E1">true</span>, the first row will be treated as ....
In the published article it appeared as (note the missing </span>):
If set <span style="color: #4169E1">true, the first row will be treated as ....
This of course caused the word "true" and all following text to appear in RoyalBlue.
3. There appears to be no way in which to colorize objects within a <pre></pre> block. In my current article this requires a significant increase in the concentration needed to understand the article. What was simple became difficult because I could not color-code some pseudo-code.
What concerns me is that these kinds of bugs are rampant. Furthermore, the paper that was finally published diverged significantly from my intent. It does not matter if I check "keep your fingers off my HTML". The changes are occurring somewhere within the Code Project publishing paradigm.
By including the Code Project stylesheets in the <head> of my documents, I thought that I could preview what I expected to see in the final Code Project article. But when it gets published, the results are different from what I saw in Firefox. This is unacceptable from an authoring standpoint. I put a lot of work into creating an article for Code Project. I appreciate the overarching philosophy to have all articles appear with the same styling. But, when I follow the "rules" and bad things happen, I must question the process involved.
It's time to fix the publishing process at Code Project! I, as usual, stand ready to help.
[Edited: turned on "Treat my content as plain text, not as HTML" to allow Gus' HTML tags to appear in the text]
Gus Gustafson
-- modified 17-Jul-17 13:54pm.
|
|
|
|
|
And this report was edited badly by the publishing software. I did not number my paragraphs. I used static text This is the type of problem I am weary of.
Gus Gustafson
|
|
|
|
|
Try disabling markdown if you still have it enabled. You can find the option under the message edit and preview area.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
I am unaware of any such option. Please be more specific. Recall that I'm referring to article authoring.
Gus Gustafson
|
|
|
|
|
Reply to or edit a message, and scroll down until you get just under the preview. There are four checkboxes, one of which is 'Use Markdown Formatting'. Uncheck that one if it's checked.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
|
|
|
|
|
Once again, I am not referring to the replying to or editing a message. Rather I am referring to difficulties when authoring an article. Your comments refer to messages. My concerns are with authoring articles.
Gus Gustafson
|
|
|
|
|
Gus,
You've entered a bunch of HTML tags in the content of your message and our forum system interprets HTML tags as, well, HTML (and has since we started CodeProject) unless you check "Treat my content as plain text, not as HTML". I've edited your message and ticked this box.
We also added support for Markdown[^]. Your message had the "Use Markdown formatting" box ticked as well which was causing the paragraphs to be numbered. I unticked this box.
Your concerns
1. I'll talk to Sean about the image issue. Did he provide you any guidance or explanation of what went wrong our end?
2. Can you please send me the original HTML you were attempting to post directly? I'll see what was happening with the HTML parser. I'm surprised an ending tag was removed. I've not seen that before.
3. We don't support coloursing code within PRE blocks. This isn't a bug, it's a style decision.
cheers
Chris Maunder
|
|
|
|
|
I notice this problem long time ago, but everything worked out finally; and I did not have precise description.
Today, I can describe the problem I observed when I updated the top picture of the article All in One Toolchain for Article Writing with Visual Studio Code.
In the article submission wizard, I first removed all uploaded files. Then I uploaded new files, not touching article text, but the file names were the same. After submission, I still saw the old picture. In second attempt, I noticed that the img element was different: its src was pointing not to the article directory, but some sub-directory (it's name made of several decimal digits). Apparently, is was some shadow copy of old .png file. On third attempt, I changed src to the name of the new file. After submission, I still saw old picture. On next attempt, I managed to fix the problem by giving the image file a new .png name, but it does not sound right.
Thank you.
—SASergey A Kryukov
|
|
|
|
|
The best thing to do is not delete images when uploading new ones. The system handles updates by placing them in a Working directory so that the original images are still available to the currently published version of your article. Once the new version is made public the images are swapped out.
cheers
Chris Maunder
|
|
|
|
|
All right, thank you for the advice. If I have a change, I'll try that way. But frankly, it's not logical. With file systems, if you delete file and immediately copy another one under the same name, or if you copy without deletion, logically, results are the same, right? 
—SASergey A Kryukov
|
|
|
|
|
You're forgetting that updates and existing articles must exist together.
If you delete a file then you delete if from the current article. Current readers suddenly see broken images.
When you upload a file it belongs to the new version of the article, which is not yet visible, and so the files are kept in a separate location. Deleting from the current and uploading a new doesn't not do a "delete and replace". You're doing a "delete and store in staging".
cheers
Chris Maunder
|
|
|
|
|
No, I'm not forgetting it. It simply means that the operations should be presented differently. Just think about it. Isn't that obvious that all the operations should do the same? There is no difference between deleting, replacing, adding. All you do you do on a new version of the article, no matter what...
—SA
Sergey A Kryukov
|
|
|
|
|
The problem we had last December, where every key press sends a synchronous XHR request to the server, seems to have come back again.
Almost impossible to post a message[^]
The textbox either doesn't respond, or skips letters.
The call-stack for the request:
TextEditor/this.getSanitisedMesssageHtml https:
RefreshPreview https:
UpdatePreview https:
Every request is followed by an error:
TypeError: o is not a function editor.min.js:1:11798
success https:
i https:
fireWith https:
z https:
c/< https:
send https:
ajax https:
TextEditor/this.getSanitisedMesssageHtml https:
RefreshPreview https:
UpdatePreview
The only way to type a message is to use the developer console to execute:
RefreshPreview = function(){}
Firefox 54.0.1 x64 / Win10 1703 / Web02
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Seems to be fixed now, I was seeing it a little while after you reported it.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Yeah, sorry - in the middle of deploying an update and one of the javascript files wasn't updated correctly. All fixed now.
cheers
Chris Maunder
|
|
|
|
|
Hi,
How long do you plan on doing this? Everything is so... fractured. Have you considered making it so these categories are hierarchical?
In other words "C++" is the parent for everything under "C++98,C++11,C++14,C++17 ... "
and
"C#" is the parent for everything under "C#1,C#2,C#3,C#4,C#5,C#6,C#7 ..."
To make matters worse... I cannot seem to get the combo box for the "Interested" filter to produce anything but C++14 on MSEdge. Even though I see questions containing other C++ tags. Also... my Interested filter doesn't even work.
Trust me... it is unnecessarily difficult to come to your website and actually locate something to contribute to in the "Quick Answers" section... requiring multiple searches. A quick/cursory analysis tells me that the complexity is due to the fractured categories and that a hierarchical tag system would make finding information so much easier.
Best Wishes,
-David Delaune
|
|
|
|
|
We've had hierarchical tags since almost the beginning. The interesting thing is that we built a big, complex system to handle setting and searching for tags and it...was never used.
For instance: when marking an article as C#7 it also means it's to do with C#, so C# should be added as well. However, if an item is marked C#7 and isn't marked with C# as well, then a search for C# should also bring up items marked with C#7. And then, suppose you mark an item as C# - do you mean all C# versions or just some?
It became complex but we added it all and apart from the load it put on the database, it was never embraced. We gave up.
So: outline your ideal and then I can see more clearly what your pain point is and how we can solve that.
cheers
Chris Maunder
|
|
|
|
|
Chris,
Chris Maunder wrote:
So: outline your ideal and then I can see more clearly what your pain point is and how we can solve that.
Typically if I take the time to point something like this out... I am looking at broad issues rather than any personal pain points. All of the issues seen within the 'Quick Answers' portion of your service seems to be with tags and tag-usage and I suspect it has a larger impact than you might suspect.
Case in point:
C++14 Tags[^]
I can't find anything in there that is actually C++14 related... nearly the same for many other language tags. If 80%-99% of the community is not correctly using tags... it's time to start looking at the site design surrounding this feature.
Hopefully I did not pick a bad week to point this out. I know you have a lot on your plate dealing with the new rules and regulations being placed upon codeproject.
Best Wishes,
-David Delaune
modified 12-Jul-17 14:28pm.
|
|
|
|
|
This is a bug
cheers
Chris Maunder
|
|
|
|
|
I want to close my account. I never used it and I don't think I will.
Thank you
|
|
|
|
|
It is easy to do yourself From here: CodeProject Member FAQ[^]
There are a few ways to do this. One way is to go your membership settings https://www.codeproject.com/script/Membership/Modify.aspx and look under your profile picture and check the box that says, "Close my account:"
Peter Wasser
"The whole problem with the world is that fools and fanatics are always so certain of themselves, and wiser people so full of doubts." - Bertrand Russell
modified 12-Jul-17 3:07am.
|
|
|
|
|
pwasser wrote: One way is to go your membership setting
Another way is to start posting SPAM. 
There are two kinds of people in the world: those who can extrapolate from incomplete data.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
That was exactly my first thought when I read the thread. But of course I can not afford such a comment.
modified 19-Jan-21 21:04pm.
|
|
|
|
|
I accidentally reported this member.
Would it be possible to remove the reports from him?
Thanks!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
