|
What ads? I don't see any ads.
".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 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
You're not on Santa's "nice" list, you realise.
You make the hamsters sad.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
That is for Santa's own protection.
Somebody in an online forum wrote: INTJs never really joke. They make a point. The joke is just a gift wrapper.
|
|
|
|
|
At home, I have a 500k hosts file that prevents my browser from allowing connections to certain URLs. At work, the Air Force has even more strict requirements than I do. The net result is that at home I get a black background with a skull/crossbones displayed whenever the browser (any browser) encounters a "bad" URL. At work, I either get nothing or the standard Air Force "can't go there" warning.
".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 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
Chris Maunder wrote: You're not on Santa's "nice" list, you realise.
I should be. I dismantled the LWDE, and as a result, Santa's eight tiny reindeer will not be transformed into a pile of neatly chopped dog food.
".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 ----- "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass." - Dale Earnhardt, 1997
|
|
|
|
|
I tried to improve this question[^] (wanted to add a code-block), but after clicking Improve, I got this (twice) :
Ticket: (No ticket provided - possibly an error in the error-system)
Error: An error occurred in this page. The error has been recorded and the site administrator informed.
Abort, Retry, Fail?_
Well, now it works.
"I love deadlines. I like the whooshing sound they make as they fly by." (DNA)
|
|
|
|
|
Smithers-Jones wrote: Well, now it works.
Must have been some kind of error in the page. I'm sure it was recorded and the site admin was well informed. Hamsters have been fed and watered and they are now snug as a bug in a rug.
Just along for the ride.
"the meat from that butcher is just the dogs danglies, absolutely amazing cuts of beef." - DaveAuld (2011) "No, that is just the earthly manifestation of the Great God Retardon." - Nagy Vilmos (2011)
|
|
|
|
|
Okay, I had the same error again just a moment ago with another question, and I figured it out:
I opened a question, then I clicked on Improve. While I had some delay between those two actions (phone rang), somebody else clicked on Improve before I did. Since I didn't refresh the page yet, I didn't see, that the question is locked by another member already. Instead I get the error message, that I posted in my original post.
"I love deadlines. I like the whooshing sound they make as they fly by." (DNA)
|
|
|
|
|
|
Actually not all comments, only some comments.
When I click a comment(from my comments page) it just loads that particular page but its not going(scrolling) to comment's location.
Browser - FF8
|
|
|
|
|
I just edited this message in the Lounge and saw that it was modified. I came back later, and saw that it still showed as modified. I just noticed I got an upvote in my reputation history, and clicked the link to navigate to the message that got upvoted and landed at that message. Only, it was the older version (the unmodified version).
I thought caching only applied to voting, but it seems it also applies to message text. I tried CTRL+F5 to see if the new content would show, but no luck. I'm guessing I got tossed from one server with the newer content to a server with the older content. Although the content was only a few minutes out of date, I don't like seeing out of date content. Perhaps it's related to the 80 to 90 thousand members online at the moment, but... but... but... I no likey to see old content.
Did I mention I don't like to see old content? Because I don't.
So... my suggestion is: no makey me see old content.
Somebody in an online forum wrote: INTJs never really joke. They make a point. The joke is just a gift wrapper.
|
|
|
|
|
Just a guess from an bystander, but I imagine a site with this much traffic is quite expensive to run, and aggressive caching would have a significant effect on reducing it.
FWIW I find this site pretty fast most of the time.
|
|
|
|
|
AspDotNetDev wrote: So... my suggestion is: no makey me see old content
What a great idea.
We're still working on moving our caching to a distributed cache. You're seeing the issues with caching in a webfarm.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
1. Make the "composing" (do not publish yet) checkbox enabled by default. I'm always worried I'll accidentally publish something. Sometimes it takes days or weeks to write an article, and I periodically check it in to test formatting etc.
2. If #1 is checked and you click submit, the next screen says "your article has been published", even if that's not true. Again -- makes me freak a bit
|
|
|
|
|
We're redoing the submission wizard and that's one of the changes we've added.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Sweet!
Even better, you could make it a web services and would could write our own clients.
Ooops, there I go again. I just don't know when to stop.
Actually, on an unrelated note, I noticed there are a half-dozen or so stats applications for member stats that keep breaking because they're based on scraping. That actually would be pretty useful as a web service. Come to think of it, one of my unpublished articles is a RESTful web services framework. It could use a good demo application and I'd be willing to do the dirty work. E-mail me if you want to talk.
|
|
|
|
|
This works (previews correctly) in the article editor, but not when published.
I understand why it wouldn't work, but it sure confused me for a while.
|
|
|
|
|
I would love it if .xap files were an allowable upload file type for articles.
|
|
|
|
|
We already have the ability to insert .xap files hosted elsewhere into your articles - we just don't yet provide the option to upload .xap files onto our servers due to security concerns. Those concerns may quite well be moot - further investigation is needed.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Yeah, I can't really speak to the security concern; although the reason I asked is that it takes extra configuration to host Silverlight in a cross-domain setup, and may in fact be a greater security threat to end-users.
Also, I don't mind the extra bandwidth on my site, but the likelihood that I remove it from my site in a year without thinking about the consequences is a real one.
|
|
|
|
|
Oh, and .svg would be a nice file type to allow too.
|
|
|
|
|
Unfortunately SVG has a little too much leeway for causing damage
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
since I switched companies and changed my emails address, I have not been getting newsletters. Does anyone know a reason for this?
|
|
|
|
|
When you switched email addresses an email would have been sent asking you to confirm you own the email address. Click the link and your email is confirmed and we start sending emails. You should also be seeing a notice at the top of all forums alerting you to the fact that your email is unconfirmed.
We do this to ensure someone can't take over someone else's email address and to ensure we aren't spamming someone who doesn't want to hear from us.
I've resent a confirmation email.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I must have missed the email and I was unaware of the alerts but I have confirmed my email address now. thanks so much
|
|
|
|