About: Martin

Hi Jason,

After installing both s@Member Framework version 18, and later version 19, the site crashed, and I had to comment out whatever had been inserted into the .htaccess file to bring it back each time.

However, I now manually entered the exact code posted above, and the site is still alive.

I hope future updates do not cause the same issue.

They are running Apache 2.2.17 on a Dreamhost shared server.

Thanks and Best Regards, Marty

• This reply was modified 4 years, 10 months ago by  Martin.
• This reply was modified 4 years, 10 months ago by  Martin.
• This reply was modified 4 years, 10 months ago by  Martin.

Hi – we’re still awaiting a word from Dreamhost about the Apache version.

However, to me the salient point seems to be the text in the .htaccess file.

I had commented out the GZIP exclusion lines, and the site was working.

When we installed s2Member Framework v. 120219, it PUT THOSE LINES BACK IN – and this is what made the site crash.

# BEGIN s2Member GZIP exclusions

	RewriteEngine On
	RewriteBase \
	RewriteCond %{QUERY_STRING} (?:^|\?|&)s2member_file_download\=.+
	RewriteRule .* - [E=no-gzip:1]

# END s2Member GZIP exclusions

Was it the author’s intention to have the s2Member Framework v. 120219 installation cause that text to be ADDED TO THE .htaccess FILE – even though it has no significance with Apache 1.3, and is known to make it crash?

Or was it NOT intended? Could it be that the installation attempts to detect the Apache version, and this detection FAILED in the configuration used by Dreamhost?

Thanks for looking into these issues. It appears that Apache 1.3 cannot be ignored in future installations.

Hi Jason,

Can you detect the Apache version and avoid causing this problem in future updates? Thanks, Marty Hirsch (a client had this problem on a Dreamhost server this morning, which I corrected by commenting out the offending lines in .htaccess)