Upload Freezes At ~ 3.4mib

[Guest deleted124536]

When trying to upload a file through the add file form (http://www.tessource.net/files/members_add.php) twice the file I was upload froze at as nearly as I can tell, the same place (well, the browser just rounds to the nearest 0.1MiB, so it could be different by a little.) My suspicion here is that perhaps it just doesn't like my browser, Opera? I know that still not many people will willingly support it, and I wonder if whatever code was used could have some problem related to it? Well, 3.4 is past the 2MiB limit to where things get shifted to that second server, but, it does seem like the problem would occur at 2MiB if that were the problem, so I'm more inclined to blame lack of browser support than anything like that. Anyway, all I know is the browser clearly shows that no more data gets uploaded from that point on and when I wait a good while (well past the time the file would have finished even assuming my upload rate suddenly slowed more than usual) it just never seems to finish.

 

In the meantime, I'll just use Firefox, but, I really hate it (albiet not even on the same scale as how much I hate IE) so I prefer to use Opera when I can. A lot of people tend to feel this kind of way about their browser of choice as well, though I couldn't really say how many preferring Opera you'll really find around here. Ok, I'll be honest with you about one thing. I am using the LATEST version. As in version 9, build 8212 (that's 9 beta 2.) However, the kind of bugs we're talking about in an Opera beta are things like the occasional rare crash (for you IE users raising an eyebrow, Opera doesn't crash very often or very easily) and a few minor GUI annoyances such as a focus bug where keyboard focus is lost if certain things take focus away from the browse and then give it back. Not bugs like broken streams (up or down.) Actually, one thing I've been impressed with is that Opera 9 seems to actually be more compatible, including some more proprietary things that are supposed to work only in IE/Firefox. Oh, but, I do set it to identify as Opera, not as IE or Firefox, so it wouldn't be fooling the site into using code for a different browser (in support of Opera, I only change it for sites that force me to like my school's webct pile of crap servers.)

 

 

EDIT: Yikes. I forgot to select the appropriate category when I redid all the data in Firefox. After it finished uploading that rather decent sized file, THEN it tells me you must select a category. It seems to me that it should just run a simple script or something to ensure you select a category before allowing you to continue. Not just to save user time, but, it can't exactly hurt server bandwidth to not upload unnecessarily.

[Dark0ne]

Hi there,

 

TESSource is tested in IE and FireFox only simply because the time:effect ratio is out of proportion. Not many people use Opera any more (not that they did before) and, if it wants to compete with IE and FireFox it needs to work on becoming more compatible with sites made to work in IE and FireFox, rather than going in it's own direction.

[Guest deleted124536]

Hi there,

 

TESSource is tested in IE and FireFox only simply because the time:effect ratio is out of proportion. Not many people use Opera any more (not that they did before) and, if it wants to compete with IE and FireFox it needs to work on becoming more compatible with sites made to work in IE and FireFox, rather than going in it's own direction.

 

I'm not sure what you mean "anymore." Its popularity is growing, not shrinking, especially since they made it completely free.

 

As for compatibility, it's not Opera's fault you have to understand. Opera is actually the most compatible browser -- the only one to pass the Acid2 test in fact. The problem lies in the fact that sites use a lot of code that is specifically made for IE or Firefox. Stick to W3C and you're more likely to get it 100% working in Opera than IE or Firefox in fact. Well, they are trying to add support for as much proprietary stuff as they can, but, since MS owns IE and both IE and Firefox do stuff they are supposed to not do, Opera can only duplicate so much of the proprietary stuff.

[Dark0ne]

The problem lies in the fact that sites use a lot of code that is specifically made for IE or Firefox.

 

That's exactly the problem. If I stuck to W3C compliant code the site wouldn't work in IE, and is unlikely to work properly in FireFox. Those are the two I aim to appease and until they both become W3C compliant browsers it'll remain that way.

 

Opera users account for only 2% of visitors to the site, of that 2% I doubt many want to upload mods. Compare that to 50% using MSIE and 40% using FireFox and I think the choice is obvious.

[Guest deleted124536]

The problem lies in the fact that sites use a lot of code that is specifically made for IE or Firefox.

 

That's exactly the problem. If I stuck to W3C compliant code the site wouldn't work in IE, and is unlikely to work properly in FireFox. Those are the two I aim to appease and until they both become W3C compliant browsers it'll remain that way.

 

Opera users account for only 2% of visitors to the site, of that 2% I doubt many want to upload mods. Compare that to 50% using MSIE and 40% using FireFox and I think the choice is obvious.

Well, the idea is you are supposed to use W3C with only fallbacks to correct for browsers that refuse to obey standards. For the most part, W3C works pretty perfectly across browsers, just the Acid2 test is designed to find minor weaknesses such as a bit of text drawn a bit off of where it's supposed to be or that sort of thing. Usually not functionality issues in particular. Ah, anyway, just what problems are you having where you are forced to use proprietary code? No, I'm not trying to correct you or something, but, if certain code is giving you problems as the web designer such that you choose not to support Opera, then perhaps it's something I should report to Opera?

 

And btw, one thing to bear in mind when you see that 2% of Opera users is that, first of all, older versions of Opera were set by default to identify as IE 6 because a lot of sites would just refuse to function correctly if they didn't see IE or Firefox and a few would even refuse to work right unless they specifically saw IE. I always switched this myself in support of Opera, but, not everyone out there is going to do this either to avoid the issues certain sites create when they send malformed code (long story, but, it happens) or just because they don't know any better. Newer versions I think now default to identifying as Opera rather than IE since the number of sites that send bad code have shrunk to a minimal amount and they can now control the identification on a per site basis via a user agent INI file (and I personally have troubles only with one site which doesn't even send malformed code, but, just simply says "Server error, please try again later" as quite possibly the dumbest error message ever -- at least, this server error has the most amazing ability to target only Opera when IDing as Opera and not IE or Firefox windows open at the exact same moment on the exact same computer, plus the server error magically goes away when I trick it into thinking Opera is IE and then the site works 100%...) Nonetheless, a lot of lazy people probably just set it to ID as IE or Mozilla and leave it at that. I'm not saying that the 2% number is off by leaps and bounds, but, it could be, say, 4% for all you know if you factor in the possibility that a few of those hits saying IE or Mozilla may actually be Opera. (On a related note, some rare people may be using the extention for Firefox that makes it pretend to be IE, though I doubt very many since it involved a bit of going out of one's way to get and all.)