CodeCanyon Directory Pro - WordPress Plugin

Guide to Setting Up and Using CodeCanyon Directory Pro

CodeCanyon Directory Pro is a WordPress plugin for building a directory site where visitors can search for businesses, services, professionals, places, or listings, and listing owners can add and edit their entries from the front end. This guide does not repeat the product page. Instead, it walks through installation, the initial check, page structure, shortcodes, directory fields, search, maps, pricing plans, the user account area, result validation, and troubleshooting common issues.

Directory Pro is one of those plugins where success depends less on the install button and more on the directory model itself. If you do not decide up front which listing types you need, which fields are required, how visitors will search, and what level of access listing owners should have, the site can quickly turn into a collection of disconnected pages. That is why this guide follows a practical path: first the information architecture, then installation, then settings, a working example, and final validation.

It is also worth remembering that this is a commercial plugin from the Envato ecosystem, not a simple extension from the WordPress.org repository. Before launching it on a live site, it makes sense to verify that the file is current, create a backup, set up a staging copy, and test compatibility with your theme, caching setup, language plugins, and payment flow if you need one. Do not start by importing hundreds of listings or enabling paid plans - first build one short, testable workflow.

What Directory Pro Does on a WordPress Site

The main purpose of Directory Pro is to turn a standard WordPress site into a managed listing directory. Depending on the niche, that might be a business directory, a professional database, a places directory, a vendor list, a services showcase, a local city guide, a private member directory, or a platform where users submit their own listings. From the visitor's perspective, the experience is simple: they open the directory page, enter a search term, choose a category, city, or other filter, review the listing cards, and open the detail page.

For the administrator, the logic is more involved. You need to create the directory pages, place the correct shortcode, configure listing fields, categories, the map, archive layout, the submission form, the account area, emails, publishing rules, and pricing if needed. CodeCanyon Directory Pro is clearly built around a set of ready-made pages and shortcodes. Its documentation shows listing archives, filters, signup forms, the account area, user profiles, categories, cities, the map, the carousel, and featured listing output. That is convenient because it lets the administrator build different pages without coding, but it also requires discipline: every shortcode should live on a clearly defined page with a clear purpose.

The plugin is especially useful when standard WordPress posts are no longer enough. If each listing needs an address, phone number, website, images, a map, category, city, user owner, contact form, favorites, publication status, and custom fields, a dedicated directory system is a better fit than trying to manage everything through default posts. Directory Pro also adds workflows that matter specifically for directories: claim listing, role-based access to listings, owner contact, favorites, paid or free packages, payment history, registration coupons, email templates, and front-end management through My Account.

That said, Directory Pro is not a universal replacement for a CRM, marketplace, or full geolocation platform. It runs inside WordPress and inherits the platform's constraints: theme quality, database performance, caching conflicts, careful role management, map support, and clean input data. If you need a massive directory with millions of records, complex ranking, a dedicated mobile platform, and a moderation team, you should evaluate the architecture more broadly from the start. But for a small to mid-sized directory where fast deployment, visual integration with WordPress, and front-end listing submissions matter, Directory Pro covers a lot in one package.

Who This Plugin Fits, and When Another Approach Makes More Sense

Directory Pro is a strong fit for site owners already running WordPress who want to add a directory without building a separate application. That could be a local portal, a club member directory, an association site, a school directory, a contractor directory, a doctor directory, a partner list, a real estate showcase, an event directory, or a company database. In projects like these, three things usually matter most: building the structure quickly, allowing users to submit listings through the site, and giving visitors an easy way to search.

The plugin also makes sense when the directory needs to connect to membership or paid features. The product page lists several membership types: free account, one-time payment, recurring payment, trial options, and a variable payment package. It also includes integrations with PayPal, Stripe, and WooCommerce Payment. That does not mean you should enable monetization on day one. But if the project plans to monetize through placement fees, promoted listings, featured listings, or access to specific sections, Directory Pro gives you a foundation for that logic.

Who may not be a good fit for this plugin? First, projects that only need a very lightweight directory with a few dozen static contacts. In that case, a simple table, editor blocks, or a lightweight contact plugin will often be enough. Second, teams that want a fully visual workflow built entirely around a modern block editor with no shortcode layer. According to the product page, Directory Pro supports Gutenberg and Elementor Pro, but its working logic still relies heavily on its own pages, shortcodes, and settings. Third, sites with strict security requirements and public registration should go through a separate review before launch, because the product has had fixes and vulnerability reports in third-party databases.

Practical rule: if the directory will accept data from outside users, launch it on a staging copy first, limit roles, and test the submission form, emails, moderation, and updates. A public submission form without proper permission checks and anti-spam measures quickly becomes a weak point in any WordPress directory.

Directory Pro should be treated as a working directory builder, not as a button that magically creates a business. It speeds up the technical side, but it does not solve your information architecture for you. The strongest projects know in advance which fields a listing needs, how categories should be named, what counts as a quality submission, who reviews new entries, which data should never be published, and which filters actually help visitors.

What to Check Before Installation and First Activation

Before installing the plugin, do not rush to upload the ZIP file to your live site. Directory Pro affects pages, user roles, forms, email templates, maps, payment workflows, and public data submission. Because of that, safe preparation matters more here than it does for a small decorative widget.

Technical Compatibility

The CodeCanyon page lists compatibility with current versions of WordPress, WooCommerce, WPML, Bootstrap, and Elementor Pro. That is a useful baseline, but your actual site still needs to be tested. First compare your WordPress, PHP, WooCommerce, and active theme versions against the product requirements. Then check whether another directory plugin is already installed that creates similar listing types, profile pages, routes, or roles. Two directory engines on one site often do not conflict immediately, but problems show up when you save permalinks, import listings, or render archive pages.

If the site already uses caching, minification, deferred JavaScript loading, and CSS optimization, prepare a list of pages that should be excluded from aggressive caching in advance: registration, login, the account area, listing submission, the owner contact form, payment steps, and pages with AJAX filters. Do not disable caching across the whole site, but keep in mind that a directory with search and user accounts usually needs more careful rules than a static article page.

Backup and Staging Copy

Before installation, create a backup of both files and the database. This is especially important if you plan to import demo data, change permalinks, add user roles, or enable payments. A staging copy lets you safely test which pages the plugin creates, which shortcodes render correctly, how the archive looks, whether fields save properly, whether emails are delivered, and whether the theme breaks.

If you do not have a staging copy, at minimum create a full database export and a file archive. Then install the plugin during a low-traffic window and do not enable public registration until testing is complete. The public listing submission form should only go live after you understand where moderation is enabled and which roles new users receive.

List of Planned Pages

Even before installation, it helps to sketch out a page map. A typical directory usually needs a main directory page, an all listings page, a listing detail page, a submission page, a login page, registration, an account area, a user profile page, pricing plans, categories, and possibly a map page. The Directory Pro documentation lists shortcodes for archives, filters, the pricing table, signup form, My Account, login, user directory, public profile, categories, category tree, the map, the carousel, and the search bar. That means you are not building a single page, but a small system.

Decide in advance which pages should be indexed by search engines and which should not. Category archives, city pages, and company listings are often worth indexing. The account area, registration, payment history, and edit forms usually are not. It is better to handle that through your SEO plugin settings and your theme's robots rules than to assume it will all work automatically.

Installation, Pages, and the Initial Check

Installing Directory Pro generally follows the same flow as any commercial WordPress plugin: in the admin panel, open Plugins, choose Add New, then Upload Plugin, upload the installation ZIP, and activate the plugin. Make sure you upload the actual installable plugin file, not the full archive that also includes documentation and source materials. If WordPress says the archive does not contain a valid plugin, the wrong ZIP file was probably uploaded, or the archive includes an extra nested folder.

After activation, check which pages were created automatically. The documentation for related e-plugins products, along with the Directory Pro documentation, shows that the plugin works through a set of pages and shortcodes. If the pages were not created automatically, you can build them manually in the WordPress editor: create a new page, insert a Shortcode block, and add the required shortcode. For Gutenberg, this is a normal workflow because WordPress officially supports the shortcode block.

Minimum Set of Pages

For the first validation pass, do not try to display every archive layout and every filter at once. Build a minimal set:

• A directory page with an archive shortcode, such as [listing_layout_style_4] or another layout from the documentation.
• A search or filter page if you want to test city, category, or ZIP code separately.
• A registration page with [iv_directories_form_wizard] if you need user accounts.
• An account page with the profile shortcode so the listing owner can manage their data.
• A login page with [iv_directories_login].

After publishing the pages, open them in an incognito window. That shows you the site through the eyes of a regular visitor rather than an administrator. Make sure the page is not empty, the form does not require admin permissions, buttons are visible, styles are not broken, and links between registration, login, and the account area point to the correct URLs.

Permalinks and Routing

After activating a directory plugin, it is a good idea to resave WordPress permalinks. This is not a magic fix for every issue. It simply refreshes routing rules after new listing types and pages appear. In the admin panel, open Settings - Permalinks and save the settings without changing the structure if your current permalink structure already works for the site.

Then create one test directory listing and check its detail page. If the archive opens but the detail page returns a 404, the issue is often tied to rewrite rules, a slug conflict, or route caching. If the 404 only appears in one language, also check your WPML, Polylang, or other language plugin settings.

Initial Test Listing

Create one demo listing that resembles a real directory entry. Do not leave fields empty. Fill in the title, category, city, address, description, phone number, email, website, image, and coordinates if needed. This lets you test not just whether the item publishes, but the full flow: data saving, archive display, filtering, the map, the contact form, and the owner page.

If the listing was created from the admin panel, repeat the process through the public My Account flow afterward. For a directory that accepts outside contributors, that path matters more. An administrator can almost always bypass restrictions, but a regular user has to go through the actual form, permissions, moderation, and email workflow.

The Directory Model: Categories, Fields, Listings, and Owners

The most important part of configuring Directory Pro is the data model. A directory should not be just a set of identical cards. A good directory answers the visitor's question: "Who or what am I looking for, where is it located, what makes it different, and how do I get in touch?" That is why the fields, categories, and listing template should be designed around the use case, not copied wholesale from the demo.

Categories and Geography

Start with categories. In a business directory, that might be "Restaurants," "Attorneys," "Home Repair," or "Education." In a professional directory, it could be service areas. In a club directory, member types. In real estate, property types. Do not create a deeply nested category structure at the start. If visitors cannot tell which branch to click, the filter is not helping.

Geography should be handled as its own logic. Directory Pro supports filtering by city and ZIP code and can work with maps, and the changelog mentions OpenStreetMap, multiple locations, and updates to map-related functionality. That means city, address, and coordinates are best stored in structured fields rather than buried only in the description text. If you are building a local directory, city and neighborhood fields may matter more than a long description.

Listing Fields

The product page says the administrator can add new fields. The changelog also mentions a Form Builder for listing data fields and a drag-and-drop search builder with custom fields. The practical takeaway is simple: divide fields into required, useful for search, and purely informational or decorative.

A common mistake is adding twenty fields before the first real test. The result is a long submission form, listing owners abandon it halfway through, and visitors end up with an overloaded listing page. Start with a short set, create several realistic listings, see what data is missing, and only then expand the form.

Listing Owner and Permissions

Directory Pro supports account workflows along with front-end listing submission and editing. That is convenient, but it requires careful permission settings. Decide whether a user can publish a listing immediately or whether every listing should go into moderation first. The product page lists a setting for User Listing Publish Ability or Pending for approval. For a new public directory, moderation is the safer place to start.

You should also think through claim listing. This feature is useful when the administrator adds company profiles in advance and the real owners later claim ownership of those listings. In that scenario, it is not enough just to enable the button. You also need to configure emails, verification rules, and the administrator's actions after a claim request is submitted. Otherwise, claim listing becomes just another form collecting requests with no clear processing workflow behind it.

Search, Filters, and Maps: How to Make the Directory Easy to Use

Search is the heart of the directory. Visitors rarely read every listing one by one. They want a specific service type, city, category, nearby location on the map, or a useful combination of filters. Directory Pro offers several display options: list with left faceted search, grid with top filter, grid with left faceted search, an A to Z filter, separate listing filter shortcodes, a search bar, and a map shortcode. The goal is not to choose the flashiest layout, but the one that fits your amount of data.

When to Use a Top Search Bar

A top search bar works well for small to medium-sized directories where the visitor starts with a broad query and refines it from there. For example: "repair," "dentist," "courses," or "hotel." This kind of search looks good on the main directory page and can act as a fast entry point into the results.

If you use [slider_search] or another search shortcode, test it without a decorative slider first. The demo search shortcode page shows that search can work as a standalone form with fields like Search, Location, Near, City, State, Reset, and Search. In practice, that is usually more useful than a heavy banner: the form should be readable, fast, and easy to use on a mobile screen.

When Faceted Filters Are Needed

A faceted filter makes sense when the directory contains many listings and visitors need to narrow the selection step by step. For example, category plus neighborhood plus available service plus a flag such as "accepting bookings." The Directory Pro changelog mentions a drag-and-drop Search builder with custom fields and field types such as drop down, multi select, and multi select group. That gives you flexibility, but it also creates a real risk of overload.

A good faceted filter only shows attributes that actually help people choose. If a field is filled out on only five percent of listings, it is almost useless as a filter. If a value can be entered ten different ways, it should not be a free-text field, but a select or multi-select. And if a filter does not change the results at all, users stop trusting it.

Maps and Addresses

Not every directory needs a map. For local businesses, real estate, places, courses, doctors, service centers, and physical service locations, a map helps visitors understand the geography immediately. For online professionals, documents, organizations that do not receive visitors, or a private member directory, a map may be unnecessary.

Directory Pro mentions OpenStreetMap, map marker image settings, address autocomplete without an API, and fixes for map-related bugs. Before launching the map, check three things: the listing receives coordinates, the marker matches the category, and the page does not break when a listing has no address. If some listings do not have a known address, it is better to show them in the list without a marker than to render a map with empty or incorrect points.

Result check: create three test listings in different categories and cities, then test search by title, category, city, ZIP code, and the map. If one of the filters does not change the results, do not enable it on the live page until the data is fixed.

The Account Area, Pricing Plans, and Front-End Listing Submission

One of Directory Pro's biggest strengths is not just directory display, but user-managed listings. Its feature list includes add/edit listing from frontend My Account, user setting, social profile, privacy setting, change password, all post, insert post, edit post, subscription upgrade, downgrade, and cancel. That turns the directory into a system where listing owners can maintain their own data.

Account Area Structure

The account area should be easy to understand for someone who does not know WordPress. Do not label the page "Dashboard" if that wording will feel unclear to your audience. In the site menu, "My Account" is often the clearest choice, while the plugin's built-in English labels can remain as they are if they come directly from the interface and have not been customized yet. For translating strings, the official e-plugins source points to Loco Translate or POEdit, and WordPress.org confirms that Loco Translate can edit translation files directly in the admin panel.

Make sure users can only see their own listings, do not get sent into the admin area unless necessary, and can update their password, profile, contact details, and listing. If the plugin hides the admin bar on public-facing profiles, that is helpful for regular users, but administrators still need convenient access to moderation tools.

Packages and Roles

Packages in Directory Pro affect user access and publishing capabilities. The product page lists free account, one-time payment, recurring payment, free trial, paid trial, and variable payment package. Documentation for related e-plugins products explains the logic: the administrator creates packages, and the user's role may change based on package status or payment status. On a real site, that means a pricing plan is not just a pretty table. It is a combination of permissions, expiration rules, and available features.

For the first version of the directory, it is usually better to start with one free package and one limited paid scenario, if monetization is needed at all. For example: a free listing is published after moderation and shows basic contact details, while an upgraded listing gets more images, featured status, or additional fields. Do not enable recurring payments, coupons, trials, and the WooCommerce flow all at once if the team has not yet validated basic publishing and email delivery.

Emails and Notifications

Directory Pro lists 11 email templates: a welcome email, password recovery, order emails, admin emails, owner contact, claim email, and subscription reminders. That is an important layer. Without email notifications, listing owners do not know whether a submission was accepted, administrators miss moderation events, and visitors do not receive confirmation that a contact form was sent.

Test emails through real actions, not just by clicking "save template." Go through registration, listing submission, owner contact, claim listing, and status changes. If emails are not arriving, configure an SMTP plugin and your sending domain first, then look for a Directory Pro issue. By default, WordPress often sends mail through the server mail function, which is unreliable with modern email filtering.

Practical Example: A Local Services Directory with Owner Submissions

Let's walk through a concrete scenario. Imagine a city portal that needs a local services directory: home repair, education, healthcare, beauty, fitness, legal help. Visitors should be able to find an organization by category and city, open the listing, view the contact details, and send a message to the owner. The owner should be able to register, add a listing, and later edit it through the account area.

Goal and Preparation

The goal is to create a working directory with one results page, a search form, a listing detail page, an account area, moderation for new listings, and owner contact. Before configuration begins, you should already have an active theme, a backup, a test page, a category list, one city or several neighborhoods, an administrator email address, and SMTP delivery configured.

Keep the listing form short. For the first version, these fields are usually enough: organization name, category, city, address, phone number, contact email, website, short description, logo or photo, and business hours. If you add long-form fields, documents, galleries, social profiles, and dozens of checkboxes right away, listing owners will complete the form less reliably.

Setup Steps

1. Create the pages "Directory," "Add Organization," "Login," "My Account," "Pricing," and "Profile."
2. On the "Directory" page, insert the archive shortcode from the documentation, such as a grid or list layout with filters.
3. On the submission or registration page, insert [iv_directories_form_wizard] if submissions go through registration.
4. On the account page, add the profile shortcode that Directory Pro uses for My Account.
5. Create service categories and make sure they appear in the listing submission form.
6. Configure listing fields: required contact details, address, description, and image.
7. Enable moderation for new listings if the directory is public and accepts submissions from outside users.
8. Create one test listing as an administrator and one listing through the public form as a regular user.
9. Test emails: registration, listing submission, owner contact, and the administrator notification.

Validating the Result

After setup, open the site as a logged-out visitor. The directory page should display the test listings, search, filters, and links to the detail pages. Open a listing and make sure the contact details, image, category, city, and map or address appear if enabled. Then send a message to the owner and confirm that the email is delivered.

After that, log in as a regular user. The account area should show that user's listings, not every listing on the site. Try editing the listing, change the phone number, and save it. If the site uses moderation for edits, verify that the change does not publish without admin review. If there is no moderation, make sure the user cannot edit someone else's listing by opening a direct link.

Details That Commonly Surface

The first issue is missing images. If the owner does not upload a photo, the listing may look broken. The Directory Pro changelog mentions a default image changer and an archive listing page without image mode, so test which option works better for your design: a default placeholder image or a clean card without an image.

The second issue is addresses without coordinates. If the map is enabled but the address is parsed incorrectly, the listing may appear in the wrong place or not show up on the map at all. Test several addresses and decide who is responsible for correcting them: the listing owner or the moderator. For a local directory, this is critical.

The third issue is the user role after registration. If packages and roles are configured incorrectly, a user may not see the submission form or may receive more access than intended. Test this path with a brand-new account, not as an administrator.

Listing Design, Templates, and Safe Customization

Directory Pro can be used without editing code, but almost any directory eventually needs listing-level adjustments: remove an unnecessary block, change the order of contact details, show a notice, add text before a list, or adapt the look to the theme. The key is to do it in a way that will not be overwritten by a plugin update.

Override Templates Instead of Editing the Plugin Directly

The Directory Pro documentation explicitly describes template overrides: the template files live in /plugins/directory-pro/template, and you are supposed to copy them into the active theme and rename the folder to directorypro. The documentation gives an example path: /themes/twentyseventeen/directorypro. The idea is straightforward: your changes live in the theme rather than the plugin folder, so a plugin update should not wipe out your custom template edits.

/wp-content/plugins/directory-pro/template
/wp-content/themes/your-child-theme/directorypro

It is best to use a child theme. Do not copy the entire template directory unless you actually need it. Start with the specific file responsible for the screen you want to change, and document exactly what you changed. After a plugin update, compare your override against the new template version if the layout or data output starts behaving unexpectedly.

When Settings and CSS Are Enough

If the task is just changing a button color, spacing between blocks, image size, or hiding a decorative element, first look for a setting in the plugin or theme interface. The changelog mentions listing archive field settings, color settings in related e-plugins products, and archive design updates. If a setting already exists, use it instead of editing templates.

Only add CSS in a child theme or another safe location meant for custom CSS. Do not place styles directly in the plugin files. After making changes, test three screen sizes: desktop, tablet, and mobile. A directory often does not break on the main archive page, but on the mobile listing page where the filter, map, and contact button start competing for space.

Interface Localization

For a non-English site, translate the public-facing strings: form buttons, hints, account tab names, error messages, emails, and submission statuses. Loco Translate works well for editing plugin strings in the browser, and POEdit can be used outside the site. Do not translate technical slugs, shortcodes, or system identifiers unless you fully understand the consequences.

After translating the interface, check the emails too, not just the visible screens. A common oversight is translating the form while the listing owner still receives registration or submission emails in English. That lowers trust and increases support requests.

Validating the Directory Before Launch

Before opening the directory to visitors, go through a short but strict validation process. It should simulate the real actions of three roles: visitor, listing owner, and administrator. If one of those flows breaks, it is better to postpone launch.

Visitor Check

A visitor should be able to open the directory, understand what can be searched, apply a filter, open a listing, and contact the owner. Test this while logged out. If the contact form is only available to registered users, say so clearly on the page. If a city filter exists but there are only a few listings, do not leave visitors with an empty results page and no explanation.

• The archive opens without errors and does not expose utility or internal pages.
• Searching by name returns the expected listing.
• Filtering by category and city changes the listing results.
• The detail page includes contact details, a description, and a clear next step.
• The contact form sends an email and shows a confirmation message.

Listing Owner Check

The listing owner should be able to register, log in, add a listing, upload an image, save the listing, see its status, and edit the data later if needed. Permissions are especially important in this scenario. If a user can see other people's listings, publish without moderation when that should be blocked, or access the admin panel with unnecessary privileges, the directory is not ready to go live.

Check what happens after a package is canceled or expires if you are using membership features. Documentation for related e-plugins products describes role changes after a failed payment or package cancellation. The same principle applies here: pricing plans and roles should be tested before real users ever touch them.

Administrator Check

The administrator should be able to quickly see new submissions, edit listings, change statuses, respond to claim listing requests, manage categories, correct addresses, and review emails. If moderation tools are buried too deep, create an internal guide for the editor. A directory needs ongoing maintenance: outdated contact details, duplicates, missing images, and weak descriptions reduce quality faster than a technical error does.

Quick pre-launch summary: publish the directory only after testing the full flow of "registration - submission - moderation - listing display - contact - editing." One polished archive page without a validated submission flow does not mean Directory Pro is ready for real use.

Common Directory Pro Issues and How to Diagnose Them

WordPress directory problems often look the same: a blank page, a 404 on the listing page, a filter that does nothing, a map that shows no markers, emails that never arrive, a user who cannot submit a listing, or a user who received too much access. What follows is not generic panic mode, but a practical troubleshooting path specifically for a directory plugin built around shortcodes, an account area, maps, and user roles.

The Directory Page Is Blank or Only Shows the Shortcode

Symptom: the page shows the shortcode text itself or a blank area instead of the directory. Possible causes include using the shortcode inside the wrong block, the plugin not being active, the page being cached as static content, or using a shortcode that does not belong to Directory Pro.

First confirm that the plugin is active, then open the page in the editor and make sure the code is placed inside a Shortcode block rather than pasted as formatted text with extra characters. Compare the syntax with the documentation, for example: [listing_layout_style_4], [listing_filter city="new york"], [directorypro_map]. After making changes, clear both page cache and browser cache.

If the shortcode starts working after optimization is disabled, add the directory page to your cache exclusions or disable deferred script loading only for that page. You usually do not need to roll back caching for the entire site.

The Listing Detail Page Returns a 404

Symptom: the archive loads, but an individual listing cannot be opened. Possible causes include permalinks not being resaved, a slug conflict with another page, the listing being in draft or pending status, or a language plugin creating the wrong route.

Start by resaving Settings - Permalinks. Then check the listing status and its public URL in the admin panel. If the issue appeared after changing the listing type name or URL, restore the previous slug and test again. If the site is multilingual, check the translated directory pages and the WPML or Polylang routing rules.

The Filter Finds Nothing

Symptom: listings exist, but filtering by category, city, or ZIP code returns no results. The problem is often not the filter itself, but the data. Values may be stored in a different field, use inconsistent casing, exist as free text, or be missing from most listings.

Create three test listings with guaranteed field values and test the filter against them. If only the test data works, your real data needs cleanup. If even the test data does not work, check the shortcode parameters and the field type in the search builder. For important attributes, use select or multi-select instead of free text.

The Map Shows No Markers

Symptom: the map page loads, but there are no markers, or the markers appear in the wrong place. Possible causes include missing coordinates, an incorrect address, a map script conflict, a hidden map container inside a tab, or a cached version of the page.

Test one listing with an exact address and coordinates first. Then temporarily switch to a simple theme or disable aggressive JavaScript optimization on that page. If the marker appears, the problem is in front-end optimization or the template. If the marker still does not appear, go back to the listing data and map settings.

Registration and Contact Emails Do Not Arrive

Symptom: the form reports success, but no email is delivered. This is a common WordPress issue. Start by checking SMTP, the sending domain, and the spam folder. Then review the Directory Pro email templates and the administrator email address. If owner contact is supposed to send to the email stored in the listing, make sure that field is filled in on the exact listing you are testing.

The fix usually starts outside Directory Pro, with proper mail delivery. Connect SMTP, send a test email, then repeat registration, claim listing, and owner contact tests. If SMTP works but one specific template is blank, check the template variables and the template text.

The User Cannot See the Submission Form or Sees Too Much

Symptom: a regular user cannot submit a listing, sees an access error, or gets access to something that should be restricted. The cause may be the user's role, package, publish ability setting, membership status, or cached account pages.

Create a new test user and assign the expected package. Check the account area in an incognito window. If access depends on payment status, verify which status the user receives after registration or a test order. The account area, forms, and payment pages are usually best excluded from full page caching.

The Design Changed or a Block Disappeared After an Update

Symptom: after updating the plugin, the listing looks different, some data stops rendering, or a template override no longer matches the new logic. If you copied templates into the theme, compare your file with the current file in /plugins/directory-pro/template. The plugin may have changed the template structure while your site is still using an older override.

Roll back only the overridden template, not the entire plugin, if the problem is tied to customization. If the issue appears without any override, check the changelog, cache, minification, and theme conflicts.

Video on Elementor Widgets and Visual Page Building

The Directory Pro changelog references a specific YouTube video about the Elementor widget for the listing detail page. That video is useful not for basic installation, but for site owners who want to control the design of the listing detail page through Elementor and go beyond the standard template. Before watching it, build the basic directory and one test listing first. Otherwise, it will be harder to connect the video to your actual site.

This video helps with a specific use case: using Directory Pro together with Elementor on a listing detail page where you want tighter control over the listing card, fields, contact details, and visual content blocks. If you are not using Elementor, you can skip this section and focus on shortcodes, templates, and archive settings.

When CodeCanyon Directory Pro Makes Sense

CodeCanyon Directory Pro is a strong choice if you need a WordPress directory with front-end listing submission, an account area, filters, maps, categories, claim listing, email templates, and the option to add pricing plans. It is especially useful when the project needs a working directory quickly without building from scratch, but still requires more than simple listing cards - it needs a managed system for users and listings.

Before a live launch, test compatibility, updates, security notes, SMTP, caching, permalinks, user roles, and one complete user workflow. If all key checks pass, you can download the latest version of CodeCanyon Directory Pro and test the plugin on a site copy. Do not move the directory to production until the forms, emails, search, map, and regular user permissions have all been verified.

The real value of Directory Pro does not come from how many features you turn on, but from how carefully you configure it for a specific niche. Start with a clear structure, then add the fields and filters you actually need, then validate the account area, and only after that connect pricing plans, more complex templates, and deeper customization. That order reduces the risk of errors and makes the directory genuinely useful for visitors, listing owners, and administrators.