secure content pro plugin for wordpress

Protect your premium content with the Content Secure Plugin for WordPress. Easily lock posts, add password protection, control member access, and secure digital products. Boost your website privacy and monetize exclusive content with powerful protection features.

1. Activate Plugin:
   • Go to Plugins and activate "Content Secure Pro".
   • Check wp-content/debug.log for errors.
2. Test Payment Proof Submission:
   • Edit a post, enable lock, set price (e.g., "2.00"), and save.
   • Visit the post as a visitor (incognito mode).
   • Click "Pay via PayPal" (links to paypal.me/masukmia/2USD).
   • Upload a test image/PDF as payment proof, optionally add a transaction ID, and click "Submit Proof".
   • Verify:
     • No "Security check failed" error.
     • A green "Payment proof submitted! Awaiting admin approval." message appears.
   • Check the console (F12 > Console) for logs:
     • Content Secure: Submitting payment proof
     • Content Secure: Payment proof AJAX response
   • Check wp-content/debug.log for:
     • Content Secure: Payment proof submitted for post ID
     • No "Payment nonce verification failed" entries.
3. Test Other Features:
   • PIN Unlock: Set a PIN (e.g., "5678"), enter it, and verify content unlocks.
   • Free User: Mark a post as free and verify it’s accessible without PIN/payment.
   • Payment Approval: Go to Content Secure Pro > Payment Proofs, approve a proof, and verify the post unlocks.
   • Copy/Right-Click: Try copying or right-clicking protected content and verify the "This content is protected" alert.
4. Clear Cache:
   • Clear WordPress caching plugins (e.g., WP Super Cache) and browser cache.
   • Disable caching during testing to avoid interference.
5. Verify Database:
   • Use phpMyAdmin to check the wp_content_secure_payments table for new entries after submitting proof.

If Issues Persist

If the "Security check failed" error appears elsewhere (e.g., PIN unlock, payment approval) or other issues arise:

• Share Logs:
  • Provide wp-content/debug.log contents, especially entries related to "Content Secure".
  • Share console logs (F12 > Console) for AJAX errors or responses.
• Specify Issue:
  • Describe the exact error message and when it occurs (e.g., after clicking "Submit Proof", "Unlock", or "Approve").
  • Note any other unexpected behavior.
• Environment:
  • WordPress version (e.g., 6.6), PHP version (e.g., 7.4), server type (e.g., Apache), active plugins, caching setup.
• Test Minimal Setup:
  • Deactivate other plugins, switch to a default theme (e.g., Twenty Twenty-Five), and retest.

Alternative: Debug Nonce Issue

If you’d prefer to keep the nonce check and fix the underlying issue, please provide:

• Debug logs showing "nonce received" or "nonce verification failed".
• Console logs showing the contentSecure object or AJAX errors.
• Confirmation of caching plugins or server-side caching (e.g., Cloudflare). I can then adjust the nonce refresh logic or address specific server issues.