Using media Path to populate att. Category

Thanks for a good question. You can use the “MLA Custom Field and IPTC/EXIF Mapping Actions and Filters (Hooks)” (see the Documentation tab) to populate the Att. Categories term assignment.

Here is an earlier support topic with a similar example:

Quick question on replacing string(s) in image metadata

This other topic includes a more elaborate example:

Export metadata

For your specific needs you can start with the mla-simple-mapping-hooks-example.php.txt example in the /media-library-assistant/examples directory.

In the initialize() function, activate the mla_mapping_exif_value filter and deactivate the mla_mapping_updates filter:

add_filter( 'mla_mapping_exif_value', 'MLASimpleMappingHooksExample::mla_mapping_exif_value_filter', 10, 5 );
//add_filter( 'mla_mapping_updates', 'MLASimpleMappingHooksExample::mla_mapping_updates_filter', 10, 5 );

Then you can add code to the mla_mapping_exif_value_filter() function to return the “first directory name” to populate the attachment_category terms:

public static function mla_mapping_exif_value_filter( $exif_value, $setting_value, $post_id, $category, $attachment_metadata ) {
    if ( 'attachment_category' == $setting_value ) {
        /*
         * You can use MLAOptions::mla_get_data_source() to get anything available;
         * for example:
         */
        $my_setting = array(
            'data_source' => 'template',
            'meta_name' => '([+path+])',
            'option' => 'array'
        );
        $path = MLAOptions::mla_get_data_source($post_id, 'single_attachment_mapping', $my_setting, $attachment_metadata);
        return pathinfo( $path, PATHINFO_BASENAME );
    }

    return $exif_value;
} // mla_mapping_exif_value_filter

On my test system, the pathinfo( $path, PATHINFO_BASENAME ) function returns the directory name, removing additional directory levels and delimiters. Make sure it works on your system.

That should get you the results you want. I am marking this topic resolved, but please update it if any part of the plugin and hooks process is unclear or you need other guidance. Thanks for your interest in the plugin and for an interesting applicationn.

Thanks David for your outstanding support.

I don’t have programming experience, so I have some basic questions:

After I make the proper changes to the lm-simple-mapping-hooks-example.pht.txt I will need to rename it to have only .php extension, right?

After that, will the system execute this php file or do I need to make any other changes in the systems so this code will be executed?

On the mla_mapping_exif_value_filter() part, I found this on the original file:

public static function mla_mapping_exif_value_filter( $exif_value, $setting_value, $post_id, $category, $attachment_metadata ) {
		//error_log( 'MLASimpleMappingHooksExample::mla_mapping_exif_value_filter $exif_value = ' . var_export( $exif_value, true ), 0 );
		//error_log( 'MLASimpleMappingHooksExample::mla_mapping_exif_value_filter $setting_value = ' . var_export( $setting_value, true ), 0 );
		//error_log( 'MLASimpleMappingHooksExample::mla_mapping_exif_value_filter $post_id = ' . var_export( $post_id, true ), 0 );
		//error_log( 'MLASimpleMappingHooksExample::mla_mapping_exif_value_filter $category = ' . var_export( $category, true ), 0 );
		//error_log( 'MLASimpleMappingHooksExample::mla_mapping_exif_value_filter $attachment_metadata = ' . var_export( $attachment_metadata, true ), 0 );

		/*
		 * You can use MLAOptions::mla_get_data_source() to get anything available;
		 * for example:
		 */
		$my_setting = array(
			'data_source' => 'template',
			'meta_name' => '([+exif:Copyright+])',
			'option' => 'array'
		);
		//$copyright = MLAOptions::mla_get_data_source($post_id, $category, $my_setting, $attachment_metadata);
		//error_log( 'MLASimpleMappingHooksExample::mla_mapping_exif_value_filter $copyright = ' . var_export( $copyright, true ), 0 );

		/*
		 * For "empty" 'text' values, return ''.
		 * For "empty" 'array' values, return NULL.
		 */
		return $exif_value;
	} // mla_mapping_exif_value_filter

Since you’ve said to “Add code” to the mlc-simple-mapping-hooks-example.phpt.txt, I am understanding that I should include the following code:

if ( 'attachment_category' == $setting_value ) {
        /*
         * You can use MLAOptions::mla_get_data_source() to get anything available;
         * for example:
         */
        $my_setting = array(
            'data_source' => 'template',
            'meta_name' => '([+path+])',
            'option' => 'array'
        );
        $path = MLAOptions::mla_get_data_source($post_id, 'single_attachment_mapping', $my_setting, $attachment_metadata);
        return pathinfo( $path, PATHINFO_BASENAME );
    }

Just before the following lines on the original code:

return $exif_value;
	} // mla_mapping_exif_value_filter

Not sure if I made myself clear on this.

Regards,

Paulo

Thanks for following up and posting your progress. It gives me a chance to clarify and expand on my earlier comments.

First, you asked:

After I make the proper changes to the lm-simple-mapping-hooks-example.pht.txt I will need to rename it to have only .php extension, right?
After that, will the system execute this php file or do I need to make any other changes in the systems so this code will be executed?

To install and activate your custom plugin you need to:

• Remove the “.txt” portion of the file name (as you said).
• Save the “.php” file in your /wp-content/plugins directory so WordPress can find it as a plugin.
• Go to your Plugins/Installed Plugins admin screen and activate the plugin. Unless you changed the plugin name, it will show up as “MLA Simple Mapping Hooks Example”.

Second, my instructions regarding the “new code” were not very clear. The error_log() and “Copyright” code you found in the source file are from an earlier example. Since you don’t need that code, you can simply replace it with your new code. In other words, the entire mla_mapping_exif_value_filter() function should look like the example I listed in my earlier post. I regret the confusion.

I hope that makes sense and gives you the final pieces of the custom plugin puzzle. Thanks for your patience and persistence.