Doesn’t allow alternate wp-content location

BE WARNED:

s2member requires your content directory to be set up like the out-of-the-box WordPress install. They ignore plugin standards which allow both moving and renaming your content directory.

It’s possible that this is because s2member needs to ensure that the content directory is below the WP install directory as part of its restriction, although I’m pretty sure that other content restriction plugins manage to figure this out.

But if that’s the case, how come it NEVER MENTIONS THIS IN ANY DOCUMENTATION? Really frustrating. If you’re going to deviate from the standard way of doing things, you should LET PEOPLE KNOW, somewhere in the process. Ugh.