2.0 coming...

maverick · **Reply #1020 on:** February 17, 2006, 10:49:22 AM

Quote from: "rejetto"

Quote
1.) Is the template section [upload-failed] still valid? If so, how is it triggered and when? I have tried different things (cancelling upload etc.) and this section of the template doesn't get activated.
i fear the only way to fail to get that section ATM is to this: Minimum disk space reached

Doesn't seem to work here. To test, I have used a minimum disk space free MB number (in limits) that's greater than my actual partition free where my upload folder is located and a upload still went through completely without error. Maybe that minimum disk space free limit only works with MB's in a certain size range or your drive is "really" short of available free space. I know this isn't a big issue, but if you get the time, try it and see if it works for you.

Anonymous · **Reply #1021 on:** February 18, 2006, 06:32:11 AM

Can't wait for beta35

Please, Rejetto, can you add an option to the 'Open directly in browser' so that if you leave it blank it acts like a browser normally would and change it so than when you type in the extention it's for what doesn't open directly in the browser because its hard and annoying to go through every extension to open in the browser like it normally would.

Hope you know what I mean, thanks.

rejetto · **Reply #1022 on:** February 19, 2006, 06:34:16 AM

Quote from: "maverick"

Doesn't seem to work here.

yes, it was a bug
fixed

rejetto · **Reply #1023 on:** February 19, 2006, 07:13:22 AM

beta35 @ www.rejetto.com/temp/hfs2.0beta35.zip

what's new
+ self test improved
+ Menu -> Virtual File System -> "Auto-save every..."
+ Menu -> Options -> "Auto-save every..."
+ File Menu -> "Visible only to anonymous users"
+ File Menu -> "Let download"
+ File Menu -> "Auto-hide empty folders"
+ new template symbols: %number-addresses%, %number-addresses-downloading%
* more external address sources
* filetime sorts from newer to older
* many menu items restricted to expert mode
- sometimes IE hangs after reaching 100%
- progress frame: progress bar was not working in Firefox and Opera
- ~files.lst showing filenames it shouldn't
- "let browse" was not inherited by subfolders of real folders
- AV on kick connection
- template: [upload-failed] was not working
- other minor bugs

rejetto · **Reply #1024 on:** February 19, 2006, 07:24:32 AM

Quote from: "Anonymous"

Can't wait for beta35

here it is

Quote

Please, Rejetto, can you add an option to the 'Open directly in browser' so that if you leave it blank it acts like a browser normally would

and how a browser normally would?
the open directly is just a suggestion the browser, it is not forced to do it
if you leave it blank, HFS won't suggest nothing

Quote

and change it so than when you type in the extention it's for what doesn't open directly in the browser because its hard and annoying to go through every extension to open in the browser like it normally would.

you don't have to type normal things... HFS by default already is configured with such things. if you miss something, just tell here.

maverick · **Reply #1025 on:** February 19, 2006, 09:57:09 AM

Quote from: "rejetto"

Quote from: "maverick"
Doesn't seem to work here.
yes, it was a bug
fixed

Thanks for checking this out rejetto. [upload-failed] is now detected based on the minimum disk space free set in limits.

However, I have a question for you. Doesn't HFS first check to see if there is enough free diskspace for the upload before the upload starts? HFS already knows the full transfer size with %total bytes%.

To test I started a 20MB upload which far exceeded the minimum disk space free limit. The whole 20MB was first uploaded (somewhere), taking up the same amount of upload time for a full 20 MB file, **BEFORE** the [upload-failed] notification popped up. I would sure hate to be the one who is actually waiting for an upload like this to complete before being notified that the minimum disk space free limit was exceeded and the upload failed.

Is this the behavior you wanted?

An upload that exceeds the minimum disk space free limit
1. shouldn't even be allowed to start IMHO
-or- similar to what you have now ...
2. the upload should be allowed to start and run but **just until** the minimum disk space free limit is reached, then quit, and the [upload-failed] notification pops up with the reason why the upload failed.

Quanta · **Reply #1026 on:** February 19, 2006, 10:17:49 AM

G'Day Rejetto,

After I upgraded to Beta35 I only can use port 80. Before I can use every port I want. I Checked everything and did not chance anything. Every time I put in the portnumber I want to use and switch over to ON, the port chanced back to port 80. The portnumber I want to use is not in use by any other program. In fact, every other portnumber than 80 won't work.

I'm goin back to Beta34 to see if the problem is gone, I will let you now if it does.

Greetz, Quanta.

maverick · **Reply #1027 on:** February 19, 2006, 10:33:06 AM

I confirm quanta's finding.

HFS v2.0 beta 35 will only allow port 80 no matter what other port you try to use.

Must be a bug.

Quanta · **Reply #1028 on:** February 19, 2006, 10:42:37 AM

Oke, i'm back and running Beta34 now without any problems. So I also think it's a bug in Beta 35.

Keep up the good work (whenever you have the time for it..:-))

Greetz, Quanta.

maverick · **Reply #1029 on:** February 19, 2006, 10:54:13 AM

Quote from: "rejetto"

beta35 what's new
+ Menu -> Options -> "Auto-save every..."

I don't see this in menu -> options (other options?). I do see it in menu -> virtual file system
This might be just a posting error.

Anonymous · **Reply #1030 on:** February 19, 2006, 01:23:55 PM

Yep HFS is only working with port 80. Please fix this rejetto.

Thanks!

rejetto · **Reply #1031 on:** February 19, 2006, 06:48:58 PM

Quote from: "maverick"

Is this the behavior you wanted?

this is the behavior expected by HTTP.
an upload is an HTTP request.
i can answer only after the request is complete.
well, i could break the connection, but this way the browser would just say that an error has occurred.
the break would PROBABLY be a better solution for big files, but SURELY a worst solution for little files.
thereforse, it is a protocol limitation.
of course, if anyone has suggestions...
maybe adding a warning in the upload page...

rejetto · **Reply #1032 on:** February 19, 2006, 06:54:28 PM

beta36 @ www.rejetto.com/temp/hfs2.0beta36.zip

- fixes the port bug

rejetto · **Reply #1033 on:** February 19, 2006, 06:56:09 PM

Quote from: "maverick"

Quote from: "rejetto"
beta35 what's new
+ Menu -> Options -> "Auto-save every..."
I don't see this in menu -> options (other options?). I do see it in menu -> virtual file system
This might be just a posting error.

yes, it is a typo, Menu -> Save options ->...

maverick · **Reply #1034 on:** February 19, 2006, 09:50:28 PM

Quote from: "rejetto"

Quote from: "maverick"
Is this the behavior you wanted?
this is the behavior expected by HTTP.
an upload is an HTTP request.
i can answer only after the request is complete.

If it is a protocol limitation, we will have to live with it. Breaking the connection producing a browser error wouldn't be a good solution as the person uploading wouldn't know what happened and why it happened and may just attempt to send the file again producing the same error.

Adding a warning to the upload page may be the best solution for now. We can easily do this with a folder comment or by adding some additional comments when using %diskfree% in the upload pages. I guess you can consider this issue closed.