Listdom 6.4.0 gives connected tools a more complete way to prepare and manage directory listings, while keeping review and publication separate. It also brings an optional compact admin menu, more precise search-form spacing, richer Booking filters and sorting, and improvements to maps, listing skins, and membership activation.
The release matters in different ways depending on how you run your directory. Administrators gain a clearer management experience. Developers can build a draft-first integration around declared fields and permissions. Directories using the Booking add-on can distinguish total capacity, guest capacity, and remaining inventory when helping visitors find a suitable option.
Prepare a listing, review it, then authorize publication
The expanded native WordPress abilities support a complete listing workflow rather than stopping after a title, category, and description. A compatible integration can discover the site’s actual supported fields, resolve existing terms, validate the proposed content, save a draft, read back what was stored, and apply corrections before explicitly requesting publication.
For example, an assistant can prepare a café listing with its address, hours, contact information, configured attributes, and accessible gallery images. The useful next step is to inspect that saved draft: is the café in the right category, are the hours complete, and are the images in the intended order? Publishing is a separate authorized action, not an assumed consequence of preparing the listing.
The practical sequence is:
- Discover the site’s writable fields and required values, including category-specific custom attributes.
- Resolve the intended category and other eligible terms. Create a missing term only when explicitly authorized.
- Validate the content, create the draft, and retain its returned ID and edit link.
- Review the saved values, make approved corrections, then request submission or publication with the appropriate permissions.
Updates preserve fields omitted from the request. An integration can change an address without replacing unrelated hours, gallery images, or attributes. Explicit removal has its own declared input rules; removing an image from a gallery does not delete its media-library file. Stable creation request IDs also help an integration identify a completed creation instead of inserting a duplicate after an uncertain response.
Membership and moderation rules remain part of the workflow. A membership must belong to the listing author and satisfy package restrictions. Premium Labelize labels still require eligible access. Managed drafts do not trigger new-listing activity merely because they have been saved; BuddyPress activity requires actual public publication, and Network policies continue to govern submission and export.
These native abilities require WordPress 6.9 or newer and an authenticated, compatible client. Listdom does not bundle an MCP server or automatically connect an assistant. The abilities themselves do not require Webilia Credits or YBee, and updating Listdom does not grant an integration new publishing privileges. Older supported WordPress versions continue running Listdom without this integration.
Developers can follow the native abilities guide for discovery, field policies, retry behavior, and the distinction between these operations and existing REST routes. REST category changes also keep the listing’s primary category synchronized with its category relationships.
Inspect settings and diagnose a directory without guessing
Administrative abilities make supported settings discoverable and give authorized integrations a defined way to inspect directory configuration. Core and active owning add-ons declare which fields can be read or changed. Updates use a fresh revision and a preview-and-verify sequence, rather than blindly replacing an entire settings object.
This boundary is especially useful when diagnosing a display issue. An integration can inspect supported saved-view settings, listing visibility, media information, or frontend submission readiness before suggesting an action. A diagnostic result is evidence about the declared configuration; it is not proof that a visitor completed checkout or that a page looks correct in a browser.
Explicitly approved repairs stay narrow. Display adjustments cover supported built-in Pro Grid and List views. Thumbnail repair creates selected missing registered image sizes from available originals; it does not replace the originals or regenerate the entire media library. Credentials are not exposed as ordinary readable settings. Local Logic, for example, reports whether its token is configured without revealing or changing that token.
Choose a compact administration menu
If your WordPress sidebar has become crowded, enable Listdom → Settings → Advanced → Admin Menu → Compact Menu. Listing management moves under Listdom → Listings, with header tabs for All Listings, Custom Fields, Categories, Locations, Tags, Features, and Labels.
The default remains disabled. Existing links and stored listing data do not need migration, and the tabs respect the configured labels and the current user’s permissions. To create a listing, use the existing Add Listing button. Disabling Compact Menu restores the standalone Listings menu.
The wider interface update improves admin icons, notification presentation, dashboard spacing, and frontend forms. Supported add-on and payment menus fit the updated navigation, while their availability still depends on the installed products and selected payment engine.
Match Booking searches to the inventory visitors need
Booking 3.6.0 expands both visitor search fields and the fixed filters on a results shortcode. The important distinction is what each field measures:
- Capacity filters total capacity.
- Guest capacity filters stored guest capacity for eligible date-range items.
- Remaining slots filters remaining inventory for supported booking setups.
- Available between, Price range, and the Available only switch provide the corresponding date, price, and availability constraints.
Adults and Children remain useful for the party a visitor wants to accommodate. Total Capacity is not a substitute for those requested guest counts. Existing forms can retain their legacy date field, while new forms should use Available between.
Shortcode filters can restrict the Booking Setup, availability, capacity basis, and price basis. Minimum price, Maximum price, and Base price are different measures; they are not choices between per-night and per-ticket pricing models. New sorting choices include Maximum booking price, Next available, End date, Start time, and End time alongside existing booking sorts.
Fixed shortcode constraints and visitor inputs must match the same eligible bookable item. A listing cannot satisfy a cheap-price filter with one item and a capacity requirement with a different item. Visitor searches also cannot remove the shortcode’s saved restrictions.
The update refreshes stale availability and next-available values and respects meaningful zero bounds, including free-price and zero remaining-slot searches. Showing sold-out inventory does not make it bookable. Native booking abilities also support availability checks, creation, authorized reads, and eligible cancellation; a paid booking can still require checkout before confirmation.
Start with the Booking search and filtering instructions, then test a listing with several bookable items so you can see how the combined conditions behave.
Activate manual memberships when they are ready
Membership 4.0.0 corrects the activation timing for memberships created by an administrator. Preparing and saving a draft does not activate access, complete its associated order, or send an activation notice before the record is ready.
Select a valid user and package, check any dates, and publish the membership. If default dates were left empty, they are calculated at activation; explicit dates remain unchanged. If a record was already published before valid user or package details were supplied, correct and update that record instead of creating a second membership.
Activation actions run once. Repeated saves do not create duplicate activation orders or notices, including for older memberships that were already notified. Managed listing assignments also retain the membership’s ownership, category, capacity, and module restrictions. For the distinction between the plan you offer and the user’s access record, see managing Listdom membership packages.
More consistent forms, maps, and listing layouts
Search styling now separates ordinary field padding from Checkbox, Radio & Range Padding in Listdom → Settings → Customizer → Forms → Search. This lets you give option groups and range controls room without making every text input equally wide. Four-sided zero values remain meaningful. The Booking Available only switch is separate from this setting, and changing the primary color does not overwrite every independently configured component color.
Maps receive fixes for Mapbox tiles, map resizing in the listing editor, and info-window styling and dimensions. Custom template directions buttons retain their configured appearance, and stacking fixes help maps, search dropdowns, and dialogs appear in the intended order. Check both the listing editor and a public map after updating cached assets.
Other frontend corrections address rating-star order and authentication notice spacing. The Table skin improves spacing and corner behavior; the Timeline shows empty results consistently and clears the message when matching listings return. Accordion listing buttons behave more predictably too. These fixes are worth checking with your own custom templates, right-to-left layouts where used, and narrow screens.
Elementor 4.1.0 brings role tabs to inline Authentication widgets, including tab labels, role selection, and styling. Tabs remain scoped to their own widget instance. The release also improves widget styling, saved-view diagnostics, and generated CSS refresh after the styling-variable update. Divi 3.7.0 improves Divi 5 attribute-table width controls and admin menu ordering.
Matching ecosystem releases
The release includes updates only for products with their own shipped changes. Many add-ons now declare supported settings for administrator integrations; this does not expose every option, grant unrestricted access, or include the add-on in Free Core.
The settings integration reaches the following releases, alongside Booking and Membership discussed above:
- Ads 2.7.0
- Advanced Map 3.7.0
- APS 2.6.0
- Auction 2.4.0
- BuddyPress 2.1.0
- Multiple Categories 2.7.0
- Claim 3.1.0
- Compare 3.1.0
- Favorites 2.7.0
- Franchise 3.0.0
- Google Places 1.5.0
- Jobs 2.7.0
- KML 2.6.0
- Labelize 2.9.0
- Local Logic 1.3.0
- Rank 2.2.0
- Reviews 3.1.0
- SMS 2.1.0
- Stats 2.1.0
- Paid Member Subscriptions 2.4.0
- Team 2.7.0
- Top Up 2.9.0
The following apps extend the same supported settings approach to their respective products:
- Mobile Application 2.2.0
- Network 2.4.0
- White Label 1.4.0
Additional refinements make these integrations more predictable. APS settings discovery does not initialize saved AI profile options. Claim respects an explicitly cleared payment-plan selection. Paid Member Subscriptions applies the selected audience’s category policy in visibility diagnostics, and Reviews provides native public reads and validated submissions without bypassing normal permissions or moderation. BuddyPress, Labelize, and Network retain the publication boundaries described above.
Bricks 1.7.0 and Connect 2.1.0 update admin navigation; Auction, Claim, Jobs, KML, Reviews, and the builder integrations also adjust menu placement where applicable. Bridge 1.9.0, Excel 2.8.0, Google Places, Network, and White Label refresh their relevant interface icons or notifications. Listdom Pro 6.4.0 stays aligned with Core and refreshes feedback icons.
Listdomer Theme 5.0.0 and Listdomer Core 5.0.0 improve frontend styling, settings controls and compatibility, demo search usability, and admin notice placement. Selected Elementor header/footer styles load before page rendering; Canvas layouts continue to omit theme headers and footers. The Directory Toolkit 2.6.0 and Real Estate Toolkit 2.6.0 update their bundled add-ons to the matching ecosystem releases.
Check the workflows your directory uses
Back up your site and test on staging before updating a live directory, particularly where memberships, paid bookings, or custom templates are involved. Update the active owning add-ons alongside Core when you need their new functionality; a Core change alone does not install an add-on update.
Try a listing search with results, no results, and results again. Check the maps and skins you use, an inline authentication form if configured, and a manually created membership. Booking directories should test fixed shortcode restrictions together with visitor criteria. Integration developers should create and inspect a draft before testing an authorized publication request.
The guide to updating Listdom and its add-ons safely provides the general update process. For the released-version record, consult the Listdom changelog and the matching product histories.
