|
Well actually I upvoted all good replies in one of my threads. The person asked me if I was the one who did it and gave me a 5 as well. That was when he noticed that he received less points.
Link to thread: GIT is awesome[^]
Link to that post: The post[^]
By the way sorry for the late reply Chris. I didn't find much time to login before.
My Blog
*cough* My Achievements: *cough*
* Posted 25,000th message in GIT O_O
* Official supporter of the "thatraja's GIT Meet Sponsor Foundation" 
What you do, when you don't know what to do is what you do when you don't want to do what you do.
|
|
|
|
|
Chris, it is happening. I created another account. I logged into that account and posted a thread. Then I went into my main account and voted a 5 on my other account thread. I only got 6 points and I am a platinum debator. So is it based also on rep points as well?
[EDIT]
I see you have fixed the problem. Thanks.
|
|
|
|
|
It doesn't seem like the editor in the Q&A section is accepting pre tags. I've tried to edit some questions to format the code snippets and it didn't work, it just adds the <pre> in plain text. I also noticed that when pasting code snippets that include html the "Ignore HTML" checkbox had no affect, everything was encoded.
Tried with both IE9 and Chrome, same results.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Below the text area edit field there's a checkbox called "Ignore HTML in text (good for code snippets)". This checkbox must be unchecked.
Uncheck it and you'll be doing fine.
Cheers!
|
|
|
|
|
Yes, I understand. Either checked or unchecked, no difference. Give me some credit for knowing how a checkbox works.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
My bad! I didn't fully read your question and had just tripped over that checkbox thing myself a couple of times lately.
I promise to be more thorough next time. 
|
|
|
|
|
The encoding and the Ignore HTML are different: just above "Ignore HTML" are four options:
When pasting:
wrap in PRE block
escape HTML characters
allow HTML
Auto detect If you select "allow HTML" then it will not encode any of the < or > characters so you existing formatting will work.
"Ignore HTML..." just treats all tags as if they were encoded so they will always display (annoying thing it is, too)
Real men don't use instructions. They are only the manufacturers opinion on how to put the thing together.
Digital man: "You are, in short, an idiot with the IQ of an ant and the intellectual capacity of a hose pipe."
|
|
|
|
|
I tried several of the combination of options and none seemed to have an effect.
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
Can you show me an example of the one you're working on?
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
I wish I could. I tried with two separate questions and know they have gone done the list. However, a quick test now finds the pre tags working.
Perhaps its my misunderstanding. Is this correct?
Allow HTML && Ignore HTML is checked
No encoding
Add pre - No code block
Uncheck Ignore HTML - code block
Escape HTML && Ignore HTML is checked
Encoded
Add pre - No code block
Uncheck Ignore HTML - Code block, characters encoded in textblock
Wrap in Pre block && Ignore HTML is checked
pre lang=xml added, encoded
Uncheck Ignore HTML - Code block, characters encoded in textblock
Though this is not what was happening yesterday. It was encoding the html regardless of any settings and not displaying the code block
I know the language. I've read a book. - _Madmatt
|
|
|
|
|
That seems correct
I find the best way to edit Questions (as well as Tips & Tricks) is to use "allow HTML" and to edit out of the window, then paste it back in
Thanks,
Sean Ewington
The Code Project
|
|
|
|
|
Is it no longer possible? How do we tell people that their "alternates" should really be posted as comments?
|
|
|
|
|
If you go back far enough - say, like this post - and then click on either the Next or Prev buttons on that page, you will be taken to the current First post, as if you had clicked the First button.
|
|
|
|
|
We know, and we need to update the UI to reflect this.
It's actually a safety mechanism.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
I don't really understand your reply; let me explain the problem I had:
When I searched for that post, I found a hit - one of the replies that were made. So I tried clicking Prev to get to the original post, and got dumped at the First.
So I'm not sure what "UI update" you have in mind, but I truly would like to have the Next and Prev buttons work.
|
|
|
|
|
I suspect the safety in question is the load on the DB servers, and wanting to avoid making it easy to DDOS the site by generating large numbers of intensive page requests.
I know a number of other sites that limit or disable searching entirely due to problems like that.
3x12=36
2x12=24
1x12=12
0x12=18
|
|
|
|
|
The UI update is to remove the next/previous simply to make it more consistent with reality.
We have a larger fix that uses some fiendishly clever SQL to allow fast paging at deep levels, but we haven't had a chance to get the bugs out of this yet.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Well, I can certainly understand why using Next and Prev to get to page 8000+ doesn't make sense, but if you land on page 8000 via search, why don't you want to have Prev and Next operable?
|
|
|
|
|
We do want it operable. But to make it operable requires and ensure the system doesn't implode requires us implementing smarter code to deal with those cases. We haven't had a chance to fix that code, so we've simply disabled the ability to page at that depth for now, since at least it protects us from spiders.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
|
|
|
|
|
Ah. Got it. Someday I'd like to hear about your anti-spider defenses.
|
|
|
|
|
Noticed a couple of bugs recently (well one ages ago and one this morning)
1) When i post an answer, there is a grey horizontal line appear which i think is the delimeter used for the Solution and vote area, it is offset to the right and therefore extends beyond the bounds of the solution area.
2) When i post a solution, the improve answer button has additional character which disappears on a refresh of the page. It shows "Improve Answer" initially.
|
|
|
|
|
DaveAuld wrote: When i post a solution, the improve answer button has additional character which disappears on a refresh of the page. It shows "Improve Answer" initially.
I too have noticed this! +1
|
|
|
|
|
DaveAuld wrote: well one ages ago
You mean the 1st one. Yes, and it was reported ages ago here[^].
See the above suggestion in that page as well. IMHO, it's a good suggestion. But the hamsters seem too busy doing changes in reputation system everyday. 
..Go Green..
|
|
|
|
|
Thanks Dave - they are on the TODO (#2064)
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
modified on Wednesday, March 16, 2011 8:07 AM
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
