[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fOZkXcZ6Sd4cE3tWNKrHHaI3Tj4UdIWLF3EOnDHyN8Wg":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},"wescleveland","https:\u002F\u002Fprofiles.wordpress.org\u002Fwescleveland\u002F",4,240,87,30,85,"2026-04-05T09:32:48.643Z",[13,38,59,75],{"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":26,"download_link":33,"security_score":34,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"wp247-body-classes","WP247 Body Classes","2.2.0","\u003Cp>Add unique classes to the body tag for easy styling based on post attributes (post type, slug, and ID) and various WordPress “is” functions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>wp_is_mobile()\u003C\u002Fli>\n\u003Cli>is_home()\u003C\u002Fli>\n\u003Cli>is_front_page()\u003C\u002Fli>\n\u003Cli>is_blog()\u003C\u002Fli>\n\u003Cli>is_admin()\u003C\u002Fli>\n\u003Cli>is_admin_bar_showing()\u003C\u002Fli>\n\u003Cli>is_404()\u003C\u002Fli>\n\u003Cli>is_super_admin()\u003C\u002Fli>\n\u003Cli>is_user_logged_in()\u003C\u002Fli>\n\u003Cli>is_search()\u003C\u002Fli>\n\u003Cli>is_archive()\u003C\u002Fli>\n\u003Cli>is_author()\u003C\u002Fli>\n\u003Cli>is_category()\u003C\u002Fli>\n\u003Cli>is_tag()\u003C\u002Fli>\n\u003Cli>is_tax()\u003C\u002Fli>\n\u003Cli>is_date()\u003C\u002Fli>\n\u003Cli>is_year()\u003C\u002Fli>\n\u003Cli>is_month()\u003C\u002Fli>\n\u003Cli>is_day()\u003C\u002Fli>\n\u003Cli>is_time()\u003C\u002Fli>\n\u003Cli>is_single()\u003C\u002Fli>\n\u003Cli>is_sticky()\u003C\u002Fli>\n\u003Cli>$post->post_type\u003C\u002Fli>\n\u003Cli>$post->name\u003C\u002Fli>\n\u003Cli>$post->ID\u003C\u002Fli>\n\u003Cli>wp_get_post_categories() (Page\u002FPost Categories)\u003C\u002Fli>\n\u003Cli>wp_get_post_tags()       (Page\u002FPost Tags)\u003C\u002Fli>\n\u003Cli>$user->nicename\u003C\u002Fli>\n\u003Cli>$user->id\u003C\u002Fli>\n\u003Cli>$user->roles\u003C\u002Fli>\n\u003Cli>$user->allcaps\u003C\u002Fli>\n\u003Cli>$archive->slug (e.g. Category slug, Tag slug, etc.)\u003C\u002Fli>\n\u003Cli>$archive->id   (e.g. Category id, Tag id, etc.)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Add post specific classes to the body tag in the post editor. Use any class name you want to uniquely style an individual post or a set of posts.\u003C\u002Fp>\n\u003Cp>Add classes based on user scrolling through the page. You can check things like:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>is-scroll-top        (at the top of the page – synonym for is-not-scroll)\u003C\u002Fli>\n\u003Cli>is-not-scroll-top    (not at the top of the page – synonym for is-scroll)\u003C\u002Fli>\n\u003Cli>is-scroll            (not at the top of the page – synonym for is-not-scroll-top)\u003C\u002Fli>\n\u003Cli>is-not-scroll        (at the top of the page – synonym for is-scroll-top)\u003C\u002Fli>\n\u003Cli>is-scroll-top-px     (has not reached the scroll start value for scroll measurement by pixels)\u003C\u002Fli>\n\u003Cli>is-scroll-top-vh     (has not reached the scroll start value for scroll measurement by viewport height)\u003C\u002Fli>\n\u003Cli>is-scroll-top-dh     (has not reached the scroll start value for scroll measurement by document height)\u003C\u002Fli>\n\u003Cli>is-scroll-10-px      (scrolled down 10 pixels)\u003C\u002Fli>\n\u003Cli>is-scroll-8-vh       (scrolled down 8% of the viewport height)\u003C\u002Fli>\n\u003Cli>is-scroll-5-dh       (scrolled down 5% of the document height)\u003C\u002Fli>\n\u003Cli>is-scroll-mid-px     (has reached the scroll start value but not the scroll limit for scroll measurement by pixels)\u003C\u002Fli>\n\u003Cli>is-scroll-mid-vh     (has reached the scroll start value but not the scroll limit for scroll measurement by viewport height)\u003C\u002Fli>\n\u003Cli>is-scroll-mid-vh     (has reached the scroll start value but not the scroll limit for scroll measurement by document height)\u003C\u002Fli>\n\u003Cli>is-scroll-max-px     (has reached the scroll limit for scroll measurement by pixels)\u003C\u002Fli>\n\u003Cli>is-scroll-max-vh     (has reached the scroll limit for scroll measurement by percent of viewport height)\u003C\u002Fli>\n\u003Cli>is-scroll-max-dh     (has reached the scroll limit for scroll measurement by percent of document height)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Add classes based on the results from mobiledetect.net’s \u003Cstrong>Mobile_Detect\u003C\u002Fstrong> script. This script parses the value passed by the browser in the HTTP_USER_AGENT string. Consequently, mobile detection is more of an art than a science and, unfortunately, is not perfect. You can check things like:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>is-mobile\u003C\u002Fli>\n\u003Cli>is-tablet\u003C\u002Fli>\n\u003Cli>is-phone\u003C\u002Fli>\n\u003Cli>Mobile Operating System\u003C\u002Fli>\n\u003Cli>Mobile Browser\u003C\u002Fli>\n\u003Cli>Type of tablet\u003C\u002Fli>\n\u003Cli>Type of phone\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This plugin adds classes to the html body tag indicating:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>whether or not the requesting device is a mobile device (.is-mobile or .is-not-mobile)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>the type of post being viewed (.is-? where ? is the post type (page, post, whetever special post types are defined) ).\u003Cbr \u002F>\n E.g. .is-page or .is-post\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>the slug of the post being viewed (.is-?-! where ? is the post type and ! is the post slug).\u003Cbr \u002F>\n E.g. a post with slug “hello-world’ would have class .is-post-hello-world\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>the ID of the post being viewed (.is-?-# where ? is the post type and # is the post ID).\u003Cbr \u002F>\n E.g. a post with ID “1” would have class .is-page-1\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>whether or not the requested page shows archived results (.is-archive or .is-not-archive)\u003C\u002Fp>\n\u003Cp>If the page being displayed is an archive\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>the type of archive being viewed (.is-? where ? represents the type of archive (author, category, date, tag) )\u003Cbr \u002F>\nE.g. .is-author\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>the slug of the archive being viewed (.is-?-! where ? is the archive type and ! is the archive slug)\u003Cbr \u002F>\nE.g. a category with slug “uncategorized’ would have class .is-category-uncategorized\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>the ID of the archive being viewed (.is-?-# where ? is the archive type and # is the archive ID)\u003Cbr \u002F>\nE.g. a category with ID “1” would have class .is-category-1\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>How far down the page the viewer has scrolled in pixels or as a percentage of viewport height or as a percentage of document height\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Post specific class(es) that are set in the post editor\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Use these classes in your styling to provide a better browsing experience for your viewers.\u003C\u002Fp>\n\u003Ch4>Custom Body Classes\u003C\u002Fh4>\n\u003Cp>Create your own Custom Body Classes by adding your PHP code in the “Custom Body Classes” section.\u003C\u002Fp>\n\u003Cp>Here’s an example. Not sure why we would want to do it, but suppose we want to do some custom styling when the page is being displayed to someone that can manage WordPress options. We might enter something like:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>if (current_user_can('manage_options')) $classes[] = 'user-can-manage-options';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Then we can use the \u003Cstrong>body.user-can-manage-options\u003C\u002Fstrong> qualifier in our CSS styling.\u003C\u002Fp>\n\u003Ch4>Example\u003C\u002Fh4>\n\u003Cp>Suppose you have a large h1 top margin that you want to eliminate on mobile devices to avoid a lot of white space. After activating the wp247-body-classes plugin and indicating that the .is-mobile class is desired, all you need to do is add this line to your CSS:\u003C\u002Fp>\n\u003Cp>body.is-mobile h1 {\u003Cbr \u002F>\n    margin-top: 0;\u003Cbr \u002F>\n}\u003C\u002Fp>\n\u003Cp>Suppose you have a sticky header but want to shrink it by dynamically reducing the top and bottom padding from 25px to 5px as the viewer scrolls down the page based on 20 pixel scroll increments up to 80 pixels of scrolling:\u003C\u002Fp>\n\u003Cp>Set WP247 Body Classes Scroll setting to “Scroll by Pixel” with a 10 pixel increment and an 80 pixel limit and then add the following to your CSS:\u003C\u002Fp>\n\u003Cp>body.is-scroll-20-px header {\u003Cbr \u002F>\n    padding-top: 20px;\u003Cbr \u002F>\n    padding-bottom: 20px;\u003Cbr \u002F>\n}\u003Cbr \u002F>\nbody.is-scroll-40-px header {\u003Cbr \u002F>\n    padding-top: 15px;\u003Cbr \u002F>\n    padding-bottom: 15px;\u003Cbr \u002F>\n}\u003Cbr \u002F>\nbody.is-scroll-60-px header {\u003Cbr \u002F>\n    padding-top: 10px;\u003Cbr \u002F>\n    padding-bottom: 10px;\u003Cbr \u002F>\n}\u003Cbr \u002F>\nbody.is-scroll-max-px header {\u003Cbr \u002F>\n    padding-top: 5px;\u003Cbr \u002F>\n    padding-bottom: 5px;\u003Cbr \u002F>\n}\u003C\u002Fp>\n","Add unique classes to the body tag for easy styling based on various attributes (archive, user, post, mobile, scrolling) and WordPress \"is\"  …",200,7558,90,6,"2024-05-24T16:06:00.000Z","6.5.8","4.0","",[28,29,30,31,32],"mobile","post-type","scroll","user-capabilities","user-roles","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp247-body-classes.2.2.0.zip",92,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":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":26,"download_link":58,"security_score":10,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"wp247-generatepress-pre-footer-widgets","WP247 GeneratePress Pre-Footer Widgets","1.0","\u003Cp>Add a Pre-Footer Widgets area  to the GeneratePress theme that is similar to the GeneratePress Footer Widgets area but appears immediately before the Footer Widgets on the page. It works just like the GeneratePress footer widgets and can be styled the same way as the GeneratePress footer widgets in the WordPress Theme Customizer. In addition, if you have GeneratePress Premium installed, the WP247 GeneratePress Pre-Footer Widgets plugin will provide additional Customization options for the Pre-Footer section.\u003C\u002Fp>\n","Add Pre-Footer Widgets to the GeneratePress theme",20,1765,100,1,"2017-12-18T18:39:00.000Z","4.9.29","4","5.6.31",[53,54,55,56,57],"before-footer","footer","generatepress","pre-footer","widgets","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp247-generatepress-pre-footer-widgets.1.0.zip",{"slug":60,"name":61,"version":62,"author":4,"author_profile":5,"description":63,"short_description":64,"active_installs":65,"downloaded":66,"rating":35,"num_ratings":35,"last_updated":67,"tested_up_to":49,"requires_at_least":25,"requires_php":51,"tags":68,"homepage":26,"download_link":74,"security_score":10,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"wp247-extension-notification-client","WP247 Extension Notification Client","1.0.1","\u003Ch4>OVERVIEW\u003C\u002Fh4>\n\u003Cp>The strength of WordPress is in it’s ability to be customized through the use of extensions (plugins and themes).\u003C\u002Fp>\n\u003Cp>The \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> provides a standard interface for WordPress extension developers to communicate important information about their extension to their extension users.\u003C\u002Fp>\n\u003Cp>The \u003Cem>Settings\u003C\u002Fem> page provides you with complete control over which extensions the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> will communicate with and which notices will continue to be displayed.\u003C\u002Fp>\n\u003Ch4>NOTICES\u003C\u002Fh4>\n\u003Cp>The \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> will display notices until they are dismissed. The extension developer assigns one of three dismissibility types to each notice they send:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>None\u003C\u002Fstrong> indicates that the notice is not dismissible. The \u003Cem>dismiss\u003C\u002Fem> button will not appear.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Temporary\u003C\u002Fstrong> indicates that the notice will be temporarily dismissed when you click the \u003Cem>dismiss\u003C\u002Fem> button. Once dismissed, the notice will not appear until the next time the Admin page is refreshed.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Permanent\u003C\u002Fstrong> indicates that the notice will be permanently dismissed when you click the \u003Cem>dismiss\u003C\u002Fem> button. Once dismissed, the notice will not appear again.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Regardless of the dimissibility setting chosen by the extension developer, you can permanently dismiss any notice by clicking the \u003Cem>Permanently Dismiss\u003C\u002Fem> link at the lower right of the notice or by checking the checkbox next to the notice title in the \u003Cstrong>WP247 Extension Notification Client\u003C\u002Fstrong>‘s \u003Cem>Settings\u003C\u002Fem> section.\u003C\u002Fp>\n\u003Ch4>SETTINGS\u003C\u002Fh4>\n\u003Cp>Use the \u003Cem>Settings\u003C\u002Fem> page to control how the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> operates on your site.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Site-wide Extension Notifications\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Checking the \u003Cem>Disable Extension Notifications for the entire site\u003C\u002Fem> checkbox will stop the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> from checking for new notices and from displaying any notices that have not been dismissed.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>New Extensions\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>As a security measure, by default, new extensions are disabled from using the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong>. You may opt-in to allowing new extensions to be enabled to use the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> at the time they are activated by checking the \u003Cem>Automatically enable Extension Notifications for new extensions when they are activated\u003C\u002Fem> checkbox. Otherwise, each individual extension may be enabled or disabled as you choose by unchecking or checking the \u003Cem>Disable extension notifications for\u003C\u002Fem>… checkbox within the individual extension’s settings.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Individual Extension Notifications\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Each plugin or theme that uses the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> is listed in the \u003Cem>Individual Extension Notifications\u003C\u002Fem> section. For each extension you can:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Immediately cease the periodic checking for new notices, and discontinue displaying any notices that have not already been dismissed by checking the \u003Cem>Disable extension notifications for\u003C\u002Fem>… checkbox.\u003C\u002Fli>\n\u003Cli>View the extension’s status by clicking the \u003Cem>Status\u003C\u002Fem> link under the extension name.\u003C\u002Fli>\n\u003Cli>Refresh the extension’s notices by clicking the \u003Cem>Refresh\u003C\u002Fem> link under the extension name. This will result in the deletion of all notices and then calling the extension’s server to retrieve any outstanding notices if the extension is enabled to use the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Reset the extension by clicking the \u003Cem>Reset\u003C\u002Fem> link under the extension name. This will result in the deletion of the extension from within the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong>‘s settings. The extension will then be re-added using default settings and, if the \u003Cem>Automatically enable Extension Notifications for new extensions when they are activated\u003C\u002Fem> checkbox is checked, the extension will be re-enabled to use the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Change the frequency that periodic checking for new notices will be performed by entering a new value in the box under the \u003Cem>Override how often to check for new notices\u003C\u002Fem> label. You can enter values like:\n\u003Cul>\n\u003Cli>“8 hours” to check once every 8 hours\u003C\u002Fli>\n\u003Cli>“2 days” to check once every other day\u003C\u002Fli>\n\u003Cli>“1 week” to check once each week\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>Permanently dismiss individual notices that have not already been dismissed by checking the checkbox next to the notice title.\u003C\u002Fli>\n\u003Cli>View individual notices by clicking the \u003Cem>View Notice\u003C\u002Fem> link under the notice title.\u003C\u002Fli>\n\u003Cli>Refresh all extensions’ notices by clicking the \u003Cem>Refresh All\u003C\u002Fem> button. This will result in the deletion of all notices for all extensions and then calling all extensions’ servers to retrieve any outstanding notices for those extensions that are enabled to use the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Reset all extensions by clicking the \u003Cem>Reset All\u003C\u002Fem> button. This will result in the deletion of all extensions from within the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong>‘s settings. The extensions will then be re-added using default settings and, if the \u003Cem>Automatically enable Extension Notifications for new extensions when they are activated\u003C\u002Fem> checkbox is checked, the extensions will be re-enabled to use the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>PRIVACY POLICY\u003C\u002Fh4>\n\u003Cp>Occasionally, the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> will contact participating extension’s servers in order to see if they have any new notices for your review. The only data sent to their server is the ID of their extension, and the last time we contacted their server. As an example, the \u003Cstrong>WP247 Extension Notification Client\u003C\u002Fstrong>‘s extension id is \u003Cem>wp247-extension-notification-client\u003C\u002Fem>.\u003C\u002Fp>\n\u003Cp>Rest assured that the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> does not capture any information about your site and does not send any information about your site when servers are polled for new notices.\u003C\u002Fp>\n\u003Cp>In addition, you can control which extensions that use the \u003Cstrong>WP247 Extension Notification System\u003C\u002Fstrong> may or may not be enabled to participate in issuing you notices.\u003C\u002Fp>\n","Provides the ability for WordPress extension developers to send notification messages to their users",10,1331,"2017-12-14T21:54:00.000Z",[69,70,71,72,73],"extension","message","notice","notification","theme","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp247-extension-notification-client.1.0.1.zip",{"slug":76,"name":77,"version":78,"author":4,"author_profile":5,"description":79,"short_description":80,"active_installs":65,"downloaded":81,"rating":35,"num_ratings":35,"last_updated":82,"tested_up_to":83,"requires_at_least":25,"requires_php":26,"tags":84,"homepage":26,"download_link":88,"security_score":10,"vuln_count":35,"unpatched_count":35,"last_vuln_date":36,"fetched_at":37},"wp247-get-option-shortcode","WP247 Get Option Shortcode","1.2","\u003Cp>Include WordPress options anywhere shortcodes are accepted.\u003C\u002Fp>\n\u003Ch4>Syntax\u003C\u002Fh4>\n\u003Cp>[wp247_get_option option=”\u003Cstrong>desired-option\u003C\u002Fstrong>” default=”\u003Cstrong>desired-default\u003C\u002Fstrong>” scope=”\u003Cstrong>desired-scope\u003C\u002Fstrong>“]\u003C\u002Fp>\n\u003Cp>where:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>desired-option\u003C\u002Fstrong> is the option to be retrieved from the WordPress wp_options table. Default: none\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>desired-default\u003C\u002Fstrong> is the default value to be returned if the desired option does not exist. Default: “”\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>desired-scope\u003C\u002Fstrong> indicates which type of option is to be retrieved. \u003Cstrong>scope=”site”\u003C\u002Fstrong> will retrieve options using the WordPress \u003Cstrong>get_site_option\u003C\u002Fstrong> function. All other values are ignored and the WordPress \u003Cstrong>get_option\u003C\u002Fstrong> function will be used to retrieve the desired \u003Cstrong>option\u003C\u002Fstrong> value. Default: “”\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cp>Include the WordPress site URL in some text somewhere:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>This is my site’s URL: [wp247_get_option option=”siteurl”].\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Set up a copyright notice in a footer widget:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Copyright © \u003Ca href=\"[wp247_get_option option='siteurl']\" rel=\"nofollow ugc\">[wp247_get_option option=’blogname’]\u003C\u002Fa>. All rights reserved.\u003C\u002Fli>\n\u003C\u002Ful>\n","Include WordPress options anywhere shortcodes are accepted.",1447,"2021-08-08T17:35:00.000Z","5.8.13",[85,86,87],"get_option","options","shortcode","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp247-get-option-shortcode.1.2.zip"]