Search results

Ok then. Since your setup is perfect the script is working here with me and with many other users in this forum with pure magic. I believe that customers like you with poor programing knowledge and leak of ability to recognize it don't worth the money. You bought the script and started posting...

It's definitely a problem with your setup, since you are the only one complaining about a basic feature like this in this forum. I have the script, I've seen the code and it works. It have some flaws like I mentioned in other topics (like leaving files in the _tmp folder sometimes) but those...

They don't. The "trash folder" is just a list of the deleted files.

The OS has nothing to do with it. 90% of this forum probably runs the script in centos. You should probably hire a sys admin.

Check the permissions on your servers. The remove file action needs to move the file to the /files/_deleted folder, as well as creating a subfolder in /_deleted. The actual removal happens 24 after by a cron job. The php on your server needs write permissions to /files/ and all its contents.

The trash folder just list the deleted file logs with their stats. The files themselves are deleted from the server.

xsendfile is an apache module. The script can use this module if you install it, but it's not the script's responsibility to install it for you. You are responsible to setup the environment to run the code.

Lots of things can go wrong with a 103gb file. After downloading the file the script will try to calculate the md5 using the md5_file function from php that loads the entire file on memory to calculate. If your server doesn't have 103gb of ram, that will take forever, assuming the php is allowed...

You mean a desktop application similar to dropbox? That would cost a lot, something between $30.000 and $50.000 and several months of development.

There isn't any more details about this to give. If you visit the download pages of several files and check the session in the database you will see the data accumulating there. Maybe the best approach to fix this would be store the download variables in an array and check the size of this...

Continuing in a reply to make it private. This can be exploited by a bot requesting the download page of all files on the website. For each file, several new variables will be stored on the database. It's possible to create several GBs of garbage in a few minutes using this method.

Hello. I just notice a bug that may leave garbage in the session data. When a user requests a download page and don't start the download, the script will leave the download info (such as _download_page_next_page) stored in the session until the session expires or the user tries to download the...

Sessions in this script are saved in the database. If your script loose the connection to the db, the write will fail.

Just for free users. Premium have no restriction.

You can limit the download by only 1 ip, or track accounts being used by lots of ips and ban them.

The plugin just allows your users to upload using an ftp program and the ftp protocol can resume uploads. The uploads in the browser will remain the same.

There is a plugin that allows users to upload via ftp.

The browser will not resume a post request if the connection drops. To do this you will need ftp or a desktop application.

This may be done by allowing multiple entries of the same folder with different user ids in the database. But users will be able to rename and remove the folder and files inside it.

How much can you spend on a custom mod to download from mega.nz?