Frequently Asked Questions (FAQ)

Detailed answers regarding licensing terms, privacy boundaries, language packs, multisite compatibility, and technical architecture.

Is the plugin really free? Are there paid upgrades?

Yes, it is 100% free software. Both the WPMMCC ATS WordPress plugin and the companion WPTSALL Client are released under the GNU General Public License v2 or later (GPL-2.0-or-later).

There are no "Pro" tiers, no feature locks, no trial periods, and no license key input fields. Every capability described in the documentation is immediately accessible to all users.

Do I have to install the WPTSALL Client?

No. The client is only for automatic translation in WPMMCC ATS. Manual translation in wp-admin does not need it. WPMMCC, the cross-site sync plugin, never uses the client.

Which plugin do I install?

Install WPMMCC ATS to translate one site into more languages (virtual prefixes or network subsites). Install WPMMCC to copy content between two WordPress sites. They are separate plugins and can be used alone. See cross-site sync.

Does the plugin make external network calls to wpmm.cc?

No. The plugin will never initiate connections to www.wpmm.cc or any remote server. There is zero telemetry tracking, no phone-home mechanism, and no analytics collection. The only network communication involves the optional client calling REST endpoints hosted on your own server, or when WordPress Core fetches language pack updates from translate.wordpress.org.

Does it write debug logs?

No. Debug logging is disabled by default in both the plugin and the client, and every feature works without it. In the plugin, a developer can enable file logging via a wp-config.php constant; in the client, the Settings page can turn local logging on or off at runtime. Client logs never leave your machine.

Where does content go during automatic translation?

During automatic translation, the WPTSALL Client running on your local machine receives the text from your WordPress site, and sends it directly to whichever translation provider endpoint you configured (e.g. DeepSeek API, OpenAI API, Anthropic, DeepL, or your local Ollama instance).

Content travels strictly between your machine and your designated provider under your own API account terms. It never passes through any intermediate WPMMCC server.

Which languages and language packs are included?

English (en_US) is built into the plugin core. Simplified Chinese (zh_CN) is fully translated:

• The GitHub release package bundles full .mo and .po files directly inside the plugin's languages/ folder.
• On sites where WordPress is configured for Simplified Chinese, the plugin automatically displays in Chinese.
• Community translations for other languages can be contributed via GitHub pull requests or through translate.wordpress.org.

Can WPMMCC ATS coexist with Polylang or WPML?

Yes. WPMMCC ATS isolates its tables, rewrite rules, and hooks under its own namespaces. It can run alongside legacy plugins without causing fatal PHP conflicts. However, WPMMCC ATS is designed as a standalone, modern multilingual system; you do not need Polylang, WPML, or TranslatePress installed to use WPMMCC ATS.

Does it work on WordPress Multisite networks?

Yes. WPMMCC ATS is fully compatible with WordPress Multisite networks. You can network-activate the plugin across the entire network or activate it selectively on individual sites.

What does the slug "wpmmcc-ats" mean?

The prefix wpmmcc represents the vendor brand name associated with https://www.wpmm.cc. The suffix ats stands for Automated Translation System. This naming format follows WordPress plugin directory trademark guidelines and does not imply any official endorsement by or affiliation with the WordPress Foundation.