| 开发者 |
sandipbiswas123
masssoftware devmanishpathak massoft |
|---|---|
| 更新时间 | 2026年10月12日 20:44 |
| 捐献地址: | 去捐款 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
get_field-style helpers.
Use it as a standalone custom field builder, register custom post types and custom taxonomies, or migrate from ACF (Advanced Custom Fields) with the built-in import tool — location rules, conditional logic, repeaters, and flexible content layouts carry over.
Highlights
{mfb_field} Dynamic Data tags + Massoftind Repeater query loop (coexists with ACF Pro {acf_…})massoftind_fb_get, have_rows, optional get_field aliases){acf_…} dynamic tags and repeater query loops after switching from ACF Promassoftind-fb/field binding source_blank, _self, _parent, _top) in the Media sidebar$img['external_url'] and $img['target'] (or massoftind_fb_the_gallery())massoftind_fb_get() / massoftind_fb_update()massoftind_fb_have_rows() / massoftind_fb_the_row() / massoftind_fb_sub_field()massoftind_fb_image() / massoftind_fb_gallery() / massoftind_fb_the_gallery()massoftind_fb_terms() / massoftind_fb_date() and moreget_field, have_rows, …) can be enabled in Settings for existing theme code.
Bricks Builder
When Bricks Builder is active (Settings → Bricks Dynamic Data on by default):
{mfb_field_name} in Dynamic Data (group Massoftind Custom Fields & Field Builder){mfb_option:field_name}{mfb_row:sub_field} inside the loop{acf_…} tags are not changed; rebind templates to {mfb_…} only when migrating fields{acf_…} tags and ACF repeater query loops are resolved by Massoftind — no Bricks template editsparent_child names in the pickermassoftind-field-builder folder to /wp-content/plugins/, or install via Plugins → Add New → Upload Plugin.No. Massoftind Custom Fields & Field Builder is a standalone custom field builder with its own metabox UI, repeaters, relationship fields, and theme helpers.
Yes. With real ACF (free or PRO) active, open Field Builders → Migrate from ACF, select field groups, and import them. Location rules, conditional logic, repeaters, and flexible content layouts are converted; unsupported field types are reported.
Yes. It is a full custom fields plugin on its own — field groups, metabox UI, repeaters, flexible content (Layout Blocks), options (Site Sections), custom post types, and custom taxonomies. Optional ACF compatibility helpers ease theme and page-builder migration.
Yes. Use block bindings (massoftind-fb/field) to bind core blocks to field values, the Massoftind Field Group block for modal editing, and the Custom Blocks registry for named Gutenberg blocks tied to field groups.
Yes. Field Builders → Post Types and Taxonomies let you register CPTs and taxonomies from the admin (labels, supports, rewrite rules, and more) without extra code.
As prefixed post meta (and option storage for Site Sections). Field-group definitions use an internal custom post type.
Open the Gallery field → Edit on a thumbnail → in Attachment Details set optional Link URL and Link Target. Values appear in Image Array as external_url and target.
Yes. Enable Allow Multiple, then set optional Minimum Selections and Maximum Selections (0 = no limit).
Yes. Use Tools → Export and Import for JSON field-group definitions (and related Post Types / Taxonomies / Site Sections when present).
Yes, optional. Enable under Field Builders → Settings. Endpoints require authenticated users with the right capabilities.
No.
Yes. With qTranslate-X or qTranslate-XT, text-like fields (including Markdown and Address sub-fields) use Language Switching Buttons. Helpers return the active language on the front end — including Bricks and Elementor dynamic tag output via massoftind_fb_format_value.
Yes, when those plugins are active (SEO variables, sitemap exclusions, import/export field exposure).
Yes. Fields register for translate/copy; WCML product translation UI is supported. Override under WPML → Settings → Custom Fields Translation.
Yes. Bricks Dynamic Data shows a Massoftind Custom Fields & Field Builder group with {mfb_field_name} tags for all 54 field types — including Table, Phone, Country, Address, Tags, Markdown, and Image Hotspot (readable text or image output). While ACF Pro is active, Bricks’ {acf_…} tags stay native to ACF. After you deactivate ACF and import field JSON into Massoftind, enable Settings → Bricks ACF tag alias (default on) so the same {acf_…} tags and ACF repeater loops keep working through Massoftind — no Bricks template or core edits. For repeaters you can also use Query Loop type Massoftind Repeater and {mfb_row:sub_field}.
Yes. With Elementor active, Dynamic Tags include a Massoftind Custom Fields & Field Builder group (text, image, URL, gallery, color, number) with all 54 field types in the picker — including Table, Phone, Country, Address, Date Range, Slug, Tags, Markdown, Post Types, Icon Picker, and Nav Menu. Image Hotspot works in Image/URL tags. Bind Heading, Image, Button, and Gallery widgets to your fields — including Site Sections / Options. Keep field names when migrating from ACF; use the Massoftind tags for a reliable CMS workflow (Elementor Pro’s ACF tags remain best-effort via the optional ACF shim).
[massoftind_fb_form] shortcode, massoftind-fb/form block, and related Settings toggles.massoftind-fb/field) — bind core blocks to MFB field values.wp mfb local-json status|push|pull [--force]; Tools documents deploy sync.menu_order on the front end for enabled post types (Custom Post Order parity) so theme WP_Query loops no longer need a manual orderby. WooCommerce product queries stay untouched; term ordering remains admin-only (WPML-safe).massoftind_fb_get( 'field', 'option' ) (and matching get_field / massoftind_fb_field) instead of post-context getters._thumbnail_id only into #postimagediv; our stable metabox now receives the same HTML so the thumbnail saves and shows.#postimagediv image max-width styles (full-width photo); constrain thumbnail to 266px sidebar size and show box header + Remove link like core.postimagediv for media-editor.js; enqueue media-editor and bind the modern frame.already_sorted (which dropped side boxes); register Featured Image under our own metabox id so postimagediv removers cannot wipe it.do_meta_boxes (when other plugins remove it), force for all custom show_ui post types, place box at high priority near Publish.get_field( $name, get_queried_object() ) / massoftind_fb_get() accept WP_Term objects (ACF parity) so taxonomy term banners and term meta render on archives.massoftind_fb_format_value.<img class="menu_svg_image" src="….svg"> to sanitized inline <svg> on the front end (no theme edit). Works even when Allow SVG Uploads is off.get_field( $name, $item ) / massoftind_fb_get() accept menu item objects (ACF parity) so Appearance → Menus fields like Menu SVG resolve on the front end.->ID from objects instead of falling back to the current page.nav_menu_item return a URL string (unless Return Format is Image Array) so existing <img src="' . $icon . '"> theme filters work without edits.nav_menu) — attach fields to Appearance → Menus items (ACF-compatible, e.g. Menu SVG).nav_menu / menu_item / nav_menu_item location rules; values save as nav_menu_item post meta for get_field( $name, $item_id ) (Elementor Pro, Bricks, themes).massoftind_fb_format_value on get.get_field() values run through massoftind_fb_format_value again (qTranslate [:lang] decode).have_rows( 'group_field' ) inside a repeater/group (e.g. video_section in banner_section) no longer drops associative group values — hero video loops work again.{acf_item_repeater_item_heading} render again (Mission / Why Live Local empty boxes).get_field() reads the active Bricks Massoftind loop row so Bricks' native ACF provider gets sub-field values.get_sub_field() keeps numeric attachment IDs (instead of converting them to arrays) when the sub-field definition is missing, so wp_get_attachment_image() works with Image ID return format.massoftind_fb_attachment_image() / massoftind_fb_get_attachment_image() helpers that render SVGs and other attachments that wp_get_attachment_image() skips.{mfb_*} / group field tags (e.g. Our Story after Mission/Vision).star_rating_field maps to native Star Rating so admin no longer shows "This field type is not available."star_rating fields outputs star HTML instead of a bare number.[current_year]) run through do_shortcode() when rendered in Bricks dynamic data and via massoftind_fb_get().{acf_*} in Bricks Heading/Text/Link element settings before render (catalog + service sections).{acf_*} Site Section / global fields resolve when called without :option — get_field() and get_field_object() now fall back to wp_options (footer, homepage sections, contact info).footer_connect_section_heading) read from Site Section option storage.massoftind_fb_format_value on options.preg_split(): array given) — remove early render_tag hook at priority 5 that returned image arrays before Bricks' ACF provider runs.filter_element_settings on the Logo element.{acf_*} dynamic tags render again — keep Bricks' native ACF provider and resolve tags early via BricksSupport (1.9.139 had disabled the provider, leaving raw {ACF_…} in templates).changelog.txt file bundled with the plugin.