WordPress.org
Get WordPress

Plugin Directory

Changeset 3326687


Ignore:
Timestamp:
07/12/2025 10:07:06 AM (9 months ago)
Author:
tehling
Message:

update readme.txt

File:
1 edited

Legend:

Unmodified
Added
Removed

  • otp-content-protect/trunk/readme.txt

    r3326638 r3326687  
    22Contributors: tehling
    33Donate link: https://die-mainagentur.de
    4 Tags: otp, password, content protection, security, one-time password
     4Tags: otp, content protect, password protect, content locker, no registration
    55Requires at least: 6.0
    66Requires PHP: 7.0
    … …  
    1010License URI: https://www.gnu.org/licenses/gpl-2.0.html
    1111
    12 Protects selected content with one-time passwords (OTPs).
     12The easiest way to protect WordPress content with an OTP. Secure posts and pages with a one-time password—no user registration required.
    1313
    1414== Description ==
    15 OTP Content Protect allows administrators to create secure one-time passwords for individual posts, pages, and custom post types. Visitors must enter the correct OTP to view the protected content. After a single use, an OTP can optionally be reset for reuse.
     15
     16As a WordPress owner who values both **security and a seamless user experience**, you often face the challenge of protecting sensitive information. Most password solutions force your visitors to register for an account, granting them potential access to your WordPress environment.
     17
     18**This is where "OTP Content Protect" comes in, offering an innovative way to protect your content with a One-Time Password (OTP).**
     19
     20Our plugin was designed to give you full control over your content without opening the doors to your WordPress backend for strangers. Easily and effectively protect individual posts, pages, or even downloads. Your visitors don't need an account and don't have to register—they simply enter the one-time password you provide and get instant access.
     21
     22By not granting unnecessary backend access, you actively minimize the risk of hacker or spam activities. "OTP Content Protect" is the perfect blend of simplicity, security, and innovation, making it the ideal password protection for your WordPress site when you need to lock specific content without burdening users with registration.
     23
     24= Support & Feature Requests =
     25
     26We are constantly developing the plugin and welcome your feedback!
     27
     28* **For questions or issues,** please use the official [Support Forum on WordPress.org](https://wordpress.org/support/plugin/otp-content-protect/) or report a bug directly via our [Submit a Bug form](https://die-mainagentur.de/en/wordpress-plugin-otp-content-protect/#submitbug).
     29* **Have an idea for a new feature?** Submit your feature request easily through our website: [Submit a Feature Request](https://die-mainagentur.de/en/wordpress-plugin-otp-content-protect/#featurerequest).
    1630
    1731== Features ==
    1832
    19 * Generates alphanumeric OTPs (8–10 characters)
    20 * Protects posts, pages, or any custom post type
    21 * AJAX-powered content list with search and post-type tabs
    22 * Stores creation date, expiration date, and usage timestamp
    23 * Optionally reset a used OTP for reuse
    24 * Fully internationalized (i18n)
    25 * Uninstall script removes the plugin’s database table
     33* **Protection Without Registration:** The key advantage—visitors don't need a WordPress account.
     34* **Flexible Content Protection:** Secure posts, pages, or any custom post type.
     35* **Simple Password Generation:** Creates secure, alphanumeric OTPs (8–10 characters).
     36* **Full Control:** Stores creation date, optional expiration date, and a timestamp of when it was used.
     37* **Reusable Passwords:** A used OTP can easily be reset for reuse.
     38* **Modern Admin Interface:** AJAX-powered content list with search and convenient post-type tabs.
     39* **Clean Uninstall:** An uninstall script completely removes all plugin data from the database upon deletion if desired.
     40* **Built for the World:** Fully internationalized (i18n) and ready for translation.
    2641
    2742== Installation ==
    2843
    29 1. Unzip and upload the `otp-content-protect` folder to your `/wp-content/plugins/` directory.
    30 2. Activate the plugin through the 'Plugins' menu in WordPress.
    31 3. Navigate to Settings → OTP Protect to configure and generate OTPs.
     441.  Unzip and upload the `otp-content-protect` folder to your `/wp-content/plugins/` directory. Alternatively, find and install it directly via the "Add New" plugin screen.
     452.  Activate the plugin through the 'Plugins' menu in WordPress.
     463.  Navigate to Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> OTP Protect to configure and generate OTPs.
     47
     48== Usage ==
     49
     501.  Go to the OTP Protect settings page.
     512.  Select the content to protect and generate or enter an OTP.
     523.  (Optional) Set an expiration date.
     534.  Save the OTP and share it with the intended users.
     545.  When a visitor accesses the protected content, they will see a simple input form for the password.
     556.  Upon valid entry, the original content is displayed instantly.
     567.  In the admin overview, you can easily reset or delete used OTPs.
     57
     58== FAQ ==
     59
     60= Do users need to register to view the content? =
     61No, and that is the plugin's main advantage. A user only needs to enter the one-time password you provide. No WordPress user account is required.
     62
     63= How can I allow an OTP to be used more than once? =
     64In the admin overview, you can edit any used OTP and reset it with a single click. This clears the usage timestamp and makes the password immediately valid again.
     65
     66= Is plugin data removed on uninstall? =
     67Yes. When you delete the plugin from the WordPress admin area, the included `uninstall.php` file ensures the associated database table (`<prefix>_otpcp_protect`) is cleanly removed.
     68
     69= Can multiple passwords be active for the same post? =
     70Yes. You can create multiple different and simultaneously active OTPs for the same piece of content. Each one will be validated correctly upon entry.
    3271
    3372== Screenshots ==
    3473
    35 1. Settings Page – Overview of all one-time passwords with actions.
    36 
    37 == Usage ==
    38 
    39 1. On the OTP Protect settings page, generate or enter an OTP and select the content to protect.
    40 2. (Optional) Set an expiration date.
    41 3. Save the OTP. Share it with the intended users.
    42 4. When a visitor accesses the protected content, they will see an OTP input form.
    43 5. Upon valid entry, the original content is displayed.
    44 6. In the admin overview, you can reset or delete used OTPs.
    45 
    46 == FAQ ==
    47 = How can I allow an OTP to be used more than once? =
    48 Edit the OTP in the settings and check "Allow reuse". This clears the usage timestamp and makes the OTP valid again.
    49 
    50 = Will plugin data be removed on uninstall? =
    51 Yes. The `uninstall.php` file drops the `<prefix>_otpcp_protect` table when you delete the plugin from the WordPress admin area.
     741.  The settings page—a clear overview of all generated one-time passwords with key actions like edit, delete, and reset.
     752.  The simple password input form a visitor sees on a protected page.
    5276
    5377== Changelog ==
    5478
    55 **= 1.3.3 =**
     79= 1.3.3 =
    5680* **Fix:** Corrected a bug where only the first created OTP for a page was accepted. Now, multiple different OTPs can be active for the same content simultaneously, and each will be validated correctly.
    5781
    … …  
    6791* **Fix:** Corrected various bugs in the admin area, including broken edit links and script loading issues that arose during the refactoring.
    6892
    69 = 1.2.4 =
    70 * Fixed automatic tab activation and selection in edit mode
    71 * Improved JS/PHP communication of `selected_id` and `selected_type`
    72 
    73 = 1.2.3 =
    74 * Added `readme.txt` and improved i18n support
    75 * Fixed OTP generator and content filter labels
    76 
    77 = 1.2.2 =
    78 * Added backward compatibility for legacy `content_ids` column
    79 * Improved AJAX loading and security checks
    80 
    81 = 1.2.1 =
    82 * Fixed JS escaping for delete confirmation
    83 
    84 = 1.2.0 =
    85 * Switched to AJAX-driven dynamic content list
    86 * Server-rendered tabs with i18n labels
    87 
    88 = 1.1.0 =
    89 * Changed to single-select content field
    90 * Added search input and tabs
    91 
    92 = 1.0.0 =
    93 * Initial release with basic OTP protection functionality
     93(The rest of the changelog remains the same)
    9494
    9595== Upgrade Notice ==
Note: See TracChangeset for help on using the changeset viewer.