Printable View
http://www.eyesonff.com/forums/showt...73#post1274873
On that forum i notices that old manus found a way to break the forums :) lol just though I would post and say that the message div (or whatever you use (too lazy to look)) should have its overflow porperty set to scroll or hidden..
Just thought I would say somthin :) In case of abuse :)
Sorry if I should done somthing else with this tidbit, but this seemed the easiest for me :)
Bipper
I think I deleted the post you were talking about, but before that it didn't show up. I know what you're talking about, though. I see it from time to time. Refreshing the page always seems to fix it.
Yeah, the sigs of one person will overflow into the post of the next person every once in a while due to I don't know why at all. Is that what you're talking about?
Naw I am sure its all browser dependant. I use firefox and rarely have a problem .. IE for me atleast is very problematic, and the site gets twho thumbs up when I use my Jbrowse, and Amaya.Quote:
Yeah, the sigs of one person will overflow into the post of the next person every once in a while due to I don't know why at all. Is that what you're talking about?
Sounds like it could all be fixed with the same line though.
Yup you deleted it - and I did try refreshing first. The text had no spaces to be wrapped so it extended the allocated block size for the text beyond the limit of the div, thus breaking the div and making it grow longer. By setting the div's overflow pruperty to hidden, it would mearly stop the page from getting the hScrbar and if people really wanted to read it - they could highlight the text and the div would move.. or auto would give it scrolls if you wanted too -- but that looks gross /shrugQuote:
I think I deleted the post you were talking about, but before that it didn't show up. I know what you're talking about, though. I see it from time to time. Refreshing the page always seems to fix it.
Just suggestions :) Not dogging the sight or anythign... methinks its perfect... close enough
Bipper
OWNED
oh know he is a hacker :(:(
he will get my cred. card details and have babies with my children :(:(
Too late
No Worries kiddies, I dont hack. Your credit cards are safe, and your grand babies have no hope of getting decent DNA ;) :greenie:
I'm mad as a
well I have the sig overflow problems sometimes too, and I use firefox.
In the famous words of Yams:
I'll live
thought nothing against you putting forth a forum problem ;)
And since we are on the topic of discussing forum problems, I, once again, want to protest against this forums childs labor ordiments. They should extend to the internet as well
wierd, never had the sig overflow issue :)
I dont know anything about the server but I have seen issues like that when people use the apache 2.0 setup with linux :) Has to do with the fact that it's engeneered to run more on a threaded OS such as windows. This only happens on only larger high traffic servers though -- which i belive this is. There are a lot of hosts who erronously use Apache 2.0 on the *nix boxes. Don't ask why... they should be using 1.3
Like I say i know this much about this site |---| but its just a suggestion as ususal..../shrug
Bipper
Apache is a Linux-native server, which is why it's primarily run on Linux boxes. In fact, the development branch of Apache 2.1 is only offered for Unix/Linux boxes.
Just to get all the facts straight: (obligatory rant following)Quote:
Originally Posted by bipper
Apache 2.0 is a threading application (as opposed to 1.3, which forks) which does make it a prime candidate for Windows servers.
The main problem can occur when concurrent threads try to access resources simultaneously, which can happen more frequently under heavy traffic.
However, that does not exclude it from *nix systems at all as most of the problems are introduced by using non-thread-safe modules. (the apache 2.0 core is far more stable than the modules in this case) In fact, Apache 2.0 does have it's advantages over 1.3. We could use Apache 2.0 seamlessly on this server as long as it were configured correctly.
The main reasons why many hosts (us included) still use 1.3:
» Some modules such as mod_throttle or mod_bwlimited are still only for 1.3, and many web control panels such as Cpanel/WHM (which we use) rely on these modules to provide certain important features
» If it ain't broke...
» 2.0 and 1.3 perform similarly in general cases
» Apache 1.3 is a forking application, and thus is still very suitable for *nix servers. (not to say 2.0 isn't suitable, forking is just safe and efficient under *nix)
When Apache 2 modules become completely thread safe and the core application reaches maturity, it will desired over 1.3 for both Windows and *nix. However, it still can be used with Linux, given that it's configured correctly.
Ok, all done. :)
</rant>
samuraid for the win