Deleting a File or Folder PDF Print E-mail
Documentation - Image Manager Extended
Written by Administrator   
Wednesday, 09 May 2007 09:54

Deleteing in the Image Manager Extended follows the same method as the Image Manager with the following differences:

If you delete an image that has a thumbnail, the thumbnail is automatically deleted as well.
If the thumbnail folder is empty after thumbnails are deleted, the thumbnail folder is automatically deleted

Multiple files or folders can be selected and deleted.

To delete a File or Folder:
A folder must be empty before it can be deleted. If it isn't, you must delete all files and folders in it before attempting to delete it otherwise an error message will be generated
1. Select the files and / or folders to delete by checking the checkbox next to each item in the File Browser list.

2. Click the 'Delete' button cross

3. An alert dialog will be displayed requesting confirmation of the action. This is to prevent accidental deletion of n item. Click the 'Yes' button to confirm or 'No' to cancel.
delete confirm

4. The request is sent to the server and the dialog is closed.

If the request is unsuccessful, and error message will be displayed in the Manager dialog message bar.  An unsuccessful deletion request will generate one of the following errors:

  • Invalid Directory - The folder does not exist. It may have been deleted by another user just before your attempt.
  • Unable to Delete Folder! - The folder's permissions may prevent it from being deleted or the server was unable to complete the request.
  • Please delete all files/folders inside the folder you wish to delete first. - The folder is not empty. Only empty folders can be deleted.
  • File Not Found! - The file does not exist. It may have been deleted by another user just before your attempt.
  • Unable to Delete File(s)! - The file(s) permissions may prevent it from being deleted or the server was unable to complete the request.
Last Updated on Tuesday, 06 September 2011 10:41
 

Search

Your Account



Tweets

JCE

@joomlablogger This appears to be a Joomla! 1.7 to 2.5 upgrade issue, not a JCE one

by JCE