MyListing plugin review and common issues

MyListing uses Vue.js for AJAX search. If search does not work: (1) check browser DevTools Console for JavaScript errors — Vue.js initialization failures prevent the search component from mounting; (2) check the Network tab for AJAX requests when typing — the search request must reach the server and return valid JSON; (3) a JavaScript conflict with another plugin or theme script may prevent Vue from initializing; (4) verify WordPress REST API is accessible — MyListing uses REST API endpoints for search; (5) deactivate other plugins to isolate a potential conflict.

In MyListing → Listing Types → [type] → Fields, add custom fields for this listing type. Fields must be configured in the Listing Type editor, not in the standard WordPress post editor. Each field has type (text, number, select, checkbox, date, etc.), label, and whether it appears in the submission form, listing detail page, and search filters. After adding fields, flush the submission form cache by visiting Listing Types editor → Save. Verify the submission form is used for this specific listing type (the form shortcode or page must reference the correct listing type).

MyListing’s Vue.js architecture is JavaScript-heavy. Optimization strategies: (1) enable object caching (Redis/Memcached) to cache MyListing’s PHP data queries; (2) use a CDN for static assets — MyListing’s JavaScript bundles are large; (3) defer non-critical JavaScript loading; (4) optimize map loading — Google Maps is a significant performance cost, consider lazy-loading maps on scroll; (5) use a performance plugin (WP Rocket, Perfmatters) configured to work with MyListing’s Vue.js requirements; (6) avoid unnecessary plugins that add additional JavaScript.

In WordPress Admin → Listing Types → Add New, create a “Restaurant” listing type. Add custom fields: Cuisine Type (select/taxonomy), Price Range (select: $, $$, $$$), Opening Hours (hours fields), Phone Number (text), Website URL (text), Menu URL (text), Outdoor Seating (checkbox). Configure search facets: which fields appear in the search/filter sidebar. Design the listing page layout: drag field blocks into the listing template sections (header, details, sidebar). Set the listing icon (fork-and-knife dashicon for restaurants). New listings created with the Restaurant type will use these fields.

MyListing has native WP Job Manager integration. Install WP Job Manager plugin and MyListing will recognize it. In MyListing → Settings → Job Board, enable WP Job Manager integration. Job listings from WP Job Manager appear alongside regular MyListing listings in search and category views, with job-specific fields (company, job type, location, salary) displayed in the search results. You can create a dedicated Job Board listing type in MyListing that maps to WP Job Manager’s data, providing a unified directory + job board experience.

MyListing’s ThemeForest listing explicitly notes that WPML multi-language support is not yet implemented. The theme is translation-ready (can be translated to a single non-English language using Loco Translate or .po/.mo files), but it does not support displaying content in multiple languages simultaneously via WPML. For international directories requiring multiple language versions, this is a significant limitation. Consider Directorist or GeoDirectory (both with WPML support) if multilingual directory support is required.

MyListing’s strengths are its Vue.js-powered UX, multi-listing-type flexibility, and Elementor design freedom. Listeo’s strengths are its comprehensive built-in booking system, vendor marketplace with Stripe split payments, and more complete monetization toolkit out of the box. MyListing is better for complex multi-type directories where different categories need fundamentally different data structures and a modern search UX. Listeo is better for booking-heavy directories (accommodation, services, rentals) where the integrated booking and payment system are core business requirements.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.