Ultivo Toolkit – Custom Fields, Forms, SEO & Enhancements
| 开发者 | royaar |
|---|---|
| 更新时间 | 2026年9月13日 22:21 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
LAUNCH10, until 30 September 2026.
Nothing 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.
Custom fields
Build field groups in a visual builder and attach them to anything with location rules.
- 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
- Location rules with AND/OR groups: post type, page template, individual page, taxonomy, user role, options page or block
- Conditional logic per field, so a field only appears when another has the right value
- Validation rules (minimum and maximum length, or a regex pattern with your own message), enforced both in the browser and on the server
- Register post types, taxonomies and options pages from the admin, with a visual icon picker
- Local JSON: field groups are written to
uploads/ultivo-json/and also read from{theme}/ultivo-json/, so they can travel through version control, with a Sync button when a file is newer than the database
- Drag-and-drop builder with a live canvas: drop a field, see what the visitor will see, or start from a ready-made contact, quote, application or booking form
- Text, email, phone, number, date, select, checkbox, radio, file upload, hidden fields, repeatable groups and free HTML, in one or more columns
- Submissions are stored in WordPress and readable per entry in the admin; a form can send several notifications, so the visitor gets a confirmation and you get the alert
- Send visitors to your own thank-you page after a submission, or keep them on the page with a message
- Spam protection with Google reCAPTCHA v2, reCAPTCHA v3 or Cloudflare Turnstile. Set the keys once, then decide per form
- Optional AJAX submit, so a form in a popup shows its confirmation instead of reloading the page underneath it
- Uploads are stored outside the media library and can only be downloaded by someone who may edit the entry
- Close a form by hand or after a maximum number of submissions, with your own message in its place
- Search your submissions by what people actually typed, and see per submission whether the notification was sent
- Title and meta description per post, page or archive, with variables such as
%title%and%sitename%, and a live preview of the Google result - Open Graph and Twitter tags, with an image per post falling back to the featured image and then to a site-wide default
- Canonical URL, noindex, and an XML sitemap that leaves noindexed content out
- Stays out of the way: with Yoast, Rank Math or All in One SEO active, Ultivo Toolkit prints no tags of its own
<head>, 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.
For developers
- Template functions:
ultivo_field( 'title' )for one value (with an optional default), andultivo_rows( 'blocks' )to loop over a repeater or flexible content. A whole flexible field renders in one line:ultivo_rows( 'blocks' )->render( 'template-parts/blocks' ) - Coming from ACF, the classic shapes work too:
ultivo_get_field(),ultivo_the_field(),ultivo_have_rows(),ultivo_the_row(),ultivo_get_sub_field(),ultivo_get_row_layout(),ultivo_update_field(),ultivo_add_row(),ultivo_add_options_page() - Field groups in code with
ultivo_add_local_field_group(), or exported as PHP from the Tools page - Values are stored in ordinary post meta as
field_nameplus a hidden_field_namepointing at the field key; repeater rows asname_0_subname. Nothing is serialised into a blob, soWP_Query,get_post_meta()and SQL all keep working. - REST API support per field group
- Blocks can be registered in PHP with
ultivo_register_block_type()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.
acf-json 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.
安装:
- Upload the
ultivofolder to/wp-content/plugins/, or install the plugin through Plugins → Add New. - Activate it through the Plugins menu.
- A short setup wizard opens once, where you pick the features and enhancements you want. You can change every choice later under Ultivo Toolkit → Settings.
屏幕截图:
常见问题:
Why one plugin instead of four?
Because 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.
Will four plugins in one slow my site down?
Only 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.
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() call. The SEO part prints a handful of tags in <head>. 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.
Can I run it alongside my current plugins?
Yes. 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.
What is not in the free version?
Three things live in Pro: Blueprints, Flexible Content and the Clone field. Everything else on this page is in the version you are reading about, without a trial period, a row limit or a feature that stops after thirty days. There are no ads in the admin and nothing nags you to upgrade.
Am I locked into this plugin?
No, and that is a deliberate design decision rather than a promise. Values are stored in ordinary post meta as field_name, with a hidden _field_name recording which field wrote it, and repeater rows as separate keys like name_0_subname. Nothing is serialised into one blob, so WP_Query, get_post_meta() and plain SQL keep working on your content whether this plugin is installed or not. Which meta table is used depends on where the field group appears: post, user, term or options.
Is it actively maintained?
Yes. Ultivo Toolkit is developed in the open and the Pro version pays for that work, which is the honest answer to why it will still be here next year. Bugs are fixed in the free version too, not held back for a paid release.
Can I migrate from ACF?
Yes. Tools → Migrate from ACF converts field groups from the database and from the theme's acf-json folder. Field keys are preserved, so no content has to be migrated with them.
What happens when I deactivate or delete the plugin?
Deactivating stops everything immediately. No menus, no hooks, and a custom login URL goes back to wp-login.php, 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.
更新日志:
- Fixed: the Update button did nothing on a form. The hidden template that a new notification row is cloned from carried a required recipient field. Because that field is empty and out of sight, the browser refused to submit the form and had nowhere to show its message, so saving failed silently. If you are on 1.2.0 and cannot save a form, this is why.
- Start a new form from a ready-made one: Contact, Quote request, Application or Booking request. The empty canvas offers them, and they disappear as soon as you add a field yourself.
- A form can stop accepting submissions, either by hand or once it reaches a maximum you set. Visitors get your own message where the form used to be. Submissions in the trash do not count towards that maximum.
- You can see whether a notification actually went out. Sending can fail for reasons that have nothing to do with your form, and WordPress tells nobody: people end up believing a form gets no submissions while they are sitting in the list. There is now a column in the list, an explanation with the mail server's own error on the submission, and a warning on the dashboard.
- Notifications link to the submission they are about, so you can open it from the email instead of going to look for it. New placeholder
{entry_link}.
- Searching now searches what visitors typed, not just the title. The search term appears above the list as a chip you can click away, and it combines with the form filter.
- The search line above a list no longer floats loose under the tabs.
- Labels next to a checkbox line up with the text beside it.
- A form can now send more than one notification, so the visitor gets a confirmation and you get the alert. Point the To field at a form field such as
{field:email}to mail the person who submitted. The old on/off checkbox is gone: an empty list means no email is sent. - New setting: Redirect URL. Send visitors to your own thank-you page after a submission instead of showing the message on the same page. Leave it empty and nothing changes. An address on another site works too.
- A notification whose recipient does not resolve to a valid email address is now skipped instead of handed to the mailer. This matters as soon as the recipient is a form field: visitors mistype, and leave fields empty.
- The entry screen is about submissions again. An entry can no longer be edited, its date column no longer says "Published", Quick Edit is gone, and the links above the list no longer offer a status that every entry shares.
- You can see which form you are looking at. The forms with the most recent submissions appear above the list with their counts, and a dropdown filters by any form.
- The character counter and the live Google and social previews under an SEO title never updated. The field shared its id with the metabox heading WordPress generates, so the script found the heading instead of the field.
- With
WP_DEBUGon, every request logged a notice about translations being loaded too early. - The author name in the plugin list links to the site again.
- The variable button next to a field is square and lines up with the field beside it.
- The menu icon sat two pixels above the icons beside it when the admin menu is collapsed.
- First release.
- Note: the Ultivo Toolkit screens and everything behind them (field groups, forms and entries) require the
manage_optionscapability. Editors and authors have no access, because all of these can change how the site behaves.