Looking for PHP/HTML/Perl CGI (with some CSS) developer required [Payment via Paypal]

(posted on Digital Point and TAZ)

I am desperately looking for someone who knows his/her stuff when it comes to the coding skill sets mentioned in the above subject. If you aren't sufficiently skilled in those skills then please don't bother replying to this thread, thanks a lot

Now: Currently a 'members only' section works like this with regards to uploads.

Member uploads a file for 'consideration' of inclusion to our database. Ultimately to assist in increasing our database and in doing so the member gains additional 'thankyou' credits to enable them to download more from the databse. File is uploaded via http post and the uploaded file then gets passed to a perl cgi script for further processing. Upon completion, user is redirected to a php script which then adds the id3 tags etc, calculates a sha hash and searches the current database to see if the hash already exists, If not, then the file is moved into an upload dir and an entry is added to the upload table.


Future: A long time ago I decided that I would like to provide the member with a more visual experience whilst uploading rather than simply waiting for a file to be uploaded. And I also always wanted to provide the functionality whereby a member could upload more than 1 file at a time.

After many, many months spent digging around and accepting that no FREE offering would do, I purchased XUpload which is basically a non AJAX upload progress bar allowing for multiple uploads and it is rather good...

I have already installed and configured the script. No problems with it functioning like it was supposed to do for testing but in buying an Upload script with a fancy frontend, it doesn't automatically make it work with the rest of the back-end that your site may currently have...

... this is where I need help

The challenge (and this is where YOU come in) is set out below:

- I need XUpload's perl script tweaked to take advantage of PERL's REGEXP feature so that naming conventions can be imposed. I've spent years making sure that our database of files is super strict on the naming convention and this must continue to be the case. (this could even be done client side with some .js) and it might actually make sense to do it at that stage rather than wait for the file(s) to be uploaded first.

- Server side, I would need somehow for the script to check the bit rate and to discard anything uploaded that's LESS than 128kpbs along with a suitable message to member to reflect this. We have more than enough rules but you always get people trying to bend them as you know.

- XUpload's user front-end needs colorizing/theming along current site's look and feel and any other new pages created along the way.

- Current Upload.php needs tweaking to cater for $POST names being different from XUpload's script.

-----------------------------------------------------------------------------------------------------

These are some very valuable notes that I have kindly been passed on from one of XUpload Pro's developers and I thought that with this infomration it might make more sense what is required. I do sometimes struggle explaining what I want done.

He says

------------------------------------------------------------------------------------------------

Hopefully I look forward to speaking with someone soon as I really need to get cracking on this, the Upload feature's been down for quite a while as it is.

I don't mind however you wish to respond to this post if you are interested. Having some response would be a good starting point.

Regards,

Rich