Listivo 2.3.86 – Classified Ads & Directory Listing WordPress

I installed Listivo on a clean WordPress 6.5 setup with PHP 8.2, MariaDB, Redis object cache, and the usual “please don’t explode” plugin stack. And yeah, Listivo works. Not “works after three evenings of swearing” — actually works. Demo import, listings, search fields, user dashboard, monetization bits. I tested it as a GPL package too, and the theme itself had no silly domain limit. Unlimited Website Usage in the normal GPL sense: install it where you want, but don’t expect official support or auto-updates without a valid vendor license.

Activation is mostly about vendor services: updates, support, maybe demo/import convenience depending on the package. I didn’t have to hack anything. Manual update is boring: upload the new ZIP via Appearance -> Themes or push it through SFTP to /wp-content/themes/listivo/, then check child theme overrides before celebrating.

What I actually liked

The best part of Listivo is the listing system. Custom fields are managed from the theme panel, not scattered across five abandoned plugins. You can build fields for cars, real estate, services, whatever, then attach them to listing types. That saves time.

Elementor integration is also decent. The homepage, listing archive blocks, CTA sections, and hero search can be moved around without touching PHP. For clients who insist on changing button labels at midnight, that’s a lifesaver.

Most visual stuff lives in Listivo Panel -> Design and Elementor templates. Typography, colors, listing cards, header variants — all fairly reachable. Not elegant, but reachable.

The ugly bits nobody puts in the sales page

I opened DevTools -> Network and immediately saw the theme pulling multiple font weights I never used. Classic. On my demo, I killed that from Listivo Panel -> Design -> Typography by switching to system fonts, then checked the waterfall again. Much better.

The DOM is heavy. Listing cards are stuffed with wrappers inside wrappers like someone got paid per <div>. On mobile archive pages, Lighthouse screamed about layout shifts. I fixed most of it by forcing image dimensions in the card template and adding CSS in the child theme:

.listivo-listing-card img {
  aspect-ratio: 4 / 3;
  object-fit: cover;
}

Not genius. Just the boring fix that should have shipped.

What breaks when you “optimize” too hard

If you delay JavaScript with WP Rocket or LiteSpeed Cache, Listivo search filters can stop firing. The dropdowns look alive, but AJAX just sits there like a dead fish.

My fix in LiteSpeed was:
LiteSpeed Cache -> Page Optimization -> JS Settings
Exclude these handles/paths from delay:

jquery-core
jquery-migrate
elementor-frontend
listivo
listivo-search

Then I checked Console. Before the fix I had jQuery is not defined and one lovely undefined filter object. After excluding jQuery and the theme search script, AJAX filtering behaved again.

Also, don’t combine all CSS blindly. The mobile menu icon disappeared once because the icon font loaded too late. I hate that bug because it looks like “client broke website” but it’s just optimization being stupid.

Builder vs PHP surgery

Here’s the line: Elementor can handle layout sections, hero blocks, text, buttons, and most landing-page nonsense. Listivo Panel handles fields, listing types, packages, monetization, basic colors, header style, and typography.

But when you want to change the actual listing card markup, stop clicking around. You’ll be in PHP. Look under:

/wp-content/themes/listivo/templates/
/wp-content/themes/listivo/templates/partials/

In my child theme I overrode the listing card partial instead of editing the parent theme, because I still have some self-respect. For deeper changes, check theme setup classes under something like:

/wp-content/themes/listivo/inc/

The listings are stored as WordPress posts, usually in wp_posts, with field values dumped into wp_postmeta. That means complex filtering can get nasty fast. If you create 40 custom fields and expect instant search on cheap hosting, congratulations, you invented pain.

My dumb workaround that worked

One client wanted “featured” listings to always appear first, but only inside one category. The panel didn’t give me the exact logic. So I hooked into pre_get_posts in functions.php, checked the taxonomy query, then sorted by a custom meta key first and date second.

Dirty? A little. Stable? Yes. Better than installing another “advanced sorting” plugin from 2017? Absolutely.

add_action('pre_get_posts', function ($q) {
    if (is_admin() || !$q->is_main_query()) return;
    if (is_post_type_archive('listivo_listing')) {
        $q->set('meta_key', 'featured');
        $q->set('orderby', [
            'meta_value_num' => 'DESC',
            'date' => 'DESC'
        ]);
    }
});

Test it properly though. Meta queries on big directories can become a database campfire.

FAQ

Why do filters break after caching?

Because delayed JS kills the order. Exclude jquery-core, elementor-frontend, and Listivo search scripts from delay/defer.

Can I edit listing cards in Elementor?

Partly. Layout blocks, yes. Real card markup usually means child theme overrides in /templates/partials/.

Is Listivo too heavy for shared hosting?

For small directories, fine. For 20k listings with many meta fields, no. Use object cache and decent MySQL.

Does GPL usage need a license key?

The theme can run without domain limits. Official auto-updates, support, and vendor services still need a real license.