The folder could still be there and as it is empty at that point, php will give you a warning on this. To prevent that from happening, use the ‘ unlink ( ) function, like the code that follows:

Just a little touch of overkill to save some grief later.

1. The add_dir limitation issue –

Steps:
– Create a catchall directory to maintain all of the user based folders/subdirectories created per user/per instance.

– Create/delete files on an indivudal site upload basis, which can easily be accomplished with mkdir( ) and rmdir( ) functions. This will allow you to set automated cycles as to how long the files stay on your system with the user having access to them during the duration.

– Use the file zip system on this posting to take care of the required zip process and output.

2. On the . php files being output in the zip drive as Ben suggested –

I have seen that issue before. Don’t put your files in the same directory that you are targeting as your holding directory. You will be able to eliminate that issue by storing your .php files in another directory and calling them to action with a simple include ( ) or require ( ) function. Note that in most cases, due to header code classes, I suggest using include_once( ) or require_once ( ) to prevent the loop causing errors.

By calling the process from another source, you protect your code from being hand delivered to the person receiving the zip.