Ultivo Toolkit – Custom Fields, Forms, SEO & Enhancements -- WordPress 插件

开发者	royaar
更新时间	2026年10月17日 07:13
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

Every WordPress build starts the same way: a field plugin, a form plugin, an SEO plugin, and a handful of one-trick utilities for the things WordPress does not do. Ultivo Toolkit is those four, in one plugin that shares one interface, one set of conventions and one place to switch things on and off. The documentation is at ultivotoolkit.com/docs: a reference for every field type, the template functions, and a guide for moving over from ACF. Every part is optional. Turn off what you do not need under Ultivo Toolkit → Settings and it registers nothing at all: no menus, no screens, no hooks, no queries. A plugin that does four things is only heavy if all four are running. Nothing you built disappears when you switch one off: the data stays put and comes back the moment you switch the feature on again. 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

Forms

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

SEO Enough to launch a site with, and nothing more. No traffic lights, no scores.

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

Site enhancements Seventeen switches for the things you set up on every site: cleanup of the <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), and ultivo_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_name plus a hidden _field_name pointing at the field key; repeater rows as name_0_subname. Nothing is serialised into a blob, so WP_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.

Pro Pro adds Blueprints, Flexible Content and the Clone field, and is available at ultivotoolkit.com. Launch offer: 10% off your first year with code LAUNCH10, until 31 October 2026. Coming from ACF? Ultivo Toolkit stores values in exactly the pattern ACF uses, and Tools → Migrate from ACF converts your field groups from the database and from the theme's 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.

1.6.0 A repeater with twelve rows was forty-eight input fields stacked on top of each other. You could never see more than two or three rows at once, you lost track of where you were, and dragging a row to a new position meant dragging it somewhere off screen.

A repeater can now point at one of its own sub fields to act as the row label. Rows that have a value for it open collapsed, so twelve rows read as twelve lines and you click open the one you need.
The heading follows what you type, so it is already right before you save.
A row with nothing in that field stays open. A row you just added does not fold itself away before you have filled anything in, and a repeater on a public form behaves exactly as it did.
Choice fields show the label you picked, not the key stored behind it.

Leave the setting empty and nothing about your repeaters changes. 1.5.1 Ultivo Toolkit now runs on PHP 7.4 or later. It asked for 8.2 before, and that number was a decision about which PHP versions we wanted to be on rather than something the code needed. If your host is on 7.4, 8.0 or 8.1, you can install it now. Nothing in the code changed for this. The requirement was checked against the real PHP 7.4 parser instead of a compatibility tool: every file in the plugin parses, WordPress boots on it, and the whole test suite gives the same result on 7.4 as it does on 8.2. The release build now refuses to ship if any file stops parsing on the version the plugin claims to support. WordPress 6.0 remains the minimum. 1.5.0 The setup wizard sends you to the dashboard when you finish it, and until now that screen said "Welcome back" to someone who had been here for thirty seconds. Most of this release is about that first minute. The dashboard:

A fresh install gets a start screen instead: one card, one sentence, and one button that takes you to the thing worth doing first. It stays until you have made something, or until you click "I know my way around" and send it away for good. That is per user, so dismissing it does not hide it from anyone else.
The heading and the sentence follow the button. With only Forms switched on it talks about forms, not about field groups you cannot make.
A button only appears if you are actually allowed to use it. Field groups and forms need the administrator capability to create, while the dashboard itself is visible to editors, so an editor used to get a button that answered "you are not allowed".
The cards below flow in columns instead of a grid. A grid row is as tall as its tallest card, so a short card left a hole under it, up to three hundred pixels wide when Recent submissions was full and Recently edited was empty.
Loose ends no longer stretches to the height of the card beside it. It is empty on a healthy site, so that was an empty bordered box of exactly the wrong size.

Other:

Links in the admin point to ultivotoolkit.com. The old address keeps working and always will.
The description on wordpress.org no longer opens the Pro pitch before it has told you what the plugin does.

1.4.0 Field groups, forms, post types, taxonomies and options pages already had an active state, but nothing on screen said which items were on and there was no way to switch one off without opening it. That is what most of this release is about. Switching things on and off:

All five list screens have a Status column with a switch in it. One click, saved as you click, nothing to confirm.
The same switch, labeled Active, sits next to the Update button in the field group and form builders, so you can switch something off while you are working on it.
Those screens drop what now said the same thing twice: the Published and Draft links above the list, the "Draft" label behind a title, and the month filter. All and Trash stay, but only once something is actually in the trash.
Quick Edit is gone from those five screens. It offered Scheduled, Pending Review and Password protected, and picking one of those takes a form off your site without saying so.

Conditional logic:

The operators read as words now: is equal to, is not equal to, contains, is greater than, is less than.
When the field you compare against has fixed choices, the value is a dropdown of those choices instead of a text box, so there is no key to mistype. A stored value that is no longer one of the choices keeps its place in the list instead of quietly becoming the first one.
The field group builder has the same condition builder as the form builder, including "and" between rules in a group.

Enhancements:

The screen is a list with a panel. The seventeen modules sit in a sidebar under Content, Media, Site and Security, each row with its own switch, and the panel on the right shows the one you picked. It was four stacked cards and seven Save buttons before, about two screens tall.
A module with its own settings screen shows a Configure link there.
Hide login shows your login address in the panel for as long as the module is on, not only in the second after you switch it on.

Entries:

The row of form links above the list is gone. It could only ever show six forms, so it could not do the job. The dropdown in the filter bar now carries each form's entry count instead.

Other:

Content ordering, Admin columns and Enhancements have a heading that says which screen you are on.
The free version no longer offers ACF users a field type it does not have.
A field that depends on another setting stayed hidden when your browser restored a dropdown to an earlier choice on reload, so you could see "Only selected post types" above nothing.

1.3.0 Content ordering, Admin columns and the Menu Organizer opened on an empty screen with nothing but a dropdown. All three now put what you can work on in a list, and the thing you picked next to it. Content ordering:

Post types and taxonomies sit in a sidebar, each with the number of items in it, so you can see what is there before you choose.
A search box above the list. Type a few letters and the list narrows to what matches, parents included, so you can still see where something sits.
Child pages are indented under their parent, and dragging a parent takes its children along instead of leaving them behind.

Admin columns:

You can set the width of a column, in pixels or as a percentage. Leave it empty and WordPress decides, as before. Widths apply on screens wide enough to show the table, so nothing changes on a phone.
You can give a column your own heading, for when "Title" is not what that column holds on your site.

Menu Organizer:

The edit panel no longer opens between the rows and pushes everything below it out of the way. It sits on the right and follows you as you scroll, so the list stays where it was. On a long menu this was the difference between editing and looking for your place again.
The list of roles is written out once instead of under every item.

Fixes:

The tab said "Order" while the module is called Content ordering everywhere else.

1.2.1

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.

1.2.0 Forms:

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}.

Entries:

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.

Fixes:

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.

1.1.0 Forms:

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.

Entries:

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.

Fixes:

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_DEBUG on, 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.

1.0.0

First release.
Note: the Ultivo Toolkit screens and everything behind them (field groups, forms and entries) require the manage_options capability. Editors and authors have no access, because all of these can change how the site behaves.

Ultivo Toolkit – Custom Fields, Repeater, Options Pages, Forms & SEO

标签

下载

详情介绍:

安装:

屏幕截图:

常见问题:

更新日志: