|
Have you considered that lounge.asp could redirect to forums.asp? I know that if this were the case that they could automatically include forumid but if code is shared across pages then is it really worth the hassle of removing it?
|
|
|
|
|
I made a post with Ignore HTML tags option checked. Everything worked fine. I took Update message and turned it on. Message came correctly, but signature shown in text mode. It will be good if CP team can clear this.
|
|
|
|
|
|
In addition to Download code, it would be helpful if there was a View code button which would show a list of files in the source code bundle, and let users click on individual files to see the code. This would help users see how a particular task is done without downloading the entire solution.
|
|
|
|
|
It would really be a CPU intensive operation to unpack the zip files, show the files with syntax colorization.
Alongside, CP Team has to be step-up the security measures to ensure that the zip file is scanned for any viruses.
|
|
|
|
|
Vasudevan Deepak Kumar wrote: Alongside, CP Team has to be step-up the security measures to ensure that the zip file is scanned for any viruses.
Not enough to worry about.
Vasudevan Deepak Kumar wrote: It would really be a CPU intensive operation to unpack the zip files, show the files with syntax colorization
No we wouldn't: we'd be reading text files, HTML encoding them, colorizing, and then outputing them. Where's the attack vector?
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: attack vector
A few articles are uploaded as ZIP files. Zip Files would contain a mix and match of EXE, DLL and OBJ files right? These binary files are susceptible to multitude of viral infections. Isn't it?
|
|
|
|
|
As I said previously: the zips would be opened, the contents of the files read and then output in HTML encoded form. We're not exactly going to go executing every file we find in the zip file on the servers...
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
i have left some messages for some articles, how can i find them?
sizheng
|
|
|
|
|
sizheng wrote: i have left some messages for some articles, how can i find them?
To see a list of the last 200(?) posts you've made, look at your profile. Click on the link to "Messages Posted."
In your case, your profile is here[^]. And the list of your posts is here[^].
|
|
|
|
|
oh, i see.
thank you very much.
|
|
|
|
|
I propose a forum just to discuss global warming. It seems to take up the soap-box every other day.
_____________________________________________
Flea Market! It's just like...it's just like...A MINI-MALL!
|
|
|
|
|
For the last time leckey, farting DOES NOT contribute to global warming 
I get all the news I need from the weather report - Paul Simon (from "The Only Living Boy in New York")
|
|
|
|
|
Actually it does[^]. Significantly
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
If anything this is not the right forum for such discussions. Or is it?
Luc Pattyn [Forum Guidelines] [My Articles]
this weeks tips:
- make Visual display line numbers: Tools/Options/TextEditor/...
- show exceptions with ToString() to see all information
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
Absolutely not. But I can't let such an important mis-understanding about cow flatulence go unchecked, can I? Besides, I get to say "Cow flatulence" in a serious sentence.
(Yeah, it's been a long day...)
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
lacking a more appropriate forum, cows outside soapbox or lounge should be
flagged as abuse. (and obviously wandering pig messages would be spam).
Luc Pattyn [Forum Guidelines] [My Articles]
this weeks tips:
- make Visual display line numbers: Tools/Options/TextEditor/...
- show exceptions with ToString() to see all information
- before you ask a question here, search CodeProject, then Google
|
|
|
|
|
This post should really have gone in the Soapbox!
"I don't want more choice. I just want better things!" - Edina Monsoon
|
|
|
|
|
Code Project is getting javascript errors on FF:
Warning: Unknown property 'text-overflow'. Declaration dropped.
Source File: http://www.codeproject.com/styles/global.css
Line: 245
Warning: Error in parsing value for property 'height'. Declaration dropped.
Source File: http://www.codeproject.com/styles/global.css
Line: 411
Warning: Error in parsing value for property 'width'. Declaration dropped.
Source File: http://www.codeproject.com/styles/global.css
Line: 412
I found this when debugging one of my scripts and I read the error log on FF. It may help solve some strange behavior in FF?
-- modified at 11:49 Tuesday 14th August, 2007
|
|
|
|
|
Those are CSS warnings, not Javascript errors. They have no effect on the operation of Firefox
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
|
Chris Maunder wrote: Those are CSS warnings, not Javascript errors. They have no effect on the operation of Firefox
Just an observation when I was debugging a script I wrote that worked on other browsers but did not work on FF.
If it is not a problem with rendering CP good. Just thought I would mention it because similar problems did cause my script to fail on FF.
|
|
|
|
|
Those are stylesheet errors. The first one is a property setting that Firefox doesn't support, that truncates text and adds an ellipsis if the text doesn't fit. The second two are CSS dynamic expressions, which are IE-only - presumably they're used here to get around some IE bugs without affecting other browsers' rendering. None of these errors should cause a problem.
--Justin,
Microsoft MVP, C#
|
|
|
|
|
JimmyRopes wrote: javascript errors
They aren't errors. But just 'Warning' messages. It can be safely ignored.
|
|
|
|
|
Yes they are warning messages from the browser but they are caused by a scripting error.
There seems to be some misunderstanding here.
There is a popular belief that they are style element warnings and not script errors.
When they appear in a style sheet they are ignored just like any other style the browser doesn't understand. That is the CSS paradigm.
The only time these warnings appear is when they are in a script, and when they do they cause the script to function improperly. If the rendered page is OK without the desired scripting action then there is no problem.
In my case I needed the scripting action to operate properly to render the page as desired. Once it was pointed out to me where my scripting error was (thanks to Guffa) then not only didn't I get any more warnings but my script also operated properly.
In the course of diagnosing my scripting error I noticed that CP was getting similar warnings. I just brought it to the attention of the staff to be helpful -- no good deed goes unpunished.
In my case I fixed a malfunctioning script and the warnings along with the problem went away. I call that a scripting error, or, more precisely, warnings as the result of a scripting error.
|
|
|
|
|
I see these warnings all the time but I still don't consider them a scripting error since it's not the javascript engine that's throwing a wobbly. It's malformed (to Firefox) CSS. It's interesting that these malformed and unrecognised CSS attributes are only showing up when there is javascript present, but javascript certainly doesn't need to be present for Firefox to still not like the attributes.
A small subtlety here is that there are, kind of, script errors in the CSS. I'm using the IE-only eval method to get around some weirdness and this is, in fact script. But only in IE. But in IE this script in the CSS is well-formed so it's not a script error. Hence there are no script errors in the CSS. (tada!)
I know I should do some funky browser specific fiddly things to try and hide all the bits that each browser doesn't like but it doesn't actually affect the operation of either browser (except to actually make the requisite browser do what I'm telling it to do. Sometimes).
But: I definitely appreciate the heads up.
cheers,
Chris Maunder
CodeProject.com : C++ MVP
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
