Fixes the rule preview on the settings screen, removes -br- from the browser tab title and from new post addresses, and names the default choice in the post editor.<\/p>","4.4.4":"
The ASB family card links to the plugin's WordPress.org page. Nothing else changes.<\/p>","4.4.3":"
Hardens output escaping in the title, featured-image and feed filters. Recommended for all users.<\/p>","4.4.2":"
Security and reliability release: images can only be drawn from your Media Library and the plugin's own files, custom font upload works again, and unexpected input no longer causes fatal errors. Recommended for all users.<\/p>","4.4.0":"
Adds hooks for other plugins (generate now, change the drawing config, know when an image is done). Nothing changes on your site unless another plugin uses them.<\/p>","4.3.0":"
Fixes per-post sidebar settings not being saved, and auto-generation not running when switched on in the same save as publishing. Images the plugin generated are now refreshed when the title or design changes; images you chose are never replaced.<\/p>","4.1.0":"
Adds optional WebP and AVIF copies for faster pages. Off by default; the featured image itself is unchanged. Safe to update.<\/p>","4.0.0":"
The Pro version is gone and all of its features are now part of this free plugin. Nothing to buy, no key to enter. Your existing settings are kept.<\/p>","3.1.7":"
Important update with security fixes and major performance improvements. Auto-generation now works when publishing from Gutenberg. Recommended for all users.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3794463,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3794463,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3794463,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3794463,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["4.4.3","4.4.4","4.4.5"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3794463,"resolution":"1","location":"assets","locale":"","width":1440,"height":1050},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3794463,"resolution":"2","location":"assets","locale":"","width":1440,"height":1050},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3794463,"resolution":"3","location":"assets","locale":"","width":1440,"height":1050},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3794463,"resolution":"4","location":"assets","locale":"","width":1200,"height":630}},"screenshots":{"1":"Main settings screen with live preview","2":"Layout settings tab","3":"Individual settings panel in the Gutenberg sidebar","4":"Example of a generated featured image"}},"plugin_section":[],"plugin_tags":[1795,52195,26918,2894,1540],"plugin_category":[],"plugin_contributors":[276744],"plugin_business_model":[],"class_list":["post-393817","plugin","type-plugin","status-publish","hentry","plugin_tags-featured-image","plugin_tags-image-generator","plugin_tags-ogp","plugin_tags-post-thumbnail","plugin_tags-social-sharing","plugin_contributors-asobit","plugin_committers-asobit"],"banners":{"banner":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/banner-772x250.png?rev=3794463","banner_2x":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/banner-1544x500.png?rev=3794463","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/icon-128x128.png?rev=3794463","icon_2x":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/icon-256x256.png?rev=3794463","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/screenshot-1.png?rev=3794463","caption":"Main settings screen with live preview"},{"src":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/screenshot-2.png?rev=3794463","caption":"Layout settings tab"},{"src":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/screenshot-3.png?rev=3794463","caption":"Individual settings panel in the Gutenberg sidebar"},{"src":"https:\/\/ps.w.org\/asb-post-thumbnail\/assets\/screenshot-4.png?rev=3794463","caption":"Example of a generated featured image"}],"raw_content":"\n
ASB Post Thumbnail automatically generates a featured image for each post by combining the post title, categories, author name or any custom text with a design template. Images are generated when a post is saved, so every article gets a polished OGP image for social sharing \u2014 no design work required.<\/p>\n\n
Everything below is included \u2014 there is no paid edition.<\/p>\n\n
The plugin connects to one third-party service, and only when an administrator asks it to.<\/p>\n\n
The settings screen offers a few optional Japanese fonts (listed under \"Credits\" below). When an administrator clicks \"Download\" next to one of them, your server downloads that font file from a fixed address on fonts.gstatic.com and saves it in the uploads folder, so the font can be used for generated images. Nothing is requested before the button is clicked, and nothing is requested again afterwards.<\/p>\n\n
What is sent: an ordinary download request for that one file. Like any request WordPress makes, it carries your server's IP address and your site's address (WordPress's standard User-Agent header). No post content, no user data and no visitor data are sent. Generated images are made on your own server and are never uploaded anywhere.<\/p>\n\n
Terms of service: https:\/\/developers.google.com\/fonts\/terms\nPrivacy policy: https:\/\/policies.google.com\/privacy<\/p>\n\n
This plugin ships with a compiled JavaScript bundle for the block-editor sidebar\nUI: The human-readable source is included in this plugin<\/strong>, under To rebuild, run No third-party analytics, tracking or obfuscation is applied to the bundle.<\/p>\n\n Yes. When the Imagick PHP extension is not available, the plugin automatically falls back to the GD library. ImageMagick renders text with higher quality, so we recommend it when available.<\/p><\/dd>\n \"Disable auto-generation for posts that already have a featured image\" is enabled by default, so a featured image you chose yourself is never replaced by auto-generation.<\/p><\/dd>\n Yes. Type Yes, as lightweight copies used for display. Turn on \"Lightweight Display Copies\" on the settings screen and the plugin writes a WebP (and, if you choose, an AVIF) next to each generated image and serves them through a The featured image itself deliberately stays a JPEG. og:image, RSS feeds, e-mail and notification plugins all read that one file, and several of them cannot read AVIF \u2014 a site can look faster and still have blank social cards. Browsers that cannot read the copy fall back to the JPEG automatically; no JavaScript and no browser detection is involved.<\/p>\n\n The settings screen reports what your server can actually encode. It does not take the PHP extension's word for it: it encodes a small test image and inspects the result, because some builds of GD advertise AVIF support and then produce nothing.<\/p><\/dd>\n Then leave this setting off. A caching or optimization plugin that already builds and serves modern formats does the same job for every image on the site, not just the generated ones, and running both simply writes the same picture twice.<\/p><\/dd>\n Copies are written at generation time. Images that already exist get theirs the next time they are regenerated \u2014 for example by opening the post and using \"Generate & Set Now\" in the editor sidebar.<\/p><\/dd>\n JPEG, PNG, GIF and WebP images from your Media Library, and the images bundled with the plugin. AVIF is used only when the server's image library (Imagick, or GD on PHP 8.1 and later) can read it, and HEIC files that WordPress did not convert to JPEG are not used. An image that cannot be drawn is skipped and the next background is used instead.<\/p><\/dd>\n Posts, pages and any public custom post type. Choose them on the settings screen.<\/p><\/dd>\n Yes. Deleting the plugin removes its settings, post meta, preview images, and the fonts you uploaded or downloaded through it. Featured images that were already generated and stored in your media library are kept.<\/p><\/dd>\n The interface is in English and fully prepared for translation. Translations are provided through translate.wordpress.org, and WordPress installs them automatically for your site's language. Contributions are welcome there.<\/p><\/dd>\n Only when you ask it to. The one outbound request is the optional font download from Google Fonts, made when an administrator clicks \"Download\" next to a font. Nothing is sent anywhere otherwise. See \"External services\" below.<\/p><\/dd>\n\n<\/dl>\n\n\n Fixed\n* Settings screen: while editing an override rule, the live preview drew fields left empty (meaning \"use the default\") as 0 \u2014 for example with a font size of 0. Empty fields now follow the default in the preview too, just as they already did in the generated image.\n* \"Remove -br- from post titles\" now also removes the marker from the browser tab title (the title tag, including titles set by SEO plugins) and from the web address WordPress makes from the title when a post is first published. Web addresses that are already set, or that you typed yourself, are not changed.\n* Post editor: the \"(Follow default: \u2026)\" choice showed the setting's internal value (such as \"stack\" or \"title\"). It now shows the same name as the choices below it.<\/p>\n\n Changed\n* The ASB family card now also links to the shop page of ASB Connect for LINE, now that its Pro version is on sale.<\/p>\n\n Changed\n* The ASB family card in the sidebar now links to this plugin's page on WordPress.org and invites a review, now that the plugin is listed there.<\/p>\n\n Security\n* A title changed by \"Remove -br- from post titles\" is passed through wp_kses_post() before it is returned. Titles the plugin does not change are left exactly as WordPress gives them.\n* The Security\n* Backgrounds and image layers can only use the plugin's own bundled images and Media Library images that the user is allowed to view \u2014 whether they are chosen on the settings screen, in the post editor or by another plugin. Other files on the server can no longer be drawn into a generated image, and an image attached to a private post can no longer end up in a public featured image.\n* Font settings accept only a font file name from the plugin's font folders.\n* Only users who can change the main settings can preview unsaved site-wide settings, and \"Generate & Set Now\" also needs permission to upload files.\n* Per-post settings are no longer shown in the public REST API. The editor receives only the settings it uses, and the rule search lists only posts the user can read.\n* A value sent in an unexpected form (such as an array) no longer causes a fatal error on saving or previewing; it falls back to its default.\n* The Permissions tab accepts only the four listed capabilities. An invalid saved value is reset to its default (Administrator for the main settings, Contributor and above for per-post settings), so nobody can be locked out of the settings.\n* File names, image addresses and search terms are inserted on the settings screen as plain text, and only .ttf and .otf files can be deleted from the font list.<\/p>\n\n Fixed\n* English and other space-separated text was broken in the middle of a word at the end of a line (\"title fo \/ r preview\"). Words now move to the next line whole; Japanese line breaking is unchanged.\n* Choosing a layout template stopped with a script error (\"Maximum call stack size exceeded\") caused by the colour pickers, and the preview was then labelled \"New Rule\".\n* The colour pickers of a newly added rule did not open until the settings were saved and the page reloaded.\n* When a background image could not be drawn, the featured image came out with a plain white background. The plugin now moves on to the next image \u2014 the per-post background, then the rule's, then the site's, and finally the bundled default \u2014 so the preview and the generated image always match.\n* \"Sequence\" backgrounds keep the same picture for every post that already had one, and the editor preview shows the right picture for each post.\n* AVIF images work as backgrounds and image layers wherever the server's image library can read them, and images WordPress converted from HEIC to JPEG are drawn.\n* The image, display size and padding chosen for an image layer in the post editor were lost when the post was saved, so automatic generation ignored them.\n* An image layer set in a rule by its address alone showed the default layer image instead.\n* On the very first save, every checkbox (and each rule's \"Disable auto-generation\") could switch itself on.\n* Uploading a custom .ttf or .otf font always failed with \"Sorry, you are not allowed to upload this file type.\" It now also works on servers whose file-type detection does not recognise fonts, and Japanese font file names keep all their characters.\n* Deleting a font that was already gone gave no message.\n* A font download that was cut off stayed marked \"Installed\". Downloads are now checked before they are kept, a damaged file can be downloaded again, and the listed font sizes are accurate.\n* Saving the settings removed the bundled default background image.\n* \"Settings saved.\" and the font upload and delete messages never appeared on the settings screen.\n* Pressing Enter in a field could ask to delete an added font.\n* Titles and names were drawn with HTML entities (for example \"\u2026\" or \"&\"), private and protected posts got a \"Private:\" or \"Protected:\" prefix, and \"-br-\" line breaks were ignored when the image was made in the background.\n* Adding a password to a post now regenerates its featured image, so text drawn before the password was set does not stay on it.\n* Regenerating an image no longer deletes the old one when another post uses it as its featured image.\n* The settings screen failed on servers without GLOB_BRACE (Alpine and other musl-based systems).\n* On servers that do not allow \"Options\" in .htaccess, the plugin's upload folders could answer with a 500 error. Existing .htaccess files are updated.\n* Deprecation notices from imagedestroy() and finfo_close() on PHP 8.5.<\/p>\n\n Changed\n* build\/index.js<\/code>, build\/index.css<\/code> and build\/index-rtl.css<\/code>. These are\ngenerated from React\/JSX source using the standard WordPress build toolchain\n(@wordpress\/scripts<\/code>, i.e. webpack under the hood).<\/p>\n\neditor-src\/<\/code>:<\/p>\n\n\n
editor-src\/src\/index.js<\/code> \u2014 the React\/JSX source of the sidebar panel<\/li>\neditor-src\/src\/index.scss<\/code> \u2014 its styles<\/li>\neditor-src\/package.json<\/code> \u2014 build scripts and the single dev dependency<\/li>\neditor-src\/babel.config.js<\/code> \u2014 the Babel settings used by the build<\/li>\neditor-src\/package-lock.json<\/code> \u2014 the exact dependency tree<\/li>\neditor-src\/README.md<\/code> \u2014 build instructions and a note on the shipped bundle<\/li>\n<\/ul>\n\nnpm install<\/code> then npm run build<\/code> inside editor-src\/<\/code>\n(development watch build: npm start<\/code>), and copy the resulting build\/<\/code> files\nover the plugin's own build\/<\/code> directory.<\/p>\n\nCredits<\/h3>\n\n
\n
vendor\/select2\/<\/code> together with its unminified files (select2.js<\/code>, select2.css<\/code>): https:\/\/select2.org\/ \u2014 source: https:\/\/github.com\/select2\/select2\/tree\/4.1.0<\/li>\n\n
\n
Does it work on servers without ImageMagick?<\/h3><\/dt>\n
What happens to posts that already have a featured image?<\/h3><\/dt>\n
Can I control where the title wraps inside the image?<\/h3><\/dt>\n
-br-<\/code> in the post title where you want the line to break in the generated image (for example, Big product announcement-br-here is what changed<\/code>). The marker is removed automatically when the title is displayed on your site, from the browser tab title, and from the web address that WordPress makes from the title when the post is published (addresses that are already set are not changed).<\/p><\/dd>\nCan it generate WebP or AVIF?<\/h3><\/dt>\n
<picture><\/code> element.<\/p>\n\nI already use a plugin that converts images to WebP<\/h3><\/dt>\n
My existing featured images have no WebP or AVIF copies<\/h3><\/dt>\n
Which image formats can be used as backgrounds and image layers?<\/h3><\/dt>\n
Which post types are supported?<\/h3><\/dt>\n
Does uninstalling remove my data?<\/h3><\/dt>\n
Is the plugin translated?<\/h3><\/dt>\n
Does the plugin call any external services?<\/h3><\/dt>\n
4.4.5<\/h4>\n\n
4.4.4<\/h4>\n\n
4.4.3<\/h4>\n\n
<picture><\/code> element for the WebP \/ AVIF display copies is filtered through wp_kses() before it is returned, keeping the image's srcset and sizes.\n* The featured image added to RSS and Atom feeds is escaped value by value where it is printed.\n* On saving a post, the classic editor's request to replace the featured image is accepted only with that post's edit nonce.<\/p>\n\n4.4.2<\/h4>\n\n
asbptp_generate_for_post()<\/code> no longer replaces a featured image chosen by hand while \"Disable auto-generation for posts that already have a featured image\" is on. Pass array( 'replace' => true )<\/code> to replace it.\n* On servers without Imagick, text outlines are limited to 20px and drawn within a time budget, so very long text can no longer tie up the server. WebP images now work as backgrounds and image layers there too.\n* The settings screen no longer prints inline style blocks; all of its styles are in the plugin's stylesheet.\n* Every global name now uses the plugin's own prefix. The admin-menu grouping helper is now asbptp_family_group_admin_menu()<\/code>.\n* The \"View on WordPress.org\" link and the review card appear once the plugin is listed there.\n* The bundled Select2 is updated to 4.1.0, and its unminified files are included.\n* The protective files in the plugin's upload folders are written with the WordPress filesystem API, and the plugin no longer clears PHP's opcode cache itself (WordPress does this when it updates a plugin).\n* Removed leftover references to the former Pro edition from comments, styles and the font license notice.<\/p>\n\n4.4.1<\/h4>\n\n
\n
4.4.0<\/h4>\n\n
\n
asbptp_generate_for_post( $post_id )<\/code> makes the featured image right away with the site's settings and returns the attachment ID (or a WP_Error). It respects the per-post switch, the enabled post types and the rules, and also works for drafts.<\/li>\nasbptp_generation_config<\/code> filter changes what is drawn \u2014 for example a background picture chosen for this post, or a shorter title with -br-<\/code> line breaks. Saving, the background job, the preview and the \"is the image still current\" check all read through it.<\/li>\nasbptp_thumbnail_generated<\/code> action fires after a featured image has been generated and set, with the post ID and the attachment ID.<\/li>\n4.3.0<\/h4>\n\n
\n
save_post<\/code>, which the block editor fires before it writes the post's meta and categories, so the switch still read as off. Generation now waits for wp_after_insert_post<\/code>, after everything from that save is stored.<\/li>\n4.2.0<\/h4>\n\n
\n
add_filter( 'asbptp_feed_featured_image', '__return_false' )<\/code> turns it off.<\/li>\n<\/ul>\n\n4.1.0<\/h4>\n\n
\n
<picture><\/code> element. Browsers that cannot read them fall back to the JPEG on their own. On a 1200 x 630 image the WebP is typically about a quarter of the JPEG, and the AVIF about a tenth.<\/li>\n4.0.3<\/h4>\n\n
\n
4.0.2<\/h4>\n\n
\n
4.0.1<\/h4>\n\n
\n
4.0.0<\/h4>\n\n
\n
3.5.9<\/h4>\n\n
\n
3.5.3<\/h4>\n\n
\n
3.1.7<\/h4>\n\n
\n
3.0.3<\/h4>\n\n
\n