Skip to content

Troubleshooting

DMS terms don't appear in WPML

Run a scan: Dealer.ms → Settings → WPML tab → Start Scan. Data that existed before the extension was activated has never been registered. See Scanning Terms.

If terms still don't appear after a scan:

  • Confirm WPML is active. The extension does nothing at all when WPML isn't detected — no columns, no registration, no language dropdown.
  • Confirm String Translation is installed. DMS names are registered as strings, so without that module there is nowhere for them to show up.
  • Check you're looking at the right domain. Terms live under dms-type-{type id}, not under a single global domain. See Where to find strings.

Only some terms in a category were registered

The scan processes large categories in batches of 50 and needs the page to stay open until it finishes. If you navigated away mid-scan, the remaining terms were never reached — re-run the scan.

If a scan consistently fails partway on a very large category, reduce the batch size with dms_wpml_max_scan_amount. See Developer Reference.

I was redirected out of the language I was working in

Expected. DMS settings, listing types, and category pages can only be edited from the site's default language, so opening one in another language sends you back with a notice explaining why.

Translate those values in WPML → String Translation instead. The notice links directly to the correct domain.

Category fields are greyed out

Also expected, and for the same reason — you're viewing the category in a non-default language. The alert at the top of the page links to the right place in WPML.

Switch to your default language to edit the original values.

A renamed term lost its translation

Renaming a value creates a new string, and the translation was attached to the old text. Re-translate it in WPML.

Only the fields you actually changed are affected — renaming a category's singular name doesn't disturb translations of its other fields.

A translation is done in WPML but the front end shows the original

Work through these in order:

  1. Check the translation is marked complete in WPML, not left as a draft. An incomplete translation isn't served, and the DMS table column will still show an X.
  2. Clear any page or object cache. Translated output is cached like any other front-end content.
  3. Check the string value still matches. Strings are keyed on their original text; if the DMS value was edited after translating, the translation no longer applies. Re-translate the new string.

A custom translatable field isn't picked up

The list of translatable option keys is cached in a transient for a week, so a key added via dms_wpml_translatable_datastore_terms won't take effect immediately:

delete_transient( 'dms_wpml_translatable_datastore_terms' );

Then run a scan so the newly translatable values are registered.

"Nonce not set or invalid, please refresh and try again."

The scan's security token expired, usually because the settings page sat open for a long time or was served from cache. Reload the page and start the scan again.