I just created this code, so it is not fully tested.

On an update page, include the PHP file attached in a zip. It is a small function for getting the directory/file information out of the cache directory.

getDirectory.zip

Below is a link to the primary code snippet used.

WA_thumbnail-clean-up-snippet.zip

One more VERY important note before we get started. I have tried to account for a variety of scenarios like uploading a new/edited picture with the same name as the original picture, and replacement of a picture vs deleting a record and associated picture. What I cannot do anything about is when Overwrite is used for file name conflicts and more than one record in the database uses the same picture (or same image file name) in the same directory location. Under these circumstances, deleting one record would cause a broken link in the other record since the file was deleted. If this could be an issue for you, be sure to use Rename new file as the file naming method to avoid this problem, and always rename the new file not the existing one.

And now for the tutorial:

IMMEDIATELY AFTER THE UPLOAD FILE CODE, add a WA delete file transaction based on a successful upload of your new file, and delete the file to be replaced.
That will still be the current value in the database because the update transaction has not happened yet.

<?php
 WA_DFP_SetupUploadStatusStruct("WA_UploadResult1");
 if((((isset($_POST["exec"]))?$_POST["exec"]:"") != "")){
 WA_DFP_UploadFiles("WA_UploadResult1", "image", "0", "", "true", $WA_UploadResult1_Params);
 }
 ?>
 <?php
 $WA_DeleteFileResult1 = false;
 if($WA_DFP_UploadStatus["WA_UploadResult1"]["statusCode"] == 1){
 $WA_DeleteFileResult1 = WA_FileAssist_DeleteFile("../../images/blogs/", "".$row_WADAblog['image']  ."");
 }
 ?>

Below that code include the following code block. Be sure to customize the first three values to match your transaction.

<?php 
// WA File Cleanup
/*
CONFIGURE THUMBNAIL TRANSACTION VALUES
*/
/*
 The results value created by the WA delete transaction to use as a trigger for whether or not to cleanup any thumbnails.
*/
$deleteResult = $WA_DeleteFileResult1;
/*
 The Server File Name Value. This is used to check if the uploaded file name is the same as the previous file name.
 If it is, resized images will still be deleted so they can be regenerated.
 This is done in case the image changed but file name remained the same, and overwrite is the method used in the upload.
 For a delete trasaction, just set the value to "". The delete file transaction will be the trigger.
*/
$newFileName = $WA_DFP_UploadStatus["WA_UploadResult1"]["serverFileName"];
/*
 Path to the directory where the image cache files are stored. This can be vary specific like /image_cache/images/blog or more general like /image_cache.
 
 The higher the directory, the more potential for an inadvertant thumbnails to be included. For example, if you had an image_cache directory and under it you had 
 thumbnails generated in directories images/blog and images/gallery, if a source image foir thumbnails existed in both the blog and the gallery that had the 
 same name, both thumbnail sets would be deleted. In addition, the higher the directory setting, the greater the execution time though this may be marginal 
 in most cases. THE BEST PRACTICE HERE IS TO SET IT TO THE DIRECTORY JUST ABOVE THE WA DIRECTORIES OF fit, proportion, and crop.
*/
$cacheDir = '/image_cache/images/blogs';
/*
 The name of the database field that held the name of the file just deleted. cachedFileName is a bit misleading since none of the cached files or directories
 have this name, but the cached item's names are all based on the old file name.
*/
$cachedFileName = $row_WADAblog['image'];
/*
 Any array of files to ignore. Usually just an .htaccess file, if anything, for our purposes.
*/
$ignore = array('.htaccess');
/*
END CONFIG
*/

// Code block continued
if( $deleteResult || ( ($newFileName == $cachedFileName) && ($cachedFileName != "") ) ){
 $dirTree = getDirectory($_SERVER['DOCUMENT_ROOT'].$cacheDir, $ignore);
 if (count($dirTree)) {
 foreach ($dirTree as $dir => $files) {
 $dirName = substr($dir,strrpos($dir,"/")+1,strlen($dir));
 $filter = substr($cachedFileName, 0, strrpos($cachedFileName, '.'));
 if (substr($dirName,0,strlen($filter)) == $filter) {
 if (count($files)) {
 foreach ($files as $file) {
 unlink($dir."/".$file);
 } }
 rmdir($dir);
 } } } }
?>

THE NEXT STEP IS VERY IMPORTANT. If you have one update transaction for the entire record, open that server behavior and remove any update value for the image file.
Add a new update transaction that is triggered off of a successful upload of your image file.
DO NOT SET A REDIRECT VALUE.
Be sure to place this update transaction before the existing update transaction that updates the rest of the fields and redirects the page.

This should now be working code with one caveat. If the user uploads a file with the same file name as the file being replaced, the file and thumbnails will be deleted. To prevent that, add a conditional statement around the delete transaction that checks whether the file server name is the same as the current file name in the database.

<?php
WA_DFP_SetupUploadStatusStruct("WA_UploadResult1");
if((((isset($_POST["exec"]))?$_POST["exec"]:"") != "")){
 WA_DFP_UploadFiles("WA_UploadResult1", "image", "0", "", "true", $WA_UploadResult1_Params);
}
?>
<?php
if ($WA_DFP_UploadStatus["WA_UploadResult1"]["serverFileName"] != $row_WADAblog['image']) {
?>
<?php
$WA_DeleteFileResult1 = false;
if($WA_DFP_UploadStatus["WA_UploadResult1"]["statusCode"] == 1){
 $WA_DeleteFileResult1 = WA_FileAssist_DeleteFile("../../images/blogs/", "".$row_WADAblog['image']  ."");
}
?>
<?php } ?>

In conclusion, if you have any problems, re-read this tutorial carefully. WebAssist may place code in places other than where the cursor was, so check and see if you need to move any code blocks around, and double check the order of the code execution which should be:

1. Include the function file from the link above at the top of the file
2. Whatever code or validations you have before the update stuff begins.
3. The WA recordset that includes the image field.
4. The upload transaction.
5. The Delete transaction with the name check conditional statement.
6. The code snippet that deletes the resized images (remember to customize the confguration values at the top of the snippet).
7. The update transaction that ONLY:
   1. Triggers on successful upload,
   2. Updates the image file field with the uploaded server name, and
   3. DOES NOT redirect the page when completed.
8. The update transaction that updates everything else EXCEPT this image field, and redirects the page afterwards to where ever you want to redirect to.

To implement this for a delete transaction, everything is the same except there is no update transaction and you want to do it every time there is an image file.

www.ShellysHouse.org

www.VRManagement.net

1. Delete the old file if there is a new one uploaded.
2. If the new file uploaded has the same name as the old one, DO NOT ACCIDENTALLY DELETE THE NEW ONE WHEN USING THE OVERWRITE METHOD FOR THE FILE NAME
3. Save the old file and do not update the database field if the upload fails

To do this, I added a file delete behavior for the existing file name in the database, then the upload behavior, and triggered both off the submit button.

Then the update transaction. You may have to juggle the code around to get it in this order.

Now, here is the trick. Enclose both the delete and the upload transactions in a PHP if statement that checks for whether or not there was an error in the file upload.
(Note the value of the PHP $_FILES array for the error key IS 0 if there were no errors, and an empty file field actually produces an error code of 4)

Now set the update binding for the file name to the WA Server File Name ($WA_DFP_UploadStatus["WA_UploadResult1"]["serverFileName"]) with a default to the recordset value of the file name (the original file name)

If there is any upload error, the WA upload code will not be executed, so $WA_DFP_UploadStatus["WA_UploadResult1"]["serverFileName"] will not be set.

Now if no file is uploaded, or there is any error in the upload, nothing will be deleted or uploaded (copied from temp to the web site space), and the file name will remain unchanged.

If a new file is uploaded, the old will be deleted, the new uploaded, and the database updated correctly.

If the new upload has the same name as the old one, the old file will be deleted first, the new one uploaded, and the database name will still be correct.

None of this will protect against collisions with the same file name from a different record, so always use caution with overwrite.

This method will also work fine with a renaming scheme like incrementing except you will never increment unless the file with the same name belongs to another record.

It would also work with a fixed file name like File_RecordID.jpg

Error 1402.Could not open key: UNKNOWN\Components\xxxxxxxxxxxxxxxxxxxx\yyyyyyyyyyyyyyyyyyyyyyyy

The problem, most likely is that the permissions on the key yyyyyyyyyyyyyyyyyyyyyyyy are incorrect. To resolve this, search the registry for xxxxxxxxxxxxxxxxxxxx.

It should come up under

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\xxxxxxxxxxxxxxxxxxxx

The key yyyyyyyyyyyyyyyyyyyyyyyy or more likely every subkey of xxxxxxxxxxxxxxxxxxxx is messed up. To correct this, you will likely need to take ownership of the subkeys and then correct permissions on those key. In my case, this proved to be easy because "Replacing owneron subcontainers and objects" worked (sometimes it doesn't).

Right click on xxxxxxxxxxxxxxxxxxxx choose permissions and then advanced. Click on the owner tab. Choose Edit. Make the owner "Administrators" if it is not already, and check the box that says "Replacing owneron subcontainers and objects".

Click on OK. Get back to the same dialogue through the procedure above, but go to the permissions tab. If the permissions were not already correct, you should see updated permissions in this dialogue now. Check the box that is labeled "Replace all child object permissions with inheritable permissions from this object" and click OK.

Rerun the installer. I found that a reboot is not necessary, but it never hurts.

If that was not clear, perhaps the example will help. Lets assume you have a list of articles and a list of publications. Many of your articles are published in more than one publication. You manage this with a many-to-many table that connects the two. If that isn't clear, Google "database many-to-many relationships." You have a results page that displays the articles, but you want to allow the end user to filter the results based on a specific publication.

You can view the demo of this here: http://www.blazingimages.com/demos/WADAm2msearch

To do this, first you create your database with the relationship. You can get the sample data for this demo here.

To do this, first create your table management using WADA's wizard. In this case I only created the results and search pages. I also chose to include the search form in the results page, so all the changes could be in the same script, but this can easily be adapted to the external search form as well. If the relationship is the only thing you want to search on, your best choice here is to include some field for the search in order to generate the rest of the search form behaviors and then remove the unwanted fields after you add the many-to-many search.

With the results page created, the first thing we need to do is modify the query for the results table. In the example, the original query came out like this:

We need to join the the many-to-many table to the query and include DISTINCT into the query so that we do not get duplicates of the same article when no filter is applied. Without DISTINCT, one row will appear for any given article for each publication the article is in.

Click to enlarge the image. The modified query reads:

"SELECT DISTINCT articles.id, title FROM articles LEFT JOIN (articles2publications) ON (idarticles=articles.id) ORDER BY id ASC"

Notice that I specified articles.id in the query. I used id for the primary key column in all the tables. If you have the same column name, you need to specify which table you are referring to. If they ar all unique you don't. Another place this can go wrong is if you use unique id names like idarticles, but also name the connecting column of the many-to-many table idarticles.

Next you need to modify the search behavior code. The original code read:

$WADbSearch needs another array value to include a search for the many-to-many table. In this example, the join statement connects the many-to-many table on the article id, but does not put any output into the recordset, so you need to know the table structure because we want to filter on the publication id. The produces the query that says show all articles that are in the specified publication. The many-to-many table uses idarticles and idpublication. In this case, I would not need to specify the table in the where clause, but I have included it anyway to demonstrate that you can include it in the WADA Search behavior.

Click to enlarge the image. S_publications will be the name of the search form input we are going to add. Notice the name of the function is different. WADA Search includes:

• addComparisonFromEdit for textbox inputs
• addComparisonFromCheck for checkbox input and
• addComparisonFromList for dropdown and multi-select inputs.

Many-to-many tables connect ID's, so the third parameter NEEDS to be "=". Finally, the last parameter is 1. That last parameter has to do with the type of qualifier that is placed around the statement. 0 is for text comparison (e.g. name='joe'). 1 is for numeric comparisons on numeric fields (e.g. id=1), and 2 is for dates.

Finally, create a recordset of the table on the other side of your many-to-many relationship. In this case that is publications. The recordset is used to create a dynamic list of the publications that the end user can filter on. Add a row to the search form and modify it to add the new search element, in this case S_publications. Be sure to include a non dynamic fist element that has no value to allow all your relationship elements to be included. In this example, that would translate to displaying all articles regardless of which publications they are in.

Click on the image to enlarge it.

That is it. Try the demo to see how it works.

Here is a way to accomplish this. First, you need some PHP criteria to identify the page you want to display or hide the module on. Next you need a couple of plugins. We are using mod_PHP and Modules Anywhere.

mod_PHP allows you to create modules that include code like Javascript and PHP code. Being able to include PHP code is essential. Modules Anywhere allows you to include modules in various place on your site including content areas and in this case, inside another module.

For the criteria, in our case, it was the GET value of view which equals Jaggyblog when we want the module to display. If you are using SEF links, you may need to hack you template to temporarily display GET values, or look at the link on a menu item or in you SEF listing if you are using a 3rd party extension. In our case we created a couple of menu items for the blog to find the parameter we needed.

Next create the module that you want to include and attach it to no menu items:

Next you need to create the module that will include the module we just created. Notice that we called the previous module a name which ended in "Include." because it won't be displayed on its own, but rather wrapped in the module we are about to create. We create a mod_PHP module (notice because mod_PHP was based on mod_HTML, it still says modHTML in the module type) which we called the same name as the previous module without the "Include."

In the first module, the position and order don't matter because it is not assigned to any menu items. This module (mod_PHP) needs to be assigned to all menu items. That tells Joomla it should always be displayed. Here is the trick. If the module contents is empty, it won't display. In our cases so far, the title bar does not display when using this technique, so if you use a module included this way and it shows up on every page as an empty module with a title bar, please let us know so we can take a look at it.

Now in the contents of the module use the PHP criteria you devised to display the contents only if your criteria is met. In our case, it was if ($_GET['view']=="jaggyblog") {

And there you go. The module only displays when the view is of the type we want. The div tag with the id of blogTags is optional. We included that so we could get the title element back. Next time we'll describe how this was done.