|
I was sent a message for sign-in email address confirmation containing this line:
Click here: https://www.codeprojectcom/script/Membership/ConfirmEmail.aspx?tg=[removed by Ed]
to confirm that this is your email address.
There is no dot between the domain name and com, so the link didn't work.
|
|
|
|
|
It would be nice if we could sort our articles on the criteria we select (without regard for what section they are in), such as:
- Alphabetically
- Date published (low to high, or high to low)
- Popularity (low to high, or high to low)
- Score (low to high, or high to low)
etc...
Of course, this would also be carried over to Tips...
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
|
The one way I can clearly reproduce is posting and article with TOC in the form:
<p>
<div class="toc">
<ul>
<li>...</li>
<!--
</ul>
</div>
</p>
Is it wrong? In this case, submission process adds empty paragraphs before and after this fragment:
<p> </p>
These empty paragraphs are, unfortunately, well visible, because the content of these paragraphs is a non-breakable space. (Implementing of formatting side effects via using of such special characters is usually described as discouraged technique.)
Thank you.
—SASergey A Kryukov
|
|
|
|
|
Before you click the Publish button, try checking the box "I'm an expert - don't mess with my HTML" (or something to that effect).
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Thank you, John.
Of course I do exactly that. What I describe happens in this case, too.
—SASergey A Kryukov
|
|
|
|
|
It hit me yesterday. I experienced it when I switched from "source" mode (not using the Ace source editor). It's also not constrained by lists. It happened A LOT.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
|
|
|
|
|
Exactly.
Sergey A Kryukov
|
|
|
|
|
The issue here is that our editor (CKEditor) is using the HTML 4 standard which says the DIV element cannot be inside another block-level element, like a P element.
In HTML5 the DIV element can be found inside and can contain other flow content elements, like P and DIV. We were looking to move to CKEditor5 but it's moved to a method we've seen other editors adopt as well: not allowing HTML source editing at all. This provides them a lot of flexibility for new features (eg they can output whatever HTML they want, or Markdown, or whatever) while ensuring the final layout can never be messed up by someone adding custom HTML through a source view and another editor wrecking that by using the editor.
So long story short: Don't put a DIV inside a P block.
cheers
Chris Maunder
|
|
|
|
|
Quoting a message with in the text results in it displaying [mastadon]. At a minimum it should quote as [elephant] if there's a reason why you can't force a translation back to directly.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, weighing 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
|
|
|
|
|
It's considered an Easter egg emoticon and so it's text trigger isn't ever shown.
cheers
Chris Maunder
|
|
|
|
|
Chris Maunder wrote: it's its text trigger isn't ever shown
FTFY.
Or, in other words, it's "its", not "it's".
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
cheers
Chris Maunder
|
|
|
|
|
I think you meant
Or possibly :mastodon:
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Since I want codeproject to continue I completely understand that ads need to be there.
And I might even be interested in something.
But I just noticed now that Adblock was successfully blocking everything. So just now I added the site to the exclusion list.
I don't think that the site ever attempted to tell me that that was the case.
I think it is reasonable that it does so.
|
|
|
|
|
On a related note, surely there must be an advertising solution that doesn't require white-listing scripts from DoubleClick.net?
For CodeProject, I've turned off my adblockers and enabled scripts from everything except that nefarious domain. I have yet to see a single ad on this site.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: I've turned off my adblockers and enabled scripts from everything except that nefarious domain
So even with no adblocker you don't see ads? Do you have developermedia.com whitelisted? Whatabout the Google doubleclick sites? This is all very curious.
cheers
Chris Maunder
|
|
|
|
|
How about fall back image only ads? So, if visitors have an ad blocker, you'd just show static images as ads (with a-href-links). Hard to block images when they are hosted on your site.
|
|
|
|
|
Interesting idea.
cheers
Chris Maunder
|
|
|
|
|
As I said, I've disabled uBlock Origin and Privacy Badger for CodeProject, and white-listed everything on the site except doubleclick.net, and I still don't see any ads.
I'm not keen on enabling doubleclick because of their poor reputation, and history of serving up malvertising.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
It's important to distinguish between the technology (doubleclick) and the marketplace (AdExchange). Google owns both and have a huge vested interest (obviously) in keeping things clean. However, their version of "clean" is like their version of "Do No Evil". It's in the eye of the beholder.
We use doubleclick to serve our ads - even the ones we hand-pick. We also source some ads from AdExchange when necessary but we keep an eye on them. Blocking AdExchange is fine, but blocking doubleclick means you throw out the baby with the bathwater. Or, err, the ads with the other ads.
cheers
Chris Maunder
|
|
|
|
|
I'm getting closer - I now have a small blue box with a white "X" in it, and no "script loading blocked" messages. But still no ads!
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
No need to tie yourself in knots on this one. Regardless, the sentiment is appreciated.
cheers
Chris Maunder
|
|
|
|
|
We've debated long and hard about alerting people to ad blockers, but our conclusion was that those that have ad blockers know they have ad blockers and don't need reminding.
However, we've also considered the case where readers install an adblocker for all those popup and nefarious ads that are around and when they come to CodeProject they simply forget they have an adblocker and would be totally fine with our ads.
If the latter's the case then we can certainly show, in blocked ad space, a "In case you forgot: you're using an adblocker"
cheers
Chris Maunder
|
|
|
|
|
Do you have stats on the percentage of visitors who block ads?
|
|
|
|