Template Overrides

The addon integrates with Dokan by intercepting Dokan’s template resolution. It does not replace Dokan’s engine; it points Dokan at Reign-styled template files where they exist.

How resolution works

The addon hooks Dokan’s dokan_get_template_part and dokan_locate_template filters. For each requested template, it checks whether a matching file exists through its own locator, and if so, returns that file.

The locator searches in this order:

1. dokan/<template-name> in the active theme (and its parent).
2. <template-name> in the active theme.
3. The addon’s own dokan/ directory as the fallback.

Because the theme is checked first, the primary Reign-styled overrides live in the Reign theme under reign-theme/dokan/. The addon’s own dokan/ directory holds the templates it ships directly, including the vendor grid template used by the shortcode and widget.

Overriding a template

To override a Dokan template that the addon or theme handles, place your version under dokan/<template-name> in a child theme. The theme copy takes priority over the addon copy.

The vendor grid template

The [rda_dokan_vendors] shortcode and the Reign - Vendors widget both render the addon’s dokan/widgets/rda-sellers.php template through dokan_get_template_part( 'widgets/rda-sellers', ... ). The vendor data is passed to the template in an atts array. Override it by providing dokan/widgets/rda-sellers.php in your theme.

Filtering the resolved path

The resolved template path passes through the reign_dokan_locate_template filter before it is returned, so you can adjust it programmatically. See Hooks and Filters.

Assets

The addon enqueues its own front-end stylesheet and scripts. Styles are loaded from the RTL directory automatically on right-to-left sites. When SCRIPT_DEBUG is on, the unminified files are used; otherwise the minified files are served. Asset versions match the plugin version for cache busting.