Support » Plugin: Strong Testimonials » HTACCESS corrupted on install of this plugin

  • Resolved pracko



    This plugin is causing the php handler in my htaccess file to be changed/corrupted upon activation.

    My php handler looked like this before activating Strong Testimonials:
    AddHandler application/x-httpd-php70 .php .php5 .php4 .php3

    After install, the handler was changed to this:
    ‘AddHandler application/x-httpd-php70s .php’

    That change causes the browser to open a file open/save dialog box that says “You have chosen to open: application/x-httpd-php (418 bytes) What should Firefox do with this file? Open with… Save File…” etc when I click the plugin’s ‘Activate’ button right after the plugin is installed.

    It also prevents me from accessing the site’s frontend and backend. All links for the site cause this file open/save box to appear.

    I tried this install twice with the same results. Each time, my htaccess file was modified as described above.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter pracko


    P.S. The site can be made functional by going back into my htaccess file after installing the plugin and changing the php handler back to the original version, but browser cookies do need to be cleared before the site is viewable again.

    Plugin Contributor Chris Dillon


    It sounds like a server misconfiguration or malware problem.

    Are you installing the zip file from your hard drive or direct from

    Does the same thing happen for any other plugin?

    Does it happen with ALL other plugins deactivated and Twenty Seventeen as the active theme?

    Is your web host tech support able to shed any light?

    I also think the problem can be in the .htaccess file. If it’s generated automatically by WordPress and you haven’t edited it, that may be the problem.
    Here is how it should looks like:

    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    # END WordPress
    	# WP Maximum Execution Time Exceeded
    	<IfModule mod_php5.c>
        php_value upload_max_filesize 1024M
    	php_value post_max_size 2048M
    	php_value max_input_time 3000
    	php_value max_execution_time 3000

    Hope that will help!

    Plugin Contributor Chris Dillon


    @pracko Any news on this?

    Thread Starter pracko


    Turns out that Siteground tech had to help me with this one. Seems that when I installed Strong Testimonials, the problem started. Tech had to crawl all WP files to find what was causing the handler to be changed. Here’s what they wrote:

    You are right – the Handler was altered once more:

    AddHandler application/x-httpd-php70s .php

    I have now manually commented out this handler and added the default one:

    AddHandler application/x-httpd-php70 .php .php5 .php4 .php3

    I then changed the permissions of your .htaccess file to 444 so any program that attempts to write in it will be denied.

    I also searched for this specific handler in your other files and I found it in one more place:


    This (Endurance PHP Edge) is a plugin that must have come from your previous host and I suspect that this was the cause for the .htaccess alterations all along.

    This is the line that was commented out:

    function htaccess_contents( $rules ) {
    $handler = get_option( 'epe_php_handler', 'application/x-httpd-php70s' );
    $handler = 'AddHandler ' . $handler . ' .php' . "\n";
    return $handler . $rules;

    Strange that the issue only cropped up immediately after Strong Testimonials though.

    He then said:

    I would strongly recommend removing the entire mu-plugins directory from your account (since it has no application here on SiteGround).

    I deleted the entire mu-plugins folder from /home/account/public_html/dev/wp-content/ and it resolved the problem.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘HTACCESS corrupted on install of this plugin’ is closed to new replies.