Better REST API Featured Images vs Simple Regenerate Slug

Note: You probably do not need this plugin. The REST API already supports adding the query param ?_embed to your URL and the response will then include all “embedded media”, including the featured image, and the data you get there is exactly what this plugin gives you. The only reasons to use this plugin at this point are if you prefer to have the featured image data in a top level field in the response rather than among other embedded media in the _embedded field, and if you always want the featured image data in the response rather than having to ask for it with ?_embed. I still use this plugin because I do usually want both these things, but definitely give ?_embed a try before using this plugin. 🙂 Version 2 of the WordPress REST API returns a featured_media field (formerly featured_image) on the post object by default, but this field is simply the image ID. This plugin adds a better_featured_image field to the post object that contains the available image sizes and urls, allowing you to get this information without making a second request. It takes this: "featured_media": 13, And turns it into this: "featured_media": 13, "better_featured_image": { "id": 13, "alt_text": "Hot Air Balloons", "caption": "The event featured hot air balloon rides", "description": "The hot air balloons from the big event", "media_type": "image", "media_details": { "width": 5760, "height": 3840, "file": "2015/09/balloons.jpg", "sizes": { "thumbnail": { "file": "balloons-150x150.jpg", "width": 150, "height": 150, "mime-type": "image/jpeg", "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-150x150.jpg" }, "medium": { "file": "balloons-300x200.jpg", "width": 300, "height": 200, "mime-type": "image/jpeg", "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-300x200.jpg" }, "large": { "file": "balloons-1024x683.jpg", "width": 1024, "height": 683, "mime-type": "image/jpeg", "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-1024x683.jpg" }, "post-thumbnail": { "file": "balloons-825x510.jpg", "width": 825, "height": 510, "mime-type": "image/jpeg", "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons-825x510.jpg" } }, "image_meta": { "aperture": 6.3, "credit": "", "camera": "Canon EOS 5D Mark III", "caption": "", "created_timestamp": 1433110262, "copyright": "", "focal_length": "50", "iso": "100", "shutter_speed": "0.004", "title": "", "orientation": 1 } }, "post": null, "source_url": "http://api.example.com/wp-content/uploads/2015/09/balloons.jpg" }, The format of the response is nearly identical to what you would get sending a request to /wp-json/wp/v2/media/13 or using ?_embed. When no featured image has been set on the post the better_featured_image field will have a value of null. I’ve done some basic performance tests that indicate the difference in response times with and without this plugin to be about 10-15ms for a collection of 10 posts and 0-5ms for a single post. For me this is much faster than making a second request to /media/, especially for multiple posts. As of version 1.1.0, there is a filter better_rest_api_featured_image that allows you to add custom data to the better_featured_image field. The filter is directly on the return value of the function that returns the better_featured_image field. This can be used to do things like add custom image meta or an SVG version of the image to the response. Here’s an example of how you might use it: add_filter( 'better_rest_api_featured_image', 'xxx_modify_rest_api_featured_image', 10, 2 ); /** * Modify the Better REST API Featured Image response. * * @param array $featured_image The array of image data. * @param int $image_id The image ID. * * @return array The modified image data. */ function xxx_modify_rest_api_featured_image( $featured_image, $image_id ) { // Add an extra_data_string field with a string value. $featured_image['extra_data_string'] = 'A custom value.'; // Add an extra_data_array field with an array value. $featured_image['extra_data_array'] = array( 'custom_key' => 'A custom value.', ); return $featured_image; } This plugin is on on Github and pull requests are always welcome. 🙂

Simple Regenerate Slug automatically regenerates URL slugs from post titles for WordPress posts, pages, and custom post types. The plugin now includes a comprehensive admin settings panel where you can: Key Features: * Enable/Disable Control – Turn the plugin functionality on or off with a simple checkbox * Custom Post Type Support – Select which post types should have automatic slug regeneration * Bulk Processing – Update multiple posts at once using WordPress bulk edit * Developer Friendly – Includes filter hooks for programmatic customization * Clean Admin Interface – Easy-to-use settings page with clear documentation How It Works: The plugin automatically updates the URL slug whenever you update a post title. This works for: – Published posts and pages – Custom post types (when selected) – Bulk edit operations – Individual post updates Usage Instructions: 1. Go to Settings → Simple Regenerate Slug in your WordPress admin 2. Enable the plugin using the checkbox 3. Select the post types where you want automatic slug regeneration 4. Save settings and you’re done! For bulk updates of existing posts: 1. Go to Posts (or Pages/Custom Post Types) 2. Select posts you want to update (recommend 50 at a time) 3. Choose ‘Bulk actions’ → ‘Edit’ → ‘Apply’ 4. Click ‘Update’ without making changes 5. Slugs will be automatically regenerated from titles Developer Features: The plugin includes the simpleregenerateslug_post_types filter hook that allows developers to programmatically modify which post types are affected: ```php // add_filter( 'simpleregenerateslug_post_types', function( $post_types ) { $post_types[] = 'custom_post_type'; return $post_types; } ); ``` Perfect for theme developers, custom post type plugins, and advanced WordPress customizations. Support Getting Help: If you need assistance with Simple Regenerate Slug, please: Check the FAQ section above Review the plugin settings at Settings → Simple Regenerate Slug Submit issues on our GitHub repository Bug Reports: If you believe you have found a security vulnerability or bug in Simple Regenerate Slug plugin, please let us know right away by submitting an issue on GitHub. When reporting bugs, please include: * Detailed description of the problem * Steps to reproduce the issue * Screenshot if possible * Your website URL (if relevant) * Current versions of WordPress and PHP * List of active plugins that might conflict Feature Requests: We welcome suggestions for new features! Please submit feature requests through our GitHub repository. Privacy Policy Simple Regenerate Slug does not collect, store, or transmit any personal data. The plugin only modifies post slugs locally within your WordPress database. No data is sent to external servers.