McLogiora Wordpress Plugin - Rating, Reviews, Demo & Download

No ratings yet

Free

Plugin Description

mcLogiora is a modular multilingual platform for WordPress.

mcLogiora is fully free and fully open source. There is no premium edition, no paid tier, no licence key, and no feature paywall. Every feature it ships is available to every user.

This release brings translation into the editing experience itself:

• Thin plugin bootstrap.
• PSR-4 autoloading architecture.
• Core application and service container.
• Module loader.
• Environment validation.
• Stable plugin contracts.
• Conditional admin assets.
• Functional language manager for plugin language data.
• Database-backed translation group and item relation records.
• Editor-independent Classic Editor, Block Editor, and Elementor compatibility adapters.
• Read-only compatibility detection for editors, builders, known plugins, and the active theme.
• Setup wizard welcome and default language steps.
• Localization and project metadata structure.
• Migration-based database schema for language and relation data.

Translation workflows:

• Create a draft translation of a post, page, or supported public custom post type.
• Link content that is already translated to its source, without copying or changing it.
• Unlink a translation. This removes the relation only and never deletes, trashes, or edits the content.
• Create translated categories, tags, and supported public custom taxonomy terms, using a translated name that you provide.
• Move translations through an explicit status lifecycle: draft, needs review, translated, and needs update.
• See translations marked as needing an update when the source title, content, or excerpt changes.
• Review language status for each post directly in the posts, pages, and custom post type list tables.

Interface strings, media, menus, and widgets:

• Scan your theme or a plugin for translatable interface strings, on request only.
• Translate those strings from a searchable String Translation screen.
• Translate image and file metadata per language: title, alternative text, caption, and description. The file itself is shared, never duplicated.
• Create a translated navigation menu that keeps the item order and nesting of its source.
• Translate the text of Text, Custom HTML, and Block widgets. Widget types mcLogiora does not understand are listed as unsupported and are never modified.

Every translation action is explicit. Nothing is translated automatically, nothing is published automatically, no source file is ever modified, and no content is ever deleted by a translation action. Scanning only ever runs when you ask for it, never during normal site traffic.

Multilingual URLs and switching:

• Serve translated content under language directories such as /tr/hakkimizda/, while your default language keeps the URLs it already has.
• Give each translation its own slug, edited normally in WordPress.
• Add a language switcher with a shortcode, a block, a widget, or a template tag, in list, dropdown, compact, or pill styles.
• Show translated interface strings, image metadata, widget text, and menus automatically once a visitor is in that language.

A translated URL with no translation behind it returns a normal 404 rather than quietly showing you the original language. Menus are the one exception: an untranslated menu still appears, so navigation never disappears.

mcLogiora never guesses your visitors’ language from their location and never redirects them automatically. Flags are off by default, because a language is not a country.

This release adds the developer and operations layer as well as optional Translation Suggestions. If you switch suggestions on and configure a WordPress AI connection or DeepL, mcLogiora can draft a translation of one field at a time, which you review before anything changes. The feature is off until you configure it, and translating by hand is unaffected. See “External Services” below for exactly what is sent and when.

Developer and operations surfaces:

• Read-only mclogiora_ functions and documented extension hooks for themes and other plugins.
• Authenticated REST routes for translation reads, status changes, relation membership, and translation creation.
• wp mclogiora commands for language, relation, and translation reads and workflow mutations.
• Portable translation packages with deterministic export, dry-run planning, additive atomic apply, rollback, and stale-plan protection. No import/export transport is exposed.
• A read-only System Status screen and native Site Health diagnostics with redacted output and no provider network calls.

The REST layer does not expose strings, suggestions, switcher, import/export, or status routes, and it does not machine-translate post bodies or page-builder layouts. See “What Translation Suggestions do not translate” below.

Privacy

mcLogiora does not track users, does not collect telemetry, does not send beacon requests, and contains no analytics of any kind.

mcLogiora contacts an external service only if you switch on Translation Suggestions, choose a provider, configure its connection, and then click a button that asks for a suggestion. Nothing is sent when a page loads, when the plugin is activated, when an editor opens, or when a visitor views your site. There is no mcLogiora server in the path: WordPress AI Client or the dedicated translation service sends the request from your site.

External Services

mcLogiora’s Translation Suggestions feature can connect to one external translation
provider that you choose and configure. It is switched off by default. If you never
enable it, mcLogiora makes no external requests at all.

For every service below, the following is true:

• The service is optional and is not used unless you enable suggestions, select that provider, and configure its connection.
• WordPress manages AI provider credentials in Settings → Connectors. DeepL uses an API key you supply in mcLogiora settings, and the provider bills you directly. mcLogiora ships no keys and no credits.
• Requests go from your site through WordPress AI Client or straight to DeepL. mcLogiora does not proxy your content through any mcLogiora service, and no data is sent to the plugin author.
• Only the single field you asked about is sent, and only at the moment you click a button. Generating a suggestion for a post title sends that title; it does not send the post body, the rest of your site, or any other field.
• Any required credential is handled by WordPress AI Client or sent to DeepL so the selected service can authenticate the request.
• Translating by hand needs none of this and works exactly the same whether the feature is on or off.

WordPress AI Client

Used when you select WordPress AI Client as your suggestion provider. The selected source text and translation instructions are passed to WordPress Core’s provider-agnostic AI Client when you click Generate. WordPress selects the configured compatible provider and model, and manages its credentials in Settings → Connectors. mcLogiora does not receive or store those credentials and does not choose a vendor or model on your behalf.

WordPress AI Client: https://developer.wordpress.org/reference/functions/wp_ai_client_prompt/
WordPress AI overview: https://make.wordpress.org/core/2026/03/24/introducing-the-ai-client-in-wordpress-7-0/

When updating from a version that stored an OpenAI, Anthropic or Google Gemini
mcLogiora credential, 1.0.2 removes those retired mcLogiora-owned credential
and model options once. It does not remove WordPress Connector settings or the
DeepL credential. The retired PHP constants are no longer read; PHP constants
cannot be removed by a plugin, so remove those old lines from wp-config.php
manually if you still have them.

DeepL

Used when you select DeepL as your suggestion provider. Your selected source text and your API key are sent to the DeepL Translate API when you click Generate, so it can return a translation. Testing the connection contacts DeepL’s usage endpoint, which reports your quota and sends none of your content.

DeepL Free and Pro keys use different hosts (https://api-free.deepl.com and https://api.deepl.com); mcLogiora selects the correct one from your key. DeepL is a dedicated translation service rather than a language model, so it has no model selection.

Terms: https://www.deepl.com/en/pro-license
Privacy: https://www.deepl.com/en/privacy

What is stored on your site

If you paste an API key into the mcLogiora settings screen it is stored in your site’s options table as you entered it. mcLogiora does not claim to encrypt it: any encryption a plugin can perform has to keep the key material on the same site, which would obstruct a casual reader while misleading a careful one.

If you prefer not to store a key in the database, define it in wp-config.php instead and mcLogiora will use that and tell you it is doing so:

define( 'MCLOGIORA_DEEPL_API_KEY', '...' );

A saved key is never shown again in the admin. The screen displays only a masked suffix so you can tell which key is installed.

Translation Suggestions

Translation Suggestions let you ask a provider you already pay for to draft a
translation of one field, which you then review before anything changes.

Turning it on

1. Open mcLogiora → Translation Suggestions.
2. Tick Allow translation suggestions on this site.
3. Choose WordPress AI Client or DeepL. Nothing is chosen for you.
4. For WordPress AI Client, configure an AI provider in Settings → Connectors. For DeepL, save your API key here or define it in wp-config.php.
5. Use Test connection to check the connection. This sends none of your content.
6. WordPress AI Client chooses a compatible provider and model; DeepL has no model selection.

The WordPress AI Client status distinguishes no registered AI provider, a
registered provider that still needs its Connector configuration, and AI
support disabled for the site. These checks are local and do not send content.

Using it

Wherever suggestions are available you get a Generate suggestion button per
field. Generating shows you a preview and changes nothing. From there you can:

• Apply suggestion — write the suggested text to that field, and only that field.
• Regenerate — ask again. One click, one request.
• Discard — throw the preview away. Nothing is saved and no request is made.

Nothing is ever translated automatically, on save, in bulk, or on publish. No
suggestion is applied without you clicking Apply.

Where suggestions are available

• Posts, pages and custom post types, in both the block editor and the Classic editor: title and excerpt.
• Interface strings, in String Translation: the translation for your target language.
• Taxonomy terms, in the Translation Manager: term name and term description.
• Media, on the attachment edit screen: title, alternative text, caption and description.

What Translation Suggestions do not translate

Phase 16 translates named fields only. It deliberately does not machine-translate:

• the raw post body (post_content), or a block document as a whole
• Elementor layouts, Beaver Builder layouts, or other page-builder payloads
• arbitrary custom fields or post meta
• a term’s slug, or a media file, filename, URL or dimensions

This is a safety decision rather than a missing feature. mcLogiora carries builder
and block structures through translation by copying them untouched, which is why
they survive. Sending a serialized block document to a language model and
reassembling the answer fails quietly when it fails — a damaged block delimiter does
not raise an error, it renders your page as visible HTML comments. That work needs a
proven extraction layer first.

A suggestion is not an approval

Applying a suggestion records that a machine produced the text, so you can find it
again and review it:

• Posts, pages, custom post types and taxonomy terms move to Machine suggested. Moving them to Translated is a separate, explicit step that only a person can take.
• Interface strings are stored with a machine-suggested status of their own.
• Media metadata is stored as Translated, because mcLogiora’s media translation storage has no machine-suggested state. Review machine output on media before relying on it — the storage cannot flag it for you.

Machine translation is a draft. Read it before you publish it.

Screenshots

1. 

   Review pages, posts, and translation status in one place.

2. 

   Create missing translations directly from WordPress content lists.

3. 

   Choose your site language and translation languages from a built-in catalog.

4. 

   Manage active languages with native names and locale details.

5. 

   Keep translation context close to the content you are editing.

6. 

   Learn the workflow with a searchable guide inside WordPress.

7. 

   Set language URL structure and switcher presentation with confidence.

Similar Plugins:

Rating Widget: Post Rating, 5 Star Rating, Reviews, Thumbs Up & Down, Reaction Reviews And Rating – Google Reviews Reviews Feed – Google Reviews & Yelp Reviews Plugin