Listdom Developer Data Structure Documentation

Why this matters

If you build integrations, migrations, or reporting, you need to know which entities Listdom persists in native WordPress objects and which ones are mirrored in custom tables.

Custom post types (constants)

Defined in LSD_Base constants:

• listdom-listing
• listdom-shortcode
• listdom-search
• listdom-notification
• listdom-order
• listdom-recurring
• listdom-plan
• listdom-coupon

Taxonomies (constants)

Defined in LSD_Base::TAX_*:

• listdom-location
• listdom-category
• listdom-tag
• listdom-feature
• listdom-attribute
• listdom-label
• listdom-tax

Custom database tables

Created in LSD_Plugin_Hooks::db_update():

1. {$wpdb->prefix}lsd_data

   • id PK
   • latitude decimal(10,8)
   • longitude decimal(11,8)
   • point point
   • index on latitude, longitude

2. {$wpdb->prefix}lsd_jobs

   • id PK
   • type, sub_type, data
   • priority, runs
   • run_at, created_at, updated_at
   • index on run_at

Meta usage patterns (verified examples)

• User meta: lsd_token, lsd_login
• Term meta: lsd_icon, lsd_disabled_icon
• Listing meta examples: lsd_latitude, lsd_longitude, lsd_price, lsd_address, lsd_gallery, lsd_contacts, lsd_related_listings

These examples are confirmed usage points, not a guaranteed exhaustive contract.

Data model summary

• Listings (listdom-listing) are the core entity.
• Geospatial data is mirrored into lsd_data for map/search operations.
• Classification is handled by Listdom taxonomies.
• API auth tokens are stored in user meta (lsd_token).