MaxLimits - Increase Maximum Upload, Post & PHP Limits

This is common. It means your web hosting provider has locked these specific PHP settings at the server level, preventing the default ini_set() function from working. Solution:

1. Go to Settings > MaxLimits.
2. In the "Direct File Writing" card, check the box that says "Enable Direct .htaccess Writing (Experimental)".
3. Click the "Save Writing Method" button.
4. Now, set your desired limits in the "Limit Settings" card above.
5. Click the "Save Limits" button. This should now work in one click.
6. The plugin will write the rules to your .htaccess file.
7. You should see a "Settings saved" notice and a blue notice saying ".htaccess file updated successfully."
8. You must refresh the page to see the new values appear in the "Current Server Values" panel. This is normal for .htaccess changes.

The plugin provides inline, context-aware recommendations. Generally:

• Memory Limit: 256MB is okay for basic sites, but 512MB or 1024MB is often better for sites using WooCommerce, page builders (Elementor, Divi, etc.), or many plugins.
• Upload/Post Size: 64MB or 128MB is usually sufficient unless you need to upload very large video files. Ensure post_max_size is equal to or greater than upload_max_filesize.
• Execution/Input Time: 300 or 600 seconds is often needed for tasks like large imports, exports, or backups that take longer to run.
• Max Input Vars: 3000 is a good baseline, but page builders or complex menus often require 5000 or more.

We believe in complete transparency. We take your privacy very seriously. We do NOT collect any sensitive data. No personal information, no site content, no passwords, and no specific settings are ever collected. To provide you with better service and develop more relevant features, we may collect some anonymous, non-sensitive usage data if you opt-in. This data serves a single purpose: Optimization & Improvement. What is collected (only if you opt-in):

• Site URL & Name (to differentiate installs)
• WordPress & PHP Version (to ensure compatibility with your environment)
• Plugin Version (to track update adoption)
• Server Software (to debug server-specific issues like Apache vs Nginx)
• Admin Email (Optional: Used strictly for critical security alerts or support context if you contact us; not for marketing spam). This helps us prioritize which features to build next and which old PHP/WP versions we need to support. You can skip this at any time.

Yes. It uses the standard WordPress Settings API and follows security best practices. The default method only attempts to modify PHP settings temporarily at runtime using ini_set(). The optional "Direct .htaccess Writing" feature is off by default and only uses the official insert_with_markers() WordPress function, which is the safest way to modify the file.