Title: DCT Sollers
Author: doblejou
Published: <strong>November 19, 2026</strong>
Last modified: November 19, 2026

---

Search plugins

![](https://ps.w.org/dct-sollers/assets/banner-772x250.png?rev=3812575)

![](https://ps.w.org/dct-sollers/assets/icon-256x256.png?rev=3812564)

# DCT Sollers

 By [doblejou](https://profiles.wordpress.org/doblejou/)

[Download](https://downloads.wordpress.org/plugin/dct-sollers.0.2.27.zip)

 * [Details](https://wordpress.org/plugins/dct-sollers/#description)
 * [Reviews](https://wordpress.org/plugins/dct-sollers/#reviews)
 *  [Installation](https://wordpress.org/plugins/dct-sollers/#installation)
 * [Development](https://wordpress.org/plugins/dct-sollers/#developers)

 [Support](https://wordpress.org/support/plugin/dct-sollers/)

## Description

DCT Sollers brings four independent modules to Settings  DCT Sollers. Enable only
what you need. Each module has its own tab, accessible even when the module is off,
and disabling a module preserves its settings and data.

 * **Login protection:** Limits failed sign-in attempts per IP, temporarily blocks
   access to `wp-login.php`, and lets administrators review active blocks and unblock
   individual IPs. Enabled by default.
 * **CLI migration:** Exports and imports single-site installations in the plugin’s
   own ZIP format. Run commands in WP-CLI; the admin tab shows instructions only.
   Enabled by default.
 * **CDN:** Rewrites eligible local asset URLs to your existing CDN hostname. Choose
   file extensions and exclusions without changing stored URLs or files. Disabled
   by default.
 * **Frontend:** Choose which WordPress-generated tags and assets to remove, which
   hosts to connect to early, and which WOFF2 fonts or front-page image to preload.
   Disabled by default; all settings start off or empty.

The plugin uses native WordPress APIs without requiring an external PHP library 
or a commercial service. WordPress Multisite is not supported.

#### Login protection and privacy

Defaults: 3 failed attempts within a rolling 1-minute window trigger a 15-minute
block. The threshold, time window, and block duration are configurable. Further 
requests do not extend a block, and changing the settings does not change when existing
blocks expire. REST, XML-RPC, and external authentication forms are not protected.

IP addresses and timestamps for failed attempts and blocks are stored locally, without
credentials. Hourly cleanup removes expired records and depends on WP-Cron. Blocks
expire on time even if cleanup is delayed. Shared IP addresses share their attempt
counter and block.

The IP address comes exclusively from REMOTE_ADDR. When using a proxy or CDN, configure
the server to resolve the real visitor IP correctly; the plugin does not interpret
proxy headers. Site operators should disclose this processing in their privacy policy
and determine its legal basis.

#### Migration through WP-CLI

Export from the source site, then run the import commands from the destination site,
with WordPress and DCT Sollers already installed. Start with `--dry-run` to validate
the package and review the plan without changing destination files or tables. Database
rows are checked against foreign key constraints during the actual import, not during
the dry run.

    ```
    wp dct-sollers export --file=/ruta/privada/sitio.zip
    wp dct-sollers import --file=/ruta/privada/sitio-0123456789abcdef0123456789abcdef.zip --mode=merge --dry-run
    wp dct-sollers import --file=/ruta/privada/sitio-0123456789abcdef0123456789abcdef.zip --mode=merge
    wp dct-sollers import --file=/ruta/privada/sitio-0123456789abcdef0123456789abcdef.zip --mode=mirror
    ```

Export appends a random 32-character hexadecimal identifier to the filename and 
prints the final path. Use that path on the destination, or the private path where
you transferred the ZIP. Exported archives and import packages are not deleted automatically.

Importing overwrites data, users, and code. It does not create a backup or guarantee
rollback. Make an independent backup before importing and only use trusted packages.
Packages contain unencrypted sensitive data: store them outside public directories
with restricted access.

Both modes replace included tables in full and overwrite matching files. `merge`
keeps additional files and tables; `mirror` removes them within the migration scope.
Exclusions are preserved. The destination keeps its existing public and WordPress
URLs unless you specify `--home-url` or `--site-url`. WordPress core, `wp-config.
php`, and server configuration are not migrated. The ZIP format is not compatible
with `.wpress`.

For a live import, WP-CLI first prints an isolated startup command using `--exec`
and stops before changing the site. Run the printed command yourself. After the 
data is imported, run the full finalization command it prints. Maintenance mode 
stays on until verification and cache cleanup succeed. Do not start another migration
between those steps. If a live import fails after changes begin, the site may be
left partially restored and in maintenance mode.

Migration requires WP-CLI, 64-bit PHP, ZipArchive, mysqli, and InnoDB tables. Custom
local content paths are supported, but overlapping roots, multiple theme roots, 
path collisions, symbolic links, views, triggers, and partitioned tables are not.
Use an absolute export path in an existing private directory. Export never overwrites
an existing ZIP; do not use an archive left behind by an interrupted export.

#### CDN and external connections

The administrator must configure a CDN separately. The plugin does not configure
providers, upload files, or purge caches. It rewrites resources in public HTML and
content.rendered and excerpt.rendered fields for REST post types, not arbitrary 
JSON or external CSS/JS files.

When this module is enabled, visitors request rewritten resources from the selected
CDN hostname. Its provider may receive visitor IP addresses and the usual HTTP request
data. Review the provider’s terms and privacy policy before configuring the hostname.

Saving settings makes no external requests. The Check CDN button explicitly sends
a HEAD request to the saved hostname at wp-includes/images/blank.gif, with the site
origin as Referer and without following redirects. HTTP 200 does not certify all
resources or their CORS headers. Fonts require appropriate CORS configuration at
the CDN/origin. Invalidate page caches after changing module settings or status.
Do not use this module simultaneously with CDN Enabler.

#### Frontend optimization and external connections

Cleanup options cover emoji compatibility assets, RSD links, shortlinks, Dashicons
for logged-out visitors, REST and oEmbed discovery, the HTML generator tag, and 
separate RSS discovery controls for content and comments. Each option explains what
it removes and what stays available. Removing discovery links does not disable the
corresponding endpoints or feeds. Removing the HTML generator tag is cosmetic, not
a security measure.

Frontend uses native WordPress resource-hint and preload APIs. Configure up to 10
HTTP(S) preconnect origins, 10 DNS-prefetch hostnames, 5 absolute WOFF2 font URLs
and one absolute image URL for the non-paginated front page. Fonts use anonymous
CORS. Do not preload unnecessary resources: this can make performance worse. Visitor
Dashicons cleanup may affect theme icons; dependency styles can still require Dashicons.

No resources are downloaded by the server. Configured hints and preloads may cause
visitors’ browsers to connect to third parties before those resources are used. 
Use trusted destinations consistent with your privacy and consent policy. No third-
party destinations are configured automatically. Match actual theme/CDN resource
URLs, including query parameters, and invalidate page caches after changes. CDN 
HTML rewriting also applies to eligible preload URLs. The module does not generate
critical CSS, defer scripts globally, or remove other plugins’ assets automatically.

## Screenshots

[⌊Modules: enable or disable each tool independently and see its saved status.⌉⌊
Modules: enable or disable each tool independently and see its saved status.⌉[

Modules: enable or disable each tool independently and see its saved status.

[⌊Login protection: configure the threshold, time window, and block duration, and
manage active IP blocks.⌉⌊Login protection: configure the threshold, time window,
and block duration, and manage active IP blocks.⌉[

Login protection: configure the threshold, time window, and block duration, and 
manage active IP blocks.

[⌊CLI migration: see export, validation, import, and finalization instructions.⌉⌊
CLI migration: see export, validation, import, and finalization instructions.⌉[

CLI migration: see export, validation, import, and finalization instructions.

[⌊CDN: set the hostname, file extensions, and exclusions, and check the saved configuration.⌉⌊
CDN: set the hostname, file extensions, and exclusions, and check the saved configuration
.⌉[

CDN: set the hostname, file extensions, and exclusions, and check the saved configuration.

[⌊Frontend: choose cleanup options and configure resource hints and preloads.⌉⌊Frontend:
choose cleanup options and configure resource hints and preloads.⌉[

Frontend: choose cleanup options and configure resource hints and preloads.

## Installation

 1. Search for DCT Sollers under Plugins  Add Plugin, or upload the ZIP from that screen.
 2. Activate DCT Sollers.
 3. Open Settings  DCT Sollers and configure the modules you need.
 4. Before enabling CDN rewriting, configure its hostname and verify the service and
    CORS.

To update, use WordPress’s plugin updater or replace the plugin files without uninstalling.
Deactivation preserves data; uninstalling removes the IP table, plugin settings,
and scheduled cleanup event. Exported ZIP files are not deleted on uninstall.

## FAQ

### How can I unblock an administrator?

From another IP address, use Settings  DCT Sollers  Login protection. Alternatively,
use WP-CLI:

    ```
    wp eval 'DCTSollers_Store::unlock("192.0.2.10");'
    ```

### Does this replace a firewall?

No. Protection is IP-based and limited to wp-login.php. It does not replace server-
side protection or a WAF against distributed attacks.

### Can I run a migration from a browser?

No. The migration tab only displays instructions; exporting and importing require
WP-CLI.

### Can I switch from DCT WP Hero or an older build that uses a different internal prefix?

DCT Sollers does not import settings, blocks, scheduled events, or migration packages
from DCT WP Hero or builds with earlier internal prefixes. Make a separate backup,
deactivate the old plugin, and configure DCT Sollers again. Do not run both plugins
together. The CLI command is `wp dct-sollers`.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“DCT Sollers” is open source software. The following people have contributed to 
this plugin.

Contributors

 *   [ doblejou ](https://profiles.wordpress.org/doblejou/)

[Translate “DCT Sollers” into your language.](https://translate.wordpress.org/projects/wp-plugins/dct-sollers)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/dct-sollers/), check
out the [SVN repository](https://plugins.svn.wordpress.org/dct-sollers/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/dct-sollers/) by
[RSS](https://plugins.trac.wordpress.org/log/dct-sollers/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 0.2.27

 * Add a cryptographically random 128-bit identifier to exported archive filenames
   and display the final local path for imports.
 * Retain private archive storage, 0600 permissions and temporary-file cleanup; 
   exported archives remain under operator control.

#### 0.2.26

 * Require explicit operator-run migration startup and finalization without launching
   programs from PHP.
 * Publish verified private exports without hard links or overwriting existing files.
 * Use WordPress filesystem APIs for migration deletions and identify persistent
   maintenance per import.
 * Remove only the matching maintenance file after verification and cache cleanup,
   without evaluating its contents.
 * Centralize plugin paths and URLs using WordPress directory functions.
 * Reject package entries that collide with customized destination roots before 
   any site writes.
 * Support unconditional mu-plugin directory definitions during isolated configuration
   loading without hiding unrelated diagnostics.
 * Translate module labels only for presentation after init, avoiding early translation-
   loading notices.

#### 0.2.25

 * Maintenance release for directory review; enable WordPress debugging throughout
   the disposable test suites.

#### 0.2.24

 * Resolve customized local migration directories and preserve destination uploads
   settings.
 * Load the ABSPATH-protected import worker through native WP-CLI isolation startup.
 * Make Settings API sanitization explicit at registration.
 * Switch all internal identifiers to dctsollers without compatibility with previous
   data or packages.

#### 0.2.23

 * Group each Frontend cleanup option’s explanations in its own collapsed accordion
   while keeping checkboxes visible.

#### 0.2.22

 * Package the current development changes for distribution.

#### 0.2.21

 * Establish independent settings, storage and CLI commands for the Sollers plugin.
 * Install separately without importing previous plugin settings, login blocks or
   migration archives.
 * Document narrowly scoped CLI diagnostic exceptions and test that URL conflicts
   identify the relevant configuration constant.

#### 0.2.20

 * Move login storage initialization and scheduled cleanup into module lifecycle
   callbacks.
 * Separate login and CDN settings into dedicated classes with consistent defaults,
   validation and read methods.
 * Split migration destination resolution, planning and file restoration from CLI
   coordination while preserving safety checks.
 * Add independent module test runners using shared disposable-site infrastructure.

#### 0.2.19

 * Redesigned the administration interface with responsive module cards, clearer
   navigation and visible saved module states.
 * Added scoped, dependency-free CSS loaded only on the plugin settings screen, 
   without custom JavaScript.
 * Improved keyboard focus, narrow-screen tables and cleanup option layout while
   preserving visible help.
 * Removed duplicate HTML identifiers from CDN and IP unlock forms without changing
   nonce protection.

#### 0.2.18

 * Added independent REST/oEmbed discovery, HTML generator and content/comment RSS
   discovery cleanup options, all off by default.
 * Added visible explanations of what each cleanup removes, preserves and may affect,
   with accessible help for every checkbox.
 * Preserve existing settings when adding the new cleanup options and keep REST,
   oEmbed and feed endpoints available.
 * Prefix frontend template variables and document narrowly scoped Plugin Check 
   false positives.

#### 0.2.17

 * Added the optional Frontend module with emoji, RSD, shortlink and visitor Dashicons
   cleanup.
 * Added configurable preconnect, DNS prefetch, WOFF2 font preloads and a front-
   page image preload using native WordPress APIs.
 * Added frontend settings validation and HTTP integration tests, including CDN 
   rewriting, permissions and persistence.

#### 0.2.16

 * Validate DOCUMENT_ROOT types during export while preserving WP-CLI support for
   absent or empty values.
 * Prefix migration finalization and verification helper variables.

#### 0.2.15

 * Added author and contributor metadata.
 * Use WordPress-compatible writable checks during migration.
 * Escape control characters in CLI diagnostics without HTML-encoding terminal output.
 * Document scoped SQL, streaming, filesystem, and early-bootstrap review exceptions.

#### 0.2.14

 * Metadata and documentation preparation for the WordPress directory.
 * Translator comments, read-only admin navigation handling, and prefixed template
   variables.
 * WordPress URL parsing and explicit WordPress/CLI guards for migration helper 
   scripts.

#### 0.2.13

 * Login protection, CLI migration, and CDN modules.

## Meta

 *  Version **0.2.27**
 *  Last updated **3 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 7.0 or higher **
 *  Tested up to **7.1.5**
 *  PHP version ** 8.4 or higher **
 * Tags
 * [cdn](https://wordpress.org/plugins/tags/cdn/)[login](https://wordpress.org/plugins/tags/login/)
   [migration](https://wordpress.org/plugins/tags/migration/)[security](https://wordpress.org/plugins/tags/security/)
 *  [Advanced View](https://wordpress.org/plugins/dct-sollers/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/dct-sollers/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/dct-sollers/reviews/)

## Contributors

 *   [ doblejou ](https://profiles.wordpress.org/doblejou/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/dct-sollers/)