Plugin Directory

Changeset 3344123


Ignore:
Timestamp:
08/13/2025 04:21:47 PM (8 months ago)
Author:
nsp-code
Message:

Version: 2.7.2

Location:
wp-hide-security-enhancer
Files:
233 added
4 edited

Legend:

Unmodified
Added
Removed
  • wp-hide-security-enhancer/trunk/include/class.compatibility.php

    r3275408 r3344123  
    7272                    include_once(WPH_PATH . 'compatibility/shortpixel-image-optimiser.php');
    7373                    include_once(WPH_PATH . 'compatibility/fluentform.php');
     74                    include_once(WPH_PATH . 'compatibility/flying-press.php');
    7475                    include_once(WPH_PATH . 'compatibility/ultimate-member.php');                   
    7576                    include_once(WPH_PATH . 'compatibility/swift-performance.php');
  • wp-hide-security-enhancer/trunk/modules/components/login_2fa.php

    r3275408 r3344123  
    3232                   
    3333                    add_action( 'login_form_validate_2fa',      array( $this, 'login_form_validate_2fa' ) );
     34                   
     35                   
     36                    add_shortcode( 'wph-2fa-user-settings',     array( $this, 'shortcode_2fa_user_settings') );
    3437
    3538                }
     
    749752   
    750753   
     754            function shortcode_2fa_user_settings()
     755                {
     756                   
     757                    if ( ! is_user_logged_in() )
     758                        return;
     759                   
     760                    global $current_user;
     761                   
     762                    ob_start();
     763                   
     764                    wp_enqueue_style( '2fa-front', WPH_URL . '/assets/css/2fa-front.css');
     765                   
     766                    $this->profile_2fa_options( $current_user );
     767                   
     768                    $html   =   ob_get_contents();
     769                    ob_end_clean();
     770                   
     771                    return $html;
     772                       
     773                }
     774   
     775   
    751776            function profile_2fa_options_update( $user_id )
    752777                {
  • wp-hide-security-enhancer/trunk/readme.txt

    r3332276 r3344123  
    55Requires at least: 2.8
    66Tested up to: 6.8.2
    7 Stable tag: 2.7
     7Stable tag: 2.7.2
    88License: GPLv2 or later
    99
     
    5454* 2FA - Two-factor Authentication - Authenticator App
    5555* 2FA - Two-factor Authentication - Recovery Codes
     56* 2FA - Two-factor Authentication - Shortcode for front-side user settings interface
    5657* Google Captcha
    5758* Blocks default wp-login.php
     
    342343Feel free to contact us at [email protected] for fast support.
    343344
     345
     346
     347
     348
    344349= Will the Plugin Alter Anything on My Server? =
    345350
    346 Absolutely Nothing!
    347 The plugin does not modify any files or directories on your server. All processes are handled virtually using URL rewrite techniques and WordPress filters to seamlessly integrate its functionalities and features. Your server remains completely untouched!
     351Under the hood, this plugin never writes to, deletes, or modifies any existing files or directories on your server. Instead, it leverages WordPress’s built-in hook system and virtual URL rewrite rules—applied in memory—to seamlessly redirect and mask asset links. Rest assured, your core files, themes, and plugins remain exactly as you left them, with zero risk of unintended changes.
    348352
    349353= Is This Plugin Suitable for Someone Without PHP Knowledge? =
    350354
    351 Absolutely! No PHP knowledge is required. The plugin’s features and functionalities are applied automatically and can be easily managed through a user-friendly, descriptive admin interface.
     355Yes—100% beginner-friendly.
     356You don’t need to write a single line of PHP to customize or manage this plugin. Every feature is controlled via a clear, intuitive admin panel with descriptive labels, tooltips, and contextual help. Whether you want to hide common WordPress paths, rename your wp-content folder, or inject security headers, each option can be toggled on or off with a simple click. If you ever get stuck, hover over the question-mark icons for guidance, or check out our step-by-step documentation.
    352357
    353358= Is There a Demo Available to Explore? =
     
    357362= Can I Use the Plugin on an Nginx Server? =
    358363
    359 The free version of the plugin cannot generate the required Nginx rewrite rules for full-stack Nginx servers. However, it is fully compatible with Apache, LiteSpeed, IIS, and Nginx when used as a reverse proxy.
     364Free Version: Does not auto generate native Nginx rewrite directives. However, you can still run it behind an Nginx reverse proxy or on hybrid setups (e.g., Apache + Nginx). However, it is fully compatible with Apache, LiteSpeed, IIS, and Nginx when used as a reverse proxy.
    360365For Nginx conside  <a target="_blank" href="https://wp-hide.com">WP Hide PRO</a>.
    361366
     367WP Hide PRO: Includes a dedicated UI for generating Nginx configuration snippets—simply paste them into your server block to enable full URL masking, asset renaming, and security header rules. For more details, check out WP Hide PRO.
     368
    362369= Can I Still Update WordPress, Plugins, and Themes? =
    363370
    364 Yes, everything works as usual. The plugin does not interfere with your ability to update WordPress core, plugins, or themes. You can run updates at any time without any issues.
     371Yes, updates remain effortless.
     372Our plugin is designed to play nicely with the WordPress update process. You can upgrade your core, themes, and all other plugins through the dashboard or via WP-CLI without disabling WP Hide. All rewrite rules and filters persist through updates, so there’s no downtime or extra steps required.
    365373
    366374= Does the Plugin Affect My Website’s SEO? =
    367375
    368 Not at all. The plugin only modifies asset links (such as CSS, JavaScript, and media files) and does not alter actual content URLs. There is no negative impact on SEO whatsoever.
     376Not in the slightest.
     377We only rewrite the paths to static assets (CSS, JS, images) and administrative URLs—your publicly visible content URLs (posts, pages, categories) remain unchanged. Search engines will continue to index your site normally, and any existing sitemaps or canonical tags will work exactly as before. In fact, by hiding version parameters and generic WordPress identifiers, you may see a slight improvement in perceived site quality.
    369378
    370379= Is the Plugin Compatible with My Site’s Cache? =
    371380
    372 Yes, the plugin works seamlessly with any caching plugin installed on your site.
     381Fully compatible.
     382Whether you’re using WP Super Cache, W3 Total Cache, LiteSpeed Cache, or any other popular caching layer, WP Hide integrates without conflict. All rewritten URLs are cached just like your standard assets. If you enable HTML, CSS, or JS minification in your cache plugin, WP Hide will automatically adjust to serve the correct file paths.
    373383
    374384= What Are HTTP Security Headers? =
    375385
    376 HTTP Security Headers are a powerful tool to enhance your website’s security. The plugin simplifies the process of adding these headers through an intuitive graphical interface—no coding or manual file editing required.
     386Critical defenses, made easy.
     387HTTP Security Headers (like Content Security Policy, X-Frame-Options, and Strict-Transport-Security) instruct browsers to apply extra safeguards when serving your site. Normally, you’d have to edit .htaccess or web server config files—now you can add, customize, and test these headers directly from a graphical interface. No manual coding, no syntax headaches; just point and click level security hardening.
    377388
    378389= Which Servers Are Compatible with This Plugin? =
    379390
    380 The free version of WP-Hide works seamlessly with Apache and IIS servers, as well as any setup that relies on .htaccess for configuration. For other server types, consider upgrading to the <a target="_blank" href="https://wp-hide.com">WP Hide PRO</a> version.
     391Out of the box:
     392•    Apache (with .htaccess support)
     393•    IIS (web.config)
     394•    Any server behind Nginx, Varnish, or HAProxy
     395
     396For other environments:
     397Consider upgrading to <a target="_blank" href="https://wp-hide.com">WP Hide PRO</a>, which provides tailored configuration snippets and an enhanced Setup page for Nginx, OpenLiteSpeed, and more.
    381398
    382399= How Can I Use the Plugin with My OpenLiteSpeed Server? =
    383400
    384 If you’re running OpenLiteSpeed, here are a few steps to ensure compatibility:
    385 
    386 * Verify that your server processes the .htaccess file, where rewrite rules are stored. For more details, refer to this <a target="_blank" href="https://www.litespeedtech.com/support/forum/threads/htaccess-is-ignored.15500/">support thread</a>.
    387 
    388 * If you’re using the LiteSpeed Cache plugin, disable the CSS/JS Minify option in the Optimization Settings.
    389 
    390 * If your server requires rewrite rules to be placed in a different file (e.g., a config file), consider upgrading to the <a target="_blank" href="https://wp-hide.com/wp-hide-pro-now-available/">WP Hide PRO</a> version, which includes a Setup page for generating the necessary rewrite code.
     4011.    Enable .htaccess Processing
     402Make sure your OpenLiteSpeed instance is configured to read .htaccess files—see this support thread for guidance.
     4032.    Adjust Cache Plugin Settings
     404If you use LiteSpeed Cache, turn off the CSS/JS Minify option (under Optimization Settings) to prevent conflicts with WP Hide’s rewrite rules.
     4053.    Custom Config File
     406If your server requires rules outside of .htaccess (e.g., in httpd-config.conf), WP Hide PRO can generate the exact rewrite blocks you need—no guesswork involved. See WP Hide PRO details.
    391407
    392408= How Do I Use the Plugin on a Bitnami Setup? =
     
    409425If you see the error “Unable to write custom rules to your .htaccess. Is this file writable?”, follow these steps:
    410426
    411 * Ensure the .htaccess file is writable (typically rw-rw-r– / 0664 permissions) and owned by the same group as PHP.
    412 
    413 * Other plugins or themes might interfere with rewrite rules. Temporarily disable them to identify the culprit.
    414 
    415 * Deactivate and reactivate the WP Hide plugin—this has resolved the issue for some users.
    416 
    417 * Create a backup of your .htaccess file, delete it, and go to Settings > Permalinks to regenerate it. Then, update WP Hide settings to rewrite the .htaccess file.
    418 
     4271.    Verify File Permissions. Ensure .htaccess has permissions 0664 (rw-rw-r–) or 0644, owned by the same user/group running PHP.
     4282.    Check for Conflicts. Temporarily disable other plugins or themes that may lock or rewrite .htaccess. Reactivate them one by one to isolate the conflict.
     4293.    Reinitialize the Plugin. Deactivate and then reactivate WP Hide; this often resets internal flags and allows writing.
     4304.    Regenerate .htaccess. Backup and delete your existing .htaccess, then visit Settings → Permalinks to rebuild it. Afterward, return to WP Hide settings to reapply your custom rules.
     431                           
    419432= Something Went Wrong – How Can I Recover My Site? =
    420433Don’t worry—your site will not be harmed. Here’s how to troubleshoot:
     
    442455= What to do if I can’t find a functionality that I’m looking for? =
    443456
    444 Please get in touch with us and we’ll do our best to include it inthe next version.
     457We’re continuously improving WP Hide! If there’s a feature you need—whether it’s a new rewrite rule type, custom header option, or integration with third party plugins—please contact us. Your suggestions drive our roadmap, and we’ll do our best to include it in an upcoming release.
     458
    445459
    446460== Screenshots ==
     
    450464
    451465== Changelog ==
     466
     467= 2.7.2 =
     468* Front shortcode [wph-2fa-user-settings] for user 2FA options configuration  https://wp-hide.com/2fa-shortcode-let-users-manage-2fa-from-the-front-end/
     469* Compatibility file for FlyingPress
    452470
    453471= 2.7 =
  • wp-hide-security-enhancer/trunk/wp-hide.php

    r3332276 r3344123  
    66* Author: Nsp Code
    77* Author URI: http://www.nsp-code.com
    8 * Version: 2.7
     8* Version: 2.7.2
    99* Text Domain: wp-hide-security-enhancer
    1010* Domain Path: /languages/
Note: See TracChangeset for help on using the changeset viewer.