by nashvillegeek » June 25th, 2011, 8:31 am
Hi Jason,
We ran into several issues which forced us to move to a regular WP install due to a tight deadline. s2Member is working seemlessly, except for on devices that were testing using Safari before the switch to the new server. Other topics related to the cache in Safari seem relevant to that situation.
I'll see if I can get the logs. We do have logging enabled. I don't have access to their server. I will contact my liaison at the company and see if he'll provide the logs on Monday. As for screenshots, I don't know if that will be possible at this point. I'll see if they'd be willing to reproduce the situation on their staging server.
On the staging server's multisite setup, they had probably ten other sites and used the domain mapping pluggin. Everything worked fine until the domain mapping was applied to the site with s2member installed, as mentioned before. The s2member multisite option updates were applied when set up.
WP version: 3.1.3
Plugins: NextGEN Gallery, Memberslist, Event Espresso(several addons), Category Posts Widget, Custom Post Templates, Quick Page/Post Redirect, PS Auto sitemap, Simple Image Link, TinyMCE Advanced.
The other glitch, which I'll mention in case anybody else is running a similar setup and searches for it. The company's production server has their WP admin area inaccessible to public. I was unable to access the admin area remotely. The server has a different domain extension indicating an internal server. When we tried testing s2Member there, we just landed on a blank screen with the Paypal return code in the address bar. I believe this setup would never work since the Paypal info didn't seem to stand a chance to get back to s2member. Again, this was their production server. Our testing setup worked seemlessly until the domain mapping was applied.
Thank you for your response, Jason. I will try to get those logs to you next week.