DCT Sollers Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
DCT Sollers provides independent modules configured under Settings DCT Sollers. It uses WordPress APIs without mandatory commercial services or external PHP libraries.
- Login protection: limits failed attempts per IP and temporarily blocks all access to wp-login.php. Enabled by default.
- CLI migration: exports and imports sites using its own ZIP format, exclusively through WP-CLI. Enabled by default.
- CDN: rewrites local public resource URLs to an administrator-configured hostname. Disabled by default.
- Frontend: optional emoji, RSD, shortlink, visitor Dashicons, REST/oEmbed discovery, HTML generator and separate content/comment feed discovery cleanup, resource hints, WOFF2 preloads and one front-page image preload. Disabled by default; all settings initially off or empty.
Disabling a module preserves its settings and data. The plugin requires a single-site installation; multisite is not supported.
Login protection and privacy
Defaults: 3 failed attempts within 1 minute, followed by a 15-minute block. Further requests do not extend a block. 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
Examples:
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 --yes
Export appends a cryptographically random 128-bit identifier (32 hexadecimal characters) to the base filename and displays the final path. Replace the illustrative import filename above with that actual path. Random names do not replace private storage. Temporary working files are cleaned up; exported archives and imported source packages remain under the operator’s control and are not automatically deleted.
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.
Merge replaces complete included tables and matching files, preserving additional items. Mirror also removes additional items within the non-excluded migration scope. WordPress core, wp-config.php, and server configuration are not migrated. The package format is not compatible with .wpress.
Requires WP-CLI, 64-bit PHP, ZipArchive, mysqli and InnoDB tables. Local content, plugins, themes, mu-plugins and uploads locations are resolved from WordPress and may be customized. Overlapping roots, multiple theme roots, logical-name collisions, views, triggers, partitions and symbolic links are rejected. Import requires an explicit isolated startup: it stops before writing and prints the native WP-CLI –exec command for the operator to run. The plugin never launches programs. After data publication it prints a separate finalization chain for the operator; maintenance stays enabled until all checks and cache cleanup succeed. Do not run another migration between these phases. The worker requires ABSPATH and CLI. A failure during the destructive phase may leave a partial state; maintenance mode remains enabled.
Export creates a new private ZIP without overwriting existing files or using hard links. The final copy is verified, but publication is not atomic: a forced interruption can leave a partial ZIP that must not be used.
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
Each cleanup option explains what it removes, what it preserves and its precautions. REST/oEmbed discovery cleanup removes announcements, not endpoints or existing embedded content. Content and comment RSS discovery are controlled separately; feeds remain accessible directly, but automatic subscription discovery may stop working. Removing the HTML generator tag is cosmetic, not a security measure; feed generators are preserved. These new cleanup settings remain off when upgrading existing configurations. Removing discovery metadata offers only small performance savings.
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
No screenshots provided

