|
Any Idea when you choose
Close my account How to reactivate that account
|
|
|
|
|
Yes, it is all explained on the Privacy page.
|
|
|
|
|
It says to contact them but which email to contact?
|
|
|
|
|
They all come to us in one way or another. Please feel free to use mine: sean@codeproject.com
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
@chris-maunder is the man who will help you. No need to email him, he will get a notification from this message.
|
|
|
|
|
Sean's on it!
cheers
Chris Maunder
|
|
|
|
|
Please take a look:
https://www.codeproject.com/Articles/5205732/libpe
See Table of content.
<details><summary>Expand
wasn't parsed well.
Also, all inner links aren't working [](#) .
Although it all work fine in the original readme.md
I guess your parcer has some issues.
|
|
|
|
|
I've added the details and summary tags to our list of allowed tags in our HTML sanitiser. Should be live soon(ish)
cheers
Chris Maunder
|
|
|
|
|
Thanks for the reply.
But what about hrefs?
|
|
|
|
|
Yep - href's fixed too.
We use GitHub itself to format the HTML, so a bit weird the amount of post-processing we need to do to get it usable.
cheers
Chris Maunder
|
|
|
|
|
|
So that when we get ones like this: Panurat[^] we can explain to the author that it can't be published if we know absolutely nothing about it?
Just a refusal with no explanation does seem rude and unhelpful - he may have worked hard on the code and it could be handy if he expanded the README to actually tell us what it was about.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
|
|
Images are there for me...
cheers
Chris Maunder
|
|
|
|
|
Huh? How is that possible?
Actually... I've just opened the site in Tor and I see them too.
On Edge, there are two of them, and there is a placeholder in a place of the third one (with a label "Image 4").
On Chrome, there is only one (after cleaning cache and refreshing CTRL+F5).
...I've just noticed that they are lazy loaded. Might that cause a problem?
modified 12-Sep-19 13:06pm.
|
|
|
|
|
Uh, now I see them too in all browsers. A weird glitch that was indeed.
|
|
|
|
|
Don't know if it's two items or one got cloned and retimed? (Took screenshot before investigating.)
Cheers,
Peter
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
Yeah - double post. All fixed.
cheers
Chris Maunder
|
|
|
|
|
|
When you edit an article there is the current, publicly viewable version, and then there's the working version. Once you finish editing and submit, any new images you've added will be in the /Working directory. After the article goes through moderation the new article will become the "current" published version and the images will be moved out of the /Working directory and replace the images from the previously published version.
It looks like we have a bug where we're not hooking up the correct version when displaying the image version. Once you submit and the article is approved it should fix itself up, but I'll dig in and get that issue sorted out
Make sure you refer to images via "image.ext" with no path in your HTML.
cheers
Chris Maunder
|
|
|
|
|
Thank you, I'll double check once published.
|
|
|
|
|
I published an article tagged "The Queen's problem solved". I'd love to get this article deleted
Thanks in advance
|
|
|
|
|
Log in with the account on which you posted the article, then you can delete it from the article page.
|
|
|
|