If you resell Zinn\u00ae hosting, this plugin connects your own WordPress site to your reseller account so your customers never have to leave it.<\/p>\n\n
It has three parts and they are separate switches<\/strong>. Turn on only what you need \u2014 nothing that is switched off loads any code, registers any hook or enqueues any stylesheet.<\/p>\n\n 1. Domain search<\/strong><\/p>\n\n Put Attributes:<\/p>\n\n 2. Panel link<\/strong><\/p>\n\n Put The sign-in link is minted when the link is clicked<\/strong>, not when the page is rendered, so it never sits in a page cache and never reaches a crawler. It is single-use and expires within minutes.<\/p>\n\n 3. WooCommerce provisioning<\/strong><\/p>\n\n Sell hosting as an ordinary WooCommerce product, take the money through your own gateway into your own account, and hosting is set up the moment the order is paid.<\/p>\n\n This plugin lets you sell Zinn Digital\u00ae hosting from your own WordPress site. It is a front end\nfor the Zinn\u00ae reseller API and requires a reseller account.<\/p>\n\n What is sent, and when<\/strong><\/p>\n\n Nothing is transmitted until you enter reseller API credentials.<\/p>\n\n Service terms: https:\/\/zinndigital.com\/legal\/terms\nPrivacy policy: https:\/\/zinndigital.com\/legal\/privacy<\/p>\n\n Every string this plugin adds to your admin is translated into 57 languages<\/strong> \u2014 labels, notices,\nerrors and settings, not a subset. The catalogues are bundled in the plugin, so they work as soon\nas you set your site language; there is no separate language pack to install.<\/p>\n\n Every user-visible string is complete in every one of the 53 languages WordPress can serve\ntoday:<\/p>\n\n Amharic (am), Arabic (ar), Azerbaijani (az), Bulgarian (bg_BG), Bengali (Bangladesh)\n(bn_BD), Czech (cs_CZ), German (de_DE), Greek (el), Spanish (Spain) (es_ES), Persian\n(fa_IR), French (France) (fr_FR), Gujarati (gu), Hebrew (he_IL), Hindi (hi_IN), Croatian\n(hr), Hungarian (hu_HU), Armenian (hy), Indonesian (id_ID), Italian (it_IT), Japanese\n(ja), Georgian (ka_GE), Kazakh (kk), Khmer (km), Kannada (kn), Korean (ko_KR), Lao (lo),\nMalayalam (ml_IN), Mongolian (mn), Marathi (mr), Malay (ms_MY), Myanmar (Burmese)\n(my_MM), Nepali (ne_NP), Dutch (nl_NL), Panjabi (India) (pa_IN), Polish (pl_PL), Pashto\n(ps), Portuguese (Brazil) (pt_BR), Romanian (ro_RO), Russian (ru_RU), Sinhala (si_LK),\nAlbanian (sq), Serbian (sr_RS), Swahili (sw), Tamil (ta_IN), Telugu (te), Thai (th),\nTagalog (tl), Turkish (tr_TR), Ukrainian (uk), Urdu (ur), Uzbek (uz_UZ), Vietnamese\n(vi), Chinese (China) (zh_CN)<\/p>\n\n A further 4 ship complete in the plugin \u2014 Hausa (ha), Somali (so_SO), Tajik (tg), Yoruba (yo) \u2014 but\nWordPress core does not currently provide a locale for them, so WordPress cannot load them.<\/p>\n\n Arabic, Persian, Hebrew, Pashto and Urdu are right-to-left. Every screen this plugin adds was\nrendered in a real WordPress install in each of those languages and checked, not assumed.<\/p>\n\n corrections and new languages can be contributed directly.<\/p>\n\n\n No. WooCommerce settles the money into your own account through your own gateway. This plugin runs after the order is paid and only tells the hosting platform to provision.<\/p><\/dd>\n Yes. It ships with a deliberately small stylesheet that sets layout and state colour and nothing else. Override these classes in your theme: Nothing is provisioned or cancelled. Uninstalling removes the plugin's own settings; it deliberately leaves the links between your customers and their hosting alone, because those are the only record of what a customer is paying for.<\/p><\/dd>\n Yes. Settings are per site, and uninstalling clears them on every site in the network.<\/p><\/dd>\n\n<\/dl>\n\n\n The domain-search widget can be styled \u2014 four presets and eight colours and sizes you can override \u2014 and the settings screen now tells you whether anything is actually switched on.<\/p>\n\n[zinn_domain_search]<\/code> on any page. A visitor types a name, and the results come back live. Once your reseller key is set they come from your own domain account with your own prices on them; before that, the search already works against the public catalogue and its prices.<\/p>\n\n\n
[zinn_domain_search placeholder=\"Find your domain\" button=\"Search\" tlds=\"com,co.uk,io\"]\n\ntlds accepts up to five extensions. Leave it out and the default set is used.\n<\/code><\/pre>\n\n[zinn_panel_link]<\/code> anywhere a signed-in customer will see it \u2014 a My Account page is the usual home. It renders a single link that takes them straight into their hosting panel, already signed in.<\/p>\n\n[zinn_panel_link label=\"Manage my hosting\"]\n<\/code><\/pre>\n\n\n
zinn_domain<\/code> meta \u2014 set it from your own domain field, or from the domain search above.<\/li>\nExternal services<\/h3>\n\n
\n
\/v1\/domains\/search<\/code> when\nauthenticated) to check availability and price. The search term is the visitor's input; no\nother visitor data, IP address or identifier is added by this plugin.<\/strong><\/li>\n\/v1\/reseller\/program<\/code> is read to render your plans and prices.<\/li>\n\/v1\/orgs<\/code> so their hosting account can be created, and the ordered\nplan and domain name then go to \/v1\/sites<\/code> so the site itself can be provisioned. This is a\ntransfer of your customer's personal data to Zinn Digital\u00ae as a processor, and you should\nreflect it in your own privacy policy.<\/li>\nhttps:\/\/app.zinndigital.com<\/code>. No password and no customer\ncredential passes through this site \u2014 only the identifier of the service being opened.<\/li>\n<\/ul>\n\n\n
https:\/\/api.zinndigital.com\/v1\/connector\/diagnostics<\/code>. You are shown the\nexact payload first, already redacted, and nothing leaves your site until you press send.<\/strong>\nCredentials are excluded by declaration rather than by matching key names, and render as\n [not sent \u2014 credential]. The plugin never sends this on its own initiative.<\/li>\n<\/ul>\n\nTranslations<\/h3>\n\n
Right-to-left<\/h4>\n\n
For translators<\/h4>\n\n
languages\/ holds the `.pot` template plus a `.po`, `.mo` and `.l10n.php` for every language, so\n<\/code><\/pre>\n\n\n
sites.create<\/code> and org.read<\/code> for WooCommerce provisioning, reseller.view<\/code> and reseller.provision<\/code> for the panel link.<\/li>\n\n
Do my customers' payments go through Zinn\u00ae?<\/h3><\/dt>\n
Can I restyle the domain search?<\/h3><\/dt>\n
.zinn-domain-search<\/code>, .zinn-domain-results<\/code>, .zinn-domain-result<\/code>, .zinn-domain-result--available<\/code>, .zinn-domain-result--taken<\/code>, .zinn-domain-result--unknown<\/code>, .zinn-domain-name<\/code>, .zinn-domain-state<\/code>, .zinn-domain-buy<\/code>, .zinn-domain-error<\/code>.<\/p><\/dd>\nWhat happens if I deactivate the plugin?<\/h3><\/dt>\n
Does it work on multisite?<\/h3><\/dt>\n
1.4.0<\/h4>\n\n
\n
1.3.0<\/h4>\n\n
\n
1.2.10<\/h4>\n\n
\n
1.2.9<\/h4>\n\n
\n
1.2.8<\/h4>\n\n
\n
1.2.7<\/h4>\n\n
\n
1.2.6<\/h4>\n\n
\n
1.2.5<\/h4>\n\n
\n
1.2.4<\/h4>\n\n
\n
1.2.3<\/h4>\n\n
\n
1.2.2<\/h4>\n\n
\n
1.2.1<\/h4>\n\n
\n
1.2.0<\/h4>\n\n
1.1.3<\/h4>\n\n
\n
1.1.2<\/h4>\n\n
1.1.0<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n