{"id":825,"date":"2021-07-23T12:38:59","date_gmt":"2021-07-23T12:38:59","guid":{"rendered":"https:\/\/ssdsunucum.com\/blog\/modify-an-account\/"},"modified":"2021-07-23T12:38:59","modified_gmt":"2021-07-23T12:38:59","slug":"modify-an-account","status":"publish","type":"post","link":"https:\/\/ssdsunucum.com\/blog\/modify-an-account\/","title":{"rendered":"Modify an Account"},"content":{"rendered":"<\/p>\n<div class=\"col-md-9\">\n<div class=\"flex-column flex-md-row article-header\">\n<div id=\"versioned-article-header\">\n<p class=\"valid-version-info\"><em>Valid for versions 98 through the latest version<\/em><\/p>\n<\/div>\n<div id=\"version-select-group\" aria-label=\"select versions\">\n<h4>Version:<\/h4>\n<h4>82<\/h4>\n<h4>86<\/h4>\n<h4>90<\/h4>\n<h4>94<\/h4>\n<h4>96<\/h4>\n<h4>98<\/h4>\n<\/div><\/div>\n<hr>\n<h2 id=\"overview\">Overview<\/h2>\n<p>The <em>Modify an Account<\/em> interface allows you to make changes to an existing account.<\/p>\n<h2 id=\"modify-an-account\">Modify an account<\/h2>\n<p>To modify an account, perform the following steps:<\/p>\n<ol>\n<li>\n<p>Select the desired account and click <em>Modify<\/em>.<\/p>\n<\/li>\n<li>\n<p>Make changes to the settings in the sections below.<\/p>\n<\/li>\n<li>\n<p>Click <em>Save<\/em>.<\/p>\n<\/li>\n<\/ol>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>\n<p>If you make changes to the <em>Resource Limits<\/em>, <em>Privileges<\/em>, <em>DNS Settings<\/em>, or <em>Package Extensions<\/em> sections, the <em>Package Conflict Resolution<\/em> dialog box appears.<\/p>\n<\/li>\n<li>\n<p>By default, the system makes the necessary changes to the server\u2019s firewall when you modify an account. To disable this behavior, enable the <em>Do not make changes to the firewall during account modification.<\/em> setting in WHM\u2019s <em>Tweak Settings<\/em> interface (<em>WHM &gt;&gt; Home &gt;&gt; Server Configuration &gt;&gt; Tweak Settings<\/em>).<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<h3 id=\"basic-information\">Basic information<\/h3>\n<p>This section allows you to edit the following settings:<\/p>\n<ul>\n<li>\n<p><em>Primary Domain<\/em> \u2014 Enter a new primary domain.<\/p>\n<\/li>\n<li>\n<p><em>Username<\/em> \u2014 Enter a username. The new username must meet the following requirements:<\/p>\n<ul>\n<li>You <strong>must<\/strong> choose a unique username that contains 16 characters or fewer.<\/li>\n<li>The username <strong>must<\/strong> contain only letters and numbers.<\/li>\n<li>The username <strong>cannot<\/strong> start with a number or the string <code>test<\/code>.<\/li>\n<li>If you plan to use MySQL or PostgreSQL as a database engine, the first eight characters <strong>must<\/strong> be unique on the system to prevent issues with database prefixing and account transfers. However, this restriction does <strong>not<\/strong> apply to servers that run MariaDB.\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>You can disable database prefixing with the <em>Add prefix to names of new databases and database users<\/em> setting in the SQL section of WHM\u2019s <em>Tweak Settings<\/em> interface (<em>WHM &gt;&gt; Home &gt;&gt; Server Configuration &gt;&gt; Tweak Settings<\/em>).<\/li>\n<li>Only the <code>root<\/code>\u00a0user can rename a self-owned reseller account.<\/li>\n<li>For more information about username restrictions, read our Reserved, Invalid, and Misconfigured Usernames documentation.<br \/>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<div class=\"callout callout-danger\">\n<div class=\"callout-heading\">Warning:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>If you <strong>must<\/strong> change the account username, we recommend that the new name be the same length or shorter. A longer name may cause MySQL\u00ae to truncate the account\u2019s database names and database usernames, which causes problems.<\/li>\n<li>If you change the username of an account, the following problems may occur:\n<ul>\n<li>You <strong>cannot<\/strong> use the associated websites and databases while the data transfers to the new username.<\/li>\n<li>The system renames the user\u2019s home directory.<\/li>\n<li>Make certain to verify the account\u2019s integrity after the transfer finishes.<br \/>\n<\/li>\n<\/ul>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p><em>Rename prefixed databases and database users<\/em> \u2014 The system selects the <em>Rename prefixed databases and database users<\/em> checkbox by default. Deselect this checkbox to rename only the cPanel account itself.<\/p>\n<ul>\n<li>\n<p>If database prefixing is active on the server, this function changes the names of associated database objects (databases and database users) to use the first eight characters of the new username as a database prefix. For example, if you change the <code>example<\/code> username to <code>example1<\/code>, the system will rename the <code>example_db<\/code> database to <code>example1_db<\/code> and the <code>fred_db1<\/code> user to <code>example1_db1<\/code>, but name of the <code>steve<\/code> database will not change.<\/p>\n<div class=\"callout callout-warning\">\n<div class=\"callout-heading\">Important:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>\n<p>When you rename an account, you can rename the account\u2019s databases and database users to preserve the visual correspondence between database names and the username. However, this causes errors in applications that depend on the previous names.<\/p>\n<\/li>\n<li>\n<p>If you do not rename the prefixed databases and database users, PostgreSQL\u00ae users <strong>cannot<\/strong> log in until they reset their passwords.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<li>\n<p>MySQL does <strong>not<\/strong> allow you to rename a database. When cPanel &#038; WHM \u201crenames\u201d a database, the system performs the following steps:<\/p>\n<\/li>\n<li>\n<p>The system creates a new database.<\/p>\n<\/li>\n<li>\n<p>The system moves data from the old database to the new database.<\/p>\n<\/li>\n<li>\n<p>The system recreates grants and stored code in the new database.<\/p>\n<\/li>\n<li>\n<p>The system deletes the old database and its grants.<\/p>\n<div class=\"callout callout-danger\">\n<div class=\"callout-heading\">Warning:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>If <strong>any<\/strong> of the first three steps fail, the system returns an error and attempts to restore the database\u2019s original state. If the restoration process fails, the API function\u2019s error response describes these additional failures.<\/li>\n<li>In rare cases, the system creates the second database successfully, but fails to delete the old database or grants. The system treats the rename action as a success; however, the API function returns warnings that describe the failure to delete the old database or grants.<br \/>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p><em>Account Owner<\/em> \u2014 Select a new account owner from the list of resellers.<\/p>\n<\/li>\n<li>\n<p><em>Contact Email<\/em> \u2014 Enter a new contact email for the account\u2019s owner.<\/p>\n<\/li>\n<li>\n<p><em>Default Locale<\/em> \u2014 Select a new default locale.<\/p>\n<\/li>\n<li>\n<p><em>cPanel Theme<\/em> \u2014 Select a theme from the menu. To modify the theme and associated style for multiple accounts, use the <code>\/scripts\/modify_accounts<\/code> script.<\/p>\n<\/li>\n<li>\n<p><em>Mail child node<\/em> \u2014 Displays the currently linked mail child node server. The linked server performs the mail tasks for the cPanel account. For more information, read our How to Use Server Profiles documentation.<\/p>\n<\/li>\n<li>\n<p><em>Enable Apache SpamAssassin\u2122<\/em> \u2014 Enable or disable Apache SpamAssassin\u2019s <em>Spam Filters<\/em> for the account.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<p>You <strong>cannot<\/strong> modify this setting if you enable the <em>Apache SpamAssassin\u2122: Forced Global ON<\/em> setting in WHM\u2019s <em>Exim Configuration Manager<\/em> interface (<em>WHM &gt;&gt; Home &gt;&gt; Service Configuration &gt;&gt; Exim Configuration Manager<\/em>).<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<h3 id=\"linked-server-nodes\">Linked Server Nodes<\/h3>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>This feature only appears if your server has a linked cPanel &#038; WHM server node.<\/li>\n<li>Only users with <code>root<\/code>-level privileges can select which server handles a cPanel account\u2019s mail functionality.<\/li>\n<\/ul><\/div>\n<\/div>\n<p>This section allows you to offload specific tasks to a linked node. Select whether to use the local server or a remote child node to handle mail functionality. You can select from the following settings:<\/p>\n<ul>\n<li><em>Use only this server.<\/em> \u2014 The cPanel account\u2019s mail functionality will only exist on the local server.<\/li>\n<li><em>Mail child node<\/em> \u2014 Select a linked <em>mail child node<\/em> server to handle the cPanel account\u2019s mail functionality.<\/li>\n<\/ul>\n<h3 id=\"resource-limits\">Resource Limits<\/h3>\n<p>This section allows you to edit the following settings:<\/p>\n<ul>\n<li>\n<p><em>Package<\/em> \u2014 Select a hosting plan, which defines the limitations of the account. Click <em>Change<\/em> to navigate to the <em>Upgrade\/Downgrade an Account<\/em> interface (<em>WHM &gt;&gt; Home &gt;&gt; Account Functions &gt;&gt; Upgrade\/Downgrade an Account<\/em>).<\/p>\n<\/li>\n<li>\n<p><em>Disk Space Quota (MB)<\/em> \u2014 Enter the amount of space on the server\u2019s hard drive for the new account, in Megabytes (MB).<\/p>\n<\/li>\n<li>\n<p><em>Monthly Bandwidth Limit (MB)<\/em> \u2014 Enter the maximum amount of data that the new account can transfer each month, in Megabytes (MB).<\/p>\n<\/li>\n<li>\n<p><em>Max FTP Accounts<\/em> \u2014 Enter the maximum number of the account\u2019s FTP accounts.<\/p>\n<\/li>\n<li>\n<p><em>Max Email Accounts<\/em> \u2014 Enter the maximum number of the account\u2019s email accounts.<\/p>\n<\/li>\n<li>\n<p><em>Mail Quota per Email Address (MB)<\/em> \u2014 Enter maximum size that the account can define when it creates an email account, in Megabytes (MB).<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<p>When you adjust this value it does <strong>not<\/strong> affect existing email accounts.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p><em>Max Mailing Lists<\/em> \u2014 Enter the maximum number of the account\u2019s mailing lists.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<p>The Mailman application handles mailing lists. For more information, read Mailman\u2019s overview documentation.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p><em>Max SQL Databases<\/em> \u2014 Enter the maximum number of each available type of SQL database. For example, if you set this value to <code>5<\/code> and allow MySQL\u00ae and PostgreSQL databases, the account can create up to five MySQL databases and up to five PostgreSQL databases.<\/p>\n<\/li>\n<li>\n<p><em>Max Subdomains<\/em> \u2014 Enter the maximum number of the account\u2019s subdomains.<\/p>\n<\/li>\n<li>\n<p><em>Max Parked Domains<\/em> \u2014 Enter the maximum number of the account\u2019s parked domains (aliases).<\/p>\n<\/li>\n<li>\n<p><em>Max Addon Domains<\/em> \u2014 Enter the maximum number of the account\u2019s addon domains.<\/p>\n<\/li>\n<li>\n<p><em>Max Passenger Applications<\/em> \u2014 Enter the maximum number of the account\u2019s Passenger applications.<\/p>\n<\/li>\n<li>\n<p><em>Maximum Hourly Email by Domain Relayed<\/em> \u2014 Enter the maximum number of emails that a domain can send per hour. This value defaults to <em>Unlimited<\/em>. You can also set this value to <code>0<\/code> to allow unlimited outbound emails.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>This setting sets the same limit for every domain on the account.<\/li>\n<li>To set different limits for each domain, read our How to Set Email Send Limits documentation. If you set different limits for each domain, <em>default<\/em> displays the limit that you set for the account\u2019s <strong>primary<\/strong> domain.<br \/>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<li>\n<p><em>Maximum percentage of failed or deferred messages a domain may send per hour<\/em> \u2014 Defines the maximum percentage of failed or deferred messages that a domain sends before your server temporarily blocks outgoing mail from that domain.<\/p>\n<ul>\n<li>This value defaults to <em>Unlimited<\/em>.<\/li>\n<li>The system examines outgoing and local mail over the previous hour to determine whether the domain exceeds the limit.<\/li>\n<li>When a domain exceeds the limit, it cannot send mail until the domain no longer exceeds the limit.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3 id=\"account-enhancements\">Account Enhancements<\/h3>\n<p>Account Enhancements allow you to control whether a cPanel account can access a third-party application, without modifying the account\u2019s package settings. Select the checkbox for each Account Enhancement that you wish to enable for the cPanel account.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>\n<p>This section will <strong>only<\/strong> appear if there are third-party applications that use Account Enhancements.<\/p>\n<\/li>\n<li>\n<p>Account Enhancements may only be managed through the parent server when an account is on a child node.<\/p>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<h3 id=\"privileges\">Privileges<\/h3>\n<p>This section allows you to edit the following settings:<\/p>\n<ul>\n<li>\n<p><em>Reseller Privileges<\/em> \u2014 Select this checkbox to grant reseller privileges to the account.<\/p>\n<\/li>\n<li>\n<p><em>CGI Privilege<\/em> \u2014 Select this checkbox to grant the ability to serve CGI files to the account.<\/p>\n<\/li>\n<li>\n<p><em>Shell Access<\/em> \u2014 Select this checkbox to enable SSH access for the account.<\/p>\n<\/li>\n<\/ul>\n<h3 id=\"dns-settings\">DNS Settings<\/h3>\n<p>This section allows you to edit the following settings:<\/p>\n<ul>\n<li>\n<p><em>Enable DKIM on this account<\/em> \u2014 Select this checkbox to create DKIM records for all of the account\u2019s zones.<\/p>\n<div class=\"callout callout-warning\">\n<div class=\"callout-heading\">Important:<\/div>\n<div class=\"callout-content\">\n<p>If you disable DKIM, the system will <strong>delete<\/strong> any existing DKIM records on the account.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p><em>Enable SPF on this account<\/em> \u2014 Select this checkbox to create SPF records for all of the account\u2019s zones.<\/p>\n<div class=\"callout callout-danger\">\n<div class=\"callout-heading\">Warning:<\/div>\n<div class=\"callout-content\">\n<p>If you disable SPF, the system will <strong>delete<\/strong> any existing SPF records on the account.<\/p>\n<\/p><\/div>\n<\/div>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li>cPanel &#038; WHM uses <code>v=spf +a +mx+ipv4:local_address ?all<\/code> as the default SPF record. Add a custom SPF record to the appropriate DNS zone template to override this setting.<\/li>\n<li>If the account\u2019s owner has also enabled SPF, the system automatically rewrites this record when you use WHM\u2019s <em>Assign IPv6 Address<\/em> interface (<em>WHM &gt;&gt; Home &gt;&gt; IP Functions &gt;&gt; Assign IPv6 Address<\/em>) to assign an IPv6 address.<br \/>\n<\/li>\n<\/ul><\/div>\n<\/div>\n<\/li>\n<\/ul>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<p>The <code>\/scripts\/enable_spf_dkim_globally<\/code> script allows you to enable SPF and DKIM for accounts that exist on the server, and to create the appropriate DNS records for their domains. For more information, read our The <code>enable_spf_dkim_globally<\/code> Script documentation.<\/p>\n<\/p><\/div>\n<\/div>\n<h3 id=\"package-extensions\">Package Extensions<\/h3>\n<p>If you included any package extensions with the account or its package, a Package Extensions section displays at the bottom of the interface. Some extensions may include variables that you can edit. Any settings or settings that you can edit appear below the extension name.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<ul>\n<li><strong>Only<\/strong> package extensions that you included in the chosen package appear in this section. To learn more about extension settings and how to change them, consult the extension\u2019s documentation.<\/li>\n<li>You <strong>cannot<\/strong> use the WHM interface to add or remove installed extensions from an existing package.<\/li>\n<li>To use a different set of extensions, use the <em>Add a Package<\/em> interface (<em>WHM &gt;&gt; Home &gt;&gt; Packages &gt;&gt; Add a Package<\/em>) or use API calls to modify package extension data.<\/li>\n<li>To change the account\u2019s package, use the <em>Upgrade\/Downgrade an Account<\/em> interface (<em>WHM &gt;&gt; Home &gt;&gt; Account Functions &gt;&gt; Upgrade\/Downgrade an Account<\/em>).<\/li>\n<\/ul><\/div>\n<\/div>\n<h4 id=\"remove-missing-extensions-from-package\">Remove missing extensions from package<\/h4>\n<p>If any of the account\u2019s extensions are not currently installed on the server, a warning message appears.<\/p>\n<div class=\"callout callout-danger\">\n<div class=\"callout-heading\">Warning:<\/div>\n<div class=\"callout-content\">\n<p>You <strong>must<\/strong> install the missing extensions before you can edit their values.<\/p>\n<\/p><\/div>\n<\/div>\n<p>If you do not wish to install the missing extensions, perform the following steps to remove them from the account\u2019s chosen package:<\/p>\n<ol>\n<li>\n<p>Select the <em>Remove missing extensions from package<\/em> checkbox.<\/p>\n<\/li>\n<li>\n<p>Click <em>Save Changes<\/em> to remove the extensions from the package.<\/p>\n<\/li>\n<li>\n<p>The <em>Package Conflict Resolution<\/em> dialog box appears. Select the desired setting and click <em>Proceed<\/em>.<\/p>\n<\/li>\n<\/ol>\n<h3 id=\"package-conflict-resolution\">Package Conflict Resolution<\/h3>\n<p>The <em>Package Conflict Resolution<\/em> dialog box appears if you attempt to save settings that do not match the account\u2019s assigned package. If this dialog box appears, select the desired setting and then click <em>Proceed<\/em>. You can choose one of the following settings:<\/p>\n<ul>\n<li>\n<p><em>Upgrade\/downgrade the account to a package that matches the new properties<\/em> \u2014 Changes the account\u2019s package to a package that matches your chosen settings. This setting only appears if one or more packages that match exist. Select the desired package from the menu.<\/p>\n<\/li>\n<li>\n<p><em>Create a new package with this name<\/em> \u2014 Creates a new package with your chosen settings.<\/p>\n<ul>\n<li>The system upgrades or downgrades the account to this package.<\/li>\n<li>The default name for the new package follows the <code>oldpackagename_accountname<\/code> format, where <code>oldpackagename<\/code> represents the name of the account\u2019s previous package, and <code>accountname<\/code> represents the account\u2019s name. You can also enter a new package name.<\/li>\n<\/ul>\n<\/li>\n<li>\n<p><em>Update package (package name) with these new values<\/em> \u2014 Updates the current package to the chosen settings.<\/p>\n<div class=\"callout callout-danger\">\n<div class=\"callout-heading\">Warning:<\/div>\n<div class=\"callout-content\">\n<p>If you choose this setting, the system applies the new settings to <strong>all<\/strong> of the accounts that use this package.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p><em>Set this account to have no package<\/em> \u2014 Dissassociates the account from a package.<\/p>\n<div class=\"callout callout-info\">\n<div class=\"callout-heading\">Note:<\/div>\n<div class=\"callout-content\">\n<p>If you choose this setting, the system continues to associate the account with the current package extensions, because the system stores package extension data in the account\u2019s <code>userdata<\/code> file.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<li>\n<p><em>Keep this account on package (package name) (not recommended)<\/em>   \u2014 Continues to associate the account with its current package, but the settings in the account\u2019s userdata file do not match the settings in the package file.<\/p>\n<div class=\"callout callout-danger\">\n<div class=\"callout-heading\">Warning:<\/div>\n<div class=\"callout-content\">\n<p>We do <strong>not<\/strong> recommend that you use this setting, because the system could easily overwrite the chosen account settings with the package settings.<\/p>\n<\/p><\/div>\n<\/div>\n<\/li>\n<\/ul><\/div>\n","protected":false},"excerpt":{"rendered":"<p>Valid for versions 98 through the latest version Version: 82 86 90 94 96 98 Overview The Modify an Account interface allows you to make changes to an existing account. Modify an account To modify an account, perform the following steps: Select the desired account and click Modify. Make changes to the settings in the &hellip;<\/p>\n","protected":false},"author":1,"featured_media":826,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/825"}],"collection":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/comments?post=825"}],"version-history":[{"count":0,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/posts\/825\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media\/826"}],"wp:attachment":[{"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/media?parent=825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/categories?post=825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ssdsunucum.com\/blog\/wp-json\/wp\/v2\/tags?post=825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}