WP StudioDDC

WordPress Plugins

Digital rain of falling binary code on a black background, the WP StudioDDC homepage hero visual — Custom WordPress Plugins.

WP StudioDDC HQ

by

Code on laptop screen in brand blue duotone, StudioDDC documentation visual

Private WordPress Plugin

WP StudioDDC HQ

Modular tools for content management, technical SEO and editorial workflows in the WordPress admin.

Request Access
GitHub

Site and Content Management

  • Insights for site and module status.
  • Editorial calendar with year, month, week, day and table views.
  • Keywords, content statistics and editorial checklists.
  • Private per-user NoteBooks and optional modules controlled through Settings.

Requirements and Distribution

  • WordPress 6.0 or later and PHP 7.4 or later, as declared by plugin version 1.0.302.
  • Language features require a supported multilingual plugin. Store features require WooCommerce.
  • Private distribution. Documentation is public; packages and updates require authorized access.

Read the documentation for each module’s settings, limits and specific requirements before enabling it.

WPSDDC Speed Timer

by

WPSDDC Speed Timer

WordPress Plugin

WPSDDC Speed Timer

Display elapsed server execution time in the WordPress toolbar for signed-in users.

WordPress.org
GitHub

What You Can Do

  • One Localized Server-Time Sample
  • Six Ranges for a Quick Visual Reference
  • Yields to Navigation on Compact Toolbars

Documentation

The WPSDDC Speed Timer WordPress Plugin is designed for observing WordPress server execution time. It helps editors show individual request timing in the toolbar for signed-in users. This is useful for quickly reviewing WordPress response times during maintenance. This indicator does not replace a full Core Web Vitals audit.

For practical context on the WPSDDC Speed Timer WordPress Plugin, read Core Web Vitals for Plugin Developers: Where to Start. The official reference on WordPress Request Timing explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Speed Timer. The native Help tab includes instructions and support.

Configuration and Use

Enable the toolbar timer and open a page while signed in with the toolbar visible. It shows elapsed server execution time until the toolbar is rendered.

Operating Limits

Only local settings are stored. Samples are not recorded or sent anywhere. This quick indicator does not measure full browser loading time or network TTFB and does not replace a profiler.

Data, Privacy and Deactivation

Only local settings are stored. Samples are not recorded or sent anywhere. This quick indicator does not measure full browser loading time or network TTFB and does not replace a profiler.

Detailed Behavior

Display elapsed server execution time in the WordPress toolbar for signed-in users.

The optional toolbar timer shows elapsed PHP execution up to toolbar rendering, not browser load time or network TTFB. Six ranges provide a quick visual reference. The localized measured value is displayed immediately, with no counting animation or client-side timing. Disabled by default; no assets load for anonymous visitors. For site administrators and signed-in editors, it provides a lightweight request-time reference. It is not a load-testing, tracing or visitor analytics service. It stores only one site-local enable setting, retained on deactivation/removal; no timings or browsing history are saved. Anonymous visitors receive no output or assets. Signed-in users with a visible toolbar receive one small layout stylesheet whose colors inherit Core and one local visibility-only guard. Duplicate timing samples, animation and empty compatibility hooks are excluded. Layout observers are scoped to the toolbar.

The plugin uses local WordPress APIs and does not send telemetry. Settings are retained after deactivation or removal.

The optional toolbar indicator yields to Core navigation on compact, touch or crowded toolbars. A small local visibility guard measures available toolbar space when its layout changes. The elapsed server-time value remains a single static sample; the script does not animate, recompute, profile or transmit timings. Disabled and anonymous requests enqueue neither toolbar asset.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Speed Timer Screenshot: WordPress Desktop Workspace.
WPSDDC Speed Timer — WordPress Desktop Workspace.
WPSDDC Speed Timer Screenshot: WordPress Mobile Workspace.
WPSDDC Speed Timer — WordPress Mobile Workspace.
WPSDDC Speed Timer Screenshot: Plugin Setup Guide.
WPSDDC Speed Timer — Plugin Setup Guide.
WPSDDC Speed Timer Screenshot: Feature Demo: Server Time Toolbar Feature Demo.
WPSDDC Speed Timer — Feature Demo: Server Time Toolbar Feature Demo.

WPSDDC Calendar Timeline

by

WPSDDC Calendar Timeline

WordPress Plugin

WPSDDC Calendar Timeline

Explore your editable content in year, month, week, day and agenda views using native WordPress dates and permissions.

WordPress.org
GitHub

What You Can Do

  • Year, Month, Week, Day and Annual Agenda
  • Content Type, Status, Date and Search Filters
  • 500-Item View Limit and 50-Item Agenda Pages

Documentation

The WPSDDC Calendar Timeline WordPress Plugin is designed for a read-only WordPress editorial calendar. It helps editors review content dates in calendar and agenda views. This is useful for visual planning for WordPress publication dates. Changes to content still use the native WordPress editor.

For practical context on the WPSDDC Calendar Timeline WordPress Plugin, read Document a Plugin So Future You Understands It. The official reference on WordPress Publication Dates explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Calendar Timeline. The native Help tab includes instructions and support.

Configuration and Use

Choose a date view and content filters, then apply them. The calendar uses the site timezone and respects content permissions.

Operating Limits

This read-only view uses existing WordPress dates. It does not create a separate calendar store, schedule posts or modify publication dates. Filters are carried in the URL.

Data, Privacy and Deactivation

This read-only view uses existing WordPress dates. It does not create a separate calendar store, schedule posts or modify publication dates. Filters are carried in the URL.

Detailed Behavior

Calendar Timeline helps WordPress writers and editors inspect the dates of content they can edit. Choose an installed public content type, a publication status, a date and an optional text search. Browse the year, month, week, day or paginated annual agenda. Native editor links let you edit or schedule content using WordPress itself; the plugin does not change content or publication dates.

The calendar uses the site timezone, the configured first weekday and native post_date values. Draft and pending dates are record dates, not promised publication dates. Authors see only their editable content; users with permission to edit others can see their team’s editable content. A final per-record capability check honors custom restrictions. Custom public types work through their registered capabilities. Private content, attachments, internal types, trash and auto-drafts are omitted.

Calendar queries retrieve at most 501 records and display up to 500. An explicit notice identifies truncated periods. A truncated year omits misleading month counts. The annual agenda shows 50 records per page with previous/next navigation; its query retrieves one extra row to detect the next page without an all-record count. Individual month/week cells show up to five items and link to the day view. Narrow the filters or use the agenda for large periods. Search uses native WordPress title/content search and accepts up to 100 characters.

There is no drag-and-drop scheduling, term-date inference, SEO dashboard, private category integration, editor warning injection or frontend publishing. No shortcode, widget, block, custom JavaScript, remote request, telemetry, cron or plugin-owned transient is registered. A small scoped stylesheet loads only on the calendar screen and leaves buttons, links and focus colors to WordPress Core.

The plugin stores no settings or editorial data. Filters are read-only URL parameters; URLs and browser history can therefore contain search text. Ordinary frontend requests return from the main entry file before feature code or hooks are loaded. Multisite views use the current site’s tables and capabilities. Deactivation/removal leaves all WordPress content untouched.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Calendar Timeline Screenshot: WordPress Desktop Workspace.
WPSDDC Calendar Timeline — WordPress Desktop Workspace.
WPSDDC Calendar Timeline Screenshot: WordPress Mobile Workspace.
WPSDDC Calendar Timeline — WordPress Mobile Workspace.
WPSDDC Calendar Timeline Screenshot: Plugin Setup Guide.
WPSDDC Calendar Timeline — Plugin Setup Guide.
WPSDDC Calendar Timeline Screenshot: Feature Demo: Editorial Calendar Feature Demo.
WPSDDC Calendar Timeline — Feature Demo: Editorial Calendar Feature Demo.

WPSDDC Broken Scanner

by

WPSDDC Broken Scanner

WordPress Plugin

WPSDDC Broken Scanner

Manually check links in saved WordPress content with native editing permissions.

WordPress.org
GitHub

What You Can Do

  • Up to 75 Unique Saved Literal Href/Src URLs
  • Native Single-Link Forms and Optional Sequential Progress
  • Bounded Public Http Checks and Validated Redirects

Documentation

The WPSDDC Broken Scanner WordPress Plugin is designed for manual checks for broken links in saved content. It helps editors review URLs from the editor with permission-aware tools. This is useful for detecting broken links on WordPress pages. Checks start manually rather than through a site-wide scheduled crawl.

For practical context on the WPSDDC Broken Scanner WordPress Plugin, read Sanitize, Validate and Escape: Plugin Security Basics. The official reference on WordPress HTTP Requests explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Broken Scanner. The native Help tab includes instructions and support.

Configuration and Use

Save the post, open Link Scanner and start a manual check. It reads saved body and excerpt links, not unsaved text or rendered third-party blocks.

Operating Limits

Manual checks send bounded HTTP requests to permitted public destinations. Private and unsafe targets are rejected. Results are not stored and no scheduled scan runs. A timeout does not prove a link is permanently broken.

Data, Privacy and Deactivation

Manual checks send bounded HTTP requests to permitted public destinations. Private and unsafe targets are rejected. Results are not stored and no scheduled scan runs. A timeout does not prove a link is permanently broken.

Detailed Behavior

Manually check links in saved WordPress content with native editing permissions.

Enable content types under WPSDDC -> Broken Scanner, then open Link Scanner from a saved content editor. All content types start disabled. The native panel works in Classic and Block Editor. Save editor changes before opening the scanner.

Inspect up to 75 unique literal href/src URLs in saved content and excerpt (maximum 256 KiB). Relative links use the object permalink. Check one link with a native form, or use optional JavaScript for sequential progress and stopping. There are no automatic checks, background crawls, repairs or scan history. Disabling/removing the plugin retains its settings only.

Each link uses at most three bounded HTTP requests, starting with HEAD and falling back to a 1 KiB GET only on HTTP 405/501. A three-second timeout applies per request, with at most two validated redirects; DNS/hosting can add time. Private/reserved/loopback destinations and credentials are rejected, including the same site when hosted on a private network. Only HTTP/HTTPS on standard ports 80/443. Failed or restricted checks are not automatically labeled broken. No soft-404, content, fragment or authenticated-link validity is claimed.

Only saved literal HTML attributes are inspected. Unsaved edits, rendered shortcodes/dynamic blocks, CSS, srcset and custom/private fields are outside scope. No frontend output, visitor cookies/tracking or external library. Native admin controls respect the user’s Core color scheme. Results remain only in the current page and disappear on reload.

No third-party scanning service is used. Opening/activating the plugin makes no HTTP checks. On an explicit Check Link or Scan All action, your server contacts the linked public website, sending its URL and query parameters; that destination receives your server IP and applies its own terms/privacy. No site login cookies, authorization header or referrer is added, and the user agent contains no site URL. Check only URLs you intend to contact, especially if query parameters contain tokens. No response bodies, credentials or scan history are stored. Stop prevents queued requests; a server check already started may still finish.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Broken Scanner Screenshot: WordPress Desktop Workspace.
WPSDDC Broken Scanner — WordPress Desktop Workspace.
WPSDDC Broken Scanner Screenshot: WordPress Mobile Workspace.
WPSDDC Broken Scanner — WordPress Mobile Workspace.
WPSDDC Broken Scanner Screenshot: Plugin Setup Guide.
WPSDDC Broken Scanner — Plugin Setup Guide.
WPSDDC Broken Scanner Screenshot: Feature Demo: Link Scanner Feature Demo.
WPSDDC Broken Scanner — Feature Demo: Link Scanner Feature Demo.

WPSDDC Functions Plus

by

WPSDDC Functions Plus

WordPress Plugin

WPSDDC Functions Plus

Duplicate drafts, edit in a focused dialog, confirm saves, select parent categories and organize pages with native taxonomies.

WordPress.org
GitHub

What You Can Do

  • Draft Duplication, Swift Edit and Save Timestamps
  • Parent-Category Selection in Native Controls
  • Independent Page Excerpts and Page Categories/Tags

Documentation

The WPSDDC Functions Plus WordPress Plugin is designed for optional tools for everyday WordPress editing. It helps editors duplicate drafts and streamline selected content or taxonomy actions. This is useful for faster editorial tasks with familiar native controls. Individual functions are optional and retain WordPress permissions.

For practical context on the WPSDDC Functions Plus WordPress Plugin, read Why Native WordPress APIs Beat Extra Dependencies. The official reference on Native WordPress Post Editing explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Functions Plus. The native Help tab includes instructions and support.

Configuration and Use

Enable only the utilities you need, one switch at a time. All six utilities start disabled. Duplication requires an explicit content action.

Operating Limits

Settings and explicitly duplicated content stay in WordPress. Taxonomies start empty. Screen Options use native controls. Disabling the plugin preserves created content.

Data, Privacy and Deactivation

Settings and explicitly duplicated content stay in WordPress. Taxonomies start empty. Screen Options use native controls. Disabling the plugin preserves created content.

Detailed Behavior

Six independent tools, all off by default, support everyday editing:

  • Draft Duplication: confirm a new draft while preserving the original, authorized plain metadata and assigned terms. WooCommerce products use its native duplicator when available.
  • Swift Edit: open the real Core editor in a native dialog, with a normal edit-link fallback and an unsaved-work guard.
  • Save Timestamps: add localized confirmation times to Classic and Block Editor feedback while preserving Core links.
  • Parent Categories: select ancestors in native Classic, Quick and Bulk Edit checklists.
  • Page Excerpts: enable Core excerpt support independently.
  • Page Categories and Tags: organize pages using your own terms, with native editor, REST, columns, filters, Quick/Bulk Edit, term-name search/sorting and optional public archives.

The plugin is for editors and site administrators who want selected small utilities. It does not supply prebuilt categories, assign default terms, replace Screen Options, add icon catalogs or require another WPSDDC plugin. Existing terms/content remain intact. Legacy grouped settings do not silently enable the new switches.

Data: site-local settings, explicitly created draft copies and user-created page taxonomy terms/relationships. Core stores this content locally. Deactivation/removal retains it. There is no HQ import, remote service, telemetry or shared private option.

Frontend: no CSS or JavaScript. Editing utility files and admin search/sort hooks do not load on visitor requests. Only explicitly enabled page excerpts/taxonomies register their Core support and public archive routes. The admin interface inherits the user’s color scheme; the dialog inherits the page’s colors.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Functions Plus Screenshot: WordPress Desktop Workspace.
WPSDDC Functions Plus — WordPress Desktop Workspace.
WPSDDC Functions Plus Screenshot: WordPress Mobile Workspace.
WPSDDC Functions Plus — WordPress Mobile Workspace.
WPSDDC Functions Plus Screenshot: Plugin Setup Guide.
WPSDDC Functions Plus — Plugin Setup Guide.
WPSDDC Functions Plus Screenshot: Feature Demo: Page Editing Tools Feature Demo.
WPSDDC Functions Plus — Feature Demo: Page Editing Tools Feature Demo.

WPSDDC Notes Archive

by

WPSDDC Notes Archive

WordPress Plugin

WPSDDC Notes Archive

Keep personal notes and checklists in WordPress administration, with private storage for each user and site.

WordPress.org
GitHub

What You Can Do

  • Personal Notes and Checklists
  • Explicit Save, Item Ordering and Confirmed Deletion
  • Stale-Save Conflict Detection

Documentation

The WPSDDC Notes Archive WordPress Plugin is designed for private administrative notes and task lists. It helps editors keep personal text entries and checklists for each WordPress user. This is useful for organizing an internal notebook in the dashboard. Personal notes are not published as public site content.

For practical context on the WPSDDC Notes Archive WordPress Plugin, read Document a Plugin So Future You Understands It. The official reference on WordPress User Metadata explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Notes Archive. The native Help tab includes instructions and support.

Configuration and Use

Create a personal note or checklist and save explicitly. Reorder items with accessible buttons. Deleting an entry requires confirmation.

Operating Limits

Plain-text entries belong to the current user and site and survive deactivation or removal. Normal capacity is 100 entries and 100 items per list. Reload after a save conflict. Database administrators can access stored data.

Data, Privacy and Deactivation

Plain-text entries belong to the current user and site and survive deactivation or removal. Normal capacity is 100 entries and 100 items per list. Reload after a save conflict. Database administrators can access stored data.

Detailed Behavior

Notes Archive is for people who write or manage content in WordPress and need a personal working notebook. Contributors, authors, editors and administrators can create notes, update their text, build checklists, mark items complete or incomplete, reorder items with keyboard-accessible buttons and delete individual entries with explicit confirmation. Core metabox controls organize and collapse entries. Changes are saved explicitly; the browser warns about unsaved edits, and stale revisions cannot silently overwrite a newer save.

Entries are plain text and have server-generated modified dates. Normal use is limited to 100 entries per user and site, with up to 100 items per checklist. Long or malformed submissions are rejected without discarding existing content. No rich-text editor, icon picker, symbol catalog, brand marks, Content Ideas, shortcode, widget, frontend block or public sharing feature is included.

Data is stored in WordPress user meta under wpsddc_notes_archive_entries_SITEID. Every operation uses the current user; a submitted target user is ignored. Each site uses a different key, including in Multisite. Core stores metabox layout preferences in its own user meta. This is private within WordPress permissions, not encrypted against database/server administrators. Note data is never sent to an external service. Deactivation or removal preserves entries; deleting a WordPress user removes that user’s metadata through Core.

Normal frontend requests load only the guarded plugin entry file: no feature modules, hooks, shortcodes, styles, scripts or plugin-initiated storage query. Only the Notes screen loads the small scoped layout stylesheet and list enhancement, alongside Core postboxes. WordPress itself can include user metadata in its normal signed-in user cache; there is no claim that stored notes have zero storage size.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Notes Archive Screenshot: WordPress Desktop Workspace.
WPSDDC Notes Archive — WordPress Desktop Workspace.
WPSDDC Notes Archive Screenshot: WordPress Mobile Workspace.
WPSDDC Notes Archive — WordPress Mobile Workspace.
WPSDDC Notes Archive Screenshot: Plugin Setup Guide.
WPSDDC Notes Archive — Plugin Setup Guide.
WPSDDC Notes Archive Screenshot: Feature Demo: Personal Notes Checklists Feature Demo.
WPSDDC Notes Archive — Feature Demo: Personal Notes Checklists Feature Demo.

WPSDDC Advanced Media

by

WPSDDC Advanced Media

WordPress Plugin

WPSDDC Advanced Media

Inspect stored attachment metadata, find images with empty alternative text and optionally manage private credit records.

WordPress.org
GitHub

What You Can Do

  • Optional Details Column and Empty-Alt Filter
  • Native Attachment Metadata Panel
  • Optional Creator Credit, Rights Notice and Source URL

Documentation

The WPSDDC Advanced Media WordPress Plugin is designed for checking attachment metadata and missing image ALT text. It helps editors inspect saved media fields and record optional private image credits. This is useful for a focused WordPress media library audit. Original image files remain unchanged.

For practical context on the WPSDDC Advanced Media WordPress Plugin, read The Weight You Don’t See: Fonts, Images and Hidden Requests. The official reference on WordPress Attachment Metadata explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Advanced Media. The native Help tab includes instructions and support.

Configuration and Use

Open an attachment to inspect supported metadata already stored by WordPress. Enable optional credits only when needed.

Operating Limits

The plugin reads an allowlist of stored Core metadata and saves entered credits. It does not scan raw files for extra EXIF, XMP or GPS data or infer missing information.

Data, Privacy and Deactivation

The plugin reads an allowlist of stored Core metadata and saves entered credits. It does not scan raw files for extra EXIF, XMP or GPS data or infer missing information.

Detailed Behavior

Advanced Media adds practical information to the native Media Library without changing how your files are stored. Enable the optional Media Details list column to see the attachment ID, stored image dimensions and recorded file size. In list view, the alternative-text filter finds images whose Core alt field is absent or exactly empty. Empty alt text can be correct for decorative images; inspect each image in the context where it is used. The plugin does not generate alt text or award SEO/accessibility scores.

A native expandable section in attachment details displays whitelisted metadata already stored by WordPress: file name, MIME type, dimensions, recorded size, alternative text and available camera/credit fields. It never scans original files. Missing or older Core metadata may omit fields such as file size. No complete EXIF/XMP/IPTC parser, GPS display, rescan, regeneration, physical metadata editing or automatic import is provided. Other plugins may filter Core’s metadata API.

Administrators can optionally enable three internal credit fields: creator credit, rights notice and source URL. Media users must have upload permission and permission to edit that specific attachment. Native WordPress save handling is supplemented by a per-attachment nonce, bounded text validation and HTTP/HTTPS-only source URLs. Invalid submissions leave the previous record intact. These fields do not grant a license, verify ownership, alter embedded file metadata or add frontend attribution. They are administrative records, not encryption against database administrators or protection from third-party code that reads post metadata.

Credit data is stored only under _wpsddc_advanced_media_credit in attachment post meta; settings use wpsddc_advanced_media_settings. Deactivation/removal preserves these records. Deleting the attachment removes its metadata through WordPress Core. Existing Core titles, captions, descriptions, alt text, file paths and binary files are not rewritten by this plugin. There is no bulk operation or HQ migration.

No custom CSS, JavaScript, overlay framework, folder taxonomy, avatar behavior, keyword synchronization, language assignment, cron, external request or telemetry is added. Ordinary frontend requests return from the main entry file before runtime/settings hooks load. Native administration screens and forms inherit the user’s WordPress color scheme. Each site in Multisite has its own settings and attachment records.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Advanced Media Screenshot: WordPress Desktop Workspace.
WPSDDC Advanced Media — WordPress Desktop Workspace.
WPSDDC Advanced Media Screenshot: WordPress Mobile Workspace.
WPSDDC Advanced Media — WordPress Mobile Workspace.
WPSDDC Advanced Media Screenshot: Plugin Setup Guide.
WPSDDC Advanced Media — Plugin Setup Guide.
WPSDDC Advanced Media Screenshot: Feature Demo: Media Details Feature Demo.
WPSDDC Advanced Media — Feature Demo: Media Details Feature Demo.

WPSDDC Multilingual Tools

by

WPSDDC Multilingual Tools

WordPress Plugin

WPSDDC Multilingual Tools

Review translation links and optionally use language-specific alt defaults for attachment-generated images with Polylang or WPML.

WordPress.org
GitHub

What You Can Do

  • Provider-Aware Reports with 25 Items per Page
  • Authorized Native Content Edit Links
  • Optional Language-Specific Image Alternative Text

Documentation

The WPSDDC Multilingual Tools WordPress Plugin is designed for reviewing translation links and multilingual image ALT text. It helps editors inspect language relationships and optional attachment descriptions. This is useful for maintaining bilingual WordPress content consistently. Your language plugin remains responsible for linking translations.

For practical context on the WPSDDC Multilingual Tools WordPress Plugin, read Hreflang and Canonical Signals on Bilingual Sites. The official reference on WordPress Internationalization explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.
  • Configure Polylang or WPML with at least two languages; neither is bundled.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Multilingual Tools. The native Help tab includes instructions and support.

Configuration and Use

Choose a supported language provider and configure translated alternative text. Use the report to inspect provider relationships and missing text.

Operating Limits

Providers own language relationships. Alternative text and settings stay local. Polylang was tested installed; WPML is contract-tested and still needs a licensed installation test.

Data, Privacy and Deactivation

Providers own language relationships. Alternative text and settings stay local. Polylang was tested installed; WPML is contract-tested and still needs a licensed installation test.

Detailed Behavior

Use the languages configured in Polylang or WPML to review original and linked translations for public content types and taxonomies you can edit. Search and select a target language. Each report page checks up to 25 items; these are page results, not whole-site totals. Open authorized native edit links to create or link translations in your language provider. Authors see their own content; subscribers cannot open the tools.

An optional administrator setting adds language-specific text fields to native image attachment forms. Core Alternative Text remains the default. Secondary language values can be enabled individually, including an intentional empty value; unchecked languages inherit Core. Nonempty inactive drafts are retained for later editing. The values affect frontend attachment alt defaults while preserving explicit image attributes, authored HTML and block alt text. REST and admin reads retain Core values.

No automatic translation, locale override, fixed language pair, shared reviews, remote service, telemetry or HQ data migration is included. Polylang or WPML must be configured separately with at least two languages. Neither is bundled or installed automatically. Polylang takes precedence if both are active.

Settings and secondary alt metadata are site-local and retained on deactivation/uninstall. With alt behavior disabled, frontend cost is the guarded entry file and one plugin option lookup. With it enabled, only provider/alt helpers load; there are no frontend assets. The read-only report uses one small scoped responsive stylesheet. Native media controls require no custom script.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Multilingual Tools Screenshot: WordPress Desktop Workspace.
WPSDDC Multilingual Tools — WordPress Desktop Workspace.
WPSDDC Multilingual Tools Screenshot: WordPress Mobile Workspace.
WPSDDC Multilingual Tools — WordPress Mobile Workspace.
WPSDDC Multilingual Tools Screenshot: Plugin Setup Guide.
WPSDDC Multilingual Tools — Plugin Setup Guide.
WPSDDC Multilingual Tools Screenshot: Feature Demo: Translation Links Feature Demo.
WPSDDC Multilingual Tools — Feature Demo: Translation Links Feature Demo.

WPSDDC Ecommerce Toolkit

by

WPSDDC Ecommerce Toolkit

WordPress Plugin

WPSDDC Ecommerce Toolkit

Configure clean product URLs, metric attribute displays and missing SKU patterns for WooCommerce.

WordPress.org
GitHub

What You Can Do

  • Conservative Product URL Collision Checks
  • Metric Display in Classic Additional Information
  • User-Defined Sku Templates for Products and Variations

Documentation

The WPSDDC Ecommerce Toolkit WordPress Plugin is designed for optional WooCommerce product management utilities. It helps editors simplify product URLs and handle supported metric attributes or empty SKUs. This is useful for consistent WooCommerce product information management. Each utility is optional and depends on the store configuration.

For practical context on the WPSDDC Ecommerce Toolkit WordPress Plugin, read Extending WooCommerce Checkout Without Slowing It Down. The official reference on Official WooCommerce Permalinks explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.
  • Requires an installed and active WooCommerce.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Ecommerce Toolkit. The native Help tab includes instructions and support.

Configuration and Use

Activate WooCommerce first. Enable only the optional features you need. Define your own SKU templates and language formats; no business identifiers are supplied.

Operating Limits

Settings are local. Optional SKU generation fills missing values only. Language formatting targets classic Additional Information, not WooCommerce Blocks. Existing product data survives deactivation.

Data, Privacy and Deactivation

Settings are local. Optional SKU generation fills missing values only. Language formatting targets classic Additional Information, not WooCommerce Blocks. Existing product data survives deactivation.

Detailed Behavior

Three optional utilities for WooCommerce store owners: clean product URLs with conservative collision checks, metric values in the classic Additional Information table, and configurable SKU patterns for products and variations whose SKU is empty. All three features are off by default.

The default SKU is the local product or variation ID. Patterns accept {ID}, {PARENT_ID}, {LANG} and {CANONICAL_ID}; an ID token is required. The canonical token explicitly selects the configured default-language translation when one exists. Language codes come from Polylang or WPML, never from a built-in language list. Existing/imported SKUs are preserved. Changes apply on a later WooCommerce product save; there is no bulk catalog update. Generated values are bounded and WooCommerce checks uniqueness before a site-local ID/language suffix is added when needed.

Metric conversion displays kilograms and centimeters for all product languages or a selected set of language codes. It works without a translation link. Only the classic WooCommerce Additional Information table is supported; the newer Product Specifications block retains the store’s units. Stored measurements, shipping calculations, cart, checkout and APIs remain unchanged.

Clean URLs need pretty permalinks. Pages, public post types, taxonomy/archive bases and native endpoints take priority; conflicting products retain their original URLs. Polylang language homes are respected. Clean URL routing is conservatively disabled with WPML until its routing contract can be verified. This plugin is not a multilingual catalog or checkout replacement.

Settings are stored in the site-local wpsddc_ecommerce_toolkit_settings option. Generated SKUs use WooCommerce’s product data API. Settings and SKU data remain after deactivation/removal. There is no telemetry, remote request, background job, frontend branding, CSS or JavaScript. Frontend work is limited to the enabled URL or classic attribute feature; SKU generation runs on WooCommerce saves.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Ecommerce Toolkit Screenshot: WordPress Desktop Workspace.
WPSDDC Ecommerce Toolkit — WordPress Desktop Workspace.
WPSDDC Ecommerce Toolkit Screenshot: WordPress Mobile Workspace.
WPSDDC Ecommerce Toolkit — WordPress Mobile Workspace.
WPSDDC Ecommerce Toolkit Screenshot: Plugin Setup Guide.
WPSDDC Ecommerce Toolkit — Plugin Setup Guide.
WPSDDC Ecommerce Toolkit Screenshot: Feature Demo: Woocommerce Sku Feature Demo.
WPSDDC Ecommerce Toolkit — Feature Demo: Woocommerce Sku Feature Demo.

WPSDDC Color Shades

by

WPSDDC Color Shades

WordPress Plugin

WPSDDC Color Shades

Build color shades and tints, compare contrast and copy a reusable palette without changing WordPress appearance.

WordPress.org
GitHub

What You Can Do

  • Eleven Variations from a Base Hex Color
  • Foreground/Background Contrast Comparison
  • Selectable CSS Variables for Manual Export

Documentation

The WPSDDC Color Shades WordPress Plugin is designed for creating color shades and checking contrast. It helps editors compare colors and copy reusable CSS palette variables. This is useful for consistent color palettes for WordPress designs. The tool does not change your site's colors automatically.

For practical context on the WPSDDC Color Shades WordPress Plugin, read Keyboard and Contrast Checks Every Plugin Interface Needs. The official reference on W3C Color Contrast Guidance explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Color Shades. The native Help tab includes instructions and support.

Configuration and Use

Enter a color to generate a generic palette, compare contrast and export CSS variables for your own project.

Operating Limits

Calculations and settings stay local. The utility does not change the administration color scheme or contact a remote service. A contrast result alone does not certify an interface as accessible.

Data, Privacy and Deactivation

Calculations and settings stay local. The utility does not change the administration color scheme or contact a remote service. A contrast result alone does not certify an interface as accessible.

Detailed Behavior

For site creators who need a local color reference, Color Shades generates eleven variations from a base hex color, compares a foreground/background pair and provides selectable CSS variables. Native Core color pickers update the preview locally; Save Changes explicitly stores the three input colors for this site. Exported CSS is plain text for the user to copy into their own design.

The plugin never registers or applies an admin color scheme. It does not recolor the editor, login, toolbar, theme or visitor content, and does not add a theme logo or presets. Admin controls inherit the current user’s Core scheme. No frontend CSS, JavaScript or automatic HTTP requests are added.

Data: only the three validated hex inputs are stored in the site-local wpsddc_color_shades_settings option. No user profile color is changed. Existing settings are retained on deactivation/removal; excluded legacy theming keys are ignored and are dropped on the next explicit settings save. No HQ import, telemetry or remote dependency is included.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Color Shades Screenshot: WordPress Desktop Workspace.
WPSDDC Color Shades — WordPress Desktop Workspace.
WPSDDC Color Shades Screenshot: WordPress Mobile Workspace.
WPSDDC Color Shades — WordPress Mobile Workspace.
WPSDDC Color Shades Screenshot: Plugin Setup Guide.
WPSDDC Color Shades — Plugin Setup Guide.
WPSDDC Color Shades Screenshot: Feature Demo: Color Palette Feature Demo.
WPSDDC Color Shades — Feature Demo: Color Palette Feature Demo.

WPSDDC Redirect Gateway

by

WPSDDC Redirect Gateway

WordPress Plugin

WPSDDC Redirect Gateway

Create local short paths that redirect to configured web, email or telephone destinations.

WordPress.org
GitHub

What You Can Do

  • Up to 50 Exact Local Path Rules
  • Http, Https, Mailto and Tel Destinations
  • Optional Generic Language-Prefix Fallback

Documentation

The WPSDDC Redirect Gateway WordPress Plugin is designed for creating short redirect paths on your own domain. It helps editors connect local aliases to approved web, email or phone destinations. This is useful for organizing short links for WordPress websites. Existing WordPress pages and endpoints take priority over aliases.

For practical context on the WPSDDC Redirect Gateway WordPress Plugin, read Hreflang and Canonical Signals on Bilingual Sites. The official reference on Safe WordPress Redirects explains related technical concepts.

Requirements and Compatibility

  • WordPress 6.0 or later; PHP 8.1 or later.
  • English and Spanish interface.
  • Works without the general HQ plugin; active collection plugins share one WPSDDC menu.

Installation and First Steps

  • Check requirements and use a test installation first.
  • When the official ZIP is available to you, open Plugins → Add New → Upload Plugin, select it and activate it.
  • Open WPSDDC → Redirect Gateway. The native Help tab includes instructions and support.

Configuration and Use

Add your source paths and destination URLs, choose supported status codes and enable only needed rules. Check destinations before saving.

Operating Limits

Up to 50 local rules are supported. Matching navigation receives an HTTP redirect; the server does not fetch the destination. Optional language prefixes depend on your configuration.

Data, Privacy and Deactivation

Up to 50 local rules are supported. Matching navigation receives an HTTP redirect; the server does not fetch the destination. Optional language prefixes depend on your configuration.

Detailed Behavior

Create local short paths that redirect to configured web, email or telephone destinations.

Configure up to 50 exact path/destination pairs, one per line. Destinations may use HTTP, HTTPS, mailto or tel. Redirects are opt-in and apply only to missing public routes requested with GET or HEAD; existing pages, posts, admin, REST, cron, AJAX and form submissions keep their normal behavior. Language-prefix fallback is disabled by default. When explicitly enabled, it accepts generic two-letter codes and regional codes; an exact stored path always takes priority over the fallback regardless of rule order. Request query parameters never supply or alter destinations. Invalid rules, reserved paths, credentials in URLs, header injection and detected local redirect cycles are rejected. No analytics, click logging, server-side fetching, rewrite flushing or runtime assets are added. Permanent redirects can be cached by browsers; use 302 while testing changes.

The plugin uses local WordPress APIs and does not send telemetry. Settings are retained after deactivation or removal.

Frequently Asked Questions

Do I Need the Whole Collection?

No. Install only the plugins you need and check any product-specific dependencies listed above.

Is It Available on WordPress.org?

Version 1.0.0 is in preparation and is not published on WordPress.org yet. The official link will be added after an approved version is published.

Support and License

Check the documented limits first. Include the plugin, WordPress and PHP versions and reproduction steps when requesting support. Do not include passwords or personal data.

Contact StudioDDC

GPL-2.0-or-later license. Author: StudioDDC. Native WordPress controls.

Real Screenshots

Captured in real test WordPress installations with synthetic content. Images show implemented features and do not depict client installations.

WPSDDC Redirect Gateway Screenshot: WordPress Desktop Workspace.
WPSDDC Redirect Gateway — WordPress Desktop Workspace.
WPSDDC Redirect Gateway Screenshot: WordPress Mobile Workspace.
WPSDDC Redirect Gateway — WordPress Mobile Workspace.
WPSDDC Redirect Gateway Screenshot: Plugin Setup Guide.
WPSDDC Redirect Gateway — Plugin Setup Guide.
WPSDDC Redirect Gateway Screenshot: Feature Demo: Redirect Rules Feature Demo.
WPSDDC Redirect Gateway — Feature Demo: Redirect Rules Feature Demo.

Search WP StudioDDC
WP StudioDDC
Powered by  GDPR Cookie Compliance (opens in a new tab)
Privacy

You control optional cookies. Necessary cookies are always active. See our Cookie Policy.