[Plugin: Htaccess Secure Files] Fatal error in WP 3.3

@immeanyhow, can you post the exact text of the error message (error message, line number, etc.)? I just created new WP 3.3 and WP 3.3.1 sites to test installing the plugin and they both worked fine. I suspect you may not be using Apache as your web server and/or Apache’s mod_rewrite module is not enabled.

During the plugin activation it intentionally raises errors if you do not have Apache (The Htaccess Secure Files plugin requires Apache), if the plugin could not check which Apache modules are installed (The Htaccess Secure Files plugin could not determine which Apache modules are active), or if mod_rewrite is not among the active Apache modules (The Htaccess Secure Files plugin requires the mod_rewrite Apache module to be installed and active).

I’m getting this error message too. WP 3.3.2

Plugin could not be activated because it triggered a fatal error.

@steve, can you add the actual fatal error message text to this thread?

This plugin was designed specifically to work with Apache with the mod_rewrite module active and configured, so if your system does not include those requirements the plugin forces a fatal error on activation.

Thanks @isaacchapman.
That’s the exact error message displayed in admin area after trying to activate.
Server does have mod_rewrite and the sites I’ve tried it on have permalinks running fine so not sure what’s causing the issue?

I was hoping there was a line number along with the error to help me narrow down what could be causing the problem. I was planning on incorporating some features from wp-includes/ms-files.php into this plugin and testing it on Apache for Windows as well, so perhaps I will run across the bug you are experiencing and squash it (possibly accidentally).

I just ran several install scenarios on various platforms and could not trigger an error that only stated “Plugin could not be activated because it triggered a fatal error.”

Please provide the entire error message as I haven’t been able to find an error besides the ones I intentionally trigger when the plugin is activated on an incompatible server.