Get a Freelance Job

After testing many of the available upload managers, Mega File Hosting, Easy Uploader, euploader, xtrafile and others, I have found they all have trouble uploading larger files in a hosted environment where there are limitations on PHP settings and server configurations.

I am interested in developing a script similar to those mentioned but that overcomes the limitations of uploading large, 2gb+ files.

An upload system similar to that used in Upload.ThinFile.Com/Resume where the uploaded file is chopped into smaller files and reassembled on the server is desired. The file must work in shared hosting environments where upload restrictions or PHP limitations are applied.

Intergration with Paypal for automatic billing.

A CSS compliant skinning system with [tokens] for site and user information

An upload progress bar that includes time, time remaining, file size, and amount transferred.

A registered or subscribing user would be able to select files from their computer to upload to the server. They can enter email addresses or select from an Email Group and optionally enter a message. When the upload is complete the email addresses entered or all addresses in the email group would receive an email with a download link and the optional message from the user.

The file would remain on the server for a configurable amount of time based on User Group or User Account Settings

ADMIN SETTINGS

Site Name [sitename]
Logo [logo]
require registration verification by email
show recent uploads on home page [recentuploads]*
show most popular downlaods [populardownloads]*
show featured downloads [featureddownloads]*
Admin email & password
Email users by registration groups

Create User registration Groups
Number of daily file uploads [dailyuploads]
Max File size [maxfilesize]
Max stored disk space [maxdiskspace]
Number of days until file is automatically deleted from server [daystodelete]
Archive files [archivefiles]
Optional password protect upload [pwprotect]
Optional add description to upload [uldescription]
allow to view catalog of uploaded files [viewfiles]
Public view of users uploads (website.com/username) [publicview]*
Allow to make folders (archive files) [allowfolders]*
Number of email groups allowed [numemailgroups]
Max addresses in each email group [maxemailgroups]
Default message to email recipients [defaultmessage]
Subscription
Cost (y/m/d) [fee]
Expiration Date [exp]

File Management
Admin View Uploads
File name [filename]
Download Link [dlink]
User Name [username]
IP Address [ipaddress]
Date uploaded [uploaddate]
Scheduled delete date [deletedate]
lock option (no delete) [locked]
Delete file
Ban file
Ban user

Members Management
Add user
User Name [username]
registered IP Address [regip]
Email [useremail]
User group [usergroup]
Date registered [regdate]
Exp date [exp date]
Delete user
Ban User

Override user group defaults
Number of daily file uploads [dailyuploads]
Max File size [maxfilesize]
Max stored disk space [maxdiskspace]
Number of days until file is automatically deleted [daystodelete]
Archive files [archivefiles]*
allow to view catalog of uploaded files [viewfiles]
Public view of users uploads (website.com/username) [publicview]*
Allow to make folders [allowfolders]*
Number of email groups allowed [numemailgroups]
Max addresses in each email group [maxemailgroups]
Default message to email recipients [defaultmessage]

Billing
View subscriptions by date
View subscriptions by user group
View subscriptions by exp.

Users have access to an account info page
User account info
UserName
IP Address
Email
Total Uploads [totuploads]
Total Downloads [totdownloads]
number of active files [activefiles]*
User Group
Exp Date
Create Email group

View files
Edit description
edit password
delete file
Archive File*
Edit Email Group
Add Email address
Add Name
Add/Edit default message

* These items are not needed for my plan for implementing the script but would provide functionality as a file storage system as well. Depending on cost these may be omitted.

We have a file that hold information for different lots tied to a product.

1 – If you click on any of the links under lot you will see on the next page you will see the item section with 2 fields next to it. One is lot.item_sku (which equals product.id) and the other is lot.item (which is the same as product.name) Basically we want to have 1 ajax field that we can either enter the product.sku or product.name and when we select it enters the product.id into lot.item_sku and product.name into lot.item. We did something similar to this on another file that we no longer use if it’s helps you can look at it and copy and tweak the code.

2 – We have a section on the product page that we can upload an image of each product. I copied and changed the code so we could upload an image of each cofa for the lot but it’s not working. So we would like where the cofa section is to be able to select and image and have it upload to pics/cofa.

3 – On the lot main page you will see COFA on the right hand side. We would like this to only show up if the lot has an image uploaded and be a link that opens up in a separate window showing the image. So if a lot doesn’t have something in cofa then the link would not show. We have this same code on product.php if you’d like to just copy it from there and tweak it as needed.

4 – When adding a new lot the received date and exp_date calendars do not show so we need them to show up.

5 – Not every item has an exp_date so if it’s not to hard we’d like to have a checkbox next to the calendar that either puts NULL or N/A in the exp_date field.

6 – on the lot main page if you do a FIND for lot K820697 and click into it you will see the inventory says 1.11907e+08. I’m not sure why it shows up that way. It should show up something like 75274.93. So i’m guessing when the inventory gets too long it converts it into this weird #. Is it because the field is FLOAT? If so is there a way to get it to print out correctly? What are the advantages or disadvantages to float.