Translations & multilingual sites (WPML, Polylang) Free

FileDeck stores documents as ordinary WordPress content — a post type and two taxonomies — which is exactly what translation plugins are built to handle. Documents and categories translate like posts and categories do, and every piece of FileDeck’s own interface text is internationalised.

What the bundled configuration does

FileDeck ships a wpml-config.xml, the standard declaration file that WPML, Polylang and compatible plugins all read. It declares:

• the document post type and both taxonomies as translatable;
• file references (the attached file, external URL, size, type) as copied to translations — a French translation of a policy points at the same PDF, it doesn’t demand a second upload;
• lifecycle settings (visibility, expiry, download limits) as copied, so a translation is governed exactly like its original;
• the download counter as ignored — each language’s copy counts its own downloads.

The honest boundary

Translation-ready is a precise claim and we keep it precise: the data model and interface are fully prepared, and the declaration file covers the meta behaviour. What we have not done is certify every workflow inside WPML’s own UI (translation management jobs, string-translation edge cases). If you run FileDeck on a multilingual site and hit anything odd, say so on the support page — multilingual reports get fixed with priority precisely because this surface is hard to test in the lab.