[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fd6j0xCCZ7VfYogmZXAgVgh-MBEcS0rXtntjTdZQApho":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":11,"num_ratings":11,"last_updated":13,"tested_up_to":14,"requires_at_least":15,"requires_php":16,"tags":17,"homepage":23,"download_link":24,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":27,"vulnerabilities":28,"developer":29,"crawl_stats":26,"alternatives":36,"analysis":138,"fingerprints":201},"anything-shortcodes","Anything Shortcodes","1.3.0","WPizard","https:\u002F\u002Fprofiles.wordpress.org\u002Fwpizard\u002F","\u003Cp>A powerful WordPress plugin that lets you retrieve and display virtually any data in WordPress using simple shortcodes. Effortlessly pull information from posts, users, options, and more — with support for dynamic attribute parsing, flexible formatting, and customizable output wrapping.\u003C\u002Fp>\n\u003Cp>It supports:\u003Cbr \u002F>\n– Post Field\u003Cbr \u002F>\n– Post Meta\u003Cbr \u002F>\n– Term Field\u003Cbr \u002F>\n– Term Meta (coming soon)\u003Cbr \u002F>\n– User Field\u003Cbr \u002F>\n– User Meta\u003Cbr \u002F>\n– Link\u003Cbr \u002F>\n– Option\u003Cbr \u002F>\n– Function (whitelisted)\u003C\u002Fp>\n\u003Cp>You can also:\u003Cbr \u002F>\n– Apply custom formatting (date, datetime, number, capitalize, uppercase, lowercase, strip_tags, etc.)\u003Cbr \u002F>\n– Add before\u002Fafter text\u003Cbr \u002F>\n– Use fallback values\u003Cbr \u002F>\n– Use nested shortcodes inside attributes\u003Cbr \u002F>\n– Use URL parameters as values\u003Cbr \u002F>\n– Cache output\u003Cbr \u002F>\n– Secure and sanitize output\u003C\u002Fp>\n\u003Ch3>Shortcode Usage\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>General syntax:\u003C\u002Fstrong>\u003Cbr \u002F>\n    \u003Ccode>[anys type=\"TYPE\" name=\"KEY\" id=\"ID\" before=\"TEXT\" after=\"TEXT\" fallback=\"TEXT\" format=\"FORMAT\" delimiter=\"DELIMITER\"]\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Attributes:\u003C\u002Fstrong>\u003Cbr \u002F>\n– \u003Ccode>type\u003C\u002Fcode> — \u003Ccode>post-field\u003C\u002Fcode>, \u003Ccode>post-meta\u003C\u002Fcode>, \u003Ccode>user-field\u003C\u002Fcode>, \u003Ccode>user-meta\u003C\u002Fcode>, \u003Ccode>option\u003C\u002Fcode>, \u003Ccode>function\u003C\u002Fcode> (required)\u003Cbr \u002F>\n– \u003Ccode>name\u003C\u002Fcode> — The field name, meta key, option name, or function call (required)\u003Cbr \u002F>\n– \u003Ccode>id\u003C\u002Fcode> — Post ID or User ID (optional; defaults to current context)\u003Cbr \u002F>\n– \u003Ccode>before\u003C\u002Fcode> — Text to prepend before output (optional)\u003Cbr \u002F>\n– \u003Ccode>after\u003C\u002Fcode> — Text to append after output (optional)\u003Cbr \u002F>\n– \u003Ccode>fallback\u003C\u002Fcode> — Value if empty (optional)\u003Cbr \u002F>\n– \u003Ccode>format\u003C\u002Fcode> — Output formatting type (optional: \u003Ccode>date\u003C\u002Fcode>, \u003Ccode>datetime\u003C\u002Fcode>, \u003Ccode>number\u003C\u002Fcode>, \u003Ccode>capitalize\u003C\u002Fcode>, \u003Ccode>uppercase\u003C\u002Fcode>, \u003Ccode>lowercase\u003C\u002Fcode>, \u003Ccode>strip_tags\u003C\u002Fcode>, \u003Ccode>values\u003C\u002Fcode>, \u003Ccode>keys_values\u003C\u002Fcode>, etc.)\u003Cbr \u002F>\n– \u003Ccode>delimiter\u003C\u002Fcode> — Separator used to join multiple values (optional)\u003C\u002Fp>\n\u003Ch3>Supported Types and Examples\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Post Field\u003C\u002Fstrong>\u003Cbr \u002F>\nRetrieve standard post fields by name.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"post-field\" name=\"post_title\"]\u003C\u002Fcode> — Shows the post title.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"post-field\" name=\"post_date\" format=\"date\"]\u003C\u002Fcode> — Shows the post publish date (formatted).\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"post-field\" name=\"post_author\" id=\"123\"]\u003C\u002Fcode> — Shows the author ID of post \u003Ccode>123\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"post-field\" name=\"post_content\" fallback=\"No content\"]\u003C\u002Fcode> — Shows the post content or fallback text.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Other fields supported: \u003Ccode>ID\u003C\u002Fcode>, \u003Ccode>post_name\u003C\u002Fcode>, \u003Ccode>post_excerpt\u003C\u002Fcode>, \u003Ccode>post_status\u003C\u002Fcode>, \u003Ccode>comment_status\u003C\u002Fcode>, \u003Ccode>ping_status\u003C\u002Fcode>, \u003Ccode>post_password\u003C\u002Fcode>, \u003Ccode>post_parent\u003C\u002Fcode>, \u003Ccode>menu_order\u003C\u002Fcode>, \u003Ccode>guid\u003C\u002Fcode>, \u003Ccode>post_type\u003C\u002Fcode>, \u003Ccode>post_mime_type\u003C\u002Fcode>, \u003Ccode>post_modified\u003C\u002Fcode>, \u003Ccode>post_modified_gmt\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Post Meta\u003C\u002Fstrong>\u003Cbr \u002F>\nRetrieve post meta by key.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"post-meta\" name=\"my_meta_key\"]\u003C\u002Fcode> — Shows value of \u003Ccode>my_meta_key\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"post-meta\" name=\"price\" id=\"456\" format=\"number\"]\u003C\u002Fcode> — Shows the \u003Ccode>price\u003C\u002Fcode> of post \u003Ccode>456\u003C\u002Fcode>, formatted as number.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"post-meta\" name=\"release_date\" format=\"date\"]\u003C\u002Fcode> — Shows release date formatted as date.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Term Field\u003C\u002Fstrong>\u003Cbr \u002F>\nRetrieve standard term fields by name.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"term-field\" name=\"name\"]\u003C\u002Fcode> — Shows the term name.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"term-field\" name=\"slug\"]\u003C\u002Fcode> — Shows the term slug.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"term-field\" name=\"term_id\" id=\"15\"]\u003C\u002Fcode> — Shows the ID of term \u003Ccode>15\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"term-field\" name=\"taxonomy\" id=\"15\"]\u003C\u002Fcode> — Shows the taxonomy of term \u003Ccode>15\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"term-field\" name=\"description\" fallback=\"No description\"]\u003C\u002Fcode> — Shows term description or fallback text.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"term-field\" name=\"count\" id=\"15\" format=\"number\"]\u003C\u002Fcode> — Shows the number of posts in term \u003Ccode>15\u003C\u002Fcode>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Other fields supported: \u003Ccode>term_group\u003C\u002Fcode>, \u003Ccode>parent\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>Notes:\u003Cbr \u002F>\n– If no “id” is provided, it defaults to the current queried term (e.g., category\u002Ftag archive page).\u003Cbr \u002F>\n– Supports “before”, “after”, “fallback”, and “format” (for number, date, etc.).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>User Field\u003C\u002Fstrong>\u003Cbr \u002F>\nRetrieve user standard fields.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"user-field\" name=\"user_email\" id=\"12\"]\u003C\u002Fcode> — Shows email of user \u003Ccode>12\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"user-field\" name=\"display_name\"]\u003C\u002Fcode> — Shows current user display name.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"user-field\" name=\"user_registered\" format=\"date\"]\u003C\u002Fcode> — Shows user registration date.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Common user fields: \u003Ccode>ID\u003C\u002Fcode>, \u003Ccode>user_login\u003C\u002Fcode>, \u003Ccode>user_nicename\u003C\u002Fcode>, \u003Ccode>user_url\u003C\u002Fcode>, \u003Ccode>user_activation_key\u003C\u002Fcode>, \u003Ccode>user_status\u003C\u002Fcode>, \u003Ccode>description\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>\u003Cstrong>User Meta\u003C\u002Fstrong>\u003Cbr \u002F>\nRetrieve user meta by key.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"user-meta\" name=\"favorite_color\" id=\"12\"]\u003C\u002Fcode> — Shows favorite_color of user \u003Ccode>12\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"user-meta\" name=\"profile_phone\"]\u003C\u002Fcode> — Shows current user’s phone.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Link\u003C\u002Fstrong>\u003Cbr \u002F>\nRetrieve URLs or generate link anchors for common WordPress locations.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"logout\"]\u003C\u002Fcode> — Returns the logout URL.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"logout\" redirect=\"\u002F\"]\u003C\u002Fcode> — Returns the logout URL and redirects to home after logout.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"login\" redirect=\"\u002Fdashboard\"]\u003C\u002Fcode> — Returns the login URL with redirect to \u003Ccode>\u002Fdashboard\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"register\"]\u003C\u002Fcode> — Returns the registration URL.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"home\"]\u003C\u002Fcode> — Returns the home page URL.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"siteurl\"]\u003C\u002Fcode> — Returns the main site URL.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"admin\"]\u003C\u002Fcode> — Returns the WordPress admin URL.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"profile\"]\u003C\u002Fcode> — Returns the user profile page URL.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"post\" id=\"123\"]\u003C\u002Fcode> — Returns the permalink for post with ID \u003Ccode>123\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"term\" id=\"45\"]\u003C\u002Fcode> — Returns the archive link for term with ID \u003Ccode>45\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"current\"]\u003C\u002Fcode> — Returns the current page URL.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"auth\"]\u003C\u002Fcode> — Dynamically returns the login or logout URL based on user status.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Formatting options:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"logout\" format=\"anchor\"]\u003C\u002Fcode> — Outputs a clickable link: \u003Ccode>\u003Ca href=\"...\">Logout\u003C\u002Fa>\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"auth\" format=\"anchor\"]\u003C\u002Fcode> — Dynamically shows Login or Logout link depending on user state.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"link\" name=\"auth\" format=\"anchor\" label_logged_in=\"Sign Out\" label_logged_out=\"Sign In\"]\u003C\u002Fcode> — Customizes labels for both states.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Attributes supported:\u003Cbr \u002F>\n– \u003Ccode>name\u003C\u002Fcode>: The link type (e.g., \u003Ccode>logout\u003C\u002Fcode>, \u003Ccode>login\u003C\u002Fcode>, \u003Ccode>home\u003C\u002Fcode>, \u003Ccode>admin\u003C\u002Fcode>, etc.).\u003Cbr \u002F>\n– \u003Ccode>redirect\u003C\u002Fcode>: Optional redirect URL (used for login\u002Flogout links).\u003Cbr \u002F>\n– \u003Ccode>format\u003C\u002Fcode>: Either \u003Ccode>url\u003C\u002Fcode> (default) or \u003Ccode>anchor\u003C\u002Fcode> for clickable links.\u003Cbr \u002F>\n– \u003Ccode>target\u003C\u002Fcode>: Optional anchor target (e.g., \u003Ccode>_blank\u003C\u002Fcode>).\u003Cbr \u002F>\n– \u003Ccode>label\u003C\u002Fcode>: Optional link text (default varies by type).\u003Cbr \u002F>\n– \u003Ccode>label_logged_in\u003C\u002Fcode>: Custom label when the user is logged in (used with \u003Ccode>auth\u003C\u002Fcode>).\u003Cbr \u002F>\n– \u003Ccode>label_logged_out\u003C\u002Fcode>: Custom label when the user is logged out (used with \u003Ccode>auth\u003C\u002Fcode>).\u003Cbr \u002F>\n– \u003Ccode>id\u003C\u002Fcode>: Used for post and term links.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Option\u003C\u002Fstrong>\u003Cbr \u002F>\nRetrieve WordPress option values.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"option\" name=\"blogname\"]\u003C\u002Fcode> — Shows site title.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"option\" name=\"admin_email\"]\u003C\u002Fcode> — Shows site admin email.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Function\u003C\u002Fstrong>\u003Cbr \u002F>\nExecute a whitelisted PHP function and optionally pass arguments.\u003C\u002Fp>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[anys type=\"function\" name=\"date_i18n, F j, Y\"]\u003C\u002Fcode> — Shows today’s date.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"function\" name=\"sanitize_text_field, (anys type='option' name='blogdescription')\"]\u003C\u002Fcode> — Sanitizes and shows site description.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"function\" name=\"date_i18n, F j, Y\" before=\"Today is \"]\u003C\u002Fcode> — Shows today’s date with custom prefix.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"function\" name=\"date_i18n, F j, Y\" after=\".\"]\u003C\u002Fcode> — Shows today’s date with custom suffix.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"function\" name=\"my_custom_function\" fallback=\"N\u002FA\"]\u003C\u002Fcode> — Shows output of custom function or fallback.\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"function\" name=\"my_custom_function\" format=\"capitalize\"]\u003C\u002Fcode> — Shows output of custom function and automatically capitalizes the output (e.g., “hello world” \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> “Hello World”).\u003C\u002Fli>\n\u003Cli>\u003Ccode>[anys type=\"function\" name=\"my_custom_function\" delimiter=\", \"]\u003C\u002Fcode> — Shows output of custom function. If the function returns an array, the values are joined using the given delimiter (e.g., \u003Ccode>[\"apple\", \"banana\"]\u003C\u002Fcode> \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> “apple, banana”).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Notes:\u003Cbr \u002F>\n– Only functions whitelisted in plugin settings can be executed.\u003Cbr \u002F>\n– Arguments can include other \u003Ccode>[anys]\u003C\u002Fcode> shortcodes using \u003Ccode>()\u003C\u002Fcode> instead of \u003Ccode>[]\u003C\u002Fcode>.\u003Cbr \u002F>\n– Output can be formatted or wrapped with \u003Ccode>before\u003C\u002Fcode>\u002F\u003Ccode>after\u003C\u002Fcode> content and fallback.\u003C\u002Fp>\n\u003Ch3>Dynamic Attribute Parsing\u003C\u002Fh3>\n\u003Cp>Supports dynamic placeholders inside attribute values:\u003Cbr \u002F>\n– \u003Ccode>{get:param}\u003C\u002Fcode> — gets value from $_GET[‘param’]\u003Cbr \u002F>\n– \u003Ccode>{post:param}\u003C\u002Fcode> — gets value from $_POST[‘param’]\u003Cbr \u002F>\n– \u003Ccode>{func:function_name,arg1,arg2}\u003C\u002Fcode> — calls a whitelisted PHP function\u003Cbr \u002F>\n– \u003Ccode>{shortcode:(tag)}\u003C\u002Fcode> — parses nested shortcode (use \u003Ccode>()\u003C\u002Fcode> instead of \u003Ccode>[]\u003C\u002Fcode>)\u003Cbr \u002F>\n– \u003Ccode>{const:CONSTANT_NAME}\u003C\u002Fcode> — replaces with PHP constant value\u003C\u002Fp>\n\u003Cp>Example:\u003Cbr \u002F>\n    \u003Ccode>[anys type=\"post_field\" name=\"post_title\" id=\"{get:post_id}\" before=\"Title: \"]\u003C\u002Fcode>\u003C\u002Fp>\n\u003Ch3>Formatting Options\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ccode>date\u003C\u002Fcode> — Format timestamps using WordPress date format.\u003C\u002Fli>\n\u003Cli>\u003Ccode>datetime\u003C\u002Fcode> — Format timestamps using WordPress date and time format.\u003C\u002Fli>\n\u003Cli>\u003Ccode>number\u003C\u002Fcode> — Localized number format.\u003C\u002Fli>\n\u003Cli>\u003Ccode>json\u003C\u002Fcode> — Encode value as JSON string.\u003C\u002Fli>\n\u003Cli>\u003Ccode>serialize\u003C\u002Fcode> — Serialize PHP value.\u003C\u002Fli>\n\u003Cli>\u003Ccode>unserialize\u003C\u002Fcode> — Unserialize string if serialized.\u003C\u002Fli>\n\u003Cli>\u003Ccode>print_r\u003C\u002Fcode> — Human-readable output of variable.\u003C\u002Fli>\n\u003Cli>\u003Ccode>var_export\u003C\u002Fcode> — Parsable string representation.\u003C\u002Fli>\n\u003Cli>\u003Ccode>implode\u003C\u002Fcode> — Join array values.\u003C\u002Fli>\n\u003Cli>\u003Ccode>values\u003C\u002Fcode> — Join array values only.\u003C\u002Fli>\n\u003Cli>\u003Ccode>keys\u003C\u002Fcode> — Join array keys only.\u003C\u002Fli>\n\u003Cli>\u003Ccode>keys_values\u003C\u002Fcode> — Join array key-value pairs.\u003C\u002Fli>\n\u003Cli>\u003Ccode>capitalize\u003C\u002Fcode> — Capitalize words.\u003C\u002Fli>\n\u003Cli>\u003Ccode>uppercase\u003C\u002Fcode> — Uppercase all characters.\u003C\u002Fli>\n\u003Cli>\u003Ccode>lowercase\u003C\u002Fcode> — Lowercase all characters.\u003C\u002Fli>\n\u003Cli>\u003Ccode>strip_tags\u003C\u002Fcode> — Remove HTML\u002FPHP tags.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Custom formats are supported via filters.\u003C\u002Fp>\n\u003Ch3>Hooks\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Filters\u003C\u002Fstrong>\u003Cbr \u002F>\n– \u003Ccode>anys\u002Fattributes\u003C\u002Fcode> — Filter attributes before processing.\u003Cbr \u002F>\n– \u003Ccode>anys\u002F{type}\u002Fattributes\u003C\u002Fcode> — Filter attributes dynamically by type.\u003Cbr \u002F>\n– \u003Ccode>anys\u002Foutput\u003C\u002Fcode> — Filter final output.\u003Cbr \u002F>\n– \u003Ccode>anys\u002F{type}\u002Foutput\u003C\u002Fcode> — Filter output dynamically by type.\u003Cbr \u002F>\n– \u003Ccode>anys\u002Flink\u002Fhandlers\u003C\u002Fcode> – Filter link handlers.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Actions\u003C\u002Fstrong>\u003Cbr \u002F>\n– \u003Ccode>anys\u002Foutput\u002Fbefore\u003C\u002Fcode> — Fires before output.\u003Cbr \u002F>\n– \u003Ccode>anys\u002F{type}\u002Foutput\u002Fbefore\u003C\u002Fcode> — Fires before output for specific type.\u003Cbr \u002F>\n– \u003Ccode>anys\u002F{type}\u002Fmissing\u003C\u002Fcode> — Fires when handler file missing.\u003Cbr \u002F>\n– \u003Ccode>anys\u002Foutput\u002Fafter\u003C\u002Fcode> — Fires after output.\u003Cbr \u002F>\n– \u003Ccode>anys\u002F{type}\u002Foutput\u002Fafter\u003C\u002Fcode> — Fires after output for specific type.\u003C\u002Fp>\n\u003Ch3>Security\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>All inputs sanitized using WordPress functions.\u003C\u002Fli>\n\u003Cli>Function calls restricted to whitelisted list.\u003C\u002Fli>\n\u003Cli>Outputs sanitized with \u003Ccode>wp_kses_post()\u003C\u002Fcode>.\u003C\u002Fli>\n\u003Cli>Dynamic parsing uses caching for performance.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support & Contribution\u003C\u002Fh3>\n\u003Cp>For bugs, feature requests, or contributions, open an issue or PR on the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fwpizard\u002Fanything-shortcodes\" rel=\"nofollow ugc\">plugin repository\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Thank you for using Anything Shortcodes!\u003C\u002Fp>\n","Retrieve and display any WordPress data with shortcodes — posts, users, options, and more, with flexible formatting and customization.",0,490,"","6.8.5","5.0","7.4",[18,19,20,21,22],"options","post","post-meta","shortcode","user","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fanything-shortcodes","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fanything-shortcodes.1.3.0.zip",100,null,"2026-03-15T10:48:56.248Z",[],{"slug":30,"display_name":7,"profile_url":8,"plugin_count":31,"total_installs":11,"avg_security_score":32,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},"wpizard",4,93,30,89,"2026-04-05T02:23:51.981Z",[37,61,82,102,121],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":25,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":57,"download_link":58,"security_score":59,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":60},"ultimate-fields","Ultimate Fields","3.0.2","Radoslav Georgiev","https:\u002F\u002Fprofiles.wordpress.org\u002Fradogeorgiev\u002F","\u003Cp>With Ultimate Fields you can easily create fields in the admin. Those fields can be displayed when you are editing a post or page (any post type actually) or in an options page (ex. Theme Options) anywhere in the admin.\u003C\u002Fp>\n\u003Cp>Please visit \u003Ca href=\"https:\u002F\u002Fwww.ultimate-fields.com\u002F\" rel=\"nofollow ugc\">https:\u002F\u002Fwww.ultimate-fields.com\u002F\u003C\u002Fa> for more details.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Easy to use.\u003C\u002Fli>\n\u003Cli>Various field types (listed below)\u003C\u002Fli>\n\u003Cli>Support for Post Type and Options Page as locations for fields. All locations have advanced placement rules, in order to only show them when needed.\u003C\u002Fli>\n\u003Cli>WYSIWYG Field Creation\u003C\u002Fli>\n\u003Cli>Focused on developers: A clean object-oriented API allows you to cleanly define all of your fields through code.\u003C\u002Fli>\n\u003Cli>Perfected tabs, alignment and styles\u003C\u002Fli>\n\u003Cli>Import, Export and in-theme JSON Synchronization\u003C\u002Fli>\n\u003Cli>JavaScript-based interface\u003C\u002Fli>\n\u003Cli>Unlimited field nesting with the Repeater and Complex fields\u003C\u002Fli>\n\u003Cli>Conditional Logic between fields in the same container (and ones on upper levels)\u003C\u002Fli>\n\u003Cli>REST API Support\u003C\u002Fli>\n\u003Cli>Admin Columns\u003C\u002Fli>\n\u003Cli>Integration with WordPress SEO for automatic field content ratings\u003C\u002Fli>\n\u003Cli>Clean styles: Ultimate Fields follows WordPress’ built in styles as much as possible and provides a seamless experience. It’s even fully responsive.\u003C\u002Fli>\n\u003Cli>Full-featured interface for data loading\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Fields\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Text\u003C\u002Fli>\n\u003Cli>Textarea\u003C\u002Fli>\n\u003Cli>WYSIWYG Editor\u003C\u002Fli>\n\u003Cli>Password\u003C\u002Fli>\n\u003Cli>Number\u003C\u002Fli>\n\u003Cli>Checkbox\u003C\u002Fli>\n\u003Cli>Select\u003C\u002Fli>\n\u003Cli>Multiselect\u003C\u002Fli>\n\u003Cli>Image-Select (a visual select)\u003C\u002Fli>\n\u003Cli>File\u003C\u002Fli>\n\u003Cli>Image\u003C\u002Fli>\n\u003Cli>WP Object (for selection of an object among posts, terms and users)\u003C\u002Fli>\n\u003Cli>WP Objects (for multiple objects)\u003C\u002Fli>\n\u003Cli>Link\u003C\u002Fli>\n\u003Cli>Section\u003C\u002Fli>\n\u003Cli>Tab\u003C\u002Fli>\n\u003Cli>Complex\u003C\u002Fli>\n\u003Cli>Repeater\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Repeaters\u003C\u002Fh4>\n\u003Cp>Repeaters can be used to add repeatable groups of fields. You can combine a text and a file field into a Slide group and allow the user to add as many slides as he needs. The value is saved in a single field!\u003C\u002Fp>\n\u003Cp>Additionally you can add different types of groups into a single repeater. This way the user could add both Video Slides and Image Slides through the same place.\u003C\u002Fp>\n\u003Ch4>Embedding in themes and plugins\u003C\u002Fh4>\n\u003Cp>Ultimate Fields has all the necessary logic built in. Just place it wherever you need and include ultimate-fields.php\u003C\u002Fp>\n","Easy and powerful custom fields management: Post Meta, Options Pages, Repeaters and many field types!",900,14539,20,"2018-05-15T13:59:00.000Z","4.9.29","4.9","5.4",[53,54,20,55,56],"custom-fields","meta","repeater","theme-options","https:\u002F\u002Fwww.ultimate-fields.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fultimate-fields.3.0.2.zip",85,"2026-03-15T15:16:48.613Z",{"slug":62,"name":63,"version":64,"author":65,"author_profile":66,"description":67,"short_description":68,"active_installs":69,"downloaded":70,"rating":71,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":13,"tags":76,"homepage":80,"download_link":81,"security_score":59,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":60},"custom-metadata","Custom Metadata Manager","0.7.1","Mohammad Jangda","https:\u002F\u002Fprofiles.wordpress.org\u002Fbatmoo\u002F","\u003Cp>An easy way to add custom fields to your object types (post, pages, custom post types, users) & to generate option pages.\u003C\u002Fp>\n\u003Cp>The goal of this plugin is to help you rapidly build familiar, intuitive interfaces for your users in a very WordPress-native way.\u003C\u002Fp>\n\u003Cp>The custom field panel is nice, but not quite the easiest thing for users to work with. Adding your own metaboxes and fields involves a lot of time and repetitive code that could be better used elsewhere.\u003C\u002Fp>\n\u003Cp>This plugin handles all that heavy-lifting for you behind-the-scenes, so that you can focus on more on building out and connecting your data rather than all the minor details. This single piece of code \u003Ccode>x_add_metadata_field( 'my-field-name', 'post' );\u003C\u002Fcode> generates a metabox with a text field inside it, with the necessary hooks to save the entered values.\u003C\u002Fp>\n\u003Cp>The API is similar to that used for registering custom post types and taxonomies so it should be familiar territory.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>NOTE\u003C\u002Fstrong>: The plugin now requires WordPress 3.3+ (chiefly for the wysiwyg & datepicker fields)\u003C\u002Fp>\n\u003Cp>Like what you see? Want more field types and features added? \u003Ca href=\"mailto:tech@stresslimitdesign.com\" rel=\"nofollow ugc\">Get in touch\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjkudish\u002Fcustom-metadata\" rel=\"nofollow ugc\">contribute on github\u003C\u002Fa>\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cem>See “Other Notes” section for usage information\u003C\u002Fem>\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Ch4>Object Types\u003C\u002Fh4>\n\u003Cp>The main idea behind this plugin is to have a single API to work with regardless of the object type. Currently, Custom Metadata Manager works with \u003Ccode>user\u003C\u002Fcode>, \u003Ccode>comment\u003C\u002Fcode> and any built-in or custom post types, e.g. \u003Ccode>post\u003C\u002Fcode>, \u003Ccode>page\u003C\u002Fcode>, etc.\u003C\u002Fp>\n\u003Ch4>Registering your fields\u003C\u002Fh4>\n\u003Cp>For the sake of performance (and to avoid potential race conditions), always register your custom fields in the \u003Ccode>admin_menu\u003C\u002Fcode> hook. This way your front-end doesn’t get bogged down with unnecessary processing and you can be sure that your fields will be registered safely. Here’s a code sample:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action( 'admin_menu', 'my_theme_init_custom_fields' );\n\nfunction my_theme_init_custom_fields() {\n    if( function_exists( 'x_add_metadata_field' ) && function_exists( 'x_add_metadata_group' ) ) {\n        x_add_metadata_field( 'my_field', array( 'user', 'post' ) );\n    }\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Getting the data\u003C\u002Fh4>\n\u003Cp>You can get the data as you normally would using the \u003Ccode>get_metadata\u003C\u002Fcode> function. Custom Metadata manager stores all data using the WordPress metadata APIs using the slug name you provide. That way, even if you decide to deactivate this wonderful plugin, your data is safe and accessible. For options, you can use \u003Ccode>get_option\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Cp>Example:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$value = get_metadata( 'post', get_the_ID(), 'featured', true ); \u002F\u002F Returns post metadata value for the field 'featured'\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Adding Metadata Groups\u003C\u002Fh4>\n\u003Cp>A group is essentially a metabox that groups together multiple fields. Register the group before any fields\u003C\u002Fp>\n\u003Cpre>\u003Ccode>x_add_metadata_group( $slug, $object_types, $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Parameters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$slug\u003C\u002Fcode> (string) The key under which the metadata will be stored.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$object_types\u003C\u002Fcode> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Options and Overrides\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'label' => $group_slug, \u002F\u002F Label for the group\n    'context' => 'normal', \u002F\u002F (post only)\n    'priority' => 'default', \u002F\u002F (post only)\n    'autosave' => false, \u002F\u002F (post only) Should the group be saved in autosave? NOT IMPLEMENTED YET!\n    'exclude' => '', \u002F\u002F see below for details\n    'include' => '', \u002F\u002F see below for details\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Adding Metadata Fields\u003C\u002Fh4>\n\u003Cpre>\u003Ccode>x_add_metadata_field( $slug, $object_types, $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Parameters\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>$slug\u003C\u002Fcode> (string) The key under which the metadata will be stored. For post_types, prefix the slug with an underscore (e.g. \u003Ccode>_hidden\u003C\u002Fcode>) to hide it from the the Custom Fields box.\u003C\u002Fli>\n\u003Cli>\u003Ccode>$object_types\u003C\u002Fcode> (string|array) The object types to which this field should be added. Supported: post, page, any custom post type, user, comment.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Options and Overrides\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'group' => '', \u002F\u002F The slug of group the field should be added to. This needs to be registered with x_add_metadata_group first.\n    'field_type' => 'text', \u002F\u002F The type of field; 'text', 'textarea', 'password', 'checkbox', 'radio', 'select', 'upload', 'wysiwyg', 'datepicker', 'taxonomy_select', 'taxonomy_radio'\n    'label' => '', \u002F\u002F Label for the field\n    'description' => '', \u002F\u002F Description of the field, displayed below the input\n    'values' => array(), \u002F\u002F Values for select and radio buttons. Associative array\n    'display_callback' => '', \u002F\u002F Callback to custom render the field\n    'sanitize_callback' => '', \u002F\u002F Callback to sanitize data before it's saved\n    'display_column' => false, \u002F\u002F Add the field to the columns when viewing all posts\n    'display_column_callback' => '', \u002F\u002F Callback to render output for the custom column\n    'required_cap' => '', \u002F\u002F The cap required to view and edit the field\n    'exclude' => '', \u002F\u002F see below for details\n    'include' => '', \u002F\u002F see below for details\n    'multiple' => false, \u002F\u002F true or false, can the field be duplicated with a click of a button?\n    'readonly' => false, \u002F\u002F makes the field be readonly (works with text, textarea, password, upload and datepicker fields)\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Include \u002F Exclude\u003C\u002Fh4>\n\u003Cp>You can exclude fields and groups from specific object. For example, with the following, field-1 will show up for all posts except post #123:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'exclude' => 123\n);\nx_add_metadata_field( 'field-1', 'post', $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Alternatively, you can limit (“include”) fields and groups to specific objects. The following will ”only” show group-1 to post #456:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'include' => 123\n);\nx_add_metadata_group( 'group-1', 'post', $args );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>You can pass in an array of IDs:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>$args = array(\n    'include' => array( 123, 456, 789 );\n);\n\nWith multiple object types, you can pass in an associative array:\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>$args = array(\u003Cbr \u002F>\n    ‘exclude’ => array(\u003Cbr \u002F>\n        ‘post’ => 123,\u003Cbr \u002F>\n        ‘user’ => array( 123, 456, 789 )\u003Cbr \u002F>\n    )\u003Cbr \u002F>\n);\u003C\u002Fp>\n\u003Ch4>Examples\u003C\u002Fh4>\n\u003Cp>For examples, please see the \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fjkudish\u002Fcustom-metadata\u002Fblob\u002Fmaster\u002Fcustom_metadata_examples.php\" rel=\"nofollow ugc\">custom_metadata_examples.php\u003C\u002Fa> file included with the plugin. Add a constant to your wp-config.php called \u003Ccode>CUSTOM_METADATA_MANAGER_DEBUG\u003C\u002Fcode> with a value of \u003Ccode>true\u003C\u002Fcode> to see it in action:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'CUSTOM_METADATA_MANAGER_DEBUG', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>TODOs\u003C\u002Fh4>\n\u003Cp>Stuff we have planned for the future:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Ability to clone (multiple) groups of fields\u003C\u002Fli>\n\u003Cli>Ability Pass in attributes for built-in fields (e.g. class, data-*, etc.)\u003C\u002Fli>\n\u003Cli>Additional field types (multi-select, multi-checkbox)\u003C\u002Fli>\n\u003Cli>Limit or exclude groups and fields using a custom callback\u003C\u002Fli>\n\u003Cli>Autosave support for fields on post types\u003C\u002Fli>\n\u003Cli>Client- and server-side validation support\u003C\u002Fli>\n\u003Cli>Add groups and fields to Quick Edit\u003C\u002Fli>\n\u003C\u002Ful>\n","An easy way to add custom fields to your object types (post, pages, custom post types, users)",800,16509,88,5,"2012-07-11T19:02:00.000Z","3.4.2","3.3",[62,77,20,78,79],"custom-metadata-manager-metadata","postmeta","user-meta","http:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fcustom-metadata\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcustom-metadata.0.7.1.zip",{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":25,"num_ratings":92,"last_updated":93,"tested_up_to":94,"requires_at_least":95,"requires_php":16,"tags":96,"homepage":100,"download_link":101,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":60},"metadata-viewer","Metadata Viewer","2.1.1","PluginizeLab","https:\u002F\u002Fprofiles.wordpress.org\u002Fpluginizelab\u002F","\u003Cp>The Metadata Viewer plugin displays post, user (ie. posts, pages, and custom post types, user, WooCommerce products & orders) meta keys and their values at the bottom of the post & user editing page. There is also integrated realtime search feature.\u003Cbr \u002F>\nJust install a single plugin to solve multiple purpose like to show posts, pages, custom post types & user meta.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Posts Metadata Viewer\u003C\u002Fli>\n\u003Cli>Custom Post Types Metadata Viewer\u003C\u002Fli>\n\u003Cli>Pages Metadata Viewer\u003C\u002Fli>\n\u003Cli>Users Metadata Viewer\u003C\u002Fli>\n\u003Cli>WooCommerce Products Metadata Viewer\u003C\u002Fli>\n\u003Cli>WooCommerce Orders Metadata Viewer\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Up-Comming Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Comment Metadata Viewer\u003C\u002Fli>\n\u003Cli>Term Metadata Viewer\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cp>If you find this plugin useful, consider supporting its development through a \u003Ca href=\"https:\u002F\u002Fwww.buymeacoffee.com\u002Faiarnob\" rel=\"nofollow ugc\">donation\u003C\u002Fa>.\u003C\u002Fp>\n","A plugin or theme developer can view metadata by this plugin easily.",300,2682,2,"2025-12-24T10:56:00.000Z","6.9.4","6.0.0",[97,98,99,20,79],"custom-post-type-meta","meta-viewer","metadata","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmetadata-viewer","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmetadata-viewer.2.1.1.zip",{"slug":103,"name":104,"version":105,"author":106,"author_profile":107,"description":108,"short_description":109,"active_installs":110,"downloaded":111,"rating":25,"num_ratings":112,"last_updated":113,"tested_up_to":114,"requires_at_least":115,"requires_php":13,"tags":116,"homepage":119,"download_link":120,"security_score":59,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":60},"cleanup-duplicate-meta","Cleanup Duplicate Meta","1.0.2","Tonya Mork","https:\u002F\u002Fprofiles.wordpress.org\u002Fhellofromtonya\u002F","\u003Cp>There are times when your database gets filled up with duplicate entries that you may not want.  Cleanup Duplicate Meta allows you to check for any duplicates in either the Post Meta or User Meta tables.  Then if you want to get rid of them, simply click on the Cleanup button and Cleanup Duplicate Meta deletes the duplicates leaving either the first or last meta (you select which).\u003C\u002Fp>\n\u003Cp>The interface is simple and easy to use:\u003C\u002Fp>\n\u003Col>\n\u003Cli>‘Check for Duplicates’ queries the database and then displays all the duplicates found.\u003C\u002Fli>\n\u003Cli>‘Count Duplicates’ counts all the duplicates found in the database (i.e. a total count).\u003C\u002Fli>\n\u003Cli>The ‘Cleanup’ buttons trigger a SQL query to run, which deletes each of the duplicate entries, leaving either the first or last one (per your selection) in the database.  All non-duplicates remain untouched by the plugin.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>See the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fcleanup-duplicate-meta\u002Fscreenshots\u002F\" rel=\"ugc\">screenshots tab\u003C\u002Fa> for more details.\u003C\u002Fp>\n","Cleanup Duplicate Meta gives you a tool to check for and delete duplicate Post and\u002For User Meta entries in the database tables.",200,9629,11,"2015-05-09T11:17:00.000Z","4.2.39","3.5",[117,118,54,20,79],"database-cleanup","duplicate-meta","http:\u002F\u002Fwpdevelopersclub.com\u002Fwordpress-plugins\u002Fcleanup-duplicate-meta\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcleanup-duplicate-meta.1.0.2.zip",{"slug":122,"name":123,"version":124,"author":125,"author_profile":126,"description":127,"short_description":128,"active_installs":110,"downloaded":129,"rating":130,"num_ratings":92,"last_updated":131,"tested_up_to":132,"requires_at_least":15,"requires_php":13,"tags":133,"homepage":136,"download_link":137,"security_score":25,"vuln_count":11,"unpatched_count":11,"last_vuln_date":26,"fetched_at":60},"metabase-post-user-meta-editor","Metabase – Post & User Meta Editor","0.8.1","David Towoju","https:\u002F\u002Fprofiles.wordpress.org\u002Fdavexpression\u002F","\u003Cp>This plugin shows the post meta and user meta of your website. Post meta of custom post types can also be viewed. Only admins can view this meta data.\u003C\u002Fp>\n\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FT0EXphFEcqo?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\n\u003Ch3>Post Meta\u003C\u002Fh3>\n\u003Cp>All user meta data can be viewed with this plugin (Metabase) – including custom post types. Both public and private meta keys can be viewed. Private meta keys start with the underscore prefix and are not meant to be seen in the admin.\u003C\u002Fp>\n\u003Cp>In short, any data that can be viewed with \u003Ccode>get_post_meta()\u003C\u002Fcode> can be viewed with this plugin.\u003C\u002Fp>\n\u003Cp>To view your post meta, please go to the open the post in the WP Admin and scroll down to end of the page, you will see a table titled “Meta”.\u003C\u002Fp>\n\u003Ch3>User Meta\u003C\u002Fh3>\n\u003Cp>All user meta data can be viewed\u002Fmanaged with this plugin (Metabase). Also, private and public meta keys can be viewed. Any data that can be viewed with \u003Ccode>get_user_meta()\u003C\u002Fcode> can be viewed with this plugin.\u003C\u002Fp>\n\u003Cp>To view your plugin, please got to the Users page and click to view a user. Scroll down and you will see the\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Free\u003C\u002Fli>\n\u003Cli>Stand-alone, no need to install any other plugin for this to work\u003C\u002Fli>\n\u003Cli>Delete meta data\u003C\u002Fli>\n\u003Cli>View private meta data\u003C\u002Fli>\n\u003Cli>Edit and change the values of your meta data\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Getting Started\u003C\u002Fh3>\n\u003Cp>After installing this plugin, a metabox will be added to your posts and users.\u003C\u002Fp>\n\u003Cp>You can filter the post types you want the metabox to appear in.\u003C\u002Fp>\n","Manage post meta, custom post type meta and user meta of your WordPress site.",4026,80,"2025-04-04T06:12:00.000Z","6.5.8",[54,20,134,135,79],"show-post-meta","show-user-meta","https:\u002F\u002Fpluginette.com\u002Fproduct\u002Fmetabase\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmetabase-post-user-meta-editor.0.8.1.zip",{"attackSurface":139,"codeSignals":180,"taintFlows":192,"riskAssessment":193,"analyzedAt":200},{"hooks":140,"ajaxHandlers":171,"restRoutes":172,"shortcodes":173,"cronEvents":178,"entryPointCount":179,"unprotectedCount":11},[141,147,150,154,158,163,166],{"type":142,"name":143,"callback":144,"file":145,"line":146},"action","plugins_loaded","init","anything-shortcodes.php",103,{"type":142,"name":144,"callback":148,"file":145,"line":149},"load_textdomain",104,{"type":142,"name":151,"callback":152,"file":145,"line":153},"anys\u002Finit","load_dependencies",105,{"type":142,"name":144,"callback":155,"file":156,"line":157},"register_shortcodes","includes\\register-shortcodes.php",52,{"type":142,"name":159,"callback":160,"file":161,"line":162},"admin_menu","add_settings_page","includes\\settings-page.php",51,{"type":142,"name":164,"callback":165,"file":161,"line":157},"admin_init","register_settings",{"type":167,"name":168,"callback":169,"file":161,"line":170},"filter","plugin_action_links_anything-shortcodes\u002Fanything-shortcodes.php","modify_plugin_action_links",53,[],[],[174],{"tag":175,"callback":176,"file":156,"line":177},"anys","render_shortcode",61,[],1,{"dangerousFunctions":181,"sqlUsage":182,"outputEscaping":184,"fileOperations":11,"externalRequests":11,"nonceChecks":11,"capabilityChecks":92,"bundledLibraries":191},[],{"prepared":11,"raw":11,"locations":183},[],{"escaped":185,"rawEcho":179,"locations":186},39,[187],{"file":188,"line":189,"context":190},"includes\\types\\anys\\function.php",41,"raw output",[],[],{"summary":194,"deductions":195},"The \"anything-shortcodes\" v1.3.0 plugin demonstrates a strong security posture based on the provided static analysis.  The code appears to follow best practices by utilizing prepared statements for all SQL queries and properly escaping the vast majority of its output.  Furthermore, the plugin has no recorded vulnerabilities, including CVEs, which suggests a history of secure development and maintenance.  The limited attack surface, consisting solely of one shortcode, and the absence of dangerous functions, file operations, or external HTTP requests further contribute to its positive security assessment.  The presence of capability checks is also a good sign of access control implementation.",[196,198],{"reason":197,"points":72},"No Nonce Checks on Entry Points",{"reason":199,"points":92},"Minimal Output Escaping (98%)","2026-03-17T05:58:58.548Z",{"wat":202,"direct":211},{"assetPaths":203,"generatorPatterns":206,"scriptPaths":207,"versionParams":208},[204,205],"\u002Fwp-content\u002Fplugins\u002Fanything-shortcodes\u002Fassets\u002Fcss\u002Fanything-shortcodes.css","\u002Fwp-content\u002Fplugins\u002Fanything-shortcodes\u002Fassets\u002Fjs\u002Fanything-shortcodes.js",[],[205],[209,210],"anything-shortcodes\u002Fassets\u002Fcss\u002Fanything-shortcodes.css?ver=","anything-shortcodes\u002Fassets\u002Fjs\u002Fanything-shortcodes.js?ver=",{"cssClasses":212,"htmlComments":213,"htmlAttributes":214,"restEndpoints":215,"jsGlobals":216,"shortcodeOutput":217},[],[],[],[],[],[218],"[anys type=\"\" name=\"\" id=\"\" before=\"\" after=\"\" fallback=\"\" format=\"\" delimiter=\"\"]"]