MDH DYNAMIC QR

MDH Dynamic QR compatibility with REEID Translate

MDH Dynamic QR compatibility with REEID Translate is being reviewed using official plugin documentation. {"task": "Research factual plugin behavior for compatibility context only. No specific text shown to visitors is currently confirmed for translation.

Visit MDH Dynamic QR ↗

AWAITING VERIFICATION

What MDH Dynamic QR does

Official plugin information supports the compatibility context documented for this category.

MANUAL REVIEW
This integration has not yet been manually verified by REEID.

PLUGIN PROFILE
MDH Dynamic QR is documented in the Other category with 8 documented features.

DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.

COMPATIBILITY REVIEW

How MDH Dynamic QR compatibility is evaluated

01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.

02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.

03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.

04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.

PLUGIN INFORMATION

What the plugin does

Plugin capabilities

  • {"task": "Research factual plugin behavior for compatibility context only.
  • Do not extract translation-surface observations.", "plugin_identity": {"name": "MDH Dynamic QR", "slug": "mdh-dynamic-qr", "homepage_url": "https://qr.mdh-group.de/", "plugin_url": "https://qr.mdh-group.de/"}, "official_search_domains": ["qr.mdh-group.de", "wordpress.org", "plugins.svn.wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search only when supplied evidence is insufficient.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent plugin behavior, capabilities, settings, or integrations.", "Do not decide REEID compatibility, translation support, approval, or eligibility.", "Follow category_research.rules for what to investigate in this Integration Category.", "Return observations as an empty list.", "Return 4 to 8 concise high-value factual capabilities in features.", "Group related implementation details into broader capability statements.", "Prefer stable product capabilities over minor settings or repeated variations.", "Do not include ratings, installation counts, version requirements, or promotional claims.", "Use unknowns only for materially relevant facts that official evidence does not establish.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name.
  • Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name.
  • Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand.
  • Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording.
  • The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity.
  • When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7.
  • Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name.

Distinctive features
{"task": "Research factual plugin behavior for compatibility context only. Do not extract translation-surface observations.", "plugin_identity": {"name": "MDH Dynamic QR", "slug": "mdh-dynamic-qr", "homepage_url": "https://qr.mdh-group.de/", "plugin_url": "https://qr.mdh-group.de/"}, "official_search_domains": ["qr.mdh-group.de", "wordpress.org", "plugins.svn.wordpress.org"], "rules": ["Return one JSON object only.", "Use only facts supported by supplied plugin evidence or web research from the allowed official domains.", "Use web search only when supplied evidence is insufficient.", "For web research, use only first-party vendor/product documentation and WordPress.org sources within official_search_domains.", "Do not use reviews, blogs, forums, aggregators, search snippets, or third-party documentation as evidence.", "Do not invent plugin behavior, capabilities, settings, or integrations.", "Do not decide REEID compatibility, translation support, approval, or eligibility.", "Follow category_research.rules for what to investigate in this Integration Category.", "Return observations as an empty list.", "Return 4 to 8 concise high-value factual capabilities in features.", "Group related implementation details into broader capability statements.", "Prefer stable product capabilities over minor settings or repeated variations.", "Do not include ratings, installation counts, version requirements, or promotional claims.", "Use unknowns only for materially relevant facts that official evidence does not establish.", "seo_display_name must be the shortest distinctive search-facing product or brand identity that can be copied exactly as one contiguous phrase from plugin_identity.name. Preserve the exact capitalization, spelling, and punctuation used in plugin_identity.name. Never invent, rename, expand, normalize, lowercase, or substitute the plugin brand. Remove generic leading or trailing descriptors when a shorter distinctive product or brand phrase is present, including terms such as Plugin, WordPress Plugin, Page Builder, Website Builder, WooCommerce, Forms, SEO, Addons, Widgets, Templates, Booking, Membership, or similar category/marketing wording. The distinctive brand may appear at the beginning, middle, or end of plugin_identity.name; for example, a title shaped like generic description – Brand should return Brand when Brand is clearly the product identity. When a short distinctive acronym, product token, or branded abbreviation appears after a separator and clearly identifies the plugin, prefer that exact token over the preceding generic description; for example Database Addon for Contact Form 7 – CFDB7 should return CFDB7. Use plugin_identity.slug only as an identity clue, not as output text unless that exact casing and phrase also appears in plugin_identity.name. If no shorter distinctive product or brand phrase can be selected safely, return the full plugin_identity.name.", "seo_keyword_candidates must contain 2 to 4 concise plugin-specific identity phrases based on seo_display_name, plugin_identity.name, and plugin_identity.slug. When the slug corresponds to a brand or product phrase present in the official name, include that phrase as a candidate. Do not return generic category-only phrases and do not assert REEID compatibility, verification, translation support, or other unsupported state claims."], "category_research": {"integration_category": "Other", "mode": "compatibility_only", "rules": ["Research concise factual plugin behavior from official sources for compatibility context without assuming any translation surface.", "This Integration Category is compatibility-only.", "Do not research, infer, or emit translation-surface observations.", "Return observations as an empty list.", "Use features and unknowns only for factual compatibility context."]}, "evidence_focus": {"integration_category": "Other", "look_for_literal_terms": []}, "output_schema": {"observations": [{"text": "", "evidence": "", "source_url": ""}], "features": [], "unknowns": [], "seo_display_name": "", "seo_keyword_candidates": []}, "evidence": {"description": "MDH Dynamic QR is a permanently free WordPress plugin for creating and managing dynamic URL QR codes directly on your own website.\n Each QR code uses a local short URL on your WordPress installation. This QR redirect points to the current destination URL, so you can change the destination later while the printed QR code stays the same.\n Features:\n* unlimited dynamic URL QR codes\n* destination URLs can be changed at any time\n* local QR redirects on your own WordPress domain\n* QR code preview\n* PNG and SVG download\n* print view for browser-based PDF output\n* shortcode output\n* simple scan counter and last-scan timestamp\n* cookie-free counting without storing full IP addresses\n* no license key required\n The free edition works entirely inside your own WordPress installation. It does not require an external license server, has no time limit, and does not impose a usage quota.\n Commercial extensions are separate products and may provide additional QR types as well as media, design, import/export, and analytics tools. The WordPress.org edition does not contain locked premium code.\n Third Party Libraries\n The plugin includes a local QR code JavaScript library based on Kazuhiko Arase’s QRCode Generator under the MIT License. License and copyright notices are included in THIRD-PARTY-LICENSES.txt and in the library files.", "sections": {"installation": "Install the plugin ZIP through Plugins > Add Plugin > Upload Plugin.\n Activate the plugin.\n Open Settings > Permalinks and click Save Changes once.\n Open MDH Dynamic QR > New QR Code and enter a title, slug, and destination URL.\n Save the QR code, test it with a smartphone, and then export it as PNG/SVG or use the print view.", "faq": "Can I change the destination URL later?\n Yes. That is the purpose of the dynamic short URL. As long as the slug remains unchanged, the printed QR code does not need to be replaced.\nDoes the free edition require a license key?\n No. The free edition can be used permanently without a license key.\nHow many QR codes can I create?\n The WordPress.org edition does not limit the number of dynamic URL QR codes.\nAre full IP addresses stored?\n No. The simple scan counter does not store full IP addresses and does not use tracking cookies.\nWill my data remain available after a later upgrade?\n The free edition uses compatible tables for URL QR codes and scan data. A commercial edition can extend and reuse this data during a later upgrade.\nDoes the plugin load code from external servers?\n No. The QR code library is bundled locally with the plugin. The free edition has no external updater and does not contact a license server.", "screenshots": "Overview of MDH Dynamic QR FREE with QR code status, scan counts, shortcodes, and quick actions.\n Edit a dynamic URL QR code, change its destination, preview the code, download PNG/SVG, use the print view, or copy the shortcode.\n Cookie-free scan statistics with total scans, last scan, and per-QR-code results.\n Clean print view for printing a QR code or saving it as a PDF from the browser.\n Plugin settings with FREE edition information, shortcode details, privacy information, and uninstall behavior.\n Help and system check with WordPress, PHP, permalink, and QR database status plus first-use guidance."}, "readme_text": "=== MDH Dynamic QR ===\nContributors: mdhgroup\nTags: qr code, dynamic qr, qr redirect, shortcode, scan counter\nRequires at least: 6.2\nTested up to: 7.1\nRequires PHP: 8.0\nStable tag: 1.0.4\nLicense: GPLv2 or later\nLicense URI: https://www.gnu.org/licenses/gpl-2.0.html\n\nCreate dynamic QR codes and QR redirects in WordPress. Change destination URLs later without replacing printed QR codes.\n\n== Description ==\n\nMDH Dynamic QR is a permanently free WordPress plugin for creating and managing dynamic URL QR codes directly on your own website.\n\nEach QR code uses a local short URL on your WordPress installation. This QR redirect points to the current destination URL, so you can change the destination later while the printed QR code stays the same.\n\nFeatures:\n* unlimited dynamic URL QR codes\n* destination URLs can be changed at any time\n* local QR redirects on your own WordPress domain\n* QR code preview\n* PNG and SVG download\n* print view for browser-based PDF output\n* shortcode output\n* simple scan counter and last-scan timestamp\n* cookie-free counting without storing full IP addresses\n* no license key required\n\nThe free edition works entirely inside your own WordPress installation. It does not require an external license server, has no time limit, and does not impose a usage quota.\n\nCommercial extensions are separate products and may provide additional QR types as well as media, design, import/export, and analytics tools. The WordPress.org edition does not contain locked premium code.\n\n== Installation ==\n\n1. Install the plugin ZIP through Plugins > Add Plugin > Upload Plugin.\n2. Activate the plugin.\n3. Open Settings > Permalinks and click Save Changes once.\n4. Open MDH Dynamic QR > New QR Code and enter a title, slug, and destination URL.\n5. Save the QR code, test it with a smartphone, and then export it as PNG/SVG or use the print view.\n\n== Screenshots ==\n\n1. Overview of MDH Dynamic QR FREE with QR code status, scan counts, shortcodes, and quick actions.\n2. Edit a dynamic URL QR code, change its destination, preview the code, download PNG/SVG, use the print view, or copy the shortcode.\n3. Cookie-free scan statistics with total scans, last scan, and per-QR-code results.\n4. Clean print view for printing a QR code or saving it as a PDF from the browser.\n5. Plugin settings with FREE edition information, shortcode details, privacy information, and uninstall behavior.\n6. Help and system check with WordPress, PHP, permalink, and QR database status plus first-use guidance.\n\n== Frequently Asked Questions ==\n\n= Can I change the destination URL later? =\nYes. That is the purpose of the dynamic short URL. As long as the slug remains unchanged, the printed QR code does not need to be replaced.\n\n= Does the free edition require a license key? =\nNo. The free edition can be used permanently without a license key.\n\n= How many QR codes can I create? =\nThe WordPress.org edition does not limit the number of dynamic URL QR codes.\n\n= Are full IP addresses stored? =\nNo. The simple scan counter does not store full IP addresses and does not use tracking cookies.\n\n= Will my data remain available after a later upgrade? =\nThe free edition uses compatible tables for URL QR codes and scan data. A commercial edition can extend and reuse this data during a later upgrade.\n\n= Does the plugin load code from external servers? =\nNo. The QR code library is bundled locally with the plugin. The free edition has no external updater and does not contact a license server.\n\n== Third Party Libraries ==\n\nThe plugin includes a local QR code JavaScript library based on Kazuhiko Arase's QRCode Generator under the MIT License. License and copyright notices are included in THIRD-PARTY-LICENSES.txt and in the library files."}}

TRANSLATION BOUNDARY

MDH Dynamic QR capabilities and translatable content are documented separately.

Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.

A feature is not considered translatable unless it includes text that users can read.

LIMITATIONS & QA

Verification notes

  • This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.

FREQUENTLY ASKED QUESTIONS

MDH Dynamic QR and REEID Translate FAQ.

What does MDH Dynamic QR do?

MDH Dynamic QR has 8 documented features listed in its official documentation. See the Plugin Information section for details.

Does MDH Dynamic QR have any content currently confirmed for translation?

No specific content is currently confirmed for translation in this integration.

What needs to be confirmed before translating content from MDH Dynamic QR?

Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.

RELATED GUIDES

Explore more compatibility guides.

COMPATIBILITY INFORMATION

Evaluate MDH Dynamic QR in a multilingual WordPress workflow.

REEID documents MDH Dynamic QR functionality separately from confirmed translation support so the distinction is clear.

Supported content will be listed when specific translatable text is identified in the official documentation.

Shopping Cart
Scroll to Top