LAUNCH10<\/code>, until 30 September 2026.<\/p>\n\nNothing is sent to us, ever. Two features do reach an outside service: spam protection, if you turn it on, and the map preview in the admin. Both are described under External services below.<\/p>\n\n
Custom fields<\/strong><\/p>\n\nBuild field groups in a visual builder and attach them to anything with location rules.<\/p>\n\n
\n- 33 field types: text, textarea, number, range, email, URL, password, phone, WYSIWYG, image, file, gallery, select, checkbox, radio, button group, true\/false, link, post object, page link, relationship, taxonomy, user, map, date picker, date & time picker, time picker, color picker, message, tab, accordion, group and repeater<\/li>\n
- Location rules with AND\/OR groups: post type, page template, individual page, taxonomy, user role, options page or block<\/li>\n
- Conditional logic per field, so a field only appears when another has the right value<\/li>\n
- Validation rules (minimum and maximum length, or a regex pattern with your own message), enforced both in the browser and on the server<\/li>\n
- Register post types, taxonomies and options pages from the admin, with a visual icon picker<\/li>\n
- Local JSON: field groups are written to
uploads\/ultivo-json\/<\/code> and also read from {theme}\/ultivo-json\/<\/code>, so they can travel through version control, with a Sync button when a file is newer than the database<\/li>\n<\/ul>\n\nForms<\/strong><\/p>\n\n\n- Drag-and-drop builder with a live canvas: drop a field, see what the visitor will see<\/li>\n
- Text, email, phone, number, date, select, checkbox, radio, file upload, hidden fields, repeatable groups and free HTML, in one or more columns<\/li>\n
- Submissions are stored in WordPress and readable per entry in the admin; notifications go to any address, with a Reply-To that can point at the visitor's own email<\/li>\n
- Spam protection with Google reCAPTCHA v2, reCAPTCHA v3 or Cloudflare Turnstile. Set the keys once, then decide per form<\/li>\n
- Optional AJAX submit, so a form in a popup shows its confirmation instead of reloading the page underneath it<\/li>\n
- Uploads are stored outside the media library and can only be downloaded by someone who may edit the entry<\/li>\n<\/ul>\n\n
SEO<\/strong><\/p>\n\nEnough to launch a site with, and nothing more. No traffic lights, no scores.<\/p>\n\n
\n- Title and meta description per post, page or archive, with variables such as
%title%<\/code> and %sitename%<\/code>, and a live preview of the Google result<\/li>\n- Open Graph and Twitter tags, with an image per post falling back to the featured image and then to a site-wide default<\/li>\n
- Canonical URL, noindex, and an XML sitemap that leaves noindexed content out<\/li>\n
- Stays out of the way: with Yoast, Rank Math or All in One SEO active, Ultivo Toolkit prints no tags of its own<\/li>\n<\/ul>\n\n
Site enhancements<\/strong><\/p>\n\nSeventeen switches for the things you set up on every site: cleanup of the <head><\/code>, disabling comments, the classic editor, maintenance mode, SVG and AVIF uploads, login branding, duplicating posts, a custom login URL, manual content ordering, disabling components you do not use, limiting login attempts, revisions and Heartbeat, redirects with a 404 log, admin columns, SMTP and a full admin menu organiser. All off by default.<\/p>\n\nFor developers<\/strong><\/p>\n\n\n- Template functions:
ultivo_field( 'title' )<\/code> for one value (with an optional default), and ultivo_rows( 'blocks' )<\/code> to loop over a repeater or flexible content. A whole flexible field renders in one line: ultivo_rows( 'blocks' )->render( 'template-parts\/blocks' )<\/code><\/li>\n- Coming from ACF, the classic shapes work too:
ultivo_get_field()<\/code>, ultivo_the_field()<\/code>, ultivo_have_rows()<\/code>, ultivo_the_row()<\/code>, ultivo_get_sub_field()<\/code>, ultivo_get_row_layout()<\/code>, ultivo_update_field()<\/code>, ultivo_add_row()<\/code>, ultivo_add_options_page()<\/code><\/li>\n- Field groups in code with
ultivo_add_local_field_group()<\/code>, or exported as PHP from the Tools page<\/li>\n- Values are stored in ordinary post meta as
field_name<\/code> plus a hidden _field_name<\/code> pointing at the field key; repeater rows as name_0_subname<\/code>. Nothing is serialised into a blob, so WP_Query<\/code>, get_post_meta()<\/code> and SQL all keep working.<\/li>\n- REST API support per field group<\/li>\n
- Blocks can be registered in PHP with
ultivo_register_block_type()<\/code> and render through a template or callback. Registering is code-only for now, and the block sidebar handles the simple field types (text, number, select, radio, true\/false and colour), while the rest is best edited in a field group.<\/li>\n<\/ul>\n\nComing from ACF?<\/strong><\/p>\n\nUltivo Toolkit stores values in exactly the pattern ACF uses, and Tools \u2192 Migrate from ACF converts your field groups from the database and from the theme's acf-json<\/code> folder. Field keys are preserved, so your existing content keeps working and your templates keep returning the same values. Migration is a feature here, not the point of the plugin. You are not buying a copy of something else.<\/p>\n\nExternal services<\/h3>\n\n
This plugin connects to two kinds of outside service, and both are listed in full below. Spam protection runs only when you pick a provider and enter its keys; the map preview runs only in the admin, on posts where you use a Map field. Nothing else leaves your site, and nothing is sent to us.<\/p>\n\n
Google reCAPTCHA (v2 and v3)<\/strong>\nUsed to tell human visitors from bots when you enable it for your forms. On any page that shows a form with reCAPTCHA enabled, the reCAPTCHA script is loaded from Google. When a visitor submits that form, their reCAPTCHA token and IP address are sent to Google for verification.\nTerms: https:\/\/policies.google.com\/terms\nPrivacy: https:\/\/policies.google.com\/privacy<\/p>\n\nCloudflare Turnstile<\/strong>\nAn alternative to reCAPTCHA with the same purpose. On any page that shows a form with Turnstile enabled, the Turnstile script is loaded from Cloudflare. When a visitor submits that form, their Turnstile token and IP address are sent to Cloudflare for verification.\nTerms: https:\/\/www.cloudflare.com\/website-terms\/\nPrivacy: https:\/\/www.cloudflare.com\/privacypolicy\/<\/p>\n\nOpenStreetMap<\/strong>\nUsed only by the Map field, and only in the WordPress admin. When you edit a post\nthat has a Map field, the plugin embeds a map preview from openstreetmap.org in an\niframe, with the coordinates you entered in its URL. Nothing is sent for visitors:\nthe Map field is not available in forms, so this never runs on your public pages.\nTerms: https:\/\/osmfoundation.org\/wiki\/Terms_of_Use\nPrivacy: https:\/\/osmfoundation.org\/wiki\/Privacy_Policy<\/p>\n\n\n\n- Upload the
ultivo<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the plugin through Plugins \u2192 Add New.<\/li>\n- Activate it through the Plugins menu.<\/li>\n
- A short setup wizard opens once, where you pick the features and enhancements you want. You can change every choice later under Ultivo Toolkit \u2192 Settings.<\/li>\n<\/ol>\n\n
Ultivo Toolkit needs WordPress 6.0 or newer and PHP 8.2 or newer.<\/p>\n\n\n
\nWhy one plugin instead of four?<\/h3><\/dt>\nBecause four plugins mean four interfaces, four update cycles and four places where something can break when WordPress changes. Ultivo Toolkit shares one set of conventions across fields, forms, SEO and the site utilities, and every part can be switched off if you would rather keep what you already have.<\/p><\/dd>\n
Will four plugins in one slow my site down?<\/h3><\/dt>\nOnly the parts you switch on do anything. A disabled feature or module is not \"loaded but idle\": its code is never included, so it registers no hooks, adds no admin screens, enqueues no CSS or JavaScript and runs no queries. A site that only uses custom fields carries the custom fields code and nothing else.<\/p>\n\n
On the front end, the parts that are on stay out of the way too. Field values are ordinary post meta, so reading them is a normal get_post_meta()<\/code> call. The SEO part prints a handful of tags in <head><\/code>. A form loads its assets while it renders, and only the ones it needs: no form on the page means no CSS and no JavaScript, and a form without a date field does not load the date picker.<\/p><\/dd>\nCan I run it alongside my current plugins?<\/h3><\/dt>\nYes. Ultivo Toolkit never switches another plugin off. Its SEO part deliberately prints nothing while Yoast, Rank Math or All in One SEO is active, and where a feature overlaps with something you already have, the dashboard says so and lets you decide.<\/p><\/dd>\n
Where are values stored?<\/h3><\/dt>\nIn ordinary post meta, as field_name<\/code>, with a hidden _field_name<\/code> recording which field wrote it. Which meta table depends on where the field group appears: post meta, user meta, term meta or options. Repeater rows become separate keys like name_0_subname<\/code>. That means your data stays readable and queryable with plain WordPress functions.<\/p><\/dd>\nCan I register field groups in code?<\/h3><\/dt>\nYes, with ultivo_add_local_field_group()<\/code> on the ultivo\/init<\/code> action. The Tools page exports any existing group as ready-to-paste PHP. Local JSON does the same thing automatically for every group.<\/p><\/dd>\nCan I migrate from ACF?<\/h3><\/dt>\nYes. Tools \u2192 Migrate from ACF converts field groups from the database and from the theme's acf-json<\/code> folder. Field keys are preserved, so no content has to be migrated with them.<\/p><\/dd>\nWho can see the Ultivo Toolkit screens?<\/h3><\/dt>\nAdministrators. Every screen requires the manage_options<\/code> capability, and so does the content behind it: field groups, forms and entries. All of them can change how the site behaves.<\/p><\/dd>\nWhat happens when I deactivate or delete the plugin?<\/h3><\/dt>\nDeactivating stops everything immediately. No menus, no hooks, and a custom login URL goes back to wp-login.php<\/code>, while your data stays untouched. Deleting the plugin also leaves your data in the database on purpose, so that reinstalling picks up exactly where you left off. If you want it gone for good, remove it yourself before deleting.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.0<\/h4>\n\n\n- First release.<\/li>\n
- Note: the Ultivo Toolkit screens and everything behind them (field groups, forms and entries) require the
manage_options<\/code> capability. Editors and authors have no access, because all of these can change how the site behaves.<\/li>\n<\/ul>","raw_excerpt":"The WordPress developer toolkit: custom fields, forms, SEO and site utilities in one plugin, without external dependencies.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361926","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361926"}],"author":[{"embeddable":true,"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/royaar"}],"wp:attachment":[{"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361926"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361926"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361926"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361926"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361926"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/ibo.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361926"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}