About: Eran

Hi Guys,
Firstly, thanks much for your quick and helpful input.
In the meantime, I found a solution (a kluge, actually): pasting the CF part of a config file saved from a fresh (yet not-configured) s2member installation into the saved config file of the site that had issues, then reloading that hacked config back into that installation.

The above kluge persuaded s2member that CF wasn’t configured, which allowed a fresh configuration (already tested to work well). Naturally, your suggestion is much cleaner. Saved it for future reference (hopefully unneeded).

I’m happy to help and will be in touch through a private communication regarding your request.

Thanks again…

Thanks Raam for the quick response.

To answer your question: yes – I did clear the CF fields in s2member. Also tried inputting the new key. Regardless of whether the fields are empty or full the configuration fails. Played with it for quite a while with and nothing really worked.

I’ve been thinking of doing something similar to what you suggested: Having confirmed that s2member is stable on my development site, I’ve been contemplating using the live site to configure CF, then turning s2member off on the live site till I’m ready to deploy.

While that’s an option, I’d rather keep away from the live site till I’m ready to deploy. This leaves your suggestion as a viable option and if left with no other choice perhaps I’ll do that. What do you think about editing the config file should that work? If so, that would be simpler than installing another instance of WP…

Many thanks

Thanks much…