This topic contains 1 reply, has 2 voices. Last updated by Cristián Lávaque 3 years, 9 months ago.
Topic Author | Topic |
---|---|
Posted: Friday Apr 5th, 2013 at 3:27 pm #46724 | |
Hi there. I’m encountering an issue on our dev site (http://test3.gaylesta.org) that’s not happening on our live site (http://gaylesta.org). The public members’ pages–which should be public– are showing up as restricted on the dev site. This is a big problem, as one of the perks of our paid members is to be part of our public, searchable directory. So, for example, the public can see http://gaylesta.org/holttom/ (correct) but not http://test3.gaylesta.org/holttom/ (suddenly restricted/redirected). I’m wondering if it’s related to having changed the domain to a subdomain? I couldn’t find anything written up on here about this, but saw something recent similar/related, that didn’t get a response: http://www.s2member.com/forums/topic/home-page-restricted/#post-43432 The database was cloned, and the sites are running the same plugins and configurations, but: the live site *is* old and outdated, and the dev site has the most recent updates to WordPress, BuddyPress, S2Member Framework and S2Member Pro. Thanks for any tips, workarounds, or pointers to what might be causing this. |