[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fuEiLy4gaj4waUvrIodfI06xPdJGGIW0dVluYarO8SWA":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"swinggraphics","https:\u002F\u002Fprofiles.wordpress.org\u002Fswinggraphics\u002F",3,1310,92,30,88,"2026-04-04T06:31:52.089Z",[13,38,53],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":19,"downloaded":20,"rating":21,"num_ratings":22,"last_updated":23,"tested_up_to":24,"requires_at_least":25,"requires_php":26,"tags":27,"homepage":33,"download_link":34,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"hotlink-file-prevention","Hotlink File Prevention","2.0.0","\u003Cp>Hotlink File Prevention (HFP) offers simple hotlink protection that can be turned on\u002Foff for individual files in the WordPress media library.\u003C\u002Fp>\n\u003Cp>“Hotlinking” is when a file, such as an image or PDF, is linked to from another website or entered manually in a web browser’s location bar. HFP only allows your file to be viewed on your website.\u003C\u002Fp>\n\u003Cp>Hotlink protection is provided via \u003Ccode>.htaccess\u003C\u002Fcode> rules in the \u003Ccode>wp-content\u002Fuploads\u003C\u002Fcode> directory.\u003C\u002Fp>\n\u003Ch3>Basic Usage\u003C\u002Fh3>\n\u003Cp>Once the HFP plugin is activated, you will have two new features in the media library:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Within the Screen Options tab (list view only), check box for the “Hotlink Prevention” column.\u003C\u002Fli>\n\u003Cli>To protect a file, edit the file and scroll down to the checkbox labelled “Hotlink Protection”.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Any asset that is checked will have “Yes” displayed in the “Hotlink Prevention” column; otherwise, this column will be blank.\u003C\u002Fp>\n\u003Ch4>Note about “Open in new tab” option\u003C\u002Fh4>\n\u003Cp>When you use the “Open in new tab” option for links, WordPress adds \u003Ccode>rel=\"noreferrer\"\u003C\u002Fcode>, which effectively makes the link act like direct access, and the link will be blocked for files protected using HFP.\u003C\u002Fp>\n","Simple hotlink protection for individual files in the media library.",700,7815,98,7,"2024-04-15T22:00:00.000Z","6.5.8","4.6","5.6",[28,29,30,31,32],"admin","attachments","files","hotlink","images","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhotlink-file-prevention.2.0.0.zip",0,null,"2026-03-15T15:16:48.613Z",{"slug":39,"name":40,"version":41,"author":4,"author_profile":5,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":24,"requires_at_least":49,"requires_php":33,"tags":50,"homepage":33,"download_link":52,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"delete-unscaled-images","Delete Unscaled Images","1.2.4","\u003Cp>WordPress 5.3 added \u003Ca href=\"https:\u002F\u002Fmake.wordpress.org\u002Fcore\u002F2019\u002F10\u002F09\u002Fintroducing-handling-of-big-images-in-wordpress-5-3\u002F\" rel=\"nofollow ugc\">“big image handling”\u003C\u002Fa> that scales uploaded images to a maximum size of 2560 pixels for use on the website. WP adds “-scaled” to the full size image file name. The original, unscaled images are kept on the server. This can mean that many large images are stored on the server that aren’t ever actually going to be displayed on the website. In my case, users are uploading 15MB files from their cameras.\u003C\u002Fp>\n\u003Cp>After the scaled version and intermediate\u002Fthumbnail images are generated, the originals are no longer needed and just taking up storage space. \u003Cem>Delete Unscaled Images\u003C\u002Fem> will remove those unneeded files.\u003C\u002Fp>\n\u003Cp>First, original images are deleted immediately after the resized versions are created for all new uploads.\u003C\u002Fp>\n\u003Cp>Second, there is a bulk deletion tool in the Media submenu to process existing images.\u003C\u002Fp>\n","Deletes original image files if they have been resized",600,3529,100,5,"2024-04-15T21:59:00.000Z","5.3",[32,51],"media-uploader","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdelete-unscaled-images.1.2.4.zip",{"slug":54,"name":55,"version":56,"author":4,"author_profile":5,"description":57,"short_description":58,"active_installs":59,"downloaded":60,"rating":61,"num_ratings":62,"last_updated":63,"tested_up_to":24,"requires_at_least":64,"requires_php":33,"tags":65,"homepage":69,"download_link":70,"security_score":8,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"priority-shortcodes","Priority Shortcodes","2.0.2","\u003Cp>\u003Cem>Intended for use with the Classic Editor plugin.\u003C\u002Fem>\u003C\u002Fp>\n\u003Cp>Ever get annoyed or frustrated by the way TinyMCE+wpautop+do_shortcode wreak havoc on your shortcodes, wrapping \u003Ccode>\u003Cp>\u003C\u002Fcode>s around \u003Ccode>\u003Cdiv>\u003C\u002Fcode>s, leaving orphan \u003Ccode>\u003C\u002Fp>\u003C\u002Fcode>s, and all sorts of craziness? This plugin allows you to specify shortcodes to be processed before those other actions, generating the clean code you expected.\u003C\u002Fp>\n\u003Cp>Priority Shortcodes works by adding an action to \u003Ccode>the_content\u003C\u002Fcode> and \u003Ccode>widget_text\u003C\u002Fcode> hooks with a higher priority than \u003Ccode>wpautop\u003C\u002Fcode> and \u003Ccode>do_shortcode\u003C\u002Fcode>. The result is that those other actions run your shortcode’s final output, rather than trying to guess if it should be wrapped in \u003Ccode>\u003Cp>\u003C\u002Fcode> tags, etc.\u003C\u002Fp>\n\u003Cp>The \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FShortcode_API#Output\" rel=\"nofollow ugc\">Codex says\u003C\u002Fa>:\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>wpautop recognizes shortcode syntax and will attempt not to wrap p or br tags around shortcodes that stand alone on a line by themselves. Shortcodes intended for use in this manner should ensure that the output is wrapped in an appropriate block tag such as \u003Ccode>\u003Cp>\u003C\u002Fcode> or \u003Ccode>\u003Cdiv>\u003C\u002Fcode>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>But sometimes shortcodes stand on their own on a line, wanting desperately to be wrapped in a paragraph tag, and sometimes they don’t. Like a shortcode that generates a \u003Ccode>\u003Cspan>\u003C\u002Fcode> tag with some classes. \u003Cem>(Yeah, you might want to use \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FTinyMCE_Custom_Styles\" rel=\"nofollow ugc\">custom TinyMCE styles\u003C\u002Fa> instead for a simple span.)\u003C\u002Fem>\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Where you want to process a shortcode with priority, use “[!” at the start. For example: \u003Ccode>[my-shortcode]\u003C\u002Fcode> becomes \u003Ccode>[!my-shortcode]\u003C\u002Fcode> and \u003Ccode>[my-shortcode]Some content.[\u002Fmy-shortcode]\u003C\u002Fcode> becomes \u003Ccode>[!my-shortcode]Some content.[\u002Fmy-shortcode]\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch4>Gutenberg\u003C\u002Fh4>\n\u003Cp>Users of the new WordPress editor, “Gutenberg”, will probably not use Priority Shortcodes within the new editor, but the plugin continues to work in the Classic Editor.\u003C\u002Fp>\n","Processes specific shortcodes before wpautop() and do_shortcode()",10,1884,20,1,"2024-04-15T22:19:00.000Z","2.5.0",[66,67,68],"classic-editor","shortcodes","tinymce","https:\u002F\u002Fgithub.com\u002Fswinggraphics\u002FPriority-Shortcodes","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fpriority-shortcodes.zip"]