{"id":349524,"date":"2026-08-11T14:11:18","date_gmt":"2026-08-11T14:11:18","guid":{"rendered":"https:\/\/ko.wordpress.org\/plugins\/aj-form\/"},"modified":"2026-08-11T14:10:55","modified_gmt":"2026-08-11T14:10:55","slug":"ajebang-form-survey-builder","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/ajebang-form-survey-builder\/","author":23543174,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.9.1","stable_tag":"1.9.1","tested":"7.0.3","requires":"5.8","requires_php":"7.4","requires_plugins":null,"header_name":"Ajebang Form and Survey Builder","header_author":"ajebang","header_description":"Build forms and surveys with a drag-and-drop builder, show aggregated results, set deadlines, and place them anywhere with shortcodes.","assets_banners_color":"","last_updated":"2026-08-11 14:10:55","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/ajebang.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":21,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.9.1":{"tag":"1.9.1","author":"ajebang","date":"2026-08-11 14:10:55"}},"upgrade_notice":{"1.8.6":"<p>Fixes choice display counts silently failing to save. Upgrade if you use that option.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.9.1"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[361,2253,2254,80,364],"plugin_category":[42,43,53],"plugin_contributors":[275207],"plugin_business_model":[],"class_list":["post-349524","plugin","type-plugin","status-publish","hentry","plugin_tags-form","plugin_tags-form-builder","plugin_tags-poll","plugin_tags-shortcode","plugin_tags-survey","plugin_category-contact-forms","plugin_category-customization","plugin_category-ratings-and-reviews","plugin_contributors-ajebang","plugin_committers-ajebang"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/ajebang-form-survey-builder.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"<!--section=description-->\n<p>Ajebang Form and Survey Builder is a lightweight form and survey builder. You create a form in the admin\narea by dragging fields into place, then publish it with a shortcode or share the\nstandalone link the plugin generates for it. Visitors can respond without logging\nin or creating an account.<\/p>\n\n<p>Every form is one of two types:<\/p>\n\n<ul>\n<li><strong>Form<\/strong> \u2014 collects responses. Administrators see the number of submissions but\nnot the content of individual answers.<\/li>\n<li><strong>Survey<\/strong> \u2014 collects responses and shows aggregated statistics: the count and\npercentage for each choice, averages for number fields, and so on. Visitors see\nthe results after they respond.<\/li>\n<\/ul>\n\n<h4>Features<\/h4>\n\n<ul>\n<li>Drag-and-drop builder with eight field types: text, textarea, email, number,\ndropdown, radio, checkbox and date<\/li>\n<li>Draft and published states. A new form starts as a draft, so nothing appears on\nyour site until you are ready<\/li>\n<li>Response deadline. Forms accept answers indefinitely by default. After the\ndeadline the server refuses new submissions and shows a closing notice; surveys\ncan keep displaying their results<\/li>\n<li>Featured image, shown above the form and as the thumbnail in listings<\/li>\n<li>Related links, listed underneath the form<\/li>\n<li>Standalone page for every form at an address such as <code>\/aj-form\/survey\/12\/<\/code>, so\nyou can share a link without embedding a shortcode anywhere<\/li>\n<li>Repeat-response limiting per form, by browser cookie or by cookie and IP address<\/li>\n<li>Submission modes: a submit button, automatic submission once every field is\nfilled, or per-question submission where answering one question immediately\nturns that question into its result<\/li>\n<li>Works without JavaScript. Submissions use AJAX when they can and fall back to a\nnormal form post when they cannot<\/li>\n<li>Translation ready. Every string is internationalised, so translations arrive\nthrough translate.wordpress.org in any language the community contributes<\/li>\n<\/ul>\n\n<h4>Shortcodes<\/h4>\n\n<p>Place a form in a post or page:<\/p>\n\n<pre><code>[aj_form id=\"123\"]\n<\/code><\/pre>\n\n<p>Turn individual parts on or off:<\/p>\n\n<pre><code>[aj_form id=\"123\" title=\"0\" image=\"0\" description=\"0\" deadline=\"0\" links=\"0\"]\n<\/code><\/pre>\n\n<p>Choose the heading level for the form title. The default is <code>h2<\/code>, which sits above\nthe <code>h3<\/code> used for question titles:<\/p>\n\n<pre><code>[aj_form id=\"123\" title_tag=\"h1\"]\n<\/code><\/pre>\n\n<p>Output a single question, counting from 1. This is useful when you want to spread\nthe questions of one form across a longer article:<\/p>\n\n<pre><code>[aj_form id=\"123\" sno=\"2\"]\n<\/code><\/pre>\n\n<p>The display defaults depend on <code>sno<\/code>. Without it you get everything: title, image,\ndescription, deadline notice and related links. With it you get the question on its\nown, because repeating the title and the deadline next to every question would be\nnoise. Writing an attribute yourself always wins over either default.<\/p>\n\n<p>List your published surveys as cards, each linking to its standalone page:<\/p>\n\n<pre><code>[aj_form_list]\n\n[aj_form_list] accepts `type=\"survey|form|all\"`, `ids=\"3,5\"`, `limit=\"10\"`,\norderby=\"date|title|deadline\", `order=\"desc|asc\"`, `excerpt=\"1\"`, `words=\"25\"`,\ncount=\"1\", `deadline=\"1\"`, `status=\"1\"` and `image=\"1\"`.\n<\/code><\/pre>\n\n<p>The Shortcodes tab under Ajebang Forms \u2192 Settings documents every attribute, with copy\nready examples for the forms on your own site.<\/p>\n\n<h4>Permissions<\/h4>\n\n<p>Creating forms and viewing statistics requires the <code>manage_options<\/code> capability, so\nonly administrators can do it. Submitting a response requires nothing at all \u2014\nanonymous visitors can take part.<\/p>\n\n<h4>Data storage<\/h4>\n\n<p>Responses are not stored as posts. The plugin creates two of its own tables:<\/p>\n\n<ul>\n<li><code>{prefix}aj_form_forms<\/code> \u2014 form definitions<\/li>\n<li><code>{prefix}aj_form_submissions<\/code> \u2014 submitted responses<\/li>\n<\/ul>\n\n<p>Deactivating or deleting the plugin leaves both tables in place, so your responses\nsurvive an uninstall.<\/p>\n\n<h4>A note on repeat responses<\/h4>\n\n<p>Because the plugin accepts anonymous submissions, repeat responses cannot be\nblocked completely. Cookies can be cleared or sidestepped with a private window,\nand IP addresses are shared in offices and on mobile networks, where blocking by IP\nwould turn away genuine participants. Treat the setting as protection against\naccidental double submissions and page reloads rather than as a guarantee.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Upload the plugin through Plugins \u2192 Add New \u2192 Upload Plugin, or copy the\n   ajebang-form-survey-builder folder into <code>wp-content\/plugins\/<\/code>.<\/li>\n<li>Activate it. The plugin creates its two database tables on activation.<\/li>\n<li>Go to Ajebang Forms \u2192 Add New to build your first form.<\/li>\n<li>Copy the shortcode from the form list, or share the standalone link shown on the\nedit screen.<\/li>\n<\/ol>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20visitors%20need%20an%20account%20to%20respond%3F\"><h3>Do visitors need an account to respond?<\/h3><\/dt>\n<dd><p>No. Anyone can submit a response without logging in. Only administrators can create\nforms and read the statistics.<\/p><\/dd>\n<dt id=\"what%20happens%20to%20my%20responses%20if%20i%20delete%20the%20plugin%3F\"><h3>What happens to my responses if I delete the plugin?<\/h3><\/dt>\n<dd><p>They stay. The plugin has no uninstall routine and never drops its tables, so\nreinstalling brings your forms and responses back exactly as they were.<\/p><\/dd>\n<dt id=\"the%20standalone%20links%20return%20%22page%20not%20found%22.\"><h3>The standalone links return \"page not found\".<\/h3><\/dt>\n<dd><p>Visit Settings \u2192 Permalinks once to let WordPress rebuild its rewrite rules. If\nyour site uses the plain permalink structure, the plugin falls back to addresses\nin the form <code>?aj_form_view=12<\/code> instead.<\/p><\/dd>\n<dt id=\"can%20i%20show%20only%20one%20question%20of%20a%20form%3F\"><h3>Can I show only one question of a form?<\/h3><\/dt>\n<dd><p>Yes, with the <code>sno<\/code> attribute: <code>[aj_form id=\"1\" sno=\"2\"]<\/code> renders the second\nquestion by itself. Validation, submission and results are all scoped to that\nquestion, and the answers are still recorded against the original form.<\/p><\/dd>\n<dt id=\"i%20use%20a%20full%20page%20cache.%20does%20that%20cause%20problems%3F\"><h3>I use a full page cache. Does that cause problems?<\/h3><\/dt>\n<dd><p>The plugin is built for it. Anonymous submissions do not rely on a nonce, because a\ncached page eventually serves an expired one and would lock every visitor out. After\nthe page loads, the plugin fetches the real participation state and corrects the\nscreen, so a cached \"not yet answered\" view does not let someone respond twice.<\/p><\/dd>\n<dt id=\"where%20do%20i%20report%20a%20problem%3F\"><h3>Where do I report a problem?<\/h3><\/dt>\n<dd><p>Email ajebang@ajebang.com or visit https:\/\/ajebang.com.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.9.1<\/h4>\n\n<ul>\n<li>The virtual post cached for a shortcut page is now removed from the post cache\nwhen the request ends, so nothing the plugin writes outlives the request on\nsites running a persistent object cache.<\/li>\n<\/ul>\n\n<h4>1.9.0<\/h4>\n\n<ul>\n<li>Renamed the plugin to \"Ajebang Form and Survey Builder\". The former name combined\na two-letter initialism with a generic term and was not distinctive enough for the\nplugin directory. The text domain, the plugin folder and the main file follow the\nnew slug, <code>ajebang-form-survey-builder<\/code>.<\/li>\n<li>The form builder's initial data is attached with <code>wp_add_inline_script()<\/code> instead\nof a <code>&lt;script&gt;<\/code> tag written into the page.<\/li>\n<li>The <code>the_title<\/code> filter callback escapes the title it returns. A filter callback's\nreturn value is output by WordPress without any escaping of its own.<\/li>\n<li>Dropped <code>load_plugin_textdomain()<\/code> and the bundled <code>.po<\/code>\/<code>.mo<\/code> files. Translations\nfor a plugin hosted on wordpress.org come from translate.wordpress.org through the\nstandard update system, so neither is needed.<\/li>\n<\/ul>\n\n<h4>1.8.8<\/h4>\n\n<ul>\n<li>Removed the <code>Plugin URI<\/code> header. It pointed at the same address as <code>Author URI<\/code>,\nwhich wordpress.org rejects on upload \u2014 the two describe different things and\nneither is required. <code>Author URI<\/code> is the accurate one here; wordpress.org\nprovides the plugin's own page.<\/li>\n<\/ul>\n\n<h4>1.8.7<\/h4>\n\n<ul>\n<li>The current URL is now derived from a sanitised <code>REQUEST_URI<\/code>. It is passed\nthrough <code>esc_url_raw()<\/code> rather than <code>sanitize_text_field()<\/code>, which strips <code>%xx<\/code>\nsequences and would mangle any address containing non-ASCII characters.<\/li>\n<li>Documented the deliberate deviations that Plugin Check reports, as <code>phpcs:ignore<\/code>\ncomments with their reasons: anonymous submissions do not carry a nonce, input is\nsanitised after decoding rather than before, and the custom tables are reached\nwith direct <code>$wpdb<\/code> calls. No change in behaviour \u2014 100 warnings down to 1.<\/li>\n<\/ul>\n\n<h4>1.8.6<\/h4>\n\n<ul>\n<li>Fixed choice display counts not saving. On any form where a count had never been\nset, the builder was not sending the changed values at all, so the screen said\n\"Form saved\" while the numbers stayed the same. The empty count list arrived as a\nJSON array rather than an object, and the values keyed by choice name were dropped\nduring serialisation. Existing forms work from this version on, with no migration.<\/li>\n<li>Plugin Check fixes: the number in the \"N responses deleted\" notice is now escaped\nat the point of output, and a <code>translators:<\/code> comment was moved onto the line\ndirectly above its gettext call. No change in behaviour.<\/li>\n<li>The readme and the plugin header description are now in English.<\/li>\n<\/ul>\n\n<h4>1.8.5<\/h4>\n\n<ul>\n<li>Reversed the display defaults for <code>sno<\/code>. <code>[aj_form id=\"1\" sno=\"1\"]<\/code> now renders the\nquestion on its own, without the title, featured image, description, deadline\nnotice or related links. The attribute exists to drop a question into the middle of\nan article, where repeating all of that was in the way. A whole form, with no <code>sno<\/code>,\nstill shows everything as before.<\/li>\n<li>Added the <code>deadline<\/code> attribute, which turns the \"you can respond until\u2026\" notice on\nand off. The notice on a closed form always appears, since it explains why there is\nno form to fill in.<\/li>\n<li>Writing an attribute yourself beats either default, for example\n  [aj_form id=\"1\" sno=\"1\" deadline=\"1\"].<\/li>\n<\/ul>\n\n<h4>1.8.4<\/h4>\n\n<ul>\n<li>Added a Shortcodes tab to the settings screen. It lists every attribute of both\nshortcodes with its values, default and description, adds examples for common\nsituations, and notes which options belong to the form rather than the shortcode.\nAt the bottom it lists the forms on your site with copy ready shortcodes and links.<\/li>\n<\/ul>\n\n<h4>1.8.3<\/h4>\n\n<ul>\n<li>The standalone page now hands its featured image to the theme, supplying it as the\nWordPress featured image, so the theme draws its usual header banner instead of\nleaving the image stranded below the content.<\/li>\n<li>Settings \u2192 General \u2192 standalone page \u2192 featured image is now a choice of three:\nleave it to the theme (default), print it in the content, or hide it. Values saved\nin 1.8.2 carry over to the first and third options respectively.<\/li>\n<\/ul>\n\n<h4>1.8.2<\/h4>\n\n<ul>\n<li>Fixed the empty title area on standalone pages. Themes render an<\/li>\n<\/ul>\n\n<p>&lt;<\/p>\n\n<p>h1 class=\"entry-title\"&gt; slot, which stayed blank because the post is virtual.\n  The plugin now fills that slot through the <code>the_title<\/code> filter, leaving other titles\n  on the page, such as navigation items, untouched.\n* Printing the title inside the content is now off by default, since the fix above\n  fills the theme's own title area and leaving both on shows the title twice. The\n  option remains under Settings \u2192 General for themes with no title area at all.\n* Added a setting for whether the standalone page shows the featured image. Listings\n  keep using it as a thumbnail either way.<\/p>\n\n<h4>1.8.1<\/h4>\n\n<ul>\n<li>Fixed the missing form title on standalone pages. The shortcode suppressed the\ntitle on the assumption that the theme would draw it, which left a page with no\ntitle on themes that do not. The title is now printed as an <code>h1<\/code> by default and can\nbe turned off under Settings \u2192 General.<\/li>\n<li>Added featured images. Pick one from the media library per form and it appears\nabove the form and as the thumbnail in listings. Turn it off with <code>image=\"0\"<\/code>.<\/li>\n<li>Question titles are now <code>&lt;h3&gt;<\/code> elements rather than labels, which were not headings\nas far as document structure was concerned. The hierarchy runs form title (<code>h2<\/code>, or\n  h1 on a standalone page) then question title (<code>h3<\/code>), and result cards match. The\nwrapper changed from <code>&lt;p&gt;<\/code> to <code>&lt;div&gt;<\/code>, because a paragraph cannot contain a heading\nand browsers break the markup apart.<\/li>\n<li>Fixed choice labels rendering in bold. A <code>font-weight<\/code> rule meant for field titles\nwas catching them too.<\/li>\n<li>Accessibility: single inputs are tied to their control with <code>label for<\/code>, and radio\nand checkbox groups are tied to their question title with <code>role=\"group\"<\/code> and\n  aria-labelledby.<\/li>\n<\/ul>\n\n<h4>1.8.0<\/h4>\n\n<ul>\n<li>Added the <code>[aj_form_list]<\/code> shortcode, which shows published surveys as cards with\nthe title, an excerpt, the response count, the deadline and an open or closed badge.\nOpen surveys sort above closed ones and each card links to its standalone page.<\/li>\n<li>Added display attributes <code>title<\/code>, <code>description<\/code> and <code>links<\/code> to <code>[aj_form]<\/code>. All\ndefault to on. Titles are printed by default from this version, so add <code>title=\"0\"<\/code>\nif your post already has one.<\/li>\n<li>Added the <code>sno<\/code> attribute for rendering a single question. Validation, submission\nand results are scoped to that question; everything else behaves as before.<\/li>\n<li>Added related links, a per-form list shown underneath the form.<\/li>\n<li>Added a response deadline. Forms run indefinitely by default. After the deadline the\nserver refuses submissions and shows a notice, and surveys can go on showing their\nresults.<\/li>\n<li>Added drafts. A draft form renders nothing, stays out of listings, and returns 404\non its standalone link; administrators see it with a notice. New forms start as\ndrafts. Existing forms all stay published.<\/li>\n<li>Added standalone links. Every form has its own page at <code>\/aj-form\/{type}\/{id}\/<\/code>. The\nbase is configurable, and sites using plain permalinks fall back to\n  ?aj_form_view=12.<\/li>\n<li>Added a Korean translation.<\/li>\n<li>No database schema change. The new options all live in the existing settings column.<\/li>\n<\/ul>\n\n<h4>1.7.4<\/h4>\n\n<ul>\n<li>Fixed the mangled plugin description in the plugins list, caused by the Korean text\nin the plugin file and readme having been saved in the wrong encoding.<\/li>\n<li>Removed a UTF-8 byte order mark from the head of the plugin file. Those three bytes\nwere sent before any header, which could make <code>setcookie()<\/code> and <code>wp_safe_redirect()<\/code>\nfail with \"headers already sent\".<\/li>\n<\/ul>\n\n<h4>1.7.3<\/h4>\n\n<ul>\n<li>Fixed \"This form has expired. Please reload the page and try again.\" blocking every\nsubmission. The nonce baked into a cached page expires after 24 hours while the page\ncache lives longer, so all visitors were posting a dead nonce. Logged out visitors\nare no longer asked for one, since without a session it carries no CSRF protection\nanyway, and the nonce for logged in users is refreshed as the page loads.<\/li>\n<\/ul>\n\n<h4>1.7.2<\/h4>\n\n<ul>\n<li>Fixed nobody being able to take part on a cached page. Once a participant's screen\nwas cached, every later visitor received the results view with no form. The state\ncorrection now works in both directions and can bring the form back.<\/li>\n<\/ul>\n\n<h4>1.7.1<\/h4>\n\n<ul>\n<li>Dark theme support. Hard-coded light colours on the front end \u2014 bar backgrounds,\ninputs, choice boxes, notices \u2014 were replaced with neutral values that follow the\ntheme, fixing bar backgrounds that glowed white on dark themes.<\/li>\n<\/ul>\n\n<h4>1.7.0<\/h4>\n\n<ul>\n<li>Page cache support. A full page cache could serve the \"not yet answered\" screen and\nallow a repeat response. The plugin now fetches the real state after the page loads,\ncorrects the screen, and refreshes an expired nonce at the same time.<\/li>\n<li>Repeat limiting by IP is stronger: a previous response is found by IP even when the\ncookie is gone.<\/li>\n<li>Added an option for showing the response count per question.<\/li>\n<li>Added survey defaults to the global settings, so new forms start with the options\nyou prefer.<\/li>\n<li>Split the settings and form edit screens into tabs.<\/li>\n<\/ul>\n\n<h4>1.6.0<\/h4>\n\n<ul>\n<li>Improved the survey results layout. Each question is a card with its response count\nbeside the title, which fixes the missing boundaries between questions.<\/li>\n<li>Added an option for showing the total response count.<\/li>\n<li>Added per-question submission. Answering one question turns that question into its\nresult immediately and leaves the rest alone.<\/li>\n<li>Added deleting all responses, from the form list and the responses screen. The form\ndefinition is kept.<\/li>\n<li>Added the global settings screen at Ajebang Forms \u2192 Settings.<\/li>\n<li>Added adjustable display counts per choice. Turn it on in the global settings and\nthe builder lets you set the number shown for each option. Turn it off and stored\nvalues are ignored, leaving the real response counts.<\/li>\n<\/ul>\n\n<h4>1.5.0<\/h4>\n\n<ul>\n<li>Added repeat-response limiting, per form: none, browser cookie, or cookie and IP.\nThe default is cookie. A visitor who has already taken part sees the results.<\/li>\n<li>Added an option to hide the submit button and send the form automatically once every\nfield is filled. Visitors without JavaScript still see the button.<\/li>\n<li>Added internationalisation: a <code>Domain Path<\/code> header, <code>load_plugin_textdomain()<\/code> and a\nbundled POT file. Translations were not being loaded before this.<\/li>\n<li>Improved string extraction with more <code>translators:<\/code> comments and <code>_n()<\/code> for counts.<\/li>\n<\/ul>\n\n<h4>1.4.0<\/h4>\n\n<ul>\n<li>Added a per-form option for whether a thank-you message appears after submission.\nWith it off, the results appear straight away.<\/li>\n<li>Added the settings column used to store per-form options. Existing rows fall back to\nthe default of showing the message.<\/li>\n<\/ul>\n\n<h4>1.3.2<\/h4>\n\n<ul>\n<li>Tidied the plugin header: added <code>Requires at least<\/code>, <code>Requires PHP<\/code> and the licence\nfields, and updated <code>Tested up to<\/code>.<\/li>\n<\/ul>\n\n<h4>1.3.1<\/h4>\n\n<ul>\n<li>Improved the survey results layout by putting each choice label on its own line with\nthe bar and figures below it, which fixes long labels overlapping in narrow columns.<\/li>\n<li>Removed the fixed width from the results screen.<\/li>\n<\/ul>\n\n<h4>1.3.0<\/h4>\n\n<ul>\n<li>Added AJAX submission on the front end. The page is not left behind, and surveys turn\ninto their results in place. Browsers without JavaScript fall back to a normal post.<\/li>\n<li>Fixed submissions redirecting to the home page. A form posting to itself made the\nredirect target impossible to work out.<\/li>\n<li>Added server-side validation of required fields, including checkbox groups.<\/li>\n<li>Added Preview to the admin form list, matching the front end with submission disabled.<\/li>\n<\/ul>\n\n<h4>1.2.1<\/h4>\n\n<ul>\n<li>Fixed a permission error when administrators opened View Statistics or\nView Submissions.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Added a description field, shown above the form controls.<\/li>\n<li>Added collapsing and expanding of individual fields in the builder.<\/li>\n<li>Improved radio and checkbox styling on the front end.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>Added form types. Surveys show aggregated statistics.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First release.<\/li>\n<\/ul>","raw_excerpt":"Build forms and surveys with a drag-and-drop builder, show aggregated results, set deadlines, and place them anywhere with shortcodes.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/349524","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=349524"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/ajebang"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=349524"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=349524"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=349524"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=349524"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=349524"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=349524"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}