Martin von Berg

Extend the REST-API to work with WordPress Media-Library. Organize images in Folders. Add and Update images including Metadata and Posts using the images. Access with Authorization only. 
This plugin extends the REST-API of WordPress to directly access the Media-Library for Images. It is intended to be used together with a Lightroom Plugin or as a stand-alone interface for headless WordPress. The new REST-API endpoints (functions) allow to add additional metadata to images, update existing metadata or update images completely without changing the WordPress-ID. Images may be added to the standard directory hierarchy of wordpress or to an additional folder which allows better organization and searching for images.
<h3>Authorization</h3>
With this plugin ALL requests to the REST-API of wordpress require an authorization method in the https-header. It is no longer possible to even read data via the REST-API. There are different authorization methods:
<ol>
<li>
Use your WP-Admin Username and Password + username + Basic-Auth 
This function is not provided by this plugin. There are plugins that allow Basic-Auth. It works fine with https. Never use it together with http. Your administrator username and password will be submitted to the internet.
</li>
<li>
Use WP REST application password + Basic auth 
This works only with wordpress 5.6+ and may be used together with Basic-Auth. The setting is only provided if your website runs with https. So, use it only together with https (see above). I prefer this method and recommend to update to at least WP 5.6. There is a setting to use this method together with http, but this is not recommended. 
Process:
<ul>
<li>Login to your wordpress-site </li>
<li>Go to Admin-Panel > User > Profile</li>
<li>Scroll down to “Application Passwords”</li>
<li>Provide a useful name for the application in the field underneath</li>
<li>Click the button “add new application password”</li>
<li>The new password will be shown. Copy it immediately and store it! It won’t be shown again. Remove the spaces from the password.</li>
<li>Use the username of the admin and the new generated password in the https-header to access to wordpress </li>
</ul>
</li>
<li>
OAuth2 
Use existing plugins for the OAuth2 process. Best security compared to the other methods but very complicated to implement on the application side.
</li>
</ol>
<h3>Usage (detailed list of endpoints and REST-API-fields)</h3>
<ol>
<li>REST-API-fields 
The additional fields are available with the standard REST-API Endpoint: https://www.example.com/wp-json/wp/v2/media</li>
</ol>
1.1 Field ‘gallery’ 
This field may be used to organize images in galleries. The wordpress standard Media-Library does not provide a sorting scheme to organize images in galleries or topics. So -provided the gallery-plugin supports it- this is a simple way to organize images. Together with the plugin ‘AdvancedCustomFields’ it is possible to search for this field (or others).
1.2 Field ‘gallery_sort’ 
This field may be used for custom sorting of images shown in an image-slider or gallery. Only Integer values are allowed. Only useable with a plugin that supports this. 
See for instance: https://github.com/MartinvonBerg/Fotorama-Leaflet-Elevation.
1.3 Field ‘md5_original_file’ 
This is an array that provides the MD5-hash-value (checksum) and the file size of the original image file. This data is used for the update process to check prior to the upload whether an image was changed or not. It’s intention is to reduce network load during update process.
1.4 Example JSON-snippet of the REST-API output for the above mentioned fields
“gallery”: “Albums”, 
“gallery_sort”: “16”, 
“md5_original_file”: { 
 “MD5”: “FCB639BB8191716A829F7B007056945B”, 
 “size”: 509168 
},
How to get this: Open you browser and type https://www.your-domain.whatever/wp-json/wp/v2/media. Use Firefox to get a formatted output of the response. You have to be logged in to get the response.
1.5 How to write the fields: 
Writing the fields is only possible with authorization. So, check the ‘authorization’ section before. This may be tested with ‘postman’, a great software for testing http(s)-requests.
Example https-request with POST-method: 
https://www.your-domain.whatever/wp-json/wp/v2/media/666?gallery=test-gallery
New functionality behind this request 
A POST-request with ‘alt_text’ and / or ‘caption’ will change the content of ALL posts using that image. The ‘alt_text’ and the ‘caption’ are updated if they are used in 
gutenberg blocks ‘image’, ‘gallery’ and ‘media-with-text’. Note: There are many, many other blocks, images, galleries around. For these I couldn’t realize the update of ‘alt-text’ and ‘caption’.
New Parameter for the above POST-request 
Add ?docaption=true to the http request and update ALL captions in the content, too. The ‘alt_text’ is always changed in the content, because IMO there could be only one alt_text for an image. 
But, the caption may depend on the context, so it is up to the user, to change it automatically for all posts or not.
Mind: It is NOT required to use quotes around the value (here: test-gallery). If you use quotes, they will be used as part of the string in the field gallery.
1.6 Note on REST-API output 
It is possible to reduce the REST-API output to dedicated fields. This is much better for overview and reducing net-load. 
Example: 
The https GET-Request 
‘https://example.com/wp-json/wp/v2/media/?_fields=id,gallery’ 
provides this response:
[ 
 { 
 “id”: 5013, 
 “gallery”: “Albums4” 
 }, 
 { 
 “id”: 5012, 
 “gallery”: “Albums4” 
 }, 
 { 
 “id”: 5011, 
 “gallery”: “Foto_Albums/Albums3” 
 }, 
 { 
 “id”: 4932, 
 “gallery”: “Foto_Albums/Franken-Dennenlohe” 
 }, 
 { 
 “id”: 4930, 
 “gallery”: “Foto_Albums/Franken-Dennenlohe” 
 }, 
 { 
 “id”: 4929, 
 “gallery”: “Foto_Albums/Franken-Dennenlohe” 
 }, 
 { 
 “id”: 4928, 
 “gallery”: “Foto_Albums/Franken-Dennenlohe” 
 }, 
 { 
 “id”: 4927, 
 “gallery”: “Foto_Albums/Franken-Dennenlohe” 
 }, 
 { 
 “id”: 4926, 
 “gallery”: “Foto_Albums/Franken-Dennenlohe” 
 }, 
 { 
 “id”: 4925, 
 “gallery”: “Foto_Albums/Franken-Dennenlohe” 
 } 
]
<ol>
<li>New REST-API-Endpoints (aka functions)</li>
</ol>
2.1 extmedialib/v1/update/(?P[\d]+) 
Function to update images. Only integer values will be accepted for the ‘id’.
2.1.1 GET-method to extmedialib/v1/update/(?P[\d]+) 
This function is just there for completeness. It provides some information for an existing image. The response to a GET-method to …/wp-json/extmedialib/v1/update/ is the following:
<pre><code>{
"message": "You requested update of original Image with ID 5013 with GET-Method. Please update with POST-Method.",
"original-file": "C:\\Bitnami\\wordpress-5.2.2-0\\apps\\wordpress\\htdocs/wp-content/uploads/Albums4/Friaul_2019_10-169_DxO.jpg",
"md5_original_file": "01CE0E6A16954C87586E9BF16044FDA0",
"max_upload_size": "41943040 bytes"
}
</code></pre>
If the given wordpress-id does not exist it returns with http status-code 404.
2.1.2 POST-method to extmedialib/v1/update/(?P[\d]+) 
This function updates the complete image including metadata. The given wordpress-id remains unchanged. Only the image-files that belong to that wordpress-id will be updated. All image sub-sizes will be regenerated. All metadata will be updated according to the EXIF-data in the provided image. To complete the update process it is required to set the fields ‘title’, ‘caption’, ‘alt_text’ and ‘description’ with the standard REST-API-methods (see above). The function ‘update_meta’ is included.
Note on image resizing: WordPress sets the standard resize quality to 82%. A setting of 100% was tested but with that the image-files were rather big. 
The setting may be changed in the PHP-code only. Up to now there is now administration panel for the settings of this plugin. A programatical setting was added for that in version 0.0.18.
Note on image size: WordPress scales all images with pixel length (long side) greater than 2560 pixels down to this size. The bigger images will be stored in the ../uploads-directory but NOT used for the wordpress pages. So, it is not useful to upload images bigger than 2560 pixels. This may be changed by setting the ‘big_image_size_threshold’ by a dedicated hook. This is out of scope of this plugin.
Header for POST-method 
To define the content-type the following fields have to be added to the header: 
 {field=’Content-Disposition’, value=’form-data; filename=<newfile.jpg>’ }, 
 {field=’Content-Type’, value=’image/jpeg’}, 
 OR 
 {field=’Content-Type’, value=’image/webp’},
Body for POST-method 
The new Webp- or JPG-file has to be provided in the body as binary string. Checks in mime-type and size are done to prevent the user from uploading wrong data.
New Parameter for the POST-request 
Add ‘?changemime=true to the http request and update the file with one that does have another mime-type.
2.2 extmedialib/v1/update_meta/(?P[\d]+) 
Function to update metadata of images. Only integer values will be accepted for the id.
2.2.1 GET-method to extmedialib/v1/update_meta/(?P[\d]+) 
This function is just there for completeness. 
The response to a GET-method to ‘…/wp-json/extmedialib/v1/update_meta/wordpress-id’ is not executed. It may be used to check whether the image with the given wordpress-id is available. The response provides the http-status-code 405, if so. This could be done with a standard REST-request, too.
2.2.2 POST-method to extmedialib/v1/update_meta/(?P[\d]+) 
This function updates the metadata of an existing image. It does not access the metadata that may be easily changed with the standard REST-API methods of wordpress (see there). It is only done if the ‘wordpress-id’ is a valid image and was added to the media-library before. For Jpegs it does NOT change ‘aperture, camera, created_timestamp, focal_length, iso, shutter_speed and orientation’. It is not very useful to change this data for an existing jpg-image. As the data is NOT set by WP for webp-images it is possible to add this data for Webp-Images now. The update or addition is done with a valid JSON-body and the respective settings in the http-header.
Header for POST-method 
To define the content-type the following fields have to be added to the header: 
 {field=’Content-Type’, value=’application/json’}
Example Body for POST-method 
 The JSON has to be formatted like that: 
 { 
 “image_meta”: { 
 “credit”: “Martin von Berg”, 
 “caption”: “Test-caption”, 
 “copyright”: “Copyright by Martin von Berg”, 
 “title”: “Auffahrt zum Vallone d`Urtier”, 
 “keywords”: [ 
 “Aosta”, 
 “Aostatal”, 
 “Berge”, 
 “Bike”, 
 “Italien”, 
 “Sommer”, 
 “Wald”, 
 “Wiese”, 
 “forest”, 
 “italy”, 
 “lärche”, 
 “meadow”, 
 “mountains”, 
 “summer” 
 ] 
 } 
 }
All fields that are provided in the JSON will be changed. Empty fields will reset the content to an empty string “”.
2.3 extmedialib/v1/addtofolder/(?P[a-zA-Z0-9\/\-_]*) 
This function stores images aside the wordpress standard folders but make them available in the media-library by generating a new wordpress-id. The ‘folder’ must not contain other characters than a-z, A-Z, 0-9, _ and -.
2.3.1 GET-method to extmedialib/v1/addtofolder/(?P[a-zA-Z0-9\/\-_]*) 
This function is just there for completeness and simple checking. The response to a GET-method to ‘…/wp-json/extmedialib/v1/addtofolder/foldername’ simply gives the information whether the folder already exists or not.
2.3.2 POST-method to extmedialib/v1/addtofolder/(?P[a-zA-Z0-9\/\-_]*) 
With the POST-method an image will be added to the given folder and with a new wordpress id. The response provides the new id and some basic information about the added image file.
Header for POST-method 
To define the content-type the following fields have to be added to the header: 
 {field=’Content-Disposition’, value=’form-data; filename='<newfile.jpg> }, 
 {field=’Content-Type’, value=’image/jpeg’}, 
 OR 
 {field=’Content-Type’, value=’image/webp’},
Body for POST-method 
The new JPG-file has to be provided in the body as binary string. Checks for mime-type and size are done to prevent the user from uploading wrong images.
2.4 extmedialib/v1/addfromfolder/(?P[a-zA-Z0-9\/\-_]*) 
This function adds already uploaded images to the media-library. This is useful for images that were uploaded with ftp before. The ‘folder’ must not contain other characters than a-z, A-Z, 0-9, _ and -.
2.4.1 GET-method to extmedialib/v1/addfromfolder/(?P[a-zA-Z0-9\/\-_]*) 
This method gives information about the folder content. If existing and not empty the folder content will be provided as an array. The array provides now the id’s and original-files that are already in the media-library.
2.4.2 POST-method to extmedialib/v1/addfromfolder/(?P[a-zA-Z0-9\/\-_]*) 
With the POST-method all images from the given ‘folder’ will be added to the media-library. Image-Files that were already added before from THAT dedicated folder will be skipped. The response contains an JSON-array with IDs to be stored in the application (e.g. Lightroom) for later access. Mind that this might be a long running process. If it runs too long it will be stopped by the server and the addition is NOT complete. So, the recommendation is to do this step by step, e.g. 10 images maximum per step.
<ol>
<li>Tests</li>
</ol>
3.0 Linting with phpstan 
Code quality was checked with phpstan and WP extensions ‘szepeviktor/phpstan-wordpress’ and ‘phpstan/extension-installer’. 
Level 5 is OK except 19 remaining Errors. These were carefully reviewed and regarded as OK. 
Command: php .\vendor\phpstan\phpstan\phpstan analyse classes inc .\wp_wpcat_json_rest.php –memory-limit 1G
3.1. Unit-Tests 
Meaningful Unit-Tests are now done with PHPUnit. The files are located in ./tests.
3.2. Integration Test 
Well, IMO this is mainly the (de-)installation procedure for the plugins. Tested manually. Works
3.3 System Test 
The plugin is now ‘completely’ system tested with a new python test suite (PTS). The PTS uses pytest and a bunch of other python modules that have to be installed in the Python environment. 
I tried to reach a ‘branch coverage’ of 100% concerning the functional branches. It’s almost impossible to test the paths that were implemented for very special 
errors on the server (domain of unit tests). The testdata contains *.webp and *.jpg files with different sizes. The use cases are ‘upload image file’, ‘change metadata’, ‘change mime type’, 
‘update image file’, ‘create posts (Gutenberg: image, gallery, image-with-text )’ and ‘delete’. Tests were conducted on a local and remote site. Additionally I 
checked the results of query monitor for every REST-request that uses a function from me. No PHP-errors at all. So, all tests passed. I could not 
claim a code coverage of 100% or even a test coverage of 100%. That is almost impossible.
3.3.1 How to repeat the system test 
– Install an empty, new WP site 
– Install this plugin 
– Install Query Monitor plugin 
– Clone the complete code from github to your local site 
– change the directory to the …./test directory in the cloned repository 
– provide a wp_site.json as described in ./test/test_rest-api.py 
– run the basic tests with: pytest -k ‘basic’ 
– The first run wil fail for one test if the required ‘testfolder’ did not exist on the server. 
– Once more: run the basic tests with: pytest -k ‘basic’. should be 100% PASSED now. 
– Check your WP-testsite and delete the generated image(s) 
– run the full test with: pytest -k ‘testimage or testfield or testpost or cleanup’ 
– check the testreport.html after the test 
– OR 
– run the full test and stop it after the post generation with 
– pytest -k ‘testimage or testfield or testpost or cleanup or testwait’ -s 
– check visually that all posts with image, gallery, image-with-text have flipped images (except one with changed mime-type) 
– continue the test with Enter to delete all generated images, posts etc. from WordPress 
– OR run 
– pytest -k ‘testimage or testfield or testpost’ –> here you have to delete all generated images, posts etc. from WordPress manually 
– NOTE: Sometimes the test_clean_up() function does not delete all files in the ./testfolder on the server. Don’t know why. 
– So it is better to check that folder ./testfolder is really empty if the test fails. 
– Finally, all tests should be PASSED and GREEN.
<h3>Credits</h3>
This plugin uses the great work from:
<ul>
<li>wordpress for coding hints: https://de.wordpress.org/</li>
<li>authorization hints: https://developer.wordpress.org/rest-api/frequently-asked-questions/</li>
<li>Enable Media Replacer: https://de.wordpress.org/plugins/enable-media-replace/ I’m using two classes of this great plugin to handle the link updates.</li>
<li>PHPunit and BrainMonkey for Testing.</li>
</ul>

wp_wpcat_json_rest

Extend the REST-API to work with Wordpress Media-Library. Organize images in Folders. Add and Update images including Metadata and Posts using the ima …

REST API Featured Image is a lightweight yet powerful plugin that simplifies how to retrieve featured images via the WordPress REST API. By introducing a top-level field called <code>featured_media_src_url</code>, this plugin embeds the direct URL of the featured image into your REST API responses. This eliminates the need for additional API calls to fetch featured images, resulting in faster load times and enhanced site performance.
Key Features:
– Direct Access to Featured Image URL: Adds <code>featured_media_src_url</code> to REST API responses, providing immediate access to the featured image URL. 
– Performance Optimization: Reduces the number of API requests, improving the speed and efficiency of your applications. 
– Custom Post Type Support: Fully supports custom post types, allowing you to enable or disable the featured image URL field for specific post types through the admin settings. 
– User-Friendly Configuration: Easy to install and configure without any coding.
Why Use REST API Featured Image?
When developing applications or themes that rely on the WordPress REST API, accessing the featured image typically requires an additional request for each post. This can be time-consuming and may negatively impact site performance. REST API Featured Image addresses this issue by including the featured image URL directly in the REST API response, saving you time and resources.
REST API Featured Image Field:
– <code>featured_media_src_url</code>

REST API Featured Image

Enhance your WordPress REST API by adding a featured image URL field directly to API responses, improving performance by eliminating extra requests.

wp_wpcat_json_rest vs REST API Featured Image